Hello stephenOtis, I also use a ID Cs under my core. Also after update to RM22.03 the setup is running. I did the following steps: - setup a Ethercat configuration and motion axis in RM21.11 - Update base image of core to RM22.03 -> motion app and ethercat is still running - Update Ethercat app -> motion app and ethercat is still running - Update Motion app -> motion app and ethercat is still running I would recommend to check if all system apps are updated - if so i would try to reset the configuration (app data) after update and reconfigure your IO configuration and motion setup.
... View more
Hello Yacine, yes the EAL library works as well with ctrlX DRIVE if you use the latest version (> EAL 2.3.0) So you can control (positon, velocity or torque) your drive by a PC application like in the past. Best regards, Christoph
... View more
The required changes will be available in ctrlX MOTION App 1.14. There will be a possibility to choose if you want to read the scaling from drive (which is not working in your case) or to define the the scaling on control side These settings can be configured in Motion app
... View more
Hello, I do not know your drive type but it looks like there is a support for Ethercat Ds402 communication. So far your configuration looks good - but your drive type was not tested in combination with our Motion as far as I know. What version of Motion App do you use? In general: In our Motion you do not need to map the Diagcode - this is optional. In your case it looks like the Motion App trys to read objects while switching to running mode which it cant find on drive side. In next release there will be the possibility to define if we want to read the setting from drive or simply define it on Motion side. I guess this will solve your issue. Best regards
... View more
