The movement is started each time the configured event occurs.
Example without using "DistanceParID" ("Execute" only set for one cycle):
A movement distance, movement parameters, etc. are specified on the first rising edge of the "Execute" input. The "WaitingForEvent" output is set to TRUE as soon as everything is configured and the drive accepts an event.
The next two rising edges of the "Execute" input change the distance and the movement parameters.
The first two events on the drive each start a movement with the specified distance. Each of the two events marked in green causes the current movement to be extended by "Distance". The event marked in red is ignored because the function block was aborted by calling an MC_Stop function block.
Example without using "DistanceParID" ("Execute" remains set):
The only difference from the previous example is that the "Execute" input remains set for longer than one task cycle here. This affects the "InPosition" and "CommandAborted" outputs.
Example using "DistanceParID" ("Execute" only set for one cycle):
The behavior is identical to that in the example for mode mcCYCLIC. The difference is that any event that occurs – even when a movement is already active – allows a new value to be specified via "DistanceParID" (see event marked in green).