【CANdelaStudio编辑CDD】-0.3-CDD中Fault Memory里DTC Column与Autosar Dem对应关系
目录
1 CDD中Fault Memory里DTC Column
2 ODX/PDX中描述一个DTC用到的标签和关键字
3 CDD中Fault Memory里DTC Column与Autosar Dem参数对照表
4 附录:ODX/PDX中描述一个UDS DTC举例
5 结尾
前一篇链接:
全网最全诊断梳理《UDS/OBD诊断&诊断描述文件CDD》总目录https://blog.csdn.net/qfmzhu/article/details/120425660
<--返回「UDS/OBD诊断需求编辑工具」博文-总目录-->
<--返回「UDS/OBD诊断需求编辑工具」专栏主页-->
1 CDD中Fault Memory里DTC Column
当你打开一个CDD诊断描述文件时,在“Available DTCs Fault Memory”项中,你会看到这个CDD文件所有的UDS DTC List描述。在DTC List的每一Columu都有专用的术语描述,是不是经常被这些术语困扰!
各个术语描述见下表:
2 ODX/PDX中描述一个DTC用到的标签和关键字
CDD文件中,UDS DTC Columu使用的是In import target(name)列;
ODX/PDX文件中,描述一个UDS DTC,“<SHORT-NAME>”标签使用的是In import target(qualifier)列;“<LONG-NAME>” 标签使用的是In import target(name)列。
详见该篇附录内容。
3 CDD中Fault Memory里DTC Column与Autosar Dem参数对照表
DTC Column中标题 | PDX中标签/短名 | 常用默认值 | DEM中参数名 |
DTC | TROUBLE-CODE | 举例:0x96555F | DemUdsDTC |
DTCText | TEXT | 举例:DTC_96555F_XXX_Name | |
Errortext shortname | DTC_SHORTNAME | 举例:DTC_96555F_XXX_Name | 对应DemDTCClass中各个DTC的名称 |
Set Condition | SetCondition | 举例:Voltage > 14V,t > 2s | 不会自动生成代码 |
Reset condition & self healing | ResetCondition | 举例:Voltage < 10V,t > 5s | 不会自动生成代码 |
Corrective action | CorrectiveAction |
Replace ECU Check wiring connector Check wiring Check power supply Update software No known corrective action See special instruction |
不会自动生成代码 |
Special instruction | SpecialInstruction | 不会自动生成代码 | |
Operation Cycle | DTC_OPERATION_CYCLE |
DEM_IGNITION DEM_OBD_DCY DEM_WARMUP DEM_POWER |
DemOperationCycleRef
DemIndicatorHealingCycleRef |
Number of Trips - Active | NUMBER_OF_TRIPS_ACTIVE | ||
Enable Conditions | Enable_Conditions | ||
Self Healing (Aging) | DTC_AGING_SUPPORTED |
supported not supported |
DemAgingAllowed |
Healing Cycle | DTC_AGING_CYCLE |
DEM_IGNITION DEM_OBD_DCY DEM_WARMUP DEM_POWER |
DemAgingCycleRef |
Healing Cycles | DTC_AGING_COUNTER | 40 | DemAgingCycleCounterThreshold |
Monitor Initialization Function | DTC_INIT_MONITOR_REQUIRED |
required not required |
DemCallbackInitMForE |
DTC Priority | DTC_PRIORITY_VALUE | 10 | DemEventPriority |
DTC Severity | DTC_SEVERITY_VALUE |
noSeverity maintenanceOnly checkAtNextHalt checkImmediately |
DemDTCSeverity |
Pre-Debounce Algorithm | DTC_DEBOUNCING_ALGORITHM |
Time based Counter based |
DemDebounceTimeBase
DemDebounceCounterBased |
Count-In step size | DTC_STEP_SIZE_PREFAILED | 127 | DemDebounceCounterIncrementStepSize |
Count-out step size | DTC_STEP_SIZE_PREPASSED | 128 | DemDebounceCounterDecrementStepSize |
Use Jump-Up (Prefailed) | DTC_JUMP_UP_PREFAILED |
Yes No |
DemDebounceCounterJumpUp |
Use Jump-Down (Prepassed) | DTC_JUMP_DOWN_PREPASSED |
Yes No |
DemDebounceCounterJumpDown |
Set WarningIndicatorBit at fault | DTC_WARNING_INDICATOR_FLAG |
supported not supported |
MalfunctionIndicatorLamp |
Functional Unit | DTC_FUNCTIONAL_UNIT_VALUE | ||
DTC Debounce Failed Timeout Value | DTC_TIMEOUT_VALUE_PREFAILED | DemDebounceTimeFailedThreshold | |
DTC Debounce Passed Timeout Value | DTC_TIMEOUT_VALUE_PREPASSED | DemDebounceTimePassedThreshold | |
DTC Storage Threshold | DTC_STORAGE_THRESHOLD |
DemDebounceTimeStorageThreshold
DemEventDebounceCounterStorageThreshold |
|
Status | |||
Vehicle System Groups |
4 附录:ODX/PDX中描述一个UDS DTC举例
当你读懂该结构时,你可以尝试手动修改(或制作脚本)一个ODX/PDX里的若干个DTC描述。该示例以ODX V2.0.1标准协议为基础。
<DTC ID="_2559"><SHORT-NAME>DTC96555F</SHORT-NAME><TROUBLE-CODE>9852255</TROUBLE-CODE><DISPLAY-TROUBLE-CODE>B16555F</DISPLAY-TROUBLE-CODE><TEXT>DTC_96555F_XXX_Name</TEXT><SDGS><SDG><SDG-CAPTION ID="_2560"><SHORT-NAME>DTC_SHORTNAME</SHORT-NAME><LONG-NAME>Errortext shortname</LONG-NAME></SDG-CAPTION><SD>DTC_96555F_XXX_Name</SD></SDG><SDG><SDG-CAPTION ID="_2561"><SHORT-NAME>SetCondition</SHORT-NAME><LONG-NAME>Set Condition</LONG-NAME></SDG-CAPTION><SD>Voltage > 14V,t > 2s</SD></SDG><SDG><SDG-CAPTION ID="_2562"><SHORT-NAME>ResetCondition</SHORT-NAME><LONG-NAME>Reset condition & self healing</LONG-NAME></SDG-CAPTION><SD>Voltage < 10V,t > 5s</SD></SDG><SDG><SDG-CAPTION ID="_2563"><SHORT-NAME>CorrectiveAction</SHORT-NAME><LONG-NAME>Corrective action</LONG-NAME></SDG-CAPTION><SD>No known corrective action</SD></SDG><SDG><SDG-CAPTION ID="_2564"><SHORT-NAME>SpecialInstruction</SHORT-NAME><LONG-NAME>Special instruction</LONG-NAME></SDG-CAPTION><SD>tbd</SD></SDG><SDG><SDG-CAPTION ID="_2565"><SHORT-NAME>DTC_OPERATION_CYCLE</SHORT-NAME><LONG-NAME>Operation Cycle</LONG-NAME><DESC><p>Kind of operation cycle for the event storage(e.g. power cycle, driving cycle, ...)<br/></p></DESC></SDG-CAPTION><SD>DEM_POWER</SD></SDG><SDG><SDG-CAPTION ID="_2566"><SHORT-NAME>NUMBER_OF_TRIPS_ACTIVE</SHORT-NAME><LONG-NAME>Number of Trips - Active</LONG-NAME><DESC><p>Number of operation cycles needed to confirm the eventThe value 0 is the standard UDS behavior of confirming the event (ConfirmedDTC status bit becomes set) with the first qualified FAILED result. A value of 1 means the event becomes confirmed if it fails again in the next operation cycle.
Larger values represent confirmation in the n-th cycle e.g. 2 is confirmation in cycle after the next cycle, etc.<br/></p></DESC></SDG-CAPTION><SD>0</SD></SDG><SDG><SDG-CAPTION ID="_2567"><SHORT-NAME>Enable_Conditions</SHORT-NAME><LONG-NAME>Enable Conditions</LONG-NAME><DESC><p>An event status report ((Pre)Failed or (Pre)Passed) will only have an effect if all EnableConditions belonging to the DTC are met at the time of report. Otherwise the result will be discarded.
Multiple C-Qualifier separated by a comma can be added here<br/></p></DESC></SDG-CAPTION><SD>tbd</SD></SDG><SDG><SDG-CAPTION ID="_2568"><SHORT-NAME>DTC_AGING_SUPPORTED</SHORT-NAME><LONG-NAME>Self Healing (Aging)</LONG-NAME><DESC><p>Supported: Aging/ unlearning of the event is supported
Not Supported: Aging/ unlearning of the event is not supported<br/></p></DESC></SDG-CAPTION><SD>supported</SD></SDG><SDG><SDG-CAPTION ID="_2569"><SHORT-NAME>DTC_AGING_CYCLE</SHORT-NAME><LONG-NAME>Healing Cycle</LONG-NAME></SDG-CAPTION><SD>DEM_WARMUP</SD></SDG><SDG><SDG-CAPTION ID="_2570"><SHORT-NAME>DTC_AGING_COUNTER</SHORT-NAME><LONG-NAME>Healing Cycles</LONG-NAME><DESC><p>Cycles necessary to heal/erase event.
Note: Activate 'Self Healing (Aging)' when using this item<br/></p></DESC></SDG-CAPTION><SD>40</SD></SDG><SDG><SDG-CAPTION ID="_2571"><SHORT-NAME>DTC_INIT_MONITOR_REQUIRED</SHORT-NAME><LONG-NAME>Monitor Initialization Function</LONG-NAME><DESC><p>Monitor initialization function is (not) required for this event<br/></p></DESC></SDG-CAPTION><SD>not required</SD></SDG><SDG><SDG-CAPTION ID="_2572"><SHORT-NAME>DTC_PRIORITY_VALUE</SHORT-NAME><LONG-NAME>DTC Priority</LONG-NAME><DESC><p>Priority of an event, in view of full event buffer (ref. to Dem104)<br/></p></DESC></SDG-CAPTION><SD>10</SD></SDG><SDG><SDG-CAPTION ID="_2573"><SHORT-NAME>DTC_SEVERITY_VALUE</SHORT-NAME><LONG-NAME>DTC Severity</LONG-NAME><DESC><p>Reports the recommended action to be taken by the system (e.g. vehicle) operator<br/></p></DESC></SDG-CAPTION><SD>noSeverity</SD></SDG><SDG><SDG-CAPTION ID="_2574"><SHORT-NAME>DTC_DEBOUNCING_ALGORITHM</SHORT-NAME><LONG-NAME>Pre-Debounce Algorithm</LONG-NAME><DESC><p>Selects a Predebounce Algorithm<br/></p></DESC></SDG-CAPTION><SD>Counter based</SD></SDG><SDG><SDG-CAPTION ID="_2575"><SHORT-NAME>DTC_STEP_SIZE_PREFAILED</SHORT-NAME><LONG-NAME>Count-In step size</LONG-NAME><DESC><p>Defines the Step size for incrementation (PREFAILED). Range: 0 - 127<br/></p></DESC></SDG-CAPTION><SD>1</SD></SDG><SDG><SDG-CAPTION ID="_2576"><SHORT-NAME>DTC_STEP_SIZE_PREPASSED</SHORT-NAME><LONG-NAME>Count-out step size</LONG-NAME><DESC><p>Defines the Step size for decrementation (PREPASSED). Range 0 - 127<br/></p></DESC></SDG-CAPTION><SD>1</SD></SDG><SDG><SDG-CAPTION ID="_2577"><SHORT-NAME>DTC_JUMP_UP_PREFAILED</SHORT-NAME><LONG-NAME>Use Jump-Up (Prefailed)</LONG-NAME><DESC><p>Switch for the activation of Jump-UP:
Jump to Zero upon a change of the reported result (i.e. when after a sequence of 'prepassed' the result changes to 'prefailed')<br/></p></DESC></SDG-CAPTION><SD>Yes</SD></SDG><SDG><SDG-CAPTION ID="_2578"><SHORT-NAME>DTC_JUMP_DOWN_PREPASSED</SHORT-NAME><LONG-NAME>Use Jump-Down (Prepassed)</LONG-NAME><DESC><p>Switch for the activation of Jump-Down – only in combination with Jump-UP activation:
Jump to Zero upon a change of the reported result (i.e. when after a sequence of 'prefailed' the result changes to 'prepassed')<br/></p></DESC></SDG-CAPTION><SD>Yes</SD></SDG><SDG><SDG-CAPTION ID="_2579"><SHORT-NAME>DTC_WARNING_INDICATOR_FLAG</SHORT-NAME><LONG-NAME>Set WarningIndicatorBit at fault</LONG-NAME><DESC><p>Yes - the warningIndicatorRequested bit (bit 7) will be set at the same time as the confirmedDTC bit (bit 3) is set.
No - the warningIndicatorRequested bit (bit 7) is 0 at all times. <br/></p></DESC></SDG-CAPTION><SD>supported</SD></SDG><SDG><SDG-CAPTION ID="_2580"><SHORT-NAME>DTC_FUNCTIONAL_UNIT_VALUE</SHORT-NAME><LONG-NAME>Functional Unit</LONG-NAME><DESC><p>Can be used to identify the corresponding basic vehicle / system function which monitors this DTC.<br/></p></DESC></SDG-CAPTION><SD>0xFF</SD></SDG><SDG><SDG-CAPTION ID="_2581"><SHORT-NAME>DTC_TIMEOUT_VALUE_PREFAILED</SHORT-NAME><LONG-NAME>DTC Debounce Failed Timeout Value</LONG-NAME><DESC><p>This parameter defines the time [ms] for event failed qualification of the DTC specific time based debouncing.<br/></p></DESC></SDG-CAPTION><SD>0</SD></SDG><SDG><SDG-CAPTION ID="_2582"><SHORT-NAME>DTC_TIMEOUT_VALUE_PREPASSED</SHORT-NAME><LONG-NAME>DTC Debounce Passed Timeout Value</LONG-NAME><DESC><p>This parameter defines the time [ms] for event passed qualification of the DTC specific time based debouncing.<br/></p></DESC></SDG-CAPTION><SD>0</SD></SDG></SDGS>
</DTC>
<--返回「UDS/OBD诊断需求编辑工具」博文-总目录-->
<--返回「UDS/OBD诊断需求编辑工具」专栏主页-->
5 结尾
获取更多“汽车电子资讯”和“工具链使用”,
请关注“汽车电子助手”(CSDN和微信公众号同名),做您的好助手。
【CANdelaStudio编辑CDD】-0.3-CDD中Fault Memory里DTC Column与Autosar Dem对应关系相关推荐
- CANdelaStudio编辑诊断描述CDD文件(最详细)
CANdela诊断描述(CANdela Diagnostic Descriptions,CDD)文件是诊断数据的数据库,与用于CAN消息和信号描述文件DBC(Data Base CAN)文件相当.CD ...
- 一、CDD在诊断开发中的作用
本专栏将由浅入深的展开诊断实际开发与测试的数据库编辑,包含大量实际开发过程中的步骤.使用技巧与少量对Autosar标准的解读.希望能对大家有所帮助,与大家共同成长,早日成为一名车载诊断.通信全栈工程师 ...
- ASP.NET 2.0 正式版中无刷新页面的开发
ASP.NET 2.0 正式版中无刷新页面的开发 在已经发布的 ASP.NET2.0 中,无刷新页面开发相关部分同 beta2 有不少改动.而且在越来越多的 Ajax 开发包被开发出来的情况下, AS ...
- .NET Core 3.0 Preview 6中对ASP.NET Core和Blazor的更新
我们都知道在6月12日的时候微软发布了.NET Core 3.0的第6个预览版.针对.NET Core 3.0的发布我们国内的微软MVP-汪宇杰还发布的官翻版的博文进行了详细的介绍.具体的可以关注&q ...
- .NET Framework 4.0 和 Dublin 中的 WCF 和 WF 服务 - z
在 2008 年 10 月份召开的专业开发人员大会 (PDC) 上,Microsoft 发布了有关 Microsoft .NET Framework 4.0 中将要提供的大量改进的详细信息,尤其是在 ...
- .NET Core 3.0 Preview 3中关于ASP.NET Core的更新内容
.NET Core 3.0 Preview 3已经推出,它包含了一系列关于ASP.NET Core的新的更新. 下面是该预览版的更新列表: Razor组件改进: 单项目模板 新的Razer扩展 End ...
- Java_JDK19.0.2_Ubuntu18.04中配合海康工业相机SDK环境搭建
Java_JDK19.0.2_Ubuntu18.04中配合海康工业相机SDK环境搭建 简介 1. JDK环境搭建 JDK下载 JDK环境安装 2. 工业相机环境SDK安装 简介 本文主要介绍在ubun ...
- UG12.0安装 出现 General Fault Exception 是硬件还是软件问题
UG12.0安装 出现 General Fault Exception 是硬件还是软件问题一般有很多种情况: NX初始化错误:General Fault Exception,的意思一般是NX软件安装没 ...
- 关于导出编辑后的PDF文件中目录带框的情况及解决
导出编辑后的PDF文件中目录带框的情况及解决 1.情况描述 1.1. 使用软件 1.2. 操作过程 2.解决办法 3.说明 1.情况描述 1.1. 使用软件 1.Word 2016 2.金山PDF专业 ...
- java grpc 服务路由_.NET Core 3.0 Preview 3中关于ASP.NET Core的更新内容
原标题:.NET Core 3.0 Preview 3中关于ASP.NET Core的更新内容 英文:devblogs.microsoft.com 来源:艾心 译文:cnblogs.com/ediso ...
最新文章
- jdk 1.8 concurrenthashmap扩容原理
- 沃顿商学院:价格杠杆,企业竞争的底层逻辑
- 【项目管理】各种常用工具图表说明和示例
- idea代码补全_不想得手指关节炎?帮你提炼IDEA常用代码补全操作
- Excel的python读写
- 手把手图文并茂教你发布Android开源库
- Caffe傻瓜系列(8):命令行解析
- latex 导出的pdf生成书签 目录
- ubuntu下安装matlab及配置vot-toolkit
- 【语音处理】时域信号分析基本工具,什么是窗函数
- android 全屏时钟,手机全屏数字时钟软件
- linux打开pkg文件怎么打开,linux中怎么打开tar.rar.gz文件
- uni-app 登录功能(2)
- 【Monte Carlo】一种器件参数变化分析
- 无需安装软件架设NOD32升级服务器指南!
- 腾讯消消乐 状压dp加普通dp
- Revit二次开发之绘制钢筋
- 《MATLAB 神经网络43个案例分析》:第32章 小波神经网络的时间序列预测——短时交通流量预测
- css背景图做水印,css给图片添加水印的方法
- PowerPoint2019删除当前ppt页上的某个动画