An other approach is to split the application into a hard real-time part running in CODESYS and the business logic running in Python asyncio. The business logic part is usually bigger and changes more often. As Python code is pure text, vscode and git are your friends. A performance example on YouTube (CODESYS SoftMotion + Python): https://www.youtube.com/watch?v=BT-L0H_4Aic Docs and code on GitHub: https://github.com/arwie/controlOS_demo/blob/main/docs/codesys_python_link.md Real-time variable exchange...
...
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?