Could you add some screenshots where you see such dab references?
Which version of ctrlX PLC Engineering and the CXA_MotionInterface is used?
Did You check the settings in CXA_MotionInterfaceUser to extend the possible size of the data structures?
Here is the screen shot. In a project that is just imported the template and configured real Axis. We did update the number of axis in the library, that's when we see the problem. This is on a Core X7.
The axis interface was updated to have a larger number of axis, it works when there are 10, it seemed to work until we went larger than 17.
PLC Engineering 2.6.3
CXA_Motion 2.6.6.0
CXA_Motion_Interface 2.6.1.2
CXA_Motion_IF_USER 2.6.1.1
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
Hello Olorin
I make following test
- ctrlX Virtual with 20 axis -> OK
- ctrlX X3 with 20 motion axis (without real drive connected) -> OK
- ctrlX X7 with 20 motion / real axis (Indradrive) -> OK (see screenshots)
So I can't reproduce your problem.
Please take a look into the log of your device to check some details of the exceptionj
Regards
Jochen
Hey Jochen,
We were able to reproduce the issue on multiple controllers, with and without axis profiles configured, using different computers to download, using standard axis configuration (Just adding the axis and leaving as is). It seems in order to see the issue you must have 30+ axis configured in the control, and have the library configured for 18 or more. If only 20 axis are configured on the control, the issue does not occur. The axis interface memory becomes corrupted once the axis interface main program has finished initialization. So it starts ok, then after some runtime it get's corrupted.
If the controller is started after motion boots, it will have no execeptions in the control unless you try and access one of the variables in the motion interface control
If you boot the motion while the PLC is already running, then when the library initializes itself it will throw an exception of an access violation and stops the control. Here is the callstack
You can see the exception here, a little down stack we got the PLC back running.
We were unable to re-produce on a virtual core. We were able to reproduce on two seperate X7 controllers and an X5 controller
