About Olorin

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         ... View more

Hey Jochen,  On the Ctrlx PLC version, it says 2.6.3 on CtrlX Works but on the about information it does say 2.6.1.  The same project on the emulate core works fine, I'll test with a real X7 with only vitural axis when I get a chance, but have suspect that works fine too.  The only thing I did was expand the array to fit my needed axis, which is 39, we have license for 40. That caused my project to crash so we went to a blank project and found that the issues started to occur at 18 axis and above configured. The min axis was left untouched, and this was all from a project working in 2.4.  The lower bound of the array was left at 1 Thanks  ... View more

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       ... View more

Thanks EngJay, I was aware of these solutions, but this is an XCS power supply that we are not using the drive on, just it's power supply. MC reset as far as I am aware needs an Axis config with a drive profile to work, and only the standalone power supply block has a clear error input in the drive utils. I imagine that i could perhaps use the standalone block though, as the control word I would imagine is the same for either. If that doesn't work I'll probably just do an SOE command for the reset since it's not RT so it doesn't need to be in process data. Thanks for the advice ... View more