Maybe this can help: https://www.youtube.com/watch?v=NgsJr0hds4k
So we pay 380€ for SoftMotion licenses for each robot, but have to implement such an obvious use case manually without any hint in the official documentation how to achieve this. This is crazy...
To better track project changes in git I created a script that exports the project structure as text files. Textual POUs are stored as text, everything else as XML (with timestamps removed). The file structure is stored under path/to/your.project.txt Git merge will not work, but at least tracking changes is much easier. Script: https://github.com/arwie/controlOS_demo/blob/main/codesys/txtfy.py Example output: https://github.com/arwie/controlOS_demo/tree/main/codesys/controlOS_demo.project.txt
To better track project changes in git I created a script that exports the project structure as text files. Textual POUs are stored as text, everything else as XML (with timestamps removed). The file structure is stored under path/to/your.project.txt Git merge will not work, but at least tracking changes is much easier. https://github.com/arwie/controlOS_demo/blob/main/codesys/txtfy.py
Hi, I am also looking for a way to solve the same issue.
This is a homing routine which is controlled by setting mode of operation and started by setting a bit in the control word. If MC_Home is not usable for this homing method then I need to implement the same functionality. But how?
Is it possible to use MC_Home without enabling the drive (MC_Power)? On the drive the homing method 35 (Homing on current position) has to be executed. The drive has to stay disabled due to safety. This is explicitly allowed by the drive. Unfortunately MC_Home reports the error SMC_REGULATOR_OR_START_NOT_SET when executed. Are there other options to start homing, if not with MC_Home?
Agree! Me and my customers are buying SL Licences from the store but we don't get proper documentation of the runtime! Only a few hints of the entries in CodesysControl.cfg are spread all over the Internet.