CAN 总线 之四 BOSCH CAN2.0 Part A

CAN2.0 Part A规范介绍了CAN总线的单通道、总线值、比特率和消息传输机制,包括数据帧、远程帧、错误帧和过载帧的详细结构。它定义了标准格式和扩展格式,以满足不同应用场景的需求,并确保兼容性。CAN总线的仲裁机制确保了高效无冲突的数据传输。

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

前言

  随着越来越多的应用程序接受和引入串行通信,这就要求对特定应用程序的通信功能分配消息标识符以进行标准化。如果将原来由 11 个标识符位定义的地址范围扩大,则可以更方便地使用 CAN 实现这些应用程序。
  因此,引入了第二种消息格式(扩展格式),它提供了由 29 位标识符定义的更大的地址范围。这将减轻系统设计者在定义结构良好的命名方案方面的负担。不需要扩展格式提供的标识符范围的用户仍然可以依赖传统的 11 位标识符范围(标准格式)。在这种情况下,他们可以使用市场上已有的 CAN 控制器,或者实现了这两种格式的新控制器。
  为了区分 标准格式扩展格式 ,使用了 CAN 消息格式的控制域的第一个保留位 r1(控制域有 r1 和 r0 两个保留位)。 这样做是为了使 CAN 规范 1.2 中的旧的消息格式等同于本规范的新的标准格式。 此外,本规范定义的扩展格式可以和标准格式的消息在同一网络中共存。

CAN2.0 规范由两部分组成

  • Part A 描述 CAN 规范 1.2 中定义的 CAN 消息格式
  • Part B 描述了标准消息格式扩展消息格式

注:根据本规范 Part A 或 根据以前的 CAN 规范设计的 CAN 实现,以及根据本规范的 Part B 设计的 CAN 实现可以相互通信,只要它不使用扩展格式即可。

The Controller Area Network (CAN) is a serial communications protocol which efficiently supports distributed realtime control with a very high level of security. Its domain of application ranges from high speed networks to low cost multiplex wiring. In automotive electronics, engine control units, sensors, anti-skid-systems, etc. are connected using CAN with bitrates up to 1 Mbit/s. At the same time it is cost effective to build into vehicle body electronics, e.g. lamp clusters, electric windows etc. to replace the wiring harness otherwise required. The intention of this specification is to achieve compatibility between any two CAN implementations. Compatibility, however, has different aspects regarding e.g. electrical features and the interpretation of data to be transferred. To achieve design transparency and implementation flexibility CAN has been subdivided into different layers. • the (CAN-) object layer • the (CAN-) transfer layer • the physical layer The object layer and the transfer layer comprise all services and functions of the data link layer defined by the ISO/OSI model. The scope of the object layer includes • finding which messages are to be transmitted • deciding which messages received by the transfer layer are actually to be used, • providing an interface to the application layer related hardware. There is much freedom in defining object handling. The scope of the transfer layer mainly is the transfer protocol, i.e. controlling the framing, performing arbitration, error checking, error signalling and fault confinement. Within the transfer layer it is decided whether the bus is free for starting a new transmission or whether a reception is just starting. Also some general features of the bit timing are regarded as part of the transfer layer. It is in the nature of the transfer layer that there is no freedom for modifications. The scope of the physical layer is the actual transfer of the bits between the different nodes with respect to all electrical properties. Within one network the physical layer, of course, has to be the same for all nodes. There may be, however, much freedom in selecting a physical layer. The scope of this specification is to define the transfer layer and the consequences of the CAN protocol on the surrounding layers.
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包

打赏作者

ZC·Shou

你的鼓励将是我创作的最大动力

¥1 ¥2 ¥4 ¥6 ¥10 ¥20
扫码支付:¥1
获取中
扫码支付

您的余额不足,请更换扫码支付或充值

打赏作者

实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值