can in automation (cia): error control protocol

最新推荐文章于 2024-05-13 22:06:47 发布

weixin_30381317

最新推荐文章于 2024-05-13 22:06:47 发布

阅读量167

点赞数

CC 4.0 BY-SA版权

原文链接：http://www.cnblogs.com/kangderui/archive/2009/12/31/1636513.html

本文介绍了CANopen中两种错误控制协议：心跳协议和节点/生命保障。心跳协议通过周期性发送心跳消息来检查设备是否正常运行，而节点/生命保障则通过请求错误控制消息来实现。对于新设计，推荐使用心跳协议。

摘要生成于 C知道，由 DeepSeek-R1 满血版支持，前往体验 >

two types of error control protocols exist in canopen: heartbeat and node/lifeguarding. for new designs, cia recommends the heartbeat protocol.

1) heartbeat:

the canopen device transmits its heartbeat cyclically. the cycle time is called producer heartbeat time and configured in object 1017h. the heartbeat consumer (e.g. the canopen manager) evaluates on reception of the heartbeat message, whether e.g. the related device is still working properly or not and remains in the correct network state. the heartbeat consumer capability is configured in object 1016h (e.g. within the canopen manager). in this object the period of time is configured, in which at least one heartbeat message has to be received from the related heartbeat producer.

2) node/life guarding:

guarding is an outdated method of checking whether the device to be guarded is still working in the correct network state or not. therefore e.g. the canopen manager requests the error control message via a can remote frame (rtr). the device to be guarded replies with a can data frame, which indicates the current nmt state. as this is an rtr-based service, the heartbeat protocol is recommended for error control purposes in new designs.

转载于:https://www.cnblogs.com/kangderui/archive/2009/12/31/1636513.html