About SchneJoe

Bug is fixed from CXA_MotionInterface and CXA_MotionInterfaceUser version 2.6.1.8 and for the next release from 3.3.0.0 on.   ... View more

@NormalOne, this did not seem to fix the problem though I have found other use for that code. I ended up rewriting the ML_SwitchOnPath for my purposes for now and opened a ticket internally on the issue. Thanks.  ... View more

This issue seems to be resolved with the new PLC / Motion / Works versions. I was not able to recreate the F2037 fault anymore. Please consider this  resolved. ... View more

@aFouraker, when you focus on PLC code, you can save the files on the OEM partition (OEM\ProjectData\PLC). If you restore these files and reboot the control, the original PLC code should run again. If you use persistent data in the PLC, it is getting a little more complicated. Please check the documentation about C-0-1001 and C-0-1002. With these commands you can save and restore persistent data (PLC variables and C-/A-Parameter) to a file (\OEM\ProjectData\MLC_NVRAM.bak). But some of the parameters are not included in this file. They are stored in parameterfiles in \OEM\ProjectData\PAR. Following scenario could be possible: - check if bootproject has changed (/OEM/ProjectData/PLC/Application.app) - stop plc - switch to P2 - restore plc-, parameter- and NVRAM files - excute C-0-1001 - reboot control I didn't try this yet. So please check it carefully before implementing this at a customer machine. ... View more

Hi Luca, if you would like to use S-0-0520, you need to change the main operation mode to "Position control with axis control word". This can be done in ctrlX IO Engineering.  And in the AxisProfile you need to configure S-0-0386 instead of S-0-0051 to use as actual position. Now you should be able to use the Motion App and PLCopen to command the axis. Of course you need to set reference for each encoder before. Regards, Jörg ... View more