35
Limitorque MX DeviceNet Field Unit FCD LMENIM2328-00 – 11/05
flowserve.com
The Device Heartbeat Message is triggered by the Identity Object Instance Attribute Heartbeat Interval
(Attribute ID 10). For this, the Heartbeat Interval has to be set to the time interval of the Device
Heartbeat Message in seconds.
4.5.1 Device Shutdown Message
The DeviceNet Limitorque Interface supports the Device Shutdown Message. The DeviceNet Limitorque
Interface produces this message when it transitions to the offline state. Table 4.43 shows the format of
the data field of the Device Shutdown in Message.
Table 4.43 – Format of the Device Shutdown Message
Byte
Offset
7
6
5
4
3
2
1
0
0
DeviceNet Protocol Specific
1
2
Class ID
3
4
Instance ID
5
6
Shutdown Code
Range 200hex – 2FFhex
7
For the DeviceNet Limitorque Interface, the Class ID and the Instance ID of this message depends on the
originator of the Device Shutdown Message, e.g. after Reset-Service performed on the Identity Object,
Class ID 1 and Instance 1, a Device Shutdown Message is sent.
For application purposes 2 Bytes of the Device Shutdown Message are reserved for the Shutdown
Code. Then vendor specific range of this code is 200 – 2FF. Table 4.44 lists all Shutdown Codes of the
DeviceNet Limitorque Interface.
Table 4.44 – Device Shutdown Codes
Class ID
Instance ID Shutdown
Code
Causes of Shutdown
1
1
4
Remote Reset: Reset service of the identity Object
3
1
4
Remote reset: Setting of the MAC ID via Attribute 1 of the DeviceNet
Object
0
0
5
Internal diagnostic fault: An internal diagnostic fault has caused the
service to shut down. Reason for this can be an overrun of the CAN
transmit queue, CAN receive queue or CAN Controller receive buffer
0
0
4
DeviceNet Limitorque Interface will be reset because SMT Main Board
signal RESET is active.
102
1
0x201
DeviceNet Limitorque Interface will be reset because SMT Main Board
has changed MAC ID via LCD
102
1
0x202
DeviceNet Limitorque Interface will be reset because SMT Main Board
has changed Baud rate via LCD
4.6 Configuration Confirmation
DNFU operation cannot be verified until the complete DeviceNet system is operational. However, routine
checks can be performed to verify many functions.
4.6.1 Checking Connections
Verify that all connections, including data wires, shield ground, are in accordance with MX wiring
diagrams and DNFU diagrams in Section 3.1.2, Network Cable Preparation.
