PDOs for AKD, AKD2G, AKD-N, and S300/S700
The KAS Motion Engine interacts with the AKD, AKD-N, and S300 "Servostar 300 drive" See Servo Drive in Glossary/S700 "Servostar 700 drive" See Servo Drive in Glossary drives through CANopen objects in the selected PDOs.
- Some of the ML and MC function blocks require specific CANopen objects in the PDOs.
- The default AKD and AKD-N PDO PDO is a type of protocol frame used in some fieldbuses. A PDO contains one or more object dictionary entries, which define the application data transferred between devices. selection includes all of the CANopen objects needed by the motion engine and function blocks.
- The default S300/S700 PDOs include only the minimal CANopen objects required by the KAS motion engine.
These tables identify the CANopen objects required by the motion engine and function blocks, and whether they are available in the default PDO for AKD, AKD-N, or S300/S700, and their corresponding AKD drive parameter.
The types of PDOs are:
- RxPDO — From Controller to Drive (RxPDO)
- TxPDO — From Drive to Controller (TxPDO)
-
-
Review these tables to verify the objects needed by the features the application uses are included in the AKD, AKD-N, and S300/S700 PDO selection.
From Controller to Drive (RxPDO)
These Controller to Drive objects are available in the default PDO.
RxPDO - AKD Drive CANopen Objects
Index - subindex | Object Name | Required | Associated ML FB | Associated MC FB | Associated AKD Parameter |
---|---|---|---|---|---|
0x20A4 - 0 or 0x2802 - 0 |
Latch control word |
No |
|
|
|
0x3470 - 3 |
AOUT.VALUE Used by Onboard I/O mappings |
No |
N/A |
N/A |
|
0x6040 - 0 |
|
Yes |
|
||
0x60B2 - 0 or 0x60F6 - 1 |
Additive torque value (Torque Feed Forward) |
No |
|
N/A 1 |
|
0x60C1 - 1 or 0x6062 - 0 |
Position demand value |
Yes |
|
|
|
0x60FE - 1 |
Digital outputs Used by Onboard I/O mappings |
No |
N/A |
N/A |
|
RxPDO - AKD2G Drive CANopen Objects
Index - subindex | Object Name | Required | Associated ML FB | Associated MC FB | Associated AKD Parameter |
---|---|---|---|---|---|
0x3601:1 |
Physical Outputs Used by Onboard I/O mappings |
No |
N/A |
N/A |
|
0x3800:2 |
Used by Onboard I/O mappings |
No |
N/A |
N/A |
|
0x3801:2 |
AOUT2.Fieldbus Value Used by Onboard I/O mappings |
No |
N/A |
N/A |
|
0x6040:0 / 0x6840:0 |
|
Yes |
Needed for motion engine axis to work properly. |
|
|
0x6070A:0 / 0x6870:0 |
Target Position Axis 1 / 2 |
Yes |
|
|
|
0x60B8:0 / 0x68B8:0 |
Touchprobe function Axis 1 / 2 |
No |
|
-
- Axis 1 objects begin with 0x60.
Axis 2 objects begin with 0x68.
RxPDO - AKD-N Drive CANopen Objects
Index - subindex | Object Name | Required | Associated ML FB | Associated MC FB | Associated AKD Parameter |
---|---|---|---|---|---|
0x20A4 - 0 or 0x2802 - 0 |
Latch control word | No |
|
|
|
0x6040 - 0 |
|
Yes | |||
0x60B2 - 0 or 0x60F6 - 1 |
Additive torque value (Torque Feed Forward) |
No |
|
N/A 2 |
|
0x60C1 - 1 or 0x6062 - 0 |
Position demand value |
Yes |
|
|
|
0x60FE - 1 |
Digital outputs Used by Onboard I/O mappings |
No |
N/A |
N/A |
|
RxPDO - S300 and S700 Drive CANopen Objects
Index - subindex | Object Name | Required | Associated ML FB | Associated MC FB | Associated AKD Parameter |
---|---|---|---|---|---|
0x20A4 - 0 or 0x2802 - 0 |
Latch control word | No |
|
|
|
0x6040 - 0 |
|
Yes |
|
||
0x60B2 - 0 or 0x60F6 - 1 |
Additive torque value (Torque Feed Forward) |
No |
|
N/A 3 |
|
0x60C1 - 1 or 0x6062 - 0 |
Position demand value |
Yes |
|
|
|
From Drive to Controller (TxPDO)
These Drive to Controller objects are available in the default PDO.
TxPDO - AKD Drive CANopen Objects
Index - subindex | Object Name | Required | Associated ML FB | Associated MC FB | Associated AKD Parameter |
---|---|---|---|---|---|
0x6041 - 0 |
|
Yes | N/A | N/A | N/A |
0x6063 - 0 or 0x6064 - 0 |
Position actual value |
No |
|
|
|
0x2050 - 0 or 0x35C9 - 0 |
Position actual value 2 |
No |
MLAxisRead2ndFB
|
|
(If DRV.CMDSOURCE = 1) |
0x606C - 0 |
Velocity actual value |
No |
|
|
|
0x6077 - 0 | No |
|
|
|
|
0x20A5 - 0 or 0x2901 - 0 |
Latch status word | No |
|
CAPx.STATE |
|
0x20A6 - 0 or 0x2902 - 0 |
Latch position | No |
|
|
|
0x60FD - 0 |
Digital inputs Used by Onboard I/O mappings |
No | N/A | N/A |
|
0x3470-4 |
AIN.VALUE Used by Onboard I/O mappings |
No | N/A | N/A | AIN.VALUE |
0x60F4 |
Following error |
No |
|
|
|
TxPDO - AKD2G Drive CANopen Objects
Index - subindex | Object Name | Required | Associated ML FB | Associated MC FB | Associated AKD Parameter |
---|---|---|---|---|---|
0x3780:1 | AIN1.VALUE | No | N/A | N/A | |
0x3781:1 | AIN2.VALUE | No | N/A | N/A | |
0x6041:0 / 0x6841:0 |
Status word - Axis 1 / 2 |
Yes |
Needed for the servo axis mapped to the drive to work properly. |
Needed for the servo axis mapped to the drive to work properly. |
|
0x6064:0 / 0x6864:0 |
Position actual value - Axis 1 / 2 |
Yes |
Needed for the servo axis mapped to the drive to work properly. |
Needed for the servo axis mapped to the drive to work properly. |
|
0x6077:0 / 0x6877:0 |
Torque actual value - Axis 1 / 2 |
No |
|
|
|
0x60B9:0 / 0x68B9:0 |
Touch Probe Status Axis 1 / 2 |
No |
|
||
0x60D1:0 / 0x68D1:0 |
Touch Probe 1 Time Stamp positive value Axis 1 / 2 |
No |
|
||
0x60D4:0 / 0x68D4:0 |
Touch Probe 2 Time Stamp positive value Axis 1 / 2 |
No |
|
||
0x60E4:3 |
3rd additional Position actual value Axis 1 |
No | MLSmpConECAT | For a digitizing axis | |
0x60E4:4 |
4th additional Position actual value Axis 1 |
MLSmpConECAT | For a digitizing axis | ||
0x60E4:5 |
5th additional Position actual value Axis 1 |
MLSmpConECAT | For a digitizing axis | ||
0x60F4:0 / 0x68F4:0 |
Following error actual value Axis 1 / 2 |
No |
|
-
- Axis 1 objects begin with 0x60.
Axis 2 objects begin with 0x68.
TxPDO - AKD-N Drive CANopen Objects
Index - subindex | Object Name | Required | Associated ML FB | Associated MC FB | Associated AKD Parameter |
---|---|---|---|---|---|
0x6041 - 0 |
|
Yes |
N/A |
N/A |
N/A |
0x6063 - 0 or 0x6064 - 0 |
Position actual value |
No |
|
|
|
0x606C - 0 |
Velocity actual value |
No |
|
|
|
0x6077 - 0 |
Torque actual value |
No |
|
|
|
0x20A5 - 0 or 0x2901 - 0 |
Latch status word | No |
|
CAPx.STATE |
|
0x20A6 - 0 or 0x2902 - 0 |
Latch position | No |
|
|
|
0x60FD - 0 |
Digital inputs Used by Onboard I/O mappings |
No |
N/A |
N/A |
|
0x60F4 |
Following error |
No |
|
|
|
TxPDO - S300 and S700 Drive CANopen Objects
Index - subindex | Object Name | Required | Associated ML FB | Associated MC FB | Associated AKD Parameter |
---|---|---|---|---|---|
0x6041 - 0 |
|
Yes |
N/A |
N/A |
N/A |
0x6063 - 0 or 0x6064 - 0 |
Position actual value |
No |
|
|
|
0x2050 - 0 or 0x35C9 - 0 |
Position actual value 2 |
No |
MLAxisRead2ndFB
|
|
(If DRV.CMDSOURCE = 1) |
0x6077 - 0 |
Torque actual value |
No |
|
|
|
0x20A5 - 0 or 0x2901 - 0 |
Latch status word | No |
|
CAPx.STATE |
|
0x20A6 - 0 or 0x2902 - 0 |
Latch position |
No |
|
CAPx.T - for time CAPx.PLFB - for position |
|
0x60F4 |
Following error |
No |
|
|
|
Examples
These are examples where the PDO object is passed as an argument in the function block.
Example 1
MLSmpConECAT( PipeNetwork.SMP1, 1001, 16#2050, 0);
Where:
PipeNetwork.SMP1
is a Sampler block ID.1001
is the EtherCAT ***EtherCAT is an open, high-performance Ethernet-based fieldbus system. The development goal of EtherCAT was to apply Ethernet to automation applications which require short data update times (also called cycle times) with low communication jitter (for synchronization purposes) and low hardware costs address for the first device.16#2050
(0x2050) is the object index and0
is the subindex for the AKD’s “Position actual value 2” object.
Example 2
MLCNVConnectEx(PipeNetwork.CNV1, PipeNetwork.AXIS1, EC_ADDITIVE_TORQUE_VALUE, 0 ) ;
The argument is a constant based on the object index.
Example 3
MLSmpConPNAxis(PipeNetwork.SMP1, PipeNetwork.AXIS1, ML_SECOND_FEEDBACK_POSITION);
Where:
ML_SECOND_FEEDBACK_POSITION specifies the secondary actual position from the Pipe Network Axis.
-
- The ML_SECOND_FEEDBACL_POSITION constant has been deprecated and only AKD devices supported it.
It is deprecated because the AKD2G supports more than one secondary feedback.