Y_MotionAxisDriver
The
Y_MotionAxisDriver
FB enables communication between the PLCopenPart1 function block (MC_Power,
MC_MoveVelocity...) and the motion axis.
Parameters
| * | Parameter | Data Type | Description | Default |
|---|---|---|---|---|
|
VAR_IN_OUT
|
||||
| V | Axis | AXIS_REF | Logical axis reference | |
| VAR_INPUT | ||||
| V | Enable | BOOL | The function block will continue to execute every scan while Enable is TRUE and there are no errors. | FALSE |
| VAR_OUTPUT | ||||
| V | Valid | BOOL | The Valid output indicates that the function block is operating normally and the outputs of the function block are valid. | |
| V | Busy | BOOL | For function blocks with Execute input, the Busy output is set to TRUE upon the rising edge of the Execute, and set to FALSE when Done, CommandAborted or Error outputs becomes TRUE. In the case of a function block with an Enable input, Busy indicates that the function block is operating, but may not be ready to provide valid outputs. | |
| V | Error | BOOL | The Error output is set to TRUE if an error has occurred during the operation of the function block. The output is cleared when the Execute or Enable input becomes FALSE. | |
| V | ErrorID | UINT | The ErrorID output provides the identifier of the error when there is an active error in the function block execution. The output is cleared when the Execute or Enable input becomes FALSE. | |
Notes
- Every axis requires a unique instance of the Driver function block to run and be in a valid state for the application to have control over the axis.
-
For VFDs with
Modbus RTU connection:
- To manage the Modbus RTU communication using a CP module an additional Driver FB is necessary see : Y_IM_MainRTUDriver
- Further details of the communication management to Yaskawa Drives and Generic Devices are described here: Modbus RTU Communication Details for Drives and generic Modbus Devices
Error Description
See the
Function Block ErrorID List