
Parameter
Name / value range / [default setting]
Info
0x1201:001
SDO2 server parameter: COB-ID client -> server (RX)
0x00000000 ... [0x80000640] ... 0xFFFFFFFF
Specification of the receive identifier for SDO server channel 2.
•
If SDO server channel 2 is activated via
0x2301:005 (PAR 510/005)
,
this parameter is set to the value "node a 0x640". This default
setting can be changed.
0x1201:002
SDO2 server parameter: COB-ID server -> client (TX)
0x00000000 ... [0x800005C0] ... 0xFFFFFFFF
Specification of the transmit identifier for SDO server channel 2.
•
If SDO server channel 2 is activated via
0x2301:005 (PAR 510/005)
,
this parameter is set to the value "node a 0x5C0". This default
setting can be changed.
0x1201:003
SDO2 server parameter: SDO client node ID
1 ... [0] ... 127
Specification of the node address for the SDO client.
0x2301:005
(PAR 510/005)
CANopen settings: Activate SDO2 channel
(CANopen sett.: SDO2 config.)
1 = activate SDO server channel 2.
0 Not active
1 Active
8.4.11
CANopen error responses
The response to CANopen errors such as missing PDOs or heartbeat frames can be configured
via the following parameters.
Parameter
Name / value range / [default setting]
Info
0x1029:000
Error behavior: Highest subindex
•
Read only
0x1029:001
Error behavior: Communication error
Selection of the NMT state to which the inverter is to change automati-
cally if a failure of a CANopen node or an internal error is detected in the
"Operational" state.
These also include the following communication errors:
•
Change-over of the CAN interface to the "Bus-off" state.
•
Occurrence of a "Life Guarding Event".
•
Occurrence of a "Heartbeat Event".
0 Status -> Pre-operational
In the "Pre-operational" state, network management, sync, and emer-
gency telegrams as well as parameter data can be received; process
data, however, are ignored.
1 No status change
2 Status -> Stopped
In the "Stopped" state, only network management telegrams can be
received.
0x2857:001
CANopen monitoring: RPDO1-Timeout
•
For possible settings see description for
0x2D45:001 (PAR 310/001)
.
^
94
Selection of the response to triggering the RPDO1 time monitoring.
3 Error
0x2857:002
CANopen monitoring: RPDO2-Timeout
•
For possible settings see description for
0x2D45:001 (PAR 310/001)
.
^
94
Selection of the response to triggering the RPDO2 time monitoring.
3 Error
0x2857:003
CANopen monitoring: RPDO3-Timeout
•
For possible settings see description for
0x2D45:001 (PAR 310/001)
.
^
94
Selection of the response to triggering the RPDO3 time monitoring.
3 Error
0x2857:005
CANopen monitoring: Heartbeat-Timeout Consumer 1
•
For possible settings see description for
0x2D45:001 (PAR 310/001)
.
^
94
Selection of the response with "Heartbeat Event" in consumer 1.
3 Error
0x2857:006
CANopen monitoring: Heartbeat-Timeout Consumer 2
•
For possible settings see description for
0x2D45:001 (PAR 310/001)
.
^
94
Selection of the response with "Heartbeat Event" in consumer 2.
3 Error
0x2857:007
CANopen monitoring: Heartbeat-Timeout Consumer 3
•
For possible settings see description for
0x2D45:001 (PAR 310/001)
.
^
94
Selection of the response with "Heartbeat Event" in consumer 3.
3 Error
Configuring the network
CANopen
CANopen error responses
124
Phone: 800.894.0412 - Fax: 888.723.4773 - Web: www.actechdrives.com - Email: [email protected]