如何使用该博文?
==>您可以将该篇博文当做“字典”,遇到疑惑的Autosar“关键字”,使用组合键Ctrl+F,快速查找该关键字。
推荐Autosar培训教程(点击下方卡片接口跳转):
《Autosar从入门到精通-实战篇》总目录_培训教程持续更新中...https://blog.csdn.net/qfmzhu/article/details/112425670https://blog.csdn.net/qfmzhu/article/details/112425670《Autosar_BSW高阶配置》总目录_培训教程持续更新中...https://blog.csdn.net/qfmzhu/article/details/118652658
https://blog.csdn.net/qfmzhu/article/details/118652658
目录
1.1 Diagnostic Communication Manager:Dcm
1.2 Diagnostic Event Manager:Dem
2.1 Universal Calibration Protocol:XCP
3.2 CAN Network Management:CanNm
3.4 Network Management Interface:NM
3.8 Time Sync Over CAN:CanTSyn
3.10 CAN Tranceiver Driver:CanTrcv
4.1 FlexRay Network Management:FrNm
4.2 FlexRay State Manager:FrSM
4.3 Time Sync Over FlexRay:FrTSyn
4.5 FlexRay Tranceiver Driver:FrTrcv
1 UDS/OBD诊断篇
1.1 Diagnostic Communication Manager:Dcm
缩写 | 描述 |
Application Layer 应用层 | The Application Layer is placed above the RTE.Within the Application Layer the AUTOSAR Software-Components are placed. 应用层放置在RTE之上。在应用层中放置了AUTOSAR软件组件。 |
Channel 通道 | A link at which a data transfer can take place.If there is more than one Channel, there is normally some kind of ID assigned to the Channel. 可以进行数据传输的链接。如果有多个通道,通常会为通道分配某种ID。 |
Diagnostic Channel 诊断通道 | A link at which a data transfer between a diagnostic tool and an ECU can take place. Example: An ECU is connected via CAN and the diagnostic channel has an assigned CAN-ID.Diagnostic channels connected to other bus-systems such as MOST, FlexRay, LIN, etc. are also possible. 诊断工具和ECU之间可以进行数据传输的链接。 举例: ECU 通过CAN连接,诊断通道具有分配的CAN-ID。连接到其他总线系统(例如MOST, FlexRay, LIN等)的诊断通道也是可能的。 |
External Diagnostic Tool 外部诊断工具 | A device which is NOT permanently connected to the vehicle communication network. This External Diagnostic Tool can be connected to the vehicle for various purposes, as e.g. for:
Example External Diagnostic Tools are:
The External Diagnostic Tool is to be connected by a mechanic to gather information from ”inside” the car. 未永久连接到车辆通信网络的设备。该外部诊断工具可以出于各种目的连接到车辆,例如,为了:
示例外部诊断工具是: • 诊断测试仪 • OBD 扫描工具 外部诊断工具将由机械师连接以从汽车“内部”收集信息。 |
冻结帧 | A set of the vehicle/system operation conditions at a specific time. 特定时间的一组车辆/系统运行条件。 |
Functional Addressing 功能寻址 | The diagnostic communication model where a group or all nodes of a specific communication network receive a message from one sending node (1-n communication). This model is also referred to as ’broadcast’ or ’multicast’. OBD communication will always be done in the Functional Addressing mode. 特定通信网络的一组或所有节点从一个发送节点接收消息的诊断通信模型(1-n 通信)。该模型也称为“广播”或“多播”。OBD通信将始终在功能寻址模式下完成。 |
Internal Diagnostic Tool 内部诊断工具 | A device/ECU which is connected to the vehicle communication network.The Internal Diagnostic Tool can be used for:
The behavior of the Internal Diagnostic Tool can be the same as of an External Diagnostic Tool. The notion of ”Internal Diagnostic Tool” does not imply that it is included in each ECU as an AUTOSAR Software-Component. 连接到车辆通信网络的设备/ECU。内部诊断工具可用于: • 高级事件跟踪 • 高级分析 • 用于服务 内部诊断工具的行为可以与外部诊断工具的行为相同。“内部诊断工具”的概念并不意味着它作为AUTOSAR软件组件包含在每个ECU中。 |
Physical Addressing 物理寻址 | The diagnostic communication model where a node of a specific communication network receives a message from one sending node (1-1 communication). This model is also referred to as ’unicast’. 特定通信网络的节点从一个发送节点接收消息的诊断通信模型(1-1通信)。该模型也称为“单播”。 |
UDS Service UDS服务 | this refers to a UDS Service as defined in ISO14229-1 [2]. 这指的是ISO14229-1 [2]中定义的UDS服务。 |
OBD服务 | This refers to an OBD Service as defined in ISO15031-5 [1]. 这是指 ISO15031-5 [1] 中定义的OBD服务。 |
AddressAndLengthFormat Identifier 地址和长度格式标识符 | Defines the number of bytes used for the memoryAddress and memorySize parameter in the request messages. 定义用于请求消息中的memoryAddress和memorySize参数的字节数。 |
OBD Scan tool OBD扫描工具 | See definition External Diagnostic Tool. 请参阅定义外部诊断工具。 |
描述 | |
Application Programming Interface 应用程序接口 | |
Controller Area Network 控制器局域网 | |
Diagnostic Communication Manager 诊断通信管理器 | |
Diagnostic Event Manager 诊断事件管理器 | |
Default Error Tracer 默认错误跟踪器 | |
DID | Data Identifier 数据标识符 |
Diagnostic Service Dispatcher (submodule of the Dcm module) 诊断服务调度器(Dcm模块的子模块) | |
Diagnostic Session Layer (submodule of the Dcm module) 诊断会话层(Dcm模块的子模块) | |
Diagnostic Service Processing (submodule of the Dcm module) 诊断服务处理(Dcm模块的子模块) | |
Diagnostic Trouble Codes 诊断故障代码 | |
ID | Identifier 标识符 |
LIN | Local Interconnect Network 本地互连网络 |
Micro-Controller Unit 微控制器单元 | |
Media Orientated System Transport 面向媒体的系统传输 | |
Negative Response Code 否定响应代码 | |
OBD | On-Board Diagnosis 车载诊断 |
Open Systems Interconnection 开放系统互连 | |
Protocol Data Unit 协议数据单元 | |
Parameter Identifier 参数标识符 | |
Routine Identifier 例程标识符 | |
ResponseOnEvent 响应事件 | |
RTE | Runtime Environment 运行环境 |
SAP | Service Access Point 服务访问点 |
Service Data Unit 服务数据单元 | |
Service Identifier 服务标识符 | |
Software-Component 软件组件 | |
Transport Protocol 传输协议 | |
UDS | Unified Diagnostic Services 统一诊断服务 |
Placeholder for an API provider 一个API提供者的占位符 | |
SPRMIB | suppressPosRspMsgIndicationBit 抑制肯定响应消息指示位 |
以上摘自《AUTOSAR_SWS_DiagnosticCommunicationManager.pdf (V4.3.0)》。
1.2 Diagnostic Event Manager:Dem
缩写 | 描述 |
Activation Mode 1 激活模式 1 | Absence of malfunction - The MIL shall blink for one flash. 无故障 - MIL 应闪烁一闪。 |
Activation Mode 2 激活模式2 | "on-demand-MI" – The MIL shall show blink for two flashes if the OBD system would command an on-demand-MI according to the discriminatory display strategy. “按需 MI”-如果OBD系统将根据区分显示策略命令按需MI,则MIL应显示闪烁两次。 |
Activation Mode 3 激活模式3 | "short-MI" – The MIL shall blink for three flashes if the OBD system would command a short-MI according to the discriminatory display strategy. “短MI”-如果OBD系统根据判别显示策略命令短MI,则MIL应闪烁 3 次。 |
Activation Mode 4 激活模式 4 | "continuous-MI" - The MIL shall remain continuously ON("continuous-MI") if the OBD system would command a continuous-MI according to the discriminatory display strategy. “连续-MI”-如果OBD系统将根据区分显示策略命令连续MI,则MIL应保持连续ON(“continuous-MI”)。 |
Aging 老化 | Unlearning/deleting of a no longer failed event/DTC after a defined number of operation cycles from event memory. 在定义的操作周期数后,从事件存储器中取消学习/删除不再失败的事件/DTC。 |
Aging Counter 老化计数器 | The "Aging Counter" or "Aging Cycle Counter" or "DTC Aging Counter" specifies the counter which is used to perform Aging. It counts the number of operation cycles until an event/DTC is removed from event memory. “老化计数器”或“老化周期计数器”或“DTC老化计数器”指定用于执行老化的计数器。它计算操作周期数,直到从事件存储器中删除事件/DTC。 |
Class B1 counter B1类计数器 | Number of engine hours during which a Class B1 malfunction has been Confirmed and TestFailed. 已确认B1级故障且测试失败的发动机小时数。 |
Combined DTC 组合故障码 | Normal DTC, but referenced by multiple events reported by several monitors (e.g. ECU Defect, consisting of different HW defects). 正常DTC,但由多个监视器报告的多个事件引用(例如ECU缺陷,由不同的硬件缺陷组成)。 |
Continuous-MI counter 连续 MI 计数器 | Hours run by the engine while a continuous MI is commanded. 指令连续MI时发动机运行的小时数。 |
Cumulative Continuous-MI counter 累积连续 MI 计数器 | Number of engine hours during which MI has been continuously commanded to be on during its lifetime. MI 在其使用寿命期间被连续命令开启的发动机小时数。 |
Debounce counter 去抖计数器 | Internal counter for counter-based debouncing algorithm(s). 基于计数器的去抖动算法的内部计数器。 |
DemComponent/Monitored Component 演示组件/监控组件 | A monitored component is a part of the system, which is checked for proper operation by one or several monitorings. (see chapter 7.5) 受监控组件是系统的一部分,通过一个或多个监控来检查其是否正常运行。(见第7.5章) |
Dem-internal data value 内部数据值 | Some data values (e.g. the occurrence counter) are calculated by the Dem module itself internally. 一些数据值(例如发生计数器)由 Dem 模块本身在内部计算。 |
Denominator 分母 | The denominator of a specific monitorm (Denominatorm) is a counter indicating the number of vehicle driving events, taking into account conditions specific to that specific monitor. 特定监视器的分母(Denominatorm)是一个计数器,指示车辆驾驶事件的数量,并考虑到特定监视器的特定条件。 |
Dependent/Secondary ECUs 从属/次要ECU | Dependent/Secondary (or dep. / sec. ) ECUs are always related to a Master or a Primary ECU. 从属/次要(或 dep./sec.)ECU 始终与主ECU或主ECU相关。 |
Directed acyclic graph 有向无环图 | Dependency graph without circular dependencies. 没有循环依赖的依赖图。 |
Displacement 移位 | Replacing the the most insignificant event memory entry by a more significant event memory entry which needs to be stored. 用需要存储的更重要的事件存储器条目替换最不重要的事件存储器条目。 |
DTC group 故障诊断组 | Uniquely identifies an set of DTCs. A DTC group is mapped into the range of valid DTCs. By providing a group of DTCs it is expressed that a certain operation is requested on all DTCs of that group. The DTC group definition is provided by ISO 14229-1[2] and OEM/supplier specific. 唯一标识一组DTC。DTC组被映射到有效DTC的范围内。通过提供一组DTC,表示对该组的所有DTC请求某个操作。DTC组定义由ISO 14229-1[2]和OEM/供应商特定提供。 |
DtcGroupAllDtcs | Grouping of all configured DTCS (representation is 0xFFFFFF). 对所有配置的DTCS进行分组(表示为 0xFFFFFF)。 |
Event combination 事件组合 | Event combination is a method to merge several events to one specific combined DTC. It is used to adapt different monitor results to one significant fault, which is clearly evaluable in a service station. 事件组合是一种将多个事件合并到一个特定组合DTC的方法。它用于使不同的监测结果适应一个重大故障,这在服务站中是明显可评估的。 |
Event debouncing 事件去抖动 | Debouncing is a specific mechanism (e.g. counter-based) to evaluate,if the diagnostic event gets qualified.This works on top of potential signal debouncing and can be done within the SW-C or inside the Dem. 去抖动是一种评估诊断事件是否合格的特定机制(例如基于计数器)。这适用于潜在的信号去抖动,可以在SW-C或Dem内部完成。 |
Event confirmation 事件确认 | A diagnostic event is confirmed in case of repeated detection of qualified events over cycles or time evaluated by means of fault confirmation counters. Therefore, also the UDS status bit 3 (ConfirmedDTC) is set. 在通过故障确认计数器评估的循环或时间重复检测合格事件的情况下,确认诊断事件。 因此,UDS状态位3(ConfirmedDTC)也被设置。 |
Event memory 事件存储 | An event memory (e.g. Primary memory) consists of several event memory entries. 一个事件存储器(例如主存储器)由多个事件存储器条目组成。 |
Event memory entry 事件存储入口 | The event memory entry is a single storage container for an event and its event related data. The event memory entry is dynamically assigned to specific events. 事件存储器条目是事件及其事件相关数据的单个存储容器。事件存储器条目动态分配给特定事件。 |
Event memory overflow indication 事件内存溢出指示 | The event memory overflow indication indicates, if this specific event memory is full and the next event occurs to be stored in this event memory. 事件存储器溢出指示指示,如果该特定事件存储器已满并且下一个事件发生将存储在该事件存储器中。 |
Event qualification 事件资格 | A diagnostic event is qualified in case of a passed or a failed result is set (Deminternal or reported from another BSW module or SW-C). 如果设置了通过或失败的结果,则对诊断事件进行限定(Deminternal或从另一个BSW 模块或SW-C报告)。 |
Event related data 事件相关数据 | Event related data is additional data, e.g. sensor values or time stamp/mileage, which is stored with an event in an event memory.ISO defines two types of event related data: freeze frames (snapshot records) and extended data. 事件相关数据是附加数据,例如,传感器值或时间戳/里程,与事件一起存储在事件存储器中。ISO定义了两种类型的事件相关数据:冻结帧(快照记录)和扩展数据。 |
Event status byte 事件状态字节 | Status byte as defined in ISO 14229-1 [1], based on event level. ISO 14229-1 [1]中定义的状态字节,基于事件级别。 |
扩展数据记录 | An extended data record is a record to store specific information assigned to a fault. 扩展数据记录是用于存储分配给故障的特定信息的记录。 |
故障计数器 | The Failure counter represents the Trip Counter according to ISO14229-1 [2].The Trip Counter counts the number of operation cycles(driving cycles) where a malfunction occurred.If the counter reaches the threshold (e.g., 2 driving cycles) the con 故障计数器表示符合ISO14229-1 [2]的跳闸计数器。行程计数器对发生故障的操作周期(驾驶周期)进行计数。如果计数器达到阈值(例如,2个驱动周期),则确认位从0变为 1。 |
Fault Detection Counter 故障检测计数器 | sint8 value as used in ISO and FDC-APIs. ISO和FDC-API中使用的sint8值。 |
冻结帧 | Freeze frame is defined as a record of data (DIDs/PIDs). Freeze frames are the same as SnapShotRecords in ISO-14229-1[2]. 冻结帧被定义为数据记录(DID/PID)。冻结帧与ISO-14229-1[2]中的SnapShotRecords 相同。 |
一般分母 | The general denominator is a counter indicating the number of times a vehicle has been operated, taking into account general conditions. 总分母是一个计数器,表示车辆已运行的次数,同时考虑了一般情况。 |
Switching off the warning indicator including the handling of reported passed results over a period of time/several operation cycles 关闭警告指示器,包括处理在一段时间/几个操作周期内报告的通过结果 | |
In-Use performance ratio 在用性能比 | The in-use performance ratio (IUPR) of a specific monitor m of the OBD system is: IUPRm = Numeratorm/Denominatorm OBD系统特定监视器m的在用性能比(IUPR)为:IUPRm = Numeratorm/Denominatorm |
主机ECU | As a primary ECU a Master ECU stores “it’s own” and “reported errors” of related dep./sec ECUs in it’s event memory.Beside this a Master has to fulfill special Master tasks as MIL Master or provision of “general nominator” information. 作为主ECU,主ECU将相关dep./sec ECU的“它自己的”和“报告的错误”存储在其事件存储器中。除此之外,Master还必须作为MIL Master完成特殊的Master任务或提供“一般提名人”信息。 |
监视器 | A diagnostic monitor is a routine entity determining the proper functionality of a component. Alternatively the term “diagnostic function” can be used. 诊断监视器是确定组件正确功能的常规实体。或者,可以使用术语“诊断功能”。 |
Numerator 分子 | The numerator of a specific monitorm (Numeratorm) is a counter indicating the number of times a vehicle has been operated such that all monitoring conditions necessary for that specific monitor to detect a malfunction have been encountered. 特定监视器的分子(Numeratorm)是一个计数器,指示车辆已被操作的次数,从而满足该特定监视器检测故障所需的所有监控条件。 |
NvM is marked for NvM_WriteAll NvM 被标记为 NvM_WriteAll | The Dem has called NvM_SetRamBlockStatus() to set the according NvM Block to be written by NvM_WriteAll() Dem调用了NvM_SetRamBlockStatus()来设置相应的NvM Block由NvM_WriteAll()写入 |
操作周期 | An ‘operation cycle’ is the base of the event qualifying and also Dem scheduling(e.g. ignition key off-on cycles, driving cycles,etc.) “操作周期”是赛事排位赛和Dem调度的基础(例如点火钥匙开关循环、驾驶循环等) |
OBD 车载诊断系统 | On-Board Diagnostics, or OBD is a generic term referring to a vehicle’s self-diagnostic and reporting capability.OBD systems give the vehicle owner or a repair technician access to state of health information for various vehicle sub-systems. 车载诊断或OBD是一个通用术语,指的是车辆的自我诊断和报告能力。OBD系统使车主或维修技术人员能够访问各种车辆子系统的健康状态信息。 |
"In a vehicle there can be 3 different types of OBD ECUs:
在车辆中可以有 3 种不同类型的 OBD ECU: • 主ECU(每辆车一个) • 主 ECU主ECU(每辆车几个) • 从属/次要ECU(每辆车有几个) | |
P码 | Power train code 动力传动代号 |
PFC cycle PFC循环 | Permanent fault code - driving cycle (OBD Term) 永久性故障代码 - 驾驶循环(OBD术语) |
Positive Callback from NvM 来自 NvM 的积极回调 | The Dem module shall use the APIs NvM_WriteBlock and NvM_GetErrorStatus of the NVRAMManager [5],if there is the necessity to store data between Dem_Init and Dem_Shutdown. Furthermore the API NvM_GetErrorStatus shall wait for positive response if writing of block completed successfully. 如果需要在Dem_Init和Dem_Shutdown之间存储数据,Dem模块应使用 NVRAMManager [5] 的APIs NvM_WriteBlock和NvM_GetErrorStatus。此外,如果块写入成功完成,API NvM_GetErrorStatus应等待肯定响应。 |
PossibleErrors 可能的错误 | PossibleErrors means the ApplicationErrors as defined in meta model 可能的错误是指元模型中定义的应用程序错误 |
主ECU | A primary ECU stores “it’s own” and "reported errors" of related dep. / sec ECUs in it’s event memory 主ECU在其事件存储器中存储相关 dep./sec ECU的“它自己的”和“报告的错误” |
RBM cycle RBM循环 | OBD Term: General Nominator / Rate-based monitoring – driving cycle (OBD Term) OBD术语:一般提名者/基于速率的监控 - 驾驶周期(OBD术语) |
Readiness 准备就绪 | The readiness refers to the tested bits TestNotCompletedSinceLastClear (bit 4) and TestNotCompleteThisOperationCycle (bit 6) of the UDS status byte. 就绪指的是UDS状态字节的测试位TestNotCompletedSinceLastClear(位4)和 TestNotCompleteThisOperationCycle(位6)。 |
Triggered to NvM 触发到 NvM | The Dem module shall use the API NvM_WriteBlock of the NVRAMManager [5], if there is the necessity to trigger the storage of data between Dem_Init and Dem_Shutdown.Furthermore the Dem module shall wait for positive response of NvM_WriteBlock if request has been accepted. 如果需要触发Dem_Init和Dem_Shutdown之间的数据存储,Dem模块应使用NVRAMManager [5]的API NvM_WriteBlock。此外,如果请求已被接受,Dem模块应等待 NvM_WriteBlock的肯定响应。 |
UDS 状态位 0 | testFailed bit of the UDS status byte. Indicates the result of the most recently performed test. UDS 状态字节的testFailed位。表示最近执行的测试的结果。 |
UDS 状态位 1 | testFailedThisOperationCycle bit of the UDS status byte. Indicates whether or not a diagnostic test has reported a testFailed result at any time during the current operation cycle. UDS状态字节的testFailedThisOperationCycle位。指示诊断测试是否在当前操作周期内的任何时间报告了testFailed结果。 |
UDS 状态位 2 | pendingDTC bit of the UDS status byte. Indicates whether or not a diagnostic test has reported a testFailed result at any time during the current or last completed operation cycle. UDS 状态字节的pendingDTC位。指示诊断测试是否在当前或最后完成的操作周期中的任何时间报告了testFailed结果。 |
UDS 状态位 3 | confirmedDTC bit of the UDS status byte. Indicates whether a malfunction was detected enough times to warrant that the DTC is desired to be stored in long-term memory. UDS状态字节的confirmedDTC位。指示故障是否被检测到足够次数以保证DTC需要存储在长期存储器中。 |
UDS 状态位 4 | testNotCompletedSinceLastClear bit of the UDS status byte.Indicates whether a DTC test has ever run and completed since the last time a call was made to ClearDiagnosticInformation. UDS状态字节的testNotCompletedSinceLastClear位。指示自上次调用ClearDiagnosticInformation以来,DTC测试是否曾经运行和完成。 |
UDS 状态位 5 | testFailedSinceLastClear bit of the UDS status byte.Indicates whether a DTC test has completed with a failed result since the last time a call was made to ClearDiagnosticInformation. UDS状态字节的testFailedSinceLastClear位。指示自上次调用 ClearDiagnosticInformation以来,DTC测试是否已完成但结果失败。 |
UDS 状态位 6 | testNotCompletedThisOperationCycle bit of the UDS status byte. Indicates whether a DTC test has ever run and completed during the current operation cycle. UDS状态字节的testNotCompletedThisOperationCycle位。指示DTC测试在当前操作周期内是否曾经运行并完成。 |
UDS status bit 7 UDS 状态位 7 | warningIndicatorRequested bit of the UDS status byte. Report the status of any warning indicators associated with a particular UDS状态字节的warningIndicatorRequested位。报告与特定DTC相关的任何警告指示器的状态。 |
UDS status byte UDS 状态字节 | Status byte as defined in ISO 14229-1 [1], based on DTC level. ISO 14229-1 [1]中定义的状态字节,基于DTC级别。 |
描述 | |
Application Programming Interface 应用程序接口 | |
Basic Software 基础软件 | |
CDD | Complex Device Driver 复杂的设备驱动程序 |
Cyclic Redundancy Check 循环冗余校验 | |
Diagnostic Communication Manager 诊断通信管理器 | |
Diagnostic Event Manager 诊断事件管理器 | |
Det | Default Error Tracer 默认错误跟踪器 |
DID | Data Identifier 数据标识符 |
Diagnostic Log and Trace 诊断日志和跟踪 | |
Diagnostic Trouble Code 诊断故障代码 | |
DTR | Diagnostic Test Result 诊断测试结果 |
OBD Term: Driving Cycle (OBD Term) OBD术语:驾驶循环(OBD术语) | |
ECU | Electronic Control Unit 电子控制单元 |
Electronic Control Unit Manager 电子控制单元管理 | |
Fault Detection Counter 故障检测计数器 | |
Fim | Function Inhibition Manager 功能抑制管理器 |
Failure Mode Indicator (SAE J1939) 故障模式指示器 (SAE J1939) | |
FTB | Failure Type Byte 故障类型字节 |
HW | Hardware 硬件 |
ID | Identification/Identifier 标识/标识符 |
International Standardization Organization 国际标准化组织 | |
In Use Monitoring Performance Ratio (OBD Term) 在用监控性能比(OBD术语) | |
SAEJ1939 Diagnostic Communication Manager SAEJ1939 诊断通信管理器 | |
MIL | Malfunction Indicator Light (SAE J1979) or Lamp (SAE J1939) 故障指示灯 (SAE J1979) 或指示灯 (SAE J1939) |
NVRAM | Non volatile RAM 非易失性RAM |
On-Board-Diagnostics 车载诊断 | |
OC | Occurrence Count (SAE J1939) 出现次数 (SAE J1939) |
OEM | Original Equipment Manufacturer (Automotive Manufacturer) 原始设备制造商(汽车制造商) |
Operating System 操作系统 | |
PID | Parameter Identification (SAE J1587 or SAE J1979) 参数标识符(SAE J1587或SAE J1979) |
PTO | Power Take Off 动力输出 |
RAM | Random Access Memory 随机存取存储器 |
Read-only Memory 只读存储器 | |
Runtime Environment 运行环境 | |
SPN | Suspect Parameter Number (SAE J1939) 可疑参数编号 (SAE J1939) |
SSCP | synchronous server call point 同步服务器调用点 |
Software 软件 | |
Unified Diagnostic Services 统一诊断服务 | |
VOBD | Vehicle On-Board-Diagnostic 车载诊断 |
WUC | OBD Term: Warm up cycle (OBD Term) OBD术语:预热周期(OBD术语) |
Warning Indicator Request 警告指示请求 | |
WWH-OBD | World Wide Harmonized On-Board-Diagnostic 全球统一的车载诊断 |
以上摘自《AUTOSAR_SWS_DiagnosticEventManager.pdf (V4.3.0)》。
1.3 CAN Transport Layer:CanTp
前缀 | 描述 |
I- | Relative to AUTOSAR COM Interaction Layer 相对于AUTOSAR COM交互层 |
L- | Relative to the CAN Interface module which is equivalent to the Logical Link Control (the upper part of the Data Link Layer – the lower part is called Media Access Control) 相对于相当于逻辑链路控制的CAN接口模块(数据链路层的上半部分-下半部分称为媒体访问控制) |
N- | Relative to the CAN Transport Layer which is equivalent to the OSI Network Layer. 相对于相当于OSI网络层的CAN传输层。 |
术语 | 描述 |
CAN L-SDU | This is the SDU of the CAN Interface module. It is similar to CAN N-PDU but from the CAN Interface module point of view. 这是CAN接口模块的SDU。它类似于CAN N-PDU,但从CAN接口模块的角度来看。 |
CAN LSduId | This is the unique identifier of a SDU within the CAN Interface. It is used for referencing L-SDU’s routing properties. Consequently, in order to interact with the CAN Interface through its API, an upper layer uses CAN LSduId to refer to a CAN L-SDU Info Structure. 这是CAN接口内SDU的唯一标识符。它用于引用L-SDU的路由属性。 因此,为了通过其API与CAN接口交互,上层使用CAN LSduId来引用CAN L-SDU信息结构。 |
CAN N-PDU | This is the PDU of the CAN Transport Layer. It contains a unique identifier, data length and data (protocol control information plus the whole N-SDU or a part of it). 这是CAN传输层的PDU。它包含唯一标识符、数据长度和数据(协议控制信息加上整个 N-SDU或其一部分)。 |
CAN N-SDU | This is the SDU of the CAN Transport Layer. In the AUTOSAR architecture, it is a set of data coming from the PDU Router. 这是CAN传输层的SDU。在AUTOSAR架构中,它是一组来自PDU路由器的数据。 |
CAN N-SDU Info Structure | This is a CAN Transport Layer internal constant structure that contains specific CAN Transport Layer information to process transmission, reception, segmentation and reassembly of the related CAN N-SDU. 这是一个CAN传输层内部常量结构,包含特定的CAN传输层信息,用于处理相关CAN N-SDU的发送、接收、分段和重组。 |
CAN NSduId | Unique SDU identifier within the CAN Transport Layer. It is used to reference N- SDU’s routing properties. Consequently, to interact with the CAN Transport Layer via its API, an upper layer uses CAN NSduId to refer to a CAN N-SDU Info Structure. CAN传输层内的唯一SDU标识符。它用于引用N-SDU的路由属性。 因此,为了通过其API与CAN传输层交互,上层使用CAN NSduId来引用CAN N-SDU信息结构。 |
I-PDU | This is the PDU of the AUTOSAR COM module. 这是AUTOSAR COM模块的PDU。 |
PDU | In layered systems, it refers to a data unit that is specified in the protocol of a given layer. This contains user data of that layer (SDU) plus possible protocol control information. Furthermore, the PDU of layer X is the SDU of its lower layer X-1 (i.e. (X)-PDU = (X-1)-SDU). 在分层系统中,它是指在给定层的协议中指定的数据单元。这包含该层 (SDU) 的用户数据以及可能的协议控制信息。 此外,X层的PDU是其下层X-1的SDU(即 (X)-PDU = (X-1)-SDU)。 |
PduInfoType | This type refers to a structure used to store basic information to process the transmission\reception of a PDU (or a SDU), namely a pointer to its payload in RAM and the corresponding length (in bytes). 这种类型是指用于存储处理PDU(或SDU)发送/接收基本信息的结构,即指向其在RAM中的有效载荷和相应长度(以字节为单位)的指针。 |
SDU | In layered systems, this refers to a set of data that is sent by a user of the services of a given layer, and is transmitted to a peer service user, whilst remaining semantically unchanged. 在分层系统中,这指的是由给定层的服务的用户发送并发送给对等服务用户的一组数据,同时在语义上保持不变。 |
缩写 | 描述 |
BS | Block Size 块大小 |
Can | CAN Driver module CAN驱动模块 |
CAN CF | CAN Consecutive Frame N-PDU CAN连续帧N-PDU |
CAN FC | CAN Flow Control N-PDU CAN流控制N-PDU |
CAN FF | CAN First Frame N-PDU CAN首帧N-PDU |
CAN SF | CAN Single Frame N-PDU CAN单帧N-PDU |
CanIf | CAN Interface CAN接口 |
CanTp | CAN Transport Layer CAN传输层 |
CanTrcv | CAN Transceiver module CAN收发器模块 |
CF | See “CAN CF” |
Com | AUTOSAR COM module |
Dcm | Diagnostic Communication Manager module 诊断通信管理器模块 |
DEM | Diagnostic Event Manager 诊断事件管理器 |
DET | Default Error Tracer 默认错误跟踪器 |
DLC | Data Length Code (part of CAN PDU that describes the SDU length) 数据长度代码(描述SDU长度的CAN PDU的一部分) |
FC | See “CAN FC” |
FF | See “CAN FF” |
FIM | Function Inhibition Manager 功能抑制管理器 |
Mtype | Message Type (possible value: diagnostics, remote diagnostics) 消息类型(可能的值:诊断、远程诊断) |
N_AI | Network Address Information (see ISO 15765-2). 网络地址信息(见 ISO 15765-2)。 |
N_Ar | Time for transmission of the CAN frame (any N-PDU) on the receiver side (see ISO 15765-2). 在接收端发送CAN帧(任何 N-PDU)的时间(见 ISO 15765-2)。 |
N_As | Time for transmission of the CAN frame (any N-PDU) on the sender side (see ISO 15765-2). 在发送方发送CAN帧(任何 N-PDU)的时间(参见 ISO 15765-2)。 |
N_Br | Time until transmission of the next flow control N-PDU (see ISO 15765-2). 直到发送下一个流控制N-PDU的时间(参见 ISO 15765-2)。 |
N_Bs | Time until reception of the next flow control N-PDU (see ISO 15765-2). 接收下一个流控制N-PDU之前的时间(参见 ISO 15765-2)。 |
N_Cr | Time until reception of the next consecutive frame N-PDU (see ISO 15765-2). 接收下一个连续帧N-PDU之前的时间(见 ISO 15765-2)。 |
N_Cs | Time until transmission of the next consecutive frame N-PDU (see ISO 15765-2). 发送下一个连续帧N-PDU之前的时间(参见 ISO 15765-2)。 |
N_Data | Data information of the transport layer 传输层数据信息 |
N_PCI | Protocol Control Information of the transport layer 传输层协议控制信息 |
N_SA | Network Source Address (see ISO 15765-2). 网络源地址(见 ISO 15765-2)。 |
N_TA | Network Target Address (see ISO 15765-2). It might already contain the N_TAtype(physical/function) in case of ExtendedAddressing. 网络目标地址(见 ISO 15765-2)。在ExtendedAddressing的情况下,它可能已经包含 N_TAtype(physical/function)。 |
N_TAtype | Network Target Address type (see ISO 15765-2). 网络目标地址类型(参见 ISO 15765-2)。 |
OBD | On-Board Diagnostic 车载诊断 |
PDU | Protocol Data Unit 协议数据单元 |
PduR | PDU Router PDU路由器 |
SDU | Service Data Unit 服务数据单元 |
FS | Flow Status 流状态 |
CAN FD | CAN flexible data rate CAN灵活数据速率 |
CAN_DL | CAN frame data length CAN 帧数据长度 |
TX_DL | Transmit data link layer data length 发送数据链路层数据长度 |
RX_DL | Received data link layer data length 接收数据链路层数据长度 |
SF_DL | SingleFrame data length in bytes 单帧数据长度(以字节为单位) |
定义 | 描述 |
Default Error Tracer 默认错误跟踪器 | The Default Error Tracer is merely a support to SW development and integration and is not contained in the production code.The API is defined, but the functionality can be chosen and implemented by the developer according to his specific needs. Default Error Tracer只是对软件开发和集成的支持,不包含在生产代码中。API已定义,但功能可由开发人员根据其特定需求选择和实现。 |
Diagnostic Event Manager 诊断事件管理器 | The Diagnostic Event Manager is a standard AUTOSAR module which is available in the production code and whose functionality is specified in the AUTOSAR project. 诊断事件管理器是一个标准的AUTOSAR模块,可在生产代码中使用,其功能在AUTOSAR项目中指定。 |
Extended addressing format 扩展寻址格式 | A unique CAN identifier is assigned to each combination of N_SA and Mtype.A unique address is filed to each combination of N_TA and N_TAtype in the first data byte of the CAN frame data field.N_PCI and N_Data are filed in the remaining bytes of the CAN frame data field. 为N_SA和Mtype的每个组合分配一个唯一的CAN标识符。CAN帧数据字段的第一个数据字节中的每个N_TA和N_TAtype组合都有一个唯一的地址。N_PCI和N_Data位于CAN帧数据字段的剩余字节中。 |
Full-duplex 全双工 | Point-to-point communication between two nodes is possible in both directions at any one time. 两个节点之间的点对点通信在任何时候都可以在两个方向进行。 |
Function Inhibition Manager 功能抑制管理器 | The Function Inhibition Manager (FIM) stands for the evaluation and assignment of events to the required actions for Software Components (e.g. inhibition of specific “monitoring functions”). The DEM informs and updates the Function Inhibition Manager (FIM) upon changes of the event status in order to stop or release functional entities according to assigned dependencies. An interface to the functional entities is defined and supported by the Mode Manager. The FIM is not part of the DEM. 功能抑制管理器 (FIM) 代表评估和分配事件到软件组件所需的操作(例如,抑制特定的“监控功能”)。DEM 在事件状态发生变化时通知并更新功能抑制管理器 (FIM),以便根据分配的相关性停止或释放功能实体。功能实体的接口由模式管理器定义和支持。FIM 不是 DEM 的一部分。 |
Functional addressing 功能寻址 | In the transport layer, functional addressing refers to N-SDU, of which parameter N_TAtype (which is an extension to the N_TA parameter [14] used to encode the communication model) has the value functional. This means the N-SDU is used in 1 to n communications. Thus with the CAN protocol, functional addressing will only be supported for Single Frame communication. In terms of application, functional addressing is used by the external (or internal) tester if it does not know the physical address of an ECU that should respond to a service request or if the functionality of the ECU is implemented as a distributed server over several ECUs. When functional addressing is used, the communication is a communication broadcast from the external tester to one or more ECUs (1 to n communication). Use cases are (for example) broadcasting messages, such as “ECUReset” or “CommunicationControl” OBD communication will always be performed as part of functional addressing. 在传输层,功能寻址是指N-SDU,其中参数N_TAtype(这是对用于编码通信模型的N_TA参数 [14] 的扩展)的值为function。 这意味着N-SDU用于1到n次通信。因此,对于CAN协议,功能寻址将仅支持单帧通信。 在应用方面,如果外部(或内部)测试人员不知道应响应服务请求的ECU的物理地址,则使用功能寻址或者如果 ECU 的功能作为分布式服务器在多个ECU上实现。当使用功能寻址时,通信是从外部测试仪到一个或多个ECU的通信广播(1到n通信)。 用例是(例如)广播消息,例如“ECUReset”或“CommunicationControl” OBD通信将始终作为功能寻址的一部分执行。 |
Half-duplex 半双工 | Point-to-point communication between two nodes is only possible in one direction at a time. 两个节点之间的点对点通信一次只能在一个方向上进行。 |
Mixed addressing format 混合寻址格式 | A unique CAN identifier is assigned to each combination of N_SA, N_TA, N_TAtype. N_AE is placed in the first data byte of the CAN frame data field. N_PCI and N_Data are placed in the remaining bytes of the CAN frame data field. 唯一的CAN标识符被分配给N_SA、N_TA、N_TAtype的每个组合。N_AE放置在CAN帧数据字段的第一个数据字节中。N_PCI和N_Data放置在CAN帧数据字段的剩余字节中。 |
Multiple connection 多重连接 | The CAN Transport Layer should manage several transport protocol communication sessions at a time. CAN 传输层应一次管理多个传输协议通信会话。 |
Normal addressing format 正常寻址格式 | A unique CAN identifier is assigned to each combination of N_SA, N_TA, N_TAtype and Mtype. N_PCI and N_Data are filed in the CAN frame data field. 唯一的CAN标识符被分配给N_SA、N_TA、N_TAtype和Mtype的每个组合。N_PCI和N_Data位于CAN帧数据字段中。 |
Physical addressing 物理寻址 | In the transport layer, physical addressing refers to N-SDU, of which parameter N_TAtype (which is an extension of the N_TA parameter [14] used to encode the communication model) has the value physical. This means the N-SDU is used in 1 to 1 communication, thus physical addressing will be supported for all types of network layer messages. In terms of application, physical addressing is used by the external (or internal) tester if it knows the physical address of an ECU that should respond to a service request. When physical addressing is used, a point to point communication takes place (1 to 1 communication). Use cases are (for example) messages, such as “ReadDataByIdentifier” or “InputOutputControlByIdentifier” 在传输层,物理寻址指的是N-SDU,其中参数N_TAtype(这是用于对通信模型进行编码的 N_TA参数[14]的扩展)的值为physical。 这意味着N-SDU用于一对一通信,因此所有类型的网络层消息都将支持物理寻址。 在应用方面,如果外部(或内部)测试人员知道应响应服务请求的ECU的物理地址,则物理寻址将被使用。使用物理寻址时,会发生点对点通信(1对1通信)。 用例是(例如)消息,例如“ReadDataByIdentifier”或“InputOutputControlByIdentifier” |
Single connection 单连接 | The CAN Transport Layer will only manage one transport protocol communication session at a time. CAN传输层一次仅管理一个传输协议通信会话。 |
Connection channel 连接通道 | The CAN Transport Layer is handling resources used by multiple connections in order to save RAM.When a connection becames active,the channel that is used by this connection will be unavailable for other connections. CAN传输层正在处理多个连接使用的资源以节省RAM。当连接变为活动状态时,此连接使用的通道将不可用于其他连接。 |
Connection 连接 | A transport protocol session, either is a transmission or a reception session on a N- SDU. 传输协议会话可以是N-SDU上的发送会话或接收会话。 |
以上摘自《AUTOSAR_SWS_CANTransportLayer.pdf (V4.3.0)》。
2 XCP测量标定篇
2.1 Universal Calibration Protocol:XCP
缩写 | 描述 |
AUTOSAR | AUTomotive Open System Architecture 汽车开放系统架构 |
A2L | File Extension for an ASAM 2MC Language File ASAM 2MC语言文件的文件扩展名 |
ASAM | Association for Standardization of Automation and Measuring Systems 自动化和测量系统标准化协会 |
BSW | Basic Software 基础软件 |
CAN | Controller Area Network 控制器局域网 |
CanIf | CAN Interface CAN接口 |
CTO | Command Transfer Object 命令传输对象 |
DAQ | Data AcQuisition, Data AcQuisition Packet 数据采集,数据采集包 |
DTO | Data Transfer Object 数据传输对象 |
ECU | Electronic Control Unit 电子控制单元 |
FrIf | FlexRay Interface FlexRay接口 |
LPDU | Data Link Layer PDU 数据链路层PDU |
MCD | Measurement Calibration and Diagnostics 测量校准和诊断 |
MISRA | Motor Industry Software Reliability Association 汽车工业软件可靠性协会 |
ODT | Object Descriptor Table 对象描述符表 |
PDU | Protocol Data Unit 协议数据单元 |
RAM | Random Access Memory 随机存取存储器 |
ROM | Read Only Memory 只读存储器 |
SchM | Schedule Manager 调度管理器 |
SVN | Subversion |
SRS | Software Requirements Specification 软件需求规范 |
STIM | Data Stimulation packet 数据刺激包 |
SW | Software 软件 |
SWS | Software Specification 软件规范 |
TCP/IP | Transfer Control Protocol / Internet Protocol 传输控制协议/互联网协议 |
TS | Time Stamp 时间戳 |
UDP/IP | User Datagram Protocol / Internet Protocol 用户数据报协议/互联网协议 |
URL | Uniform Resource Locator 统一资源定位器 |
XCP | Universal Calibration Protocol 通用标定协议 |
XML | Extensible Markup Language 可扩展标记语言 |
ISR | Interrupt Service Routine 中断服务程序 |
DET | Default Error Tracer (AUTOSAR BSW module) 默认错误跟踪器(AUTOSAR BSW模块) |
以上摘自《AUTOSAR_SWS_XCP.pdf (V4.3.0)》。
3 CAN通信篇
3.1 COM Manager:ComM
缩写 | 描述 |
BSW | Basic Software 基础软件 |
BswM | Basic Software Mode Manager 基础软件模式管理器 |
ComM | Communication Manager 通讯管理 |
DCM | Diagnostic Communication Manager 诊断通信管理器 |
Det | Default Error Tracer 默认错误跟踪器 |
EcuM | ECU State Manager module ECU状态管理器模块 |
I-PDU | Information Protocol Data Unit 信息协议数据单元 |
NM | Network Management 网络管理 |
PDU | Protocol Data Unit 协议数据单元 |
VMM | Vehicle Message Matrix 车辆信息矩阵 |
术语 | 描述 |
DCM_ActiveDiagnostic indication | The DCM module indicates an active diagnostic session. DCM need “full communication” = COMM_FULL_COMMUNICATION for diagnostic purpose DCM 模块指示一个激活的诊断会话。DCM 需要“full communication” = COMM_FULL_COMMUNICATION用于诊断目的 |
Active wake-up 主动唤醒 | Wake-up caused by the hosting ECU e.g. by a sensor. 由主机 ECU 引起的唤醒,例如 通过传感器。 |
Application signal scheduling 应用信号调度 | Sending of application signals according to the VMM. Scheduling of CAN application signals is performed by the Communication Module, scheduling of LIN application I-PDUs (a PDU containing signals) is performed by the LIN interface and scheduling of FlexRay application PDUs is performed by the FlexRay Interface module. 根据VMM发送应用信号。CAN应用信号的调度由通信模块执行,LIN 应用I-PDU(包含信号的 PDU)的调度由LIN接口执行,FlexRay应用PDU的调度由FlexRay接口模块执行。 |
Bus sleep 总线休眠 | No activity required on the communication bus (e.g. CAN bus sleep). 通信总线上无需活动(例如CAN总线休眠)。 |
Bus communication messages 总线通信消息 | Bus communication messages are all messages that are sent on the communication bus. This can be either a diagnostic message or an application message. 总线通信消息是在通信总线上发送的所有消息。这可以是诊断消息或应用程序消息。 |
COM Inhibition status COM 抑制状态 | Defines whether full communication, silent communication or wakeup is allowed or not. 定义是否允许完全通信、静默通信或唤醒。 |
Communication Channel 通讯通道 | The medium used to convey information from a sender (or transmitter) to a receiver. 用于将信息从发送方(或发射器)传送到接收方的媒介。 |
Communication Mode 通讯方式 | Mode determining which kind of communication are allowed: “full communication” = COMM_FULL_COMMUNICATION “no communication” = COMM_NO_COMMUNICATION “silent communication” = COMM_SILENT_COMMUNICATION Note: COMM_SILENT_COMMUNICATION can not be requested by a user. Internal mode for synchronizing network at shutdown 确定允许哪种通信的模式: “full communication” = COMM_FULL_COMMUNICATION “no communication” = COMM_NO_COMMUNICATION “silent communication” = COMM_SILENT_COMMUNICATION 注意:用户不能请求 COMM_SILENT_COMMUNICATION。 关闭时同步网络的内部模式 |
Diagnostic PDU scheduling 诊断 PDU 调度 | Sending of diagnostic PDUs. Scheduling of CAN diagnostic PDUs is performed by the diagnostic module, scheduling of LIN diagnostic PDUs is performed by the diagnostic module and the LIN interface and scheduling of FlexRay diagnostic PDUs is performed by the diagnostic module and the FlexRay Interface module. 发送诊断PDU。CAN诊断PDU的调度由诊断模块执行,LIN诊断PDU的调度由诊断模块和LIN接口执行,FlexRay诊断PDU的调度由诊断模块和FlexRay接口模块执行。 |
ECU shut down ECU关闭 | See ECU State Manager specification [6]. 请参阅ECU状态管理器规范 [6]。 |
Fan-out 扇出 | Same message/indication are sent to multiple destinations/receivers 相同的消息/指示被发送到多个目的地/接收者 |
Independent software component 独立软件组件 | A separately developed software component performing a coherent set of functions with a minimum amount of interfaces to other software applications on an ECU.This can be e.g. a basic software component or an application software component. 一个单独开发的软件组件,执行一组连贯的功能,与ECU上的其他软件应用程序的接口数量最少。这可以是例如 基础软件组件或应用软件组件。 |
Passive wake-up 被动唤醒 | Wake-up by another ECU and propagated (e.g. by bus or wake-up-line) to the ECU currently in focus. 由另一个ECU唤醒并传播(例如总线或叫唤醒线)到当前聚焦的ECU。 |
System User 系统用户 | An administration functionality (a specific "user", which is generated within the internal context of the ComM) for making a default request and for overriding the user requests. 用于发出默认请求和覆盖用户请求的管理功能(在 ComM 的内部上下文中生成的特定“用户”)。 |
User 用户 | Concept for requestors of the ECU State Manager module and of the Communication Manager Module. A user may be the BswM,a runnable entity,a SW-C or a group of SW-Cs,which act as a single unit towards the ECU State Manager module and the Communication Manager Module. ECU状态管理器模块和通信管理器模块的请求者的概念。一个用户可以是 BswM、一个可运行的实体、一个SW-C或一组SW-C,它们作为一个单独的单元用于ECU状态管理器模块和通信管理器模块。 |
User Request 用户请求 | A User can request different Communication Modes from ComM 用户可以从ComM请求不同的通信模式 |
以上摘自《AUTOSAR_SWS_COMManager.pdf (V4.3.0)》。
3.2 CAN Network Management:CanNm
缩写 | 描述 |
CanIf | Abbreviation for the CAN Interface CAN接口(CanIf)的缩写 |
CanNm | Abbreviation for CAN Network Management CAN网络管理的缩写 |
CBV | Control Bit Vector 控制位向量 |
CWU | Car Wakeup 汽车唤醒 |
ERA | External Request Array 外部请求数组 |
EIRA | External and Internal Request Array 外部和内部请求数组 |
NM | Network Management 网络管理 |
PNC | Partial Network Cluster 部分网络集群/簇 |
PNI | Partial Network Information 部分网络信息 |
术语 | 描述 |
“PDU transmission ability is disabled” PDU发送能力被禁用 | This means that the Network Management PDU transmission has been disabled by the service CanNm_DisableCommunication. 这意味着网络管理PDU发送已被CanNm_DisableCommunication服务禁用。 |
“Repeat Message Request Bit Indication” 重复消息请求位指示 | CanNm_RxIndication finds the RptMsgRequest set in the Control Bit Vector of a received Network Management PDU. CanNm_RxIndication在收到的网络管理PDU的控制位向量中找到设置的RptMsgRequest。 |
“PN filter mask” PN过滤掩码 | Vector of filter mask bytes defined by configuration container(s) CanNmPnFilterMaskByte 由配置容器CanNmPnFilterMaskByte定义的过滤器掩码字节向量 |
以上摘自《AUTOSAR_SWS_CANNetworkManagement.pdf (V4.3.0)》。
3.3 CAN State Manager:CanSM
缩写 | 描述 |
API | Application Program Interface 应用程序接口 |
BSW | Basic Software 基础软件 |
CAN | Controller Area Network 控制器局域网 |
CanIf | CAN Interface CAN接口 |
CanSM | CAN State Manager CAN状态管理器 |
ComM | Communication Manager 通讯管理器 |
DEM | Diagnostic Event Manager 诊断事件管理器 |
DET | Default Error Tracer 默认错误跟踪器 |
EcuM | ECU State Manager ECU状态管理器 |
PDU | Protocol Data Unit 协议数据单元 |
RX | Receive 收到 |
TX | Transmit 发送 |
SchM | BSW Scheduler BSW调度器 |
SWC | Software Component 软件组件 |
BswM | Basic Software Mode Manager 基础软件模式管理器 |
以上摘自《AUTOSAR_SWS_CANStateManager.pdf (V4.3.0)》。
3.4 Network Management Interface:NM
缩写 | 描述 |
CanIf | CAN Interface module CAN接口模块 |
CanNm | CAN Network Management module CAN网络管理模块 |
CC | Communication controller 通讯控制器 |
ComM | Communication Manager module 通讯管理器模块 |
EcuM | ECU State Manager module ECU状态管理器模块 |
DEM | Diagnostic Event Manager module 诊断事件管理器模块 |
Nm | Generic Network Management Interface module, this ist the abreviation used for this module throughout this specification 通用网络管理接口模块,这是整个规范中用于该模块的缩写 |
NM | Network Management 网络管理 |
OEM | Original Equipment Manufacturer 原始设备制造商 |
CBV | Control Bit Vector in NM-message NM消息中的控制位向量 |
术语 | 描述 |
Bus-Sleep Mode | Network mode where all interconnected communication controllers are in the sleep mode. 网络模式,其中所有互连的通信控制器都处于休眠模式。 |
NM-Channel | Logical channel associated with the NM-cluster 与NM-cluster关联的逻辑通道 |
NM-Cluster | Set of NM nodes coordinated with the use of the NM algorithm. 与使用NM算法协调的一组NM节点。 |
NM-Coordinator | A functionality of the Nm which allows coordination of network sleep for multiple NM Channels. Nm的一项功能,允许协调多个NM通道的网络休眠。 |
NM-Message | Packet of information exchanged for purposes of the NM algorithm. 为NM算法而交换的信息包。 |
NM-Timeout | Timeout in the NM algorithm that initiates transition into Bus-Sleep Mode. 启动转换到总线休眠模式的NM算法中的超时 |
NM User Data | Supplementary application specific piece of data that is attached to every NM message sent on the bus. 附加到总线上发送的每个NM消息的补充应用程序特定数据。 |
Node Identifier | Node address information exchanged for purposes of the NM algorithm. 为NM算法目的而交换的节点地址信息。 |
Node Identifier List | List of Node Identifiers recognized by the NM algorithm. 通过NM算法已识别的节点标识符列表 |
Bus | Physical communication medium to which a NM node/ecu is connected to. NM节点/ecu连接到的物理通信介质。 |
network | Entity of all NM nodes/ecus which are connected to the same bus. 连接到同一总线的所有NM节点/ecus的实体。 |
channel | Logical bus to which the NM node/ecu is connected to. NM节点/ecu连接到的逻辑总线。 |
Coordinated shutdown | Shutdown of two or more busses in a way that their shutdown is finished coinciding. 关闭两个或多个总线,它们的关闭同时完成。 |
Coordination algorithm | Initiation of coordinated shutdown in case all conditions are met. 在满足所有条件的情况下启动协调关闭。 |
以上摘自《AUTOSAR_SWS_NetworkManagementInterface.pdf (V4.3.0)》。
3.5 COM
缩写 | 描述 |
AUTOSAR COM | The AUTOSAR COM module is derived from [17]. For details, see Chapter 7.2.1. AUTOSAR COM模块源自[17]。详情请参见第7.2.1章。 |
DM | Deadline Monitoring, for details see Chapter 7.3.6 超时监控,详见第7.3.6章 |
I-PDU | Interaction Layer Protocol Data Unit An I-PDU carries signals. It is defined in [17]. 交互层协议数据单元 I-PDU 承载信号。它在[17]中定义。 |
L-PDU | Data Link Layer Protocol Data Unit. In AUTOSAR, the Data Link Layer is equivalent to the Communication Hardware Abstraction and Microcontroller Abstraction Layer. 数据链路层协议数据单元。在AUTOSAR中,数据链路层相当于通信硬件抽象和微控制器抽象层。 |
MDT | A detailed description of the Minimum Delay Timer (MDT) can be found in [17]. See also Chapter 7.3.5.5. 可以在 [17] 中找到最小延迟定时器(MDT)的详细说明。另见第7.3.5.5章。 |
PDU Router | The PDU Router is a module transferring I-PDUs from one module to another module. The PDU Router can be utilized for gateway operations and for internal routing purposes. PDU路由器是一个将I-PDU从一个模块传输到另一个模块的模块。PDU路由器可用于网关操作和内部路由目的。 |
SDU | Service Data Unit For a description see [1] Chapter 4. 服务数据单元 有关说明,请参阅[1]第4章。 |
TM | Transmission Mode 发送方式 |
TMC | Transmission Mode Condition, see Chapter 7.3.3.2 发送模式条件,见第7.3.3.2章 |
TMS | Transmission Mode Selector, see Chapter 7.3.3.2 发送模式选择器,见第7.3.3.2章 |
术语 | 描述 |
Confirmation 确认 | With a Confirmation, the PDU Router reports that a request by the AUTOSAR COM module has been completed successfully. It is a reaction to a request of COM. E.g. when a PDU has been successfully transmitted. 通过确认,PDU路由器报告AUTOSAR COM模块的请求已成功完成。它是对COM请求的反应。例如。当PDU成功发送时。 |
Data Invalid Value 数据无效值 | Value sent by the AUTOSAR COM module to indicate that the sender side AUTOSAR Software Component is not able to provide a valid value. AUTOSAR COM模块发送的值,用于指示发送方AUTOSAR软件组件无法提供有效值。 |
Dynamic Length Signal 动态长度信号 | A dynamic length signal is a signal which length can vary at run-time. 动态长度信号是长度可以在运行时变化的信号。 |
Dynamic Length I-PDU 动态长度 I-PDU | A dynamic length I-PDU is an I-PDU containing a dynamic length signal. It length varies depending on the length of the included dynamic length signal. 动态长度I-PDU是包含动态长度信号的I-PDU。它的长度取决于包含的动态长度信号的长度。 |
Group signal 组信号 | A group signal is a signal that is contained in a signal group. 组信号是包含在信号组中的信号。 |
Indication 指示 | An Indication is asynchronous information from PDU Router to COM, e.g. to acknowledge that something has been received. 指示是从PDU路由器到COM的异步信息,例如,承认已经收到某物。 |
Init Value 初始值 | I-PDUs and signals are set to the Init Value by the AUTOSAR COM module after start-up. This value is used until it is overwritten. I-PDU和信号在启动后由AUTOSAR COM模块设置为初始值。该值将一直使用,直到被覆盖。 |
I-PDU group I-PDU组 | An I-PDU Group is an arbitrary collection of I-PDUs of the same direction (i.e. send or receive) in the COM module. I-PDU组是COM模块中相同方向(即发送或接收)的I-PDU的任意集合。 |
Inter-ECU-communication ECU间通讯 | Communication between two or more ECUs for example via a CAN network 两个或多个ECU之间的通信,例如通过CAN网络 |
Intra-ECU-communication ECU内部通信 | Communication between Software components that reside on the same ECU 驻留在同一ECU上的软件组件之间的通信 |
Large Signal 大信号 | A large signal is a signal that is too large to fit into a single L-PDU of the underlying communication protocol. 大信号是太大而无法放入底层通信协议的单个L-PDU的信号。 |
Large I-PDU 大型 I-PDU | Large I-PDU are I-PDU that do not fit into a single L-PDU of the underlying communication protocol. Large I-PDU will be transmitted via TP. 大型I-PDU是不适合底层通信协议的单个L-PDU的I-PDU。大型I-PDU将通过TP发送。 |
Message 信息 | [17] uses always the synonym message. In AUTOSAR, message is replaced by signal but with the same meaning. [17]始终使用同义词消息。在AUTOSAR中,消息被信号替换,但具有相同的含义。 |
Metadata 元数据 | For some I-PDUs, e.g. J1939 I-PDUs, the payload is extended with additional metadata containing for example the CAN-ID. 对于一些I-PDU,例如J1939 I-PDU,有效载荷扩展了额外的元数据,例如包含CAN-ID。 |
Notification 通知 | Information by the AUTOSAR COM module to RTE, e.g. when new data is available, an error occurred. AUTOSAR COM模块到RTE的信息,例如,当新数据可用时,发生错误。 |
Signal 信号 | A signal in the AUTOSAR COM module’s context is equal to a message in [17]; see also [7]. AUTOSAR COM模块上下文中的信号等同于[17]中的消息;另见[7]。 |
Signal group 信号组 | In AUTOSAR, so called complex data types are used. Inside a complex data type, there are one or more data elements (primitive data types), like in a C struct. The data consistency of such complex data types must be ensured. The RTE decomposes the complex data type in single signals and sends them to the AUTOSAR COM module. As these signals altogether need to be treated consistently, they are called signal group. See also [7]. 在AUTOSAR中,使用了所谓的复杂数据类型。在复杂数据类型中,有一个或多个数据元素(原始数据类型),就像在C结构中一样。必须保证这种复杂数据类型的数据一致性。 RTE将复杂数据类型分解为单个信号并将它们发送到AUTOSAR COM模块。由于这些信号需要统一处理,因此称为信号组。 另见[7]。 |
Update-bit 更新位 | A mechanism supported by the AUTOSAR COM module with that the receiver of a signal/signal group could identify whether the sender has updated the data in this signal/signal group before sending. See Chapter 7.8. AUTOSAR COM模块支持的一种机制,信号/信号组的接收方可以在发送之前确定发送方是否更新了该信号/信号组中的数据。见第7.8章。 |
以上摘自《AUTOSAR_SWS_COM.pdf (V4.3.0)》。
3.6 IPDU Multiplexer:IpduM
术语 | 描述 |
COM I-PDU | I-PDU assembled in the COM module out of COM Signals I-PDU组装在COM模块中的COM信号 |
contained I-PDU | I-PDU assembled into or extracted from a Container PDU I-PDU组装到容器PDU中或从容器PDU中提取 |
Container PDU 容器PDU | PDU containing I-PDUs and headers 包含I-PDU和报头的PDU |
dynamic part 动态部分 | see [4] |
instance of an I-PDU I-PDU 的实例 | IpduM I-PDU with one specific layout and content 具有一种特定布局和内容的IpduM I-PDU |
Instances of a Container 容器实例 | Instances of the same Container PDU 相同Container PDU的实例 |
IpduM | I-PDU Multiplexer I-PDU多路复用器 |
IpduM I-PDU | I-PDU assembled in the IpduM module out of two COM I-PDUs I-PDU由两个COM I-PDU组装在IpduM模块中 |
multiplexed I-PDU 多路I-PDU | see IpduM I-PDU |
Segment 段 | The static or dynamic part may consist of more than one piece. These pieces are called segments. See also Chapter 7.2.1 and Figure 3. 静态或动态部分可能由不止一件组成。这些片段称为段。另请参阅第7.2.1章和图3。 |
selector field 选择器字段 | see [4] |
Signal 信号 | see [5] |
signal group 信号组 | see [5] |
static part 静态部分 | see [4] |
以上摘自《AUTOSAR_SWS_IPDUMultiplexer.pdf (V4.3.0)》。
3.7 PDU Router:PduR
术语 | 描述 |
Upper Layer Modules (Up) 上层模块(Up) | Modules above the PDU Router. This layer usually includes COM and Diagnostic Communication Manager (DCM). The upper layer modules are configured in the configuration. PDU路由器上方的模块。该层通常包括COM和诊断通信管理器 (DCM)。上层模块在配置中配置。 |
Lower Layer Modules (Lo) 下层模块 (Lo) | Modules below the PDU Router. This layer may include CAN, LIN, FlexRay,Ethernet communication interface modules and the respective TP modules. Modules used are configured in the configuration PDU路由器下方的模块。该层可能包括CAN、LIN、FlexRay、以太网通信接口模块和相应的TP模块。使用的模块在配置中配置 |
PDU Router PDU路由器 | Module that transfers I-PDUs from one module to another module. The PDU Router module can be utilized for gateway operations and for internal routing purposes. 将I-PDU从一个模块发送到另一个模块的模块。PDU路由器模块可用于网关操作和内部路由目的。 |
gatewaying-on-the-fly 即时网关 | Gateway capability; routing between two TP modules where forwarding of data is started (when a specified threshold is reached) before all data have been received. If larger amount of data is transported between two interfaces it is desirable to be able to start the transmission on the destination network before receiving all data from the source network. This saves memory and time. 网关能力;两个TP模块之间的路由,其中在接收到所有数据之前开始数据转发(达到指定阈值时)。如果在两个接口之间传输大量数据,则希望能够在接收来自源网络的所有数据之前在目标网络上开始发送。这样可以节省内存和时间。 |
multicast operation 组播操作 | Simultaneous transmission of PDUs to a group of receivers, i.e. 1:n routing. 将PDU同时发送到一组接收器,即 1:n 路由。 |
data provision 数据提供 | Provision of data to interface modules.
向接口模块提供数据。 (a) 直接数据提供:要发送的数据直接在发送请求时提供。目标通信接口可以以两种方式运行,直接复制数据或将复制推迟到触发发送。 (b) 触发发送数据提供:发送请求中不提供要发送的数据,而是由接口模块通过回调函数检索 |
last-is-best buffering | Buffering strategy where the latest value overwrites the last value. 最新值覆盖最后一个值的缓冲策略。 |
FIFO buffering 先进先出缓冲 | Buffer concept, which uses first in first out strategy. 缓冲区概念,采用先进先出策略。 |
缩写 | 描述 |
I-PDU ID | PDU Identifier PDU标识符 |
I-PDU | Interaction Layer PDU. An I-PDU consists of data (buffer), length and I-PDU ID. The PDU router will mainly route I-PDUs (exception is routing-on-the-fly) 交互层PDU。一个I-PDU由数据(缓冲区)、长度和I-PDU ID组成。PDU路由器将主要路由 I-PDU(动态路由除外) |
N-PDU | Network Layer PDU. Used by transport protocol modules to fragment an I-PDU 网络层PDU。由传输协议模块用于对I-PDU进行分段 |
L-PDU | Data Link Layer PDU. One or more I-PDUs are packed into one L-PDU. The L-PDU is bus specific, e.g. CAN frame. 数据链路层PDU。一个或多个I-PDU被打包成一个L-PDU。L-PDU是特定于总线的,例如CAN帧。 |
SF | Single Frame, Transport Protocol term 单帧,传输协议术语 |
FF | First Frame, Transport Protocol term 首帧,传输协议术语 |
CF | Consecutive Frame, Transport Protocol term 连续帧,传输协议术语 |
PDU | Protocol Data Unit 协议数据单元 |
BSW | Basic Software 基础软件 |
<SrcLo> | Lower layer communication interface module acting as a source of the I-PDU. The SrcLo is always one. 低层通信接口模块充当I-PDU的来源。SrcLo始终是一个。 |
<DstLo> | Lower layer communication interface module acting as a destination of the I-PDU. The DstLo may by one to many. 低层通信接口模块充当I-PDU的目的地。DstLo可以一对多。 |
<SrcLoTp> | Lower layer transport protocol module acting as a source of the I-PDU. The SrcLoTp is always one. 低层传输协议模块充当I-PDU的来源。SrcLoTp始终是一个。 |
<DstLoTp> | Lower layer transport protocol module acting as a destination of the I-PDU. The DstLoTp may by one to many. 低层传输协议模块充当I-PDU的目的地。DstLoTp可能是一对多。 |
<Lo> | Lower layer communication interface module 下层通信接口模块 |
<Up> | Upper layer module 上层模块 |
<LoTp> | Lower layer transport protocol module 下层传输协议模块 |
<module> | Any type of module <...> 任何类型的模块<...> |
以上摘自《AUTOSAR_SWS_PDURouter.pdf (V4.3.0)》。
3.8 Time Sync Over CAN:CanTSyn
缩写 | 描述 |
(G)TD | (Global) Time Domain (全局)时域 |
(G)TM | (Global)Time Master (全局)时间主 |
<Bus>TSyn | A bus specific Time Synchronization module 总线特定的时间同步模块 |
CAN | Controller Area Network 控制器局域网 |
CanTSyn | Time Synchronization module for CAN CAN 时间同步模块 |
CRC | Cyclic Redundancy Checksum 循环冗余校验和 |
Debounce Time | Minimum gap between two Tx messages with the same PDU 具有相同PDU的两个Tx消息之间的最小间隙 |
DEM | Diagnostic Event Manager 诊断事件管理器 |
DET | Default Error Tracer 默认错误跟踪器 |
DLC | Data Length Code 数据长度代码 |
FUP message | Follow-Up message 后续消息 |
OFNS message | Offset adjustment message 偏移调整信息 |
OFS message | Offset Synchronization message 偏移同步消息 |
StbM | Synchronized Time-Base Manager 同步时基管理器 |
SYNC message | Time Synchronization message 时间同步消息 |
TG | Time Gateway 时间网关 |
Timesync | Time Synchronization 时间同步 |
TS | Time Slave 时间从机 |
TSD | Time Sub-domain 时间子域 |
以上摘自《AUTOSAR_SWS_TimeSyncOverCAN.pdf (V4.3.0)》。
3.9 CAN Interface:CanIf
缩写 | 描述 |
CAN L-PDU | CAN Protocol Data Unit. Consists of an identifier, Data Length and data (SDU) Visible to the CAN driver. CAN 协议数据单元。由标识符、数据长度和数据(SDU)组成,对CAN驱动程序可见。 |
CAN L-SDU | CAN Service Data Unit. Data that are transported inside the CAN L-PDU. Visible to the upper layers of the CAN interface (e.g. PDU Router). CAN服务数据单元。在CAN L-PDU内传输的数据。对CAN接口的上层可见(例如PDU路由器)。 |
CanDrv | CAN Driver module CAN驱动模块 |
CAN FD | CAN with Flexible Data-Rate 具有灵活数据速率的CAN |
CanId | CAN Identifier CAN标识符 |
CanIf | CAN Interface module CAN接口模块 |
CanNm | CAN Network Management module CAN网络管理模块 |
CanSm | CAN State Manager module CAN状态管理器模块 |
CanTp | CAN Transport Layer module CAN传输层模块 |
CanTrcv | CAN Transceiver Driver module CAN收发器驱动模块 |
CanTSyn | Global Time Synchronization over CAN CAN全球时间同步 |
ComM | Communication Manager module 通讯管理器模块 |
DCM | Diagnostic Communication Manager module 诊断通信管理器模块 |
EcuM | ECU State Manager module ECU状态管理器模块 |
HOH | CAN hardware object handle CAN硬件对象句柄 |
HRH | CAN hardware receive handle CAN硬件接收句柄 |
HTH | CAN hardware transmit handle CAN硬件发送句柄 |
J1939Nm | J1939 Network Management module J1939网络管理模块 |
J1939Tp | J1939 Transport Layer module J1939传输层模块 |
PduR | PDU Router module PDU路由器模块 |
PN | Partial Networking 部分网络 |
SchM | Scheduler Module 调度模块 |
术语 | 描述 |
Buffer 缓冲 | Fixed sized memory area for a single data unit (e.g.CAN ID,Data Length,SDU,etc.) is stored at a dedicated memory address in RAM. 单个数据单元(例如CAN ID、数据长度、SDU等)的固定大小的内存区域存储在RAM中的专用内存地址处。 |
CAN communication matrix CAN通讯矩阵 | Describes the complete CAN network:
描述完整的CAN网络: • 参与节点 • 所有CAN PDU的定义(标识符、数据长度) • PDU的源和汇 |
CAN Controller CAN控制器 | A CAN Controller is a CPU on-chip or external standalone hardware device.One CAN Controller is connected to one physical channel. CAN控制器是片上CPU或外部独立硬件设备。一个CAN控制器连接到一个物理通道。 |
CAN Device Driver CAN 设备驱动程序 | Generic term of CAN Driver and CAN Transceiver Driver. CAN Driver 和 CAN Transceiver Driver 的总称。 |
CAN Hardware Unit CAN硬件单元 | A CAN Hardware Unit may consist of one or multiple CAN Controllers of the same type and one, two or multiple CAN RAM areas.The CAN Hardware Unit is located on-chip or as external device. The CAN hardware unit is represented by one CAN Driver. 一个CAN硬件单元可以由一个或多个相同类型的CAN控制器和一个、两个或多个CAN RAM 区域组成。CAN硬件单元位于片上或作为外部设备。CAN硬件单元由一个CAN驱动程序表示。 |
CanIf Controller mode state machine CanIf 控制器模式状态机 | This is not really a state machine, which may be influenced by transmission requests. This is an image of the current abstracted state of an appropriate CAN Controller. The state transitions can only be realized by upper layer modules like the CanSm or by external events like e.g. if a BusOff occurred. 这并不是真正的状态机,它可能会受到发送请求的影响。这是适当CAN控制器的当前抽象状态的图像。状态转换只能由像CanSm这样的上层模块或像这样的外部事件来实现,例如,如果发生BusOff。 |
CanIf Receive L-PDU / CanIf Rx L-PDU CanIf 接收 L-PDU | L-PDU of which the direction is set to "lower to upper layer". 方向设置为“从低到高”的L-PDU。 |
CanIf Receive L-PDU buffer /CanIfRxBuffer CanIf 接收 L-PDU 缓冲区 | Single element RAM buffer located in the CAN Interface module to store whole receive L-PDUs. 位于CAN接口模块中的单元素RAM缓冲区,用于存储整个接收L-PDU。 |
CanIf Transmit L-PDU / CanIf Tx L-PDU CanIf 发送 L-PDU | L-PDU of which the direction is set to "upper to lower layer". 方向设置为“从上到下”的L-PDU。 |
CanIf Transmit L-PDU buffer / CanIfTxBuffer CanIf 发送 L-PDU 缓冲区 | Single CanIfTxBuffer element located in the CanIf to store one or multiple CanIf Tx L-PDUs. If the buffersize of a single CanIfTxBuffer element is set to 0,a CanIfTxBuffer element is only used to refer a HTH. 位于CanIf中的单个CanIfTxBuffer元素用于存储一个或多个CanIf Tx L-PDU。如果单个 CanIfTxBuffer元素的buffersize设置为 0,则CanIfTxBuffer元素仅用于引用HTH。 |
Hardware object / HW object 硬件对象 | A CAN hardware object is defined as a PDU buffer inside the CAN RAM of the CAN Hardware Unit / CAN Controller. CAN硬件对象被定义为CAN硬件单元/CAN控制器的CAN RAM内的PDU缓冲区。 |
Hardware Receive Handle (HRH) 硬件接收句柄 (HRH) | The Hardware Receive Handle (HRH) is defined and provided by the CAN Driver. Each HRH typically represents just one hardware object.The HRH is used as a parameter by the CAN Interface Layer for i.e. software filtering. 硬件接收句柄 (HRH) 由CAN驱动程序定义和提供。每个HRH通常仅代表一个硬件对象。 HRH被CAN接口层用作参数,用于软件过滤。 |
Hardware Transmit Handle (HTH) 硬件发送句柄 (HTH) | The Hardware Transmit Handle (HTH) is defined and provided by the CAN Driver. Each HTH typically represents just one or multiple CAN hardware objects that are configured as CAN hardware transmit buffer pool. 硬件发送句柄 (HTH) 由CAN驱动程序定义和提供。每个HTH通常仅代表一个或多个配置为 CAN硬件发送缓冲池的CAN硬件对象。 |
Inner priority inversion 内部优先级倒置 | Transmission of a high-priority L-PDU is prevented by the presence of a pending low-priority L-PDU in the same transmit hardware object. 同一发送硬件对象中存在未决的低优先级L-PDU会阻止高优先级L-PDU的发送。 |
Integration Code 集成代码 | Code that the Integrator needs to add to an AUTOSAR System,to adapt non-standardized functionalities.Examples are Callouts of the ECU State Manager and Callbacks of various other BSW modules.The I/O Hardware Abstraction is called Integration Code, too. 集成商需要添加到AUTOSAR系统以适应非标准化功能的代码。 示例是ECU状态管理器的标注和各种其他BSW模块的回调。I/O硬件抽象也称为集成代码。 |
Lowest In - First Out / LOFO 最低入先出 | This is a data storage procedure, whereas always the elements with the lowest values will be extracted. 这是一个数据存储过程,而总是提取具有最低值的元素。 |
L-PDU channel group L-PDU 通道组 | Group of CAN L-PDUs, which belong to just one underlying network. Usually they are handled by one upper layer module. 一组CAN L-PDU,仅属于一个底层网络。通常它们由一个上层模块处理。 |
Outer priority inversion 外优先级倒置 | A time gap occurs between two consecutive transmit L-PDUs.In this case a lower priority L-PDU from another node can prevent sending the own higher priority L-PDU.Here the higher priority L-PDU cannot participate in arbitration during network access because the lower priority L-PDU already won the arbitration. 两个连续发送的L-PDU之间出现时间间隙。在这种情况下,来自另一个节点的较低优先级 L-PDU 可以阻止发送自己的较高优先级L-PDU。这里优先级较高的L-PDU在网络访问期间不能参与仲裁,因为较低优先级的L-PDU已经赢得了仲裁。 |
Physical channel 物理通道 | A physical channel represents an interface from a CAN Controller to the CAN Network. Different physical channels of the CAN Hardware Unit may access different networks. 物理通道代表从CAN控制器到CAN网络的接口。CAN硬件单元的不同物理通道可以访问不同的网络。 |
Tx request 发送请求 | Transmit request to the CAN Interface module from a upper layer module of the CanIf 从CanIf的上层模块向CAN Interface模块发送请求 |
以上摘自《AUTOSAR_SWS_CANInterface.pdf (V4.3.0)》。
3.10 CAN Tranceiver Driver:CanTrcv
缩写 | 描述 |
ComM | Communication Manager 通讯管理器 |
DEM | Diagnostic Event Manager 诊断事件管理器 |
DET | Default Error Tracer 默认错误跟踪器 |
DIO | Digital Input Output (SPAL module) 数字输入输出(SPAL模块) |
EB | Externally Buffered channels.Buffers containing data to transfer are outside the SPI Handler/Driver. 外部缓冲通道。包含要传输的数据的缓冲区位于SPI处理程序/驱动程序之外。 |
EcuM | ECU State Manager ECU状态管理器 |
IB | Internally Buffered channels.Buffers containing data to transfer are inside the SPI Handler/Driver. 内部缓冲通道。包含要传输的数据的缓冲区位于SPI处理程序/驱动程序内部。 |
ISR | Interrupt Service Routine 中断服务程序 |
MCAL | Micro Controller Abstraction Layer 微控制器抽象层 |
Port | Port module (SPAL module) 端口模块(SPAL模块) |
n/a | Not Applicable 不适用 |
SBC | System Basis Chip;a device, which integrates e.g.CAN and/or LIN transceiver, watchdog and power control. 系统基础芯片;一种设备,它集成了例如CAN和/或LIN收发器、看门狗和电源控制。 |
SPAL | Standard Peripheral Abstraction Layer 标准外围抽象层 |
SPI Channel | A channel is a software exchange medium for data that are defined with the same criteria: configuration parameters,number of data elements with same size and data pointers (source & destination) or location.See specification of SPI driver for more details. 通道是数据的软件交换介质,这些数据的定义标准相同:配置参数、具有相同大小和数据指针(源和目标)或位置的数据元素的数量。有关详细信息,请参阅SPI驱动程序的规范。 |
SPI Job | A job is composed of one or several channels with the same chip select.A job is considered to be atomic and therefore cannot be interrupted.A job has also an assigned priority.See specification of SPI driver for more details. 一个作业由一个或多个具有相同芯片选择的通道组成。一个作业被认为是原子的,因此不能被中断。一个作业也有一个指定的优先级。更多详细信息,请参阅SPI驱动程序的规范。 |
SPI Sequence | A sequence is a number of consecutive jobs to be transmitted. A sequence depends on a static configuration. See specification of SPI driver for more details. 序列是要发送的多个连续作业。序列取决于静态配置。有关更多详细信息,请参阅SPI驱动程序的规范。 |
CAN Channel | A physical channel which is connected to a CAN network from a CAN controller through a CAN transceiver. CAN 控制器通过CAN收发器连接到CAN网络的物理通道。 |
API | Application Programming Interface 应用程序接口 |
以上摘自《AUTOSAR_SWS_CANTransceiverDriver.pdf (V4.3.0)》。
4 FlexRay通信篇
4.1 FlexRay Network Management:FrNm
缩写 | 描述 |
CC | Communication Controller 通讯控制器 |
NM | Network Management 网络管理 |
WCET | Worst Case Execution Time 最坏情况执行时间 |
DET | Default Error Tracer. AUTOSAR Module for detection and reporting of errors during development. 默认错误跟踪器。AUTOSAR模块,用于在开发过程中检测和报告错误。 |
API | Application program interface 应用程序接口 |
Com | Communication module 通讯模块 |
OS | Operating system 操作系统 |
SchM | Schedule Manager 日程管理器 |
PDU | Protocol data unit 协议数据单元 |
CPU | Central processing unit 中央处理器 |
FrIf | Abbreviation for the FlexRay Interface FlexRay接口的缩写 |
FrNm | Abbreviation for the Network Management on FlexRay FlexRay网络管理的缩写 |
NmIf | Abbreviation for the generic Network Management 通用网络管理的缩写 |
ECU | Electronic control unit 电子控制单元 |
ComM | Communication manager 通讯管理器 |
FrSm | FlexRay State Manager FlexRay状态管理器 |
HW | Hardware 硬件 |
术语 | 描述 |
Bus-Sleep Mode 总线休眠模式 | Network mode where all interconnected communication controllers are in the sleep mode. 网络模式,其中所有互连的通信控制器都处于休眠模式。 |
NM-Network NM-网络 | Instance of the FlexRay NM to handle one physical FlexRay Bus. Caution: The FlexRay Bus contains two FlexRay channels which cannot be handled independent of the other. Therefore the NM-Network covers both FlexRay bus channels. This is equivalent to one NM-Cluster 处理一个物理FlexRay总线的FlexRay NM实例。注意:FlexRay总线包含两个FlexRay 通道,不能相互独立处理。因此,NM-Network覆盖了两个FlexRay总线通道。这相当于一个NM-Cluster |
Network requested 网络请求 | NM network is requested if FrNm_NetworkRequest has been called and neither the network has been released nor Bus Sleep Mode has been entered afterwards 如果FrNm_NetworkRequest已被调用,并且此后既没有释放网络也没有进入总线休眠模式,则请求NM网络 |
Network released 网络发布 | NM network is released if FrNm_NetworkRelease has been called and network has not been requested afterwards 如果调用了FrNm_NetworkRelease并且此后没有请求网络,则NM网络被释放 |
Repeat Message Request active 重复消息请求激活 | A Repeat Message Request is active if FrNm_RepeatMessageRequest has been called or a NM PDU with Repeat Message Request bit set has been received in Network Mode. It is not active anymore if Repeat Message State is left or Bus Sleep Mode is entered. 如果FrNm_RepeatMessageRequest已被调用或在网络模式下已接收到具有重复消息请求位设置的NM PDU,则重复消息请求处于活动状态。如果保留重复消息状态或进入总线休眠模式,则它不再处于活动状态。 |
NM Data Cycle NM数据周期 | Number of FlexRay cycles necessary for all nodes to be able to send NM Data at least once. 所有节点能够至少发送一次NM数据所需的FlexRay周期数。 |
NM Message 网管消息 | Packet of information exchanged for purposes of the NM algorithm. 为NM算法而交换的信息包。 |
NM Repetition Cycle NM 重复周期 | Number of FlexRay cycles where no change of voting behavior is possible. Value has to be a multiple of the NM Voting Cycle. Used to improve the reliability of the voting. 无法更改投票行为的FlexRay周期数。价值必须是NM投票周期的倍数。用于提高投票的可靠性。 |
NM Slot | Slot reserved for purposes of network management. 为网络管理目的保留的插槽。 |
NM Timeout NM 超时 | Timeout in the NM algorithm that initiates transition into Bus-Sleep Mode. 启动转换到总线休眠模式的NM算法中的超时。 |
NM User Data NM用户数据 | Supplementary application specific data that is sent independent of the NM Vote on the bus. 独立于总线上的NM投票发送的补充应用程序特定数据。 |
NM Voting Cycle NM 投票周期 | Number of FlexRay cycles necessary for all nodes to vote at least once. 所有节点至少投票一次所需的FlexRay周期数。 |
NM-Vote NM-投票 | Information transmitted using the FlexRay Bus indicating the vote of a ECU to keep the bus awake 使用FlexRay总线发送的信息指示ECU投票以保持总线唤醒 |
NM-Vector | FlexRay NM Vector is the aggregated data available when the FlexRay CC optional NM Hardware Vector Service is used. FlexRay NM Vector是使用FlexRay CC可选NM硬件向量服务时可用的聚合数据。 |
NM-Data | Data related to NM transmitted using the FlexRay Bus. 与使用FlexRay总线发送的NM相关的数据。 |
NM-Cluster | Obsolete, equivalent to NM-Network 已过时,相当于NM-Network |
CBV | Control bit vector 控制位向量 |
ClusterAwakeVote | At least one Node other than itself votes for keeping the cluster awake. 除了自身之外,至少有一个节点投票支持保持集群唤醒。 |
Positive NM-Vote in static segment 静态段中的积极 NM-Vote | NM-Vote PDU reception or transmission with Voting Bit set to '1' NM-Vote PDU接收或发送,投票位设置为“1” |
Positive NM-Vote in dynamic segment 动态段中的积极 NM-Vote | NM-Vote PDU received or transmitted NM-Vote PDU接收或发送 |
Negative NM-Vote in static segment 静态段中的否定NM-Vote | NM-Vote PDU reception or transmission with Voting Bit set '0' NM-Vote PDU接收或发送,投票位设置为“0” |
Negative NM-Vote 否定 NM 投票 | In dynamic segment: NM-Vote PDU is neither received nor transmitted 在动态段:NM-Vote PDU既不接收也不发送 |
以上摘自《AUTOSAR_SWS_FlexRayNetworkManagement.pdf (V4.3.0)》。
4.2 FlexRay State Manager:FrSM
缩写 | 描述 |
API | Application Program Interface 应用程序接口 |
AUTOSAR | Automotive Open System Architecture 汽车开放系统架构 |
BSW | Basic Software 基础软件 |
CC | Communication Controller 通讯控制器 |
CHI | Controller Host Interface 控制器主机接口 |
ComM | AUTOSAR Communication Manager AUTOSAR通讯管理器 |
DCM | Diagnostic Communication Manager 诊断通信管理器 |
Dem/DEM | Diagnostic Event Manager 诊断事件管理器 |
Det/DET | Default Error Tracer 默认错误跟踪器 |
e.g. | [lat.] exempli gratia = [eng.] for example [lat.] exempli gratia = [eng.] 例如 |
ECU | Electronic Control Unit 电子控制单元 |
EcuM | ECU State Manager ECU状态管理器 |
Fr | FlexRay Driver FlexRay驱动程序 |
FrIf | FlexRay Interface (AUTOSAR BSW module) FlexRay接口(AUTOSAR BSW 模块) |
FrSM | FlexRay State Manager FlexRay状态管理器 |
FrTrcv | FlexRay Transceiver Driver FlexRay收发器驱动程序 |
i.e. | [lat.] id est = [eng.] that is [lat.] id est = [eng.] 即 |
Id/ID | Identifier 标识符 |
N/A | Not applicable 不适用 |
NM | Network Management 网络管理 |
PDU | Protocol Data Unit 协议数据单元 |
POC | Protocol Operation Control 协议操作控制 |
POCState | Actual CC internal state of the POC. This state might differ from vPOC!State in certain cases, e.g. after FREEZE command invocation (see [11] for details). POC的实际CC内部状态。在某些情况下,此状态可能与vPOC!State不同,例如,在调用FREEZE命令之后(详见[11])。 |
RTE | Runtime Environment 运行环境 |
RX | Reception 接收 |
SchM | Schedule Manager 日程管理器 |
SW | Software 软件 |
TX | Transmission 发送 |
UML | Unified Modeling Language 统一建模语言 |
vPOC | Data structure provided from the CC to the host at the CHI, which contains the actual POC status of the CC. CC向CHI主机提供的数据结构,包含CC的实际POC状态。 |
vPOC!Freeze | vPOC!Freeze denotes the Freeze bit that is part of the vPOC data structure. The Freeze bit is used by the CC to indicate that the HALT state has been entered due to an error condition. vPOC!Freeze表示作为vPOC数据结构一部分的冻结位。CC使用冻结位来指示由于错误条件已进入HALT状态。 |
vPOC!SlotMode | vPOC!SlotMode denotes the SlotMode field that is part of the vPOC data structure. vPOC!SlotMode表示SlotMode字段,它是vPOC数据结构的一部分。 |
WUP | Wake-Up Pattern 唤醒模式 |
术语 | 描述 |
Active wake-up 主动唤醒 | Wake-up caused by the ECU e.g. by a sensor. 由ECU引起的唤醒,例如,通过传感器。 |
Passive wake-up 被动唤醒 | Wakeup caused by another ECU and propagated (e.g. by bus or wakeup-line) to the ECU currently in focus. 由另一个ECU引起并传播(例如通过总线或唤醒线)到当前关注的ECU的唤醒。 |
Remote wake-up 远程唤醒 | A passive wake-up received by the FlexRay bus or wakeup-line. FlexRay总线或唤醒线接收到的被动唤醒。 |
以上摘自《AUTOSAR_SWS_FlexRayStateManager.pdf (V4.3.0)》。
4.3 Time Sync Over FlexRay:FrTSyn
缩写 | 描述 |
(G)TD | (Global) Time Domain (全局)时域 |
(G)TM | (Global) Time Master (全局)时间主 |
<Bus>TSyn | A bus specific Time Synchronization module 总线特定的时间同步模块 |
CRC | Cyclic Redundancy Checksum 循环冗余校验和 |
Debounce Time | Minimum gap between two Tx messages with the same PDU 具有相同 PDU 的两个 Tx 消息之间的最小间隙 |
DEM | Diagnostic Event Manager 诊断事件管理器 |
DET | Default Error Tracer 默认错误跟踪器 |
FR | FlexRay |
FUP message | Follow-Up message 后续消息 |
OFNS message | Offset adjustment message 偏移调整信息 |
OFS message | Offset Synchronization message 偏移同步消息 |
StbM | Synchronized Time-Base Manager 同步时基管理器 |
SYNC message | Time Synchronization message 时间同步消息 |
TG | Time Gateway 时间网关 |
Timesync | Time Synchronization 时间同步 |
TS | Time Slave 时间奴隶 |
TSD | Time Sub-domain 时间子域 |
以上摘自《AUTOSAR_SWS_TimeSyncOverFlexRay.pdf (V4.3.0)》。
4.4 FlexRay Interface:FrIf
缩写 | 描述 |
BSW | (AUTOSAR) Basic Software (AUTOSAR) 基础软件 |
CAS | Collision Avoidance Symbol 防撞符号 |
CC | (FlexRay) Communication Controller (FlexRay) 通信控制器 |
CDD | Complex Driver 复杂的驱动程序 |
CHI | Controller Host Interface of a FlexRay CC FlexRay CC的控制器主机接口 |
COM | Communication (AUTOSAR BSW module) 通信(AUTOSAR BSW模块) |
ComM | Communication Manager (AUTOSAR BSW module) 通信管理器(AUTOSAR BSW模块) |
DEM | Diagnostic Event Manager (AUTOSAR BSW module) 诊断事件管理器(AUTOSAR BSW模块) |
DET | Default Error Tracer (AUTOSAR BSW module) 默认错误跟踪器(AUTOSAR BSW模块) |
FrIf | FlexRay Interface (AUTOSAR BSW module) FlexRay接口(AUTOSAR BSW模块) |
FrNm | FlexRay Network Management (AUTOSAR BSW module) FlexRay网络管理(AUTOSAR BSW模块) |
FrTp | FlexRay Transport Layer (AUTOSAR BSW module) FlexRay传输层(AUTOSAR BSW模块) |
ISR | Interrupt Service Routine 中断服务程序 |
MCG | Module Configuration Generator 模块配置生成器 |
PduR | PDU Router (AUTOSAR BSW module) PDU路由器(AUTOSAR BSW模块) |
POC | Protocol Operation Control 协议操作控制 |
WUDOP | Wake-Up During Operation 运行中唤醒 |
WUP | Wake-Up Pattern 唤醒模式 |
WUS | Wake-Up Symbol 唤醒符号 |
System Designer | The person responsible for the configuration of all system parameters that do not influence the executable code itself (i.e. the sequence of instructions executed during runtime), but the data used to configure which operations this executable code performs on which data and at which points in time. 负责配置所有不影响可执行代码本身的系统参数的人(即运行时执行的指令序列),但是用于配置此可执行代码对哪些数据以及在哪些时间点执行哪些操作的数据。 |
以上摘自《AUTOSAR_SWS_FlexRayInterface.pdf (V4.3.0)》。
4.5 FlexRay Tranceiver Driver:FrTrcv
缩写 | 描述 |
µC | Microcontroller 微控制器 |
Active Star (Network) | Star topology networks consist of one ore more active central nodes which rebroadcast(s) all transmissions received from a branch to all other branches on the network. All peripheral nodes may thus communicate with all others by transmitting to, and receiving from, the central node(s) if they are located on another branch. On detection of the failure of a branch the active star will isolate its peripheral nodes from all other branches resulting in fault confinement 星形拓扑网络由一个或多个活动中心节点组成,这些节点将从一个分支接收到的所有发送重新广播到网络上的所有其他分支。 因此,如果所有外围节点位于另一个分支上,则所有外围节点可以通过向中央节点发送和从中央节点接收来与所有其他节点通信。 在检测到分支故障时,活动星会将其外围节点与所有其他分支隔离,从而导致故障限制 |
API | Application Programming Interface 应用程序接口 |
AUTOSAR | Automotive Open System Architecture 汽车开放系统架构 |
BD | Bus Driver 总线驱动 |
Branch | Element of an active star network topology sharing (i.e. electrically connected to) the same transmitter and receiver circuit on the physical layer. The failure of a branch will result in the isolation of its peripheral nodes by the active star from all other branches resulting in fault confinement. 有源星型网络拓扑的元素在物理层上共享(即电连接到)相同的发送器和接收器电路。 一个分支的故障将导致其外围节点被活动星与所有其他分支隔离,从而导致故障限制。 |
BSW | Basic Software 基础软件 |
CC | Communication Controller 通讯控制器 |
ComM | Communication Manager, See [8] for details 通讯管理器,详见[8] |
DEM/Dem | Diagnostic Event Manager 诊断事件管理器 |
DET/Det | Default Error Tracer 默认错误跟踪器 |
DIO/Dio | Digital input output, one of the SPAL SW modules 数字输入输出,SPAL SW模块之一 |
EB | Externally buffered channel. Buffers containing data to transfer are outside the SPI Handler/Driver. 外部缓冲通道。包含要传输的数据的缓冲区位于SPI处理程序/驱动程序之外。 |
ECU | Electronic Control Unit 电子控制单元 |
EcuM | ECU State Manager, see [7] for details ECU状态管理器,详见[7] |
EPL | Electrical Physical Layer 电物理层 |
ERRN | ERRor output signal, Negated i.e. active LOW ERR或输出信号,否定即低电平有效 |
FlexRay Node | A logical entity connected to the FlexRay Network that is capable of sending and/or receiving frames. 连接到FlexRay网络的逻辑实体,能够发送和/或接收帧。 |
FrIf | FlexRay Interface FlexRay接口 |
FrTrcv | FlexRay Transceiver FlexRay收发器 |
GPIO | General Purpose Input Output 通用输入输出 |
I/O | Input/Output 输入输出 |
IB | Internally buffered channel. Buffers containing data to transfer are inside the SPI Handler/Driver. 内部缓冲通道。包含要传输的数据的缓冲区位于SPI处理程序/驱动程序内部。 |
ID/Id | Identifier 标识符 |
ISR | Interrupt Service Routine 中断服务程序 |
MCAL | Micro controller Abstraction Layer 微控制器抽象层 |
MCG | Module Configuration Generator 模块配置生成器 |
MISRA | Motor Industry Software Reliability Association 汽车工业软件可靠性协会 |
n/a | Not applicable 不适用 |
OS | Operating System 操作系统 |
Port | Port, one of the SPAL SW modules 端口,SPAL SW模块之一 |
RAM | Random Access Memory 随机存取存储器 |
RxD | Receive Data 接收数据 |
RxEN | Receive Enable 接收使能 |
SBC | System Basis Chip; A device, which integrates e.g. CAN and/or FlexRay and/or LIN transceiver, watchdog and power control. 系统基础芯片;一种设备,它集成了,例如CAN和/或FlexRay和/或LIN收发器、看门狗和电源控制。 |
SchM | Schedule Manager 调度管理器 |
SPAL | Standard Peripheral Abstraction Layer 标准外围抽象层 |
SPI/Spi | Serial Peripheral Interface. 串行外设接口。 |
SPI/Spi Channel | A channel is a software exchange medium for data that are defined with the same criteria: configuration parameters, number of data elements with same size and data pointers (source & destination) or location. See specification of SPI driver for more details. 通道是使用相同标准定义的数据的软件交换介质:配置参数,具有相同大小和数据指针(源和目标)或位置的数据元素的数量。有关更多详细信息,请参阅SPI驱动程序的规范。 |
SPI/Spi Job | A job is composed of one or several channels with the same chip select. A job is considered to be atomic and therefore cannot be interrupted. A job has also an assigned priority. See specification of SPI driver for more details. 一个作业由一个或多个具有相同片选的通道组成。作业被认为是原子的,因此不能被中断。 作业也有指定的优先级。有关更多详细信息,请参阅SPI驱动程序的规范。 |
SPI/Spi Sequence | A sequence is a number of consecutive jobs to be transmitted. A sequence depends on a static configuration. See specification of SPI driver for more details. 序列是要发送的多个连续作业。序列取决于静态配置。有关更多详细信息,请参阅SPI驱动程序的规范。 |
以上摘自《AUTOSAR_SWS_FlexRayTransceiverDriver.pdf (V4.3.0)》。
推荐Autosar培训教程(点击下方卡片接口跳转):
《Autosar从入门到精通-实战篇》总目录_培训教程持续更新中...
《Autosar_BSW高阶配置》总目录_培训教程持续更新中...
AUTOSAR中各BSW模块_“模块缩写”_“参考文档”以及所属“AUTOSAR软件层级”清单
END