I noticed that version 0.0.0.6 is now available, so I tested it using CODESYS V3.5 SP19 Patch 7 and SoftMotion 4.17.0.0. While the project compiles and downloads without issues, I encountered a problem with the 'Enable: GPIO pin number that is set when the axis is enabled (with MC_Power) (0: not used)' functionality — it no longer works (HIGH level not present at the output pin). I observed the same behavior with version 0.0.0.5, whereas version 0.0.0.4 functions correctly. Could you help me identify what might be causing this issue or suggest how to resolve it?
Thanks.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Ok, so i made some tests in the meantime and i have some conclusions.
It apears that the enable bit is activated only when a motion function is executed.
I implemented a very simple program with MC_Power and MC_Jog. If i enable everything on MC_Power, the enable GPIO pin stays off. However, as soon as the MC_Jog function is used the enable GPIO pin turns ON and remains ON.
In version 0.0.0.4 this is not happening. The GPIO enable pin turns on or off when the MC_Power is enabled or disabled.
From this behaviour i understand that in version 0.0.0.6 the GPIO enable bit is activated together with pulse and dir pins when motion starts. When motion stops, enable bit remains with the last state (on in this case) and you cannot turn it off for example.
For me this bit is useful because i can turn on and off the stepper drive with MC_Power function. Now i can turn it on, but never off.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
I noticed that version 0.0.0.6 is now available, so I tested it using CODESYS V3.5 SP19 Patch 7 and SoftMotion 4.17.0.0. While the project compiles and downloads without issues, I encountered a problem with the 'Enable: GPIO pin number that is set when the axis is enabled (with MC_Power) (0: not used)' functionality — it no longer works (HIGH level not present at the output pin). I observed the same behavior with version 0.0.0.5, whereas version 0.0.0.4 functions correctly. Could you help me identify what might be causing this issue or suggest how to resolve it?
Thanks.
I would expect that this is more or less Bookworm related - the GPIO access is different now - and need to be adapted
Thanks for the replay. My RPI is a 3B+ model with bullseye OS. I don't understand why 0.0.0.4 is working ok and future versions not.
yes this is another issue then.
Last edit: eschwellinger 2025-03-22
Ok, so i made some tests in the meantime and i have some conclusions.
It apears that the enable bit is activated only when a motion function is executed.
I implemented a very simple program with MC_Power and MC_Jog. If i enable everything on MC_Power, the enable GPIO pin stays off. However, as soon as the MC_Jog function is used the enable GPIO pin turns ON and remains ON.
In version 0.0.0.4 this is not happening. The GPIO enable pin turns on or off when the MC_Power is enabled or disabled.
From this behaviour i understand that in version 0.0.0.6 the GPIO enable bit is activated together with pulse and dir pins when motion starts. When motion stops, enable bit remains with the last state (on in this case) and you cannot turn it off for example.
For me this bit is useful because i can turn on and off the stepper drive with MC_Power function. Now i can turn it on, but never off.