Speed control is started each time the configured event occurs.
Example without using "VelocityParID" ("Execute" only set for one cycle):
New movement parameters are specified on each 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 first three and the fifth event on the drive each start speed control with the specified speed.
The event marked in green has no effect since the target speed was not changed previously. The event marked in red is rejected because the function block was aborted by calling an MC_Stop function block.
Example without using "VelocityParID" ("Execute" stays 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 "VelocityParID" ("Execute" only set for one cycle):
New movement parameters are specified on each 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. If the value of the "VelocityParID" is already the same as the current speed, then the "InVelocity" output is set.
The first three and the fifth event on the drive each start speed control with the specified speed.
The event marked in green has no effect since the target speed was not changed previously. The event marked in red is rejected because the function block was aborted by calling an MC_Stop function block.
Example using "VelocityParID" ("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.