Axis interface breaks application when moving from earlier version

[aFouraker]

I was moving my ctrlX from an older version of the firmware and apps (1.20.0) to the latest (1.20.6). I updated the PLC in my PLC project and was able to build and download. However, after this change my application gives the following errors immediately on startup. Any ideas how to resolve this? I would expect these to be compatibility. 

[bostroemc]

I verified that MotionInterface appeared to be working properly with ctrlX CORE virtual (base image 1.20.9) and the device and library versions shown below:

Complete snap listing:

Can you check your MotionInterface library version?  I did go through the docs and could not an error corresponding the combination (16#090F2002, 16#0C560000).

[CodeShepherd · Accepted solution]

See our online documentation for further details about the error: 090F2002 General axis command error, 0C560000 Axis for axis command was not found

In general compatibility should be granted but you should always check release notes of the ctrlX AUTOMATION - MOTION including the changes in CXA_MotionInterface.

@aFouraker did you update the apps on the ctrlX CORE and the ctrlX PLC Engineering?

[bostroemc]

@CodeShepherd: Thanks for the tip.  The ctrlX CORE runtime documentation that you cite seems to give a much neater listing of the diagnostic codes than any of the documents linked to directly from ctrlX PLC Engineering:

[aFouraker]

The documentation helped track down the error. I think the process for startup of the motion interface changed slightly so that it took a little longer and in some cases was cuasing errors on the application when attempting to access the ctrl/status structure because it had not been initialized fully. Adding a check that the axis and kinematic interfaces were initialized fixed this problem.