tk096

Hi, a few questions that you can check regarding your kinematics: * Does your kinematics FB implement the interface ISMKinematicWithInfo2? * Does AxesToCartesian(a, out f) -> CartesianToAxes(f, out aCompare) result in a=aCompare for random positions a? * Do you return a valid rotation matrix f.mR (SMC_Matrix3) in AxesToCartesian()?

Hi, you have to define how many increments of the drive correspond to one unit in your application. This is done in the Scaling/Mapping Tab in the drive editor.

Hi, you can call the decoder function block in a loop and/or decrease the task cycle interval of Task_PATH.

Hi, you can call the decoder function block in a loop and/or increase the task cycle interval of Task_PATH.

Hi, you could calculate the position/dynamics of the slave axis yourself and use one of the function blocks SMC_FollowPosition/SMC_FollowSetValues to move the slave axis. https://content.helpme-codesys.com/en/libs/SM3_Basic/Current/SM3_Basic/POUs/Movement/Direct/SMC_FollowPosition.html https://content.helpme-codesys.com/en/libs/SM3_Basic/Current/SM3_Basic/POUs/Movement/Direct/SMC_FollowSetValues.html

Meanwhile, I would like to understand why the motion FB instances must still be called even after the Execute is set to FALSE, especially in view of the fact that the next instruction is programmed to abort the previous one, with BufferMode set to 'Aborting'. All these unnecessary FB calls are an unnecessary overhead on the CPU anyway. Is there any precise rule about when to cease calling the various instances? (It should precisely be the 'done' status that says this one has finished its work). In...

Meanwhile, I would like to understand why the motion FB instances must still be called even after the Execute is set to FALSE, especially in view of the fact that the next instruction is programmed to abort the previous one, with BufferMode set to 'Aborting'. All these unnecessary FB calls are an unnecessary overhead on the CPU anyway. Is there any precise rule about when to cease calling the various instances? (It should precisely be the 'done' status that says this one has finished its work). In...

Hi, dwIpoTime should be set to the cycle time of your motion task. It defines the interpolation interval of the interpolator. E.g. in the attached screenshot, the task has a task interval of 4ms. The dwIpoTime input of the interpolator should be set to 4000.