![Festo CMMP-AS-***-M0 Series Скачать руководство пользователя страница 42](http://html1.mh-extra.com/html/festo/cmmp-as-m0-series/cmmp-as-m0-series_manual_2283119042.webp)
3
CANopen access procedure
42
Festo – GDCP-CMMP-M3/-M0-C-CO-EN – 1510b – English
3.8
Heartbeat (Error Control Protocol)
3.8.1
Overview
The so-called Heartbeat protocol can be activated to monitor communication between slave (drive) and
master: Here, the drive sends messages cyclically to the master. The master can check whether these
messages occur cyclically and introduce corresponding measures if they do not. Since both Heartbeat
and Nodeguarding telegrams (
chap. 3.9) are sent with the identifier 700
h
+ node number, both pro
tocols can be active at the same time. If both protocols are activated simultaneously, only the Heart
beat protocol is active.
3.8.2
Structure of the Heartbeat Message
The Heartbeat telegram is transmitted with the identifier 700
h
+ node number. It contains only 1 byte of
user data, the NMT status of the controller (
chapter 3.6, Network Management (NMT Service)).
701
h
1
N
Identifier: 700
h
+ node number
NMT status
Data length
N
Significance
04
h
Stopped
05
h
Operational
7F
h
Pre-Operational
3.8.3
Description of the Objects
Object 1017
h
: producer_heartbeat_time
To activate then Heartbeat function, the time between two Heartbeat telegrams can be established via
the object producer_heartbeat_time.
Index
1017
h
Name
producer_heartbeat_time
Object Code
VAR
Data Type
UINT16
Access
rw
PDO
no
Units
ms
Value Range
0 … 65535
Default Value
0