Difference between revisions of "Extensions.DiagComPlus"
Jump to navigation
Jump to search
(Edited by Ngoc Tran.) |
(Edited by Ngoc Tran. Add: Checker rules) |
||
| Line 36: | Line 36: | ||
{{TableRowKeyValueList|[[Extensions.DiagComPlus.DiagComPlusException|DiagComPlusException]]|}} | {{TableRowKeyValueList|[[Extensions.DiagComPlus.DiagComPlusException|DiagComPlusException]]|}} | ||
| + | |||
| + | |} | ||
| + | |||
| + | == Checker Rules == | ||
| + | {| {{TableHeader}} | ||
| + | |||
| + | {{TableRowKeyValueList|[[Extensions.DiagComPlus.DiagComPlusChk001|DiagComPlus_Chk001]]|Correct element types for responses map in [[Extensions.DiagComPlus.ExecuteHexDiagServiceFunctional|ExecuteHexDiagServiceFunctional]]. }} | ||
|} | |} | ||
Revision as of 04:21, 12 November 2019
Contents
Classification
| Name | DiagComPlus |
| Short Description | Extended to a functional addressing level (means more than one ECU is involved). |
| Class | OTX Extension |
| Base Extension | - |
| Pre-Conditions | - |
| Specified by | ISO 13209-4 |
Introduction
In ISO 13209-3 the extension DiagCom is specified, but the functionality of this extension is limited. There is no possibility to send a functional hexadecimal diagnostic service because with the diag:ExecuteHexDiagService action of part 3 only one response can be received.
The execution of hexadecimal diagnostic services is extended to a functional addressing level, this means more than one ECU is involved. Additionally, a term is introduced, that enables creating a diag:ComChannel to a base variant without starting the communication, in case of an underlying MCD system.
Actions
| ExecuteHexDiagServiceFunctional | |
| StartCommunication | |
| StopCommunication |
Terms
| CreateComChannel | |
| GetComChannelState | |
| GetComParameterList |
Data Types
| ComChannelStates |
Exceptions
| DiagComPlusException |
Checker Rules
| DiagComPlus_Chk001 | Correct element types for responses map in ExecuteHexDiagServiceFunctional. |
