2 heartbeat protocol, 1 telegram structure, Heartbeat protocol – Lenze 8400 BaseLine C User Manual
Page 207: Telegram structure, System bus "can on board": heartbeat protocol, 9system bus "can on board

Lenze · 8400 BaseLine C · Reference manual · DMS 1.6 EN · 01/2014 · TD05
207
9
System bus "CAN on board"
9.8
Monitoring
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
9.8.2
Heartbeat protocol
The heartbeat protocol can be used for node monitoring purposes within a CAN network.
Basic workflow
[9-8]
Heartbeat protocol
1. A heartbeat producer cyclically transmits a so-called heartbeat telegram to one or more consu-
mers.
2. The consumer(s) monitor the heartbeat telegram for arrival on a regular basis.
9.8.2.1
Telegram structure
• The heartbeat telegram of the producer has the following identifier:
Identifier (COB-ID) = 1792 + producer's node address
• The user data (1 byte) contain the status (s) of the producer:
r: Reserved (always 0)
s: Status of the producer (0: Boot-up, 4: Stopped, 5: Operational, 127: Pre-Operational)
U
UHTXHVW
LQGLFDWLRQ
+HDUWEHDWSURGXFHU
(0(5*(1&<
+HDUWEHDWFRQVXPHUV
V
LQGLFDWLRQ
LQGLFDWLRQ
U
UHTXHVW
LQGLFDWLRQ
V
LQGLFDWLRQ
LQGLFDWLRQ
+HDUWEHDWSURGXFHUWLPH
+HDUWEHDWFRQVXPHU
WLPH
+HDUWEHDW
HYHQW
LQGLFDWLRQ
+HDUWEHDWFRQVXPHU
WLPH
107PDVWHU
Heartbeat producer status
Data
Communication status
Decimal value
(s)
(r)
Producer status (s)
Bit 7
Bit 6
Bit 5
Bit 4
Bit 3
Bit 2
Bit 1
Bit 0
Boot-up
0
0
0
0
0
0
0
0
0
Stopped
4
0
0
0
0
0
1
0
0
Operational
5
0
0
0
0
0
1
0
1
Pre-Operational
127
0
1
1
1
1
1
1
1