Lenze 8400 - Heartbeat Protocol; Telegram Structure

Lenze · 8400 HighLine · Reference manual · DMS 12.0 EN · 06/2017 · TD23 749
11 System bus "CAN on board"
11.10 Monitoring
_ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _ _
11.10.2 Heartbeat protocol
The heartbeat protocol can be used for node monitoring purposes within a CAN network.
Basic workflow
[11-9] Heartbeat protocol
1. A heartbeat producer cyclically transmits a so-called heartbeat telegram to one or more
consumers.
2. The consumer(s) monitor the heartbeat telegram for arrival on a regular basis.
11.10.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
+
HDUW
E
HDWSUR
G
XFHU
(0(5*(1&<
+
HDUW
E
HDWFRQVXPHUV
V

LQGLFDWLRQ
LQGLFDWLRQ
U
UHTXHVW LQGLFDWLRQ
V

LQGLFDWLRQ
LQGLFDWLRQ
+HDUWEHDWSURGXFHUWLPH
+HDUWEHDWFRQVXPHU
WLPH
+HDUWEHDW
HYHQW
LQGLFDWLRQ
+HDUWEHDWFRQVXPHU
WLPH
107PDVWHU
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 00000000
Stopped 4 00000100
Operational 5 00000101
Pre-Operational 127 01111111