Welcome to our new forum
All users of the legacy CODESYS Forums, please create a new account at account.codesys.com. But make sure to use the same E-Mail address as in the old Forum. Then your posts will be matched.
Close
It seems that is not possible to call a motion function block from outside the task where the ethercat runs.
Normaly, the task where the machine state works is slower than the low level motion process runs (motion task 1 or 2 ms, state machine ~10 ms).
Solution: Put motion fbs in the quick task and enable its from outside, and normaly via level booleans.
I think that we are loosing the fantastic utility of call from the state machine the edge controlled (As common behaviour library from Codesys) motion fb (mc_moveabsolute).
Sent from my Moto G (5S) Plus using Tapatalk
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi.
It seems that is not possible to call a motion function block from outside the task where the ethercat runs.
Normaly, the task where the machine state works is slower than the low level motion process runs (motion task 1 or 2 ms, state machine ~10 ms).
Solution: Put motion fbs in the quick task and enable its from outside, and normaly via level booleans.
I think that we are loosing the fantastic utility of call from the state machine the edge controlled (As common behaviour library from Codesys) motion fb (mc_moveabsolute).
Sent from my Moto G (5S) Plus using Tapatalk