Lenze 8400 - Manual (Page 674)

11 CANopen option
11.10 Monitoring
674
Lenze · 8400 protec HighLine · Reference manual · DMS 3.0 EN · 03/2013 · TD05
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
11.10.2.3 Commissioning example
Task
An 8400 controller (node 2) which is configured as heartbeat consumer is to monitor another 8400
controller (heartbeat producer, node 1).
• The heartbeat producer is to transmit a heartbeat telegram to the heartbeat consumer every
10 ms.
• The heartbeat consumer monitors the heartbeat telegram for arrival. A response is to be
activated in the event of an error.
Parameterising the heartbeat producer (node 1)
1. Set the heartbeat producer time ( C00381 ) to 10 ms.
Parameterising the heartbeat consumer (node 2)
1. Set the CAN node address of the producer in C00385/1 .
2. Set the heartbeat consumer time in C00386/1 .
• Note: The heartbeat consumer time must be greater than the heartbeat producer time of the
node to be monitored set in C00381 .
3. Set the desired response in C00592/5 which is to be activated should a heartbeat event in the
consumer occur.

Tip!
C00347/1...n displays the heartbeat status of the monitored nodes.
Heartbeat telegram
• The heartbeat telegram of the producer has the following identifier:
Identifier (COB-ID) = 1792 + producer's node address = 1792 + 1 = 1793 = 0x701

Note!
The heartbeat monitoring will not start until the first heartbeat telegram of a monitored
producer has been received successfully and the "Pre-Operational" NMT status has been
assumed.
The boot-up telegram counts as the first heartbeat telegram.