Hello,
I'm trying to connect an ctrlX Drive with ctrlX Core through Ethercat but I have a problem with the Feedback Torque parameter.
When I add this parameter in the ctrlX IO and mapping in Motion (in the webserver), all the parameters that I mapping in Motion are freezing (position and velocity). If I quit the feedback torque, it works perfectly.
That is the configuration of ctrlX IO:
I'm working with 2.6 version and the drive has V-0602.
Any ideas?
Hello everybody
Summarizing this issue (tested with version 3.4)
SoE communication
works without any problem
CoE comminication
bug inside the motion app if the torque is mapped at the axis profile
activation of one drive -> freeze of actual data
activation of more than one drive -> error message by PowerOn
development department is informed. They are working on the problem
Possible workarounds
use SoE instead CoE for the ctrlX Drives
stay at CoE
delete the torque mapping -> motion app is working
read the torque feedback via PLC directly.
Read via FB
set up cyclic RT-data
Regards
Jochen