Made a short test with a virtual core and 18 configured axis. Here all works ok. No exception, the status is correct. (see screenshot 1)
Known Bug: In the motion interface lib version you have you will get an exception if you do not start with the axis array at element 1 (eg. at element 2). So the question did you change the min axis indey (see screenshot 2).
By the way, you wrote that you use the PLC engineering version 2.6.3. The last official version is the 2.6.1. coming with the patch 1 at the collaboration room. (see Screenshot 3). Can you explain this.
Haven't test it with real control/axis. Maybe you can do some further test:
a) only use motion axis without axisprofile assigned and see what happend.
b) check it with a virtual core, to see if the problem still occure.
Question: Do you license the 18 axis at the X7?
Regards
Jochen
... View more