BECKHOFF BK51x0 - Manual (Page 3)

BECKHOFF New Automation Technology page 3/4
Update info CANopen version 3 to version 4.01 2002-04-30
Advantage: Uniform and manufacturer independent LED behaviour
Effects when using new bus couplers in existing networks: Optical diagnosis in error case
has changed minimally. No change in normal operation.
3. Object Dictionary
3.1 Identity Object now supported
New: The new CANopen Identity Object 0x1018 is now supported. It provides the following
information about the device:
Sub index 1: Vendor ID. Beckhoff has the Vendor ID 2.
Sub index 2: Product Code. BK5120: 0x11400; BK5110: 0x113F6; LC5100: 0x113EC;
IPwxyz-B510: 0x2wxyz; IL2301-B510: 0x2008FD.
Sub index 3: Revision Number
Sub index 4: Production date; Low Word, High Byte: Calendar week (dec), Low Byte:
Calendar year
Advantage: Additional information about the device is provided manufacturer independently.
Effects when using new bus couplers in existing networks: none
3.2 0x100E: Guarding-Identifier now Read-Only
New: The default identifier for the Guarding and Heartbeat Protocol may not be changed any
more.
Advantage: Clear assignment of the corresponding CAN Frames to the node addresses.
Effects when using new bus couplers in existing networks: Only, if Guarding identifier was
changed.
3.3 Object 0x1004 removed
New: In CANopen Version 4.0 Object 0x1004 (Number of PDOs) is not supported any more,
as it did not provide valuable information.
Advantage: reduced memory usage.
Effects when using new bus couplers in existing networks: Only, if number of PDOs was
derived from object 0x1004.
3.4 Time-Out at SYNC monitoring extended
New: The watchdog for the SNYC monitoring is now set to the 1,5-fold of the value in Object
0x1006.
Advantage: Now the actually intended SYNC Interval can be written to Object 0x1006.
Effects when using new bus couplers in existing networks: none
4. Network Management
4.1 Boot-Up message now uses guarding identifier
New: The boot-up message, that Beckhoff had introduced, in CANopen version 4 now has
been defined manufacturer independently. Instead of an Emergency message without
data now a Guarding telegram with one data byte (0) is sent.