WAGO I/O-SYSTEM 750, Technical Description

Page: 109 / 192

CANopen • 109
Network Communication
WAGO-I/O-SYSTEM 750
CANopen
4.3.4.2.7 Object 0x1009, Manufacturer Hardware Version
Idx S-Idx Name Type Attribute Default Value
0x1009 0 Manufacturer Hard-
ware Version
Visible
String RO Current HW-Version
The object indicates the current hardware version of the bus coupler.
4.3.4.2.8 Object 0x100A, Manufacturer Software Version
Idx S-Idx Name Type Attribute Default Value
0x100A 0 Manufacturer Soft-
ware Version Visible
String RO Current SW-Version
The object indicates the current software version of the bus coupler.
4.3.4.2.9 Object 0x100C, Guard Time
Idx S-Idx Name Type Attribute Default Value
0x100C 0 Guard Time Unsigned16 RW 0
The object indicates the Guarding Time in milli-seconds. An NMT master cy-
clically interrogates the NMT slave for its status. The time between two inter-
rogations is termed
Guard Time .
4.3.4.2.10 Object 0x100D, Life Time Factor
Idx S-Idx Name Type Attribute Default Value
0x100D 0 Lifetime Factor Unsigned8 RW 0
The life Time Factor is part of the Node Guarding Protocol . The NMT slave
checks if it was interrogated within the Node Life Time (Guardtime multiplied
with the life time factor). If not, the slave works on the basis that the NMT
master is no longer in its normal operation. It then triggers a
Life Guarding
Event .
If the node life time is zero, no monitoring will take place.
4.3.4.2.11 Object 0x1010, Store Parameters
Idx S-Idx Name Type Attribute Default Value
0x1010 0 Max. supported Sub-
Index Unsigned8 RO 1
1 Store all Parameter Unsigned32 RW 1
This object allows to permanently store the settings made by the user. For this
purpose, the signature „save" (lower case letters ASCII -
MSB – 0x65 76 61
73 - LSB) must be written into the index 0x1010 sub index 1. The storing
process runs in the background and takes approx. 2-3 seconds. When the stor-
ing process is finished, the SDO reply telegram is sent. Communication re-
mains possible during storage by means of SDOs. An error message as a result
of a new storage attempt only occurs, when the previous one was not yet fin-
ished. It is also not possible to trigger the storage function for as long as „Re-
store" is active.