Hello,
We are commisioning an application with 2 CtrlX drives, one with core (with Ethercat, motion and PLC app). The axes will work in jog mode, synchronized (as long as a button is pressed, the axes will move synchronized in one direction). We managed to configure the Ethercat and Motion App, and to power the drives with PLC app using MC_Power_on fb. The problem is that we receive immediately the error F4037. I have attached the par from both drives and the system report also. The behavior is strange, as sometimes we manage to power the drives and to synchronize them with MB_AddToGantry fb, but when we try to move (with MC_Jog or MC_MoveAbsolute) the error pops up immediately. Same thing with the drives independently controlled. What can be the problem? Motion configuration, operating modes or incorrect/incomplete telegram parameters?
Thank you!