ASAM MCD-2 D ODX 作者指南

需积分: 1 196 浏览量更新于2024-06-28 收藏 1.43MB PDF 举报

"ASAM-AE-MCD-2-D-AuthoringGuidelines-AS-V1-0-0文档详细阐述了ODX(Open Diagnostic Data Exchange)规范的定义和最佳实践，旨在促进公司间基于ODX的数据交换。" ODX（开放诊断数据交换）是一种标准，用于在汽车行业的不同公司之间交换电子控制单元（ECU）的诊断数据。ASAM（Association for Standardization of Automation and Measuring Systems，自动化与测量系统标准化协会）的MCD-2 D标准是ODX的核心组成部分，它定义了如何创建、交换和使用诊断信息。 ASAM MCD-2 D ODX Authoring Guidelines版本1.0.0是该标准的一个补充，它提供了一系列推荐的实践规则，帮助作者按照ODX规范有效地创建和维护诊断数据库。这些指南确保了数据的一致性、完整性和可互操作性，从而降低了跨企业合作时的兼容性问题。文档的主要内容可能包括以下几个方面： 1. **ODX数据模型**：详细描述了ODX的数据结构和模型，包括ECU诊断信息的组织方式，如服务、故障码、变量等。 2. **作者指导原则**：提供了一套最佳实践，涵盖了从创建诊断数据包到验证其正确性的全过程，包括命名约定、数据结构的使用、错误处理和文档结构等。 3. **版本管理**：指导如何有效地管理和更新ODX文件，确保每次变更都能被准确记录和理解。 4. **互操作性**：强调了确保不同系统之间数据交换无障碍的重要性，可能包括数据格式的标准化、协议兼容性测试等方面。 5. **质量保证**：提供了验证ODX文件质量和符合性的方法，以确保数据的可靠性和有效性。 6. **版权和使用条款**：文档中明确了ASAM对内容的所有权，并规定了未经明确授权不得复制或修改的条款。尽管ASAM尽力确保文档的准确性，但仍然可能存在错误或不一致之处。使用者在应用这些指南时应自行承担风险，ASAM及其作者不对因使用此文档导致的任何损害或后果负责。通过遵循这些ODX Authoring Guidelines，汽车行业内的开发者和工程师可以更高效地创建和维护诊断数据库，促进整个行业的标准化和协作。

Authoring Guidelines Recommendations Collection

ASAM MCD-2 D ODX Authoring Guidelines Version 1.0.0

To fill the SHORT-NAME with an appropriate value the following algorithms should be

considered.

Algorithm 1: Fill the LONG-NAME with a precise naming and copy this into the

SHORT-NAME by omitting the blanks between the words of the LONG-NAME

and by omitting all special characters of the LONG-NAME. In the SHORT-

NAME every word shall start with an upper case letter to improve the readability

of the SHORT-NAME.

Figure 3-1: Creation of SHORT-NAME by copying the LONG-NAME, omitting special

characters and capitalizing the first character of every LONG-NAME - word

Algorithm 2: Fill the LONG-NAME with a precise naming and apply a chopping

character rule on the LONG-NAME to build the SHORT-NAME. This rule shall

assure that the SHORT-NAME also delivers the possibility to identify the

meaning of the data element by reading the SHORT-NAME. This could be

resolved by chopping every word of the LONG-NAME to its e. g. first five

characters and afterwards concatenating those shortened words. In the

SHORT-NAME every word shall start with an upper case letter to improve the

readability of the SHORT-NAME.

Figure 3-2: Creation of the SHORT-NAME by chopping every single word of the

LONG-NAME

The first suggestion is not really a SHORT-NAME because the SHORT-NAME is nearly

as long as the LONG-NAME. On the other hand it is easy to understand the meaning of

this data element reading the SHORT-NAME. This could be important for applications that

do show the SHORT-NAME at the graphical user interface of an application instead of the

LONG-NAME. It is also very helpful for all developers of ODX-Jobs.

The second nomination abbreviates the LONG-NAME to a real SHORT-NAME. But it is a

little bit more difficult to understand the meaning of the SHORT-NAME because of the

accomplished chopping of the LONG-NAME. Otherwise the use of an, e. g. five character

chopping, still is a good compromise in understanding the SHORT-NAME as well as the

LONG-NAME. In the end it leads to less data in an odx-data-file.

P3-15

If the resulting SHORT-NAME consists of up to 128 characters the first

algorithm is proposed. If the resulting SHORT-NAME is longer than 128

characters the second algorithm is proposed.

The usage of these algoritms is not allowed if it results in a non-unique

SHORT-NAME.

Authoring Guidelines Recommendations Collection

ASAM MCD-2 D ODX Authoring Guidelines Version 1.0.0

Requirements:

R3-18

The filename shall be built according to the rule prefix plus intention plus file

extension as shown in the following examples.

Table 3-5: Examples for ODX file names:

C_ISO_15765_3_on_ISO_15765_2.odx-c

PR_UDSOnCAN.odx-d

ES_DataLibra.odx-d

FG_AllUDSSyste.odx-d

BV_DashBoard.odx-d

EV_DashBoardSiemensVDO.odx-d

F_5K0920860A_X005.odx-f

E_DashBoard.odx-e

FD_Light.odx-fd

M_EraseDTCs.odx-m

V_VW36X.odx-v

3.1.1.8 IDENTIFICATION OF ODX-RS STANDARDIZED OBJECTS

According to chapter 2.2 ODX authoring guidelines provides some libraries of

standardized objects like physical units, DATA-OBJECT-PROPERTIEs or GLOBAL-NEG-

RESPONSEs. The OIDs of ODX-RS standardized objects are identical regarding different

versions of ODX. Those objects should be used in the following way:

ODX V 2.0.1:

If a standardized ODX-RS object is used within a DIAG-LAYER which is no ECU-

SHARED-DATA the ECU-SHARED-DATA (library) which contains the standardized ODX-

RS object has to be imported or inherited by the using DIAG-LAYER.

If an ECU-SHARED-DATA wants to use a standardized ODX-RS object it has to generate

a working copy of that object within the DIAG-LAYER. The ID of the copied object should

be build by concatenating the original ID of the ODX-RS object with another specific ID.

That convention generates a direct relationship to the corresponding original ODX-RS

object which can be used to identify the original ODX-RS object. If there are any conflicts

of the SHORT-NAME of the copied ODX-RS object it is proposed to concatenate the

SHORT-NAME of the ODX-RS object with a specific term e.g. the SHORT-NAME of the

DIAG-LAYER where the copied object resides. The OID of an ODX-RS standardized

object should remain unchanged if it is copied into another ECU-SHARED-DATA.

ODX V 2.1.0 and higher:

These ODX standards have no restriction for cascading ECU-SHARED-DATA. Therefore

the recommendation is:

If a standardized ODX-RS object is used within any DIAG-LAYER the ECU-SHARED-

DATA (library) which contains the standardized ODX-RS object has to be imported or

inherited by the using DIAG-LAYER. With that convention SHORT-NAME conflicts cannot

occur.

剩余101页未读，继续阅读

车载诊断技术

粉丝: 6975
资源: 753

ASAM MCD-2 D ODX 作者指南

ASAM MCD2D v2.01

TOC-ASAM-AE-MCD-2-D-BS-ODX-V2-2-0.pdf

TOC-ASAM-AE-MCD-2-NET-FIBEX-BS-4-1-2.pdf

ASAM-AE-MCD-2-D-BS-ODX-V2-2-0

asam_ae_mcd-2d_v2.2.zip_ASAM MCD-2D_MCD 2D_asam mcd-2_asam3mc协议_

ASAM-XCP-Part2-Protocol-Layer-Specification-V1-1-0

ASAM-SOVD-BS-V1-0-0 最新版基于服务的诊断规范

ASAM-XCP-Part4-Interface-Specification-V1-1-0

ASAM-XCP-Part5-Example-Communication-Sequences-V1-1-0

ASAM_MCD-2MC_DataSpecifcation_V1.6.rar_ASAM mcd_ASAM-MCD-2MC_ASA

最新资源