The ctrlX MOTION has interpolation algorithms that calculate a target position for a drive each fieldbus cycle. When using a motion command it will start interpolating and sending target positions.
From PLC side you have the possibility to directly write to the drive command word and read the drive status word. That is what the ctrlX MOTION is doing in the background. Same is for Target position and current position.
See "Object “DataLayer_Realtime”" for further information
So possibility is to add all cyclic drive parameter to the realtime area of the PLC and then use them for commanding and checking response. Beware that then the application using the parameter needs also to, interpret control and status word depending on fieldbus communication type, calculate target positions, handle error reaction, set bits to switch power, choose active operation mode on and so on and so forth. This normally done by the ctrlX MOTION in the background.
See "ctrlX DRIVE, Objects/Parameters of Runtime AXS-V-0504, Reference Book" for information about how to interpret parameter
If special drive features needs to be used acyclic communication is used to directly execute drive functions like switch off error when torque limit is reached and so on. This is depending on the fieldbus type. Also this normally done by the ctrlX MOTION in the background.
See "ctrlX PLC Engineering, PLC Libraries 02VRS, Reference Book" for further information.
To sum it up, it can be quite a lot work to do and things to know in an application handling fieldbus drives like the ctrlX MOTION does.
