Like mentioned above, commanding of axes is always possible, independently of the cycle time of the fieldbus, e.g. via the PLC in different tasks and cycle times. So it doesn't matter if ctrlX MOTION or Codesys Softmotion is used. The update rate of the EtherCat and so the cyclic position command value would still be sent each 2ms.
As an example:
- You have two tasks one running in 10ms and one in 4ms. You use the first one to check position and command some axes and the same in the second for other axes. Then the commands are added to the ctrlX Motion in 10ms/4ms but the interpolator will run in 2ms to be able to send each bus cycle a new position to the drive.
- Same for Codesys softmotion but if its interpolator is running in the first task, the drive will get five times the same position command as the fieldbus is still running in 2ms. Further more the softstack could/will utilize more CPU load the ctrlX MOTION does.