BLE(1)—— 简介

介绍

BLE 的全称叫做 Bluetooth Low Energy,也称之为低功耗蓝牙,属于蓝牙技术中的一种。与之对应的是 Classic Bluetooth,经典蓝牙。当然,经典蓝牙是最先推出来的,后面才有了 LE 的版本。在兼容性上,LE 的蓝牙不兼容 Classic 的版本,可以理解成为独立的一种蓝牙形态。旨在针对低功耗的领域进行的一种无线数据传送的解决方案。

 

频段

“蓝牙低功耗”技术采用与“经典蓝牙”技术相同的工作频率(2.400GHz-2.4835GHz - ISM频带),但使用另一组信道。不同于经典蓝牙的79 1-MHz信道,蓝牙低功耗使用40个 RF Channel,2MHz带宽信道。在一个信道内,数据使用高斯频移调制(GFSK)传输,类似经典蓝牙的基本速率方案;比特率1Mbit/s,最大发射功率10mW。

由于使用了免许可的 2.4GHz 频段,这个频段很多无线产品都在用(WIFI),所以为了稳定性,蓝牙在链接状态下,有一种称之为跳频的技术(Hopping),链接双方在约定好的时间段同时调到另外的频率上进行数据收发,避免了信道上的数据拥堵。

应用

手环,门锁,智能家居的节点等等,都能够使用 LE 的方案进行数据传送。

在一颗蓝牙芯片上,既能够支持 Classic 也支持 LE 的,称之为双模。否则,为单模。手机上的蓝牙芯片,绝大多数都是双模的蓝牙芯片。

当然,无线产品还有很多,ZigBee、Wifi、LTE 等等都是属于无线产品,BLE 只是其中的一种。

 

构成

既然是无线芯片呢,其组成由软件和硬件构成。软件部分,为 BLE 协议栈,硬件部分包含 RF PHY(无线收发装置),Modem(调制解调器),以及 Baseband(基带)构成。BLE 的协议规范,全部需要遵循 Core Spec 来进行定制,Core Spec 中包含了 RF 、Modem、Air Interface,数据编码/解码,以及软件的协议规范:

https://www.bluetooth.com/specifications/bluetooth-core-specification/

 

发展

蓝牙技术有一个叫做 SIG 的蓝牙技术联盟,联盟负责推动蓝牙技术的持续发展,包括定制 Spec,组织一些会议等等。

从最初的 BLE4.2 版本,发展到 BLE 5.0 (支持 Extend Advertising,Periodic Advertising,2M/Coded PHY等),到现在的 BLE 5.1 版本(AoA/AoD Antenna矩阵蓝牙定位,以及 ISO 同步传输),可见蓝牙的 LE 技术一直在高速的演进。

 

### AUTOSAR CAN PDU Specification and Implementation Details #### Definition of CAN PDU A **CAN PDU (Protocol Data Unit)** represents a segment of information that is processed at the protocol layer within the CAN communication stack. According to the definition provided, a CAN hardware object serves as an L-PDU buffer located inside the CAN RAM of the CAN hardware unit/controller[^2]. This implies that PDUs act as buffers holding data intended for transmission over the CAN bus or received from it. #### Structure and Handling of CAN PDUs Within the context of AUTOSAR, different types of PDUs exist such as I-PDUs (Inter-PDU), which carry application-layer messages between ECUs; N-PDUs (Network Layer Protocol Data Units) used in transport protocols like CanTp where segmentation/reassembly occurs; and others depending on specific requirements. For instance, when dealing with J1939 requests through COM and PduR configurations, certain actions need to be taken regarding IPDU group management and routing path setup[^4]. #### Configuration Parameters Related to CAN PDUs Configuration settings play a crucial role in defining how PDUs operate within systems adhering to AUTOSAR standards. In particular, modules like CanTp involve configuring various parameters including those related to SDUs (Service Data Units). Although older versions might have included deprecated fields like `CanTpRxDl` and `CanTpTxDl`, these do not affect current implementations since newer revisions disregard them entirely[^1]. #### Vendor-Specific Customizations Through Attributes To accommodate diverse hardware platforms while maintaining compatibility across vendors' products implementing CAN drivers under AUTOSAR guidelines, unique identifiers named `"VendorId"` along with `"VendorApiInfix"` attribute values serve as means to address distinct driver instances correctly during system integration processes[^3]. ```cpp // Example C++ code snippet showing usage of vendor-specific attributes if ((canDriver->getVendorId() == VENDOR_ID_BOSCH) && (!strcmp(canDriver->getVendorApiInfix(), "BoschAPI"))) { // Specific initialization routine for Bosch CAN driver } ```
评论 2
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

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

余额充值