Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
I am facing a problem in v3.5, there is a motor driver connect via EtherCAT slave, and one remote plc via Modbus TCP Slave.
the EtherCAT is for driving the motor, and Modbus TCP is only I/O exchanging with CoDeSys v3.5.
problem is:
The motor was not running smoothly enough(rotating fastly or reversely suddenly), it seems motor was lost some pulses/step sometimes, if I delete the Modbus TCP slave, motor was runing perfectly, EtherCAT seems was affected by Modbus TCP, when I changed Modbus TCP polling cycle time, motor running better.
can any one gives any tips? I really need some help from you guys now.
thanks a lot.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Try moving your ECAT processing block onto high priority interrupt? For example in ABB AC500, "Ext CouplerX Hi Priority" would process ECAT blocks at every frame.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
hello, all
I am facing a problem in v3.5, there is a motor driver connect via EtherCAT slave, and one remote plc via Modbus TCP Slave.
the EtherCAT is for driving the motor, and Modbus TCP is only I/O exchanging with CoDeSys v3.5.
problem is:
The motor was not running smoothly enough(rotating fastly or reversely suddenly), it seems motor was lost some pulses/step sometimes, if I delete the Modbus TCP slave, motor was runing perfectly, EtherCAT seems was affected by Modbus TCP, when I changed Modbus TCP polling cycle time, motor running better.
can any one gives any tips? I really need some help from you guys now.
thanks a lot.
Try moving your ECAT processing block onto high priority interrupt? For example in ABB AC500, "Ext CouplerX Hi Priority" would process ECAT blocks at every frame.