Programming the PTOMoveVelocity Function Block
|
Step |
Action |
|---|---|
|
1 |
With the Input Assistant, add the PTOMoveVelocity function block from the following path: Function Block (Libraries) > HMISCU_PTOPWM > PTOMoveVelocity and click OK |
|
2 |
Declare the function block instance. |
|
3 |
Associate the PTO_REF_IN input of the function block to the PTO_REF output of the PTOSimple function block. |
|
4 |
The inputs/outputs are detailed in the function block description PTOMoveVelocity . The interactions between the inputs/outputs are detailed in the General Information. The interactions between the motion commands are detailed in the Command Sequence. |
Any aborted motion commands cannot be completed after having been stopped. A new motion command must be issued.
The PTOMoveVelocity movement is aborted when:
oa PTOStop function block is called
othe Drive Ready Input (if defined at configuration time) becomes inactive
othe sequence of commands is not supported
othe application is stopped
oan error is detected
oa new PTOMoveVelocity motion command is issued while the current PTOMoveVelocity command is currently in Acceleration or Deceleration phase (while Busy =TRUE)
