Difference between revisions of "Extensions.DiagCom"
Jump to navigation
Jump to search
Line 16: | Line 16: | ||
== Actions == | == Actions == | ||
− | |||
− | |||
− | |||
{| {{TableHeader}} | {| {{TableHeader}} | ||
+ | {{TableRowCatagory|ComChannel related actions}} | ||
+ | {{TableRowKeyValueList|[[IdentifyAndSelectVariant]]|}} | ||
+ | {{TableRowKeyValueList|[[CloseComChannel]]|}} | ||
− | + | {{TableRowCatagory|ComParameter related actions}} | |
− | + | {{TableRowKeyValueList|[[SetComParameter]]|}} | |
− | + | {{TableRowKeyValueList|[[SetComplexComParameter]]|}} | |
− | |||
− | |||
− | |||
− | |||
− | |||
− | | ComParameter related actions | ||
− | |||
− | |[[SetComParameter]] | | ||
− | |||
− | |[[SetComplexComParameter]] | | ||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
− | |||
+ | {{TableRowCatagory|DiagService related actions}} | ||
+ | {{TableRowKeyValueList|[[ExecuteDiagService]]|Sending a diagnostic services to the ECU.}} | ||
+ | {{TableRowKeyValueList|[[ExecuteHexDiagService]]|}} | ||
+ | {{TableRowKeyValueList|[[StartRepeatedExecution]]|}} | ||
+ | {{TableRowKeyValueList|[[StopRepeatedExecution]]|}} | ||
+ | {{TableRowKeyValueList|[[SetRepetitionTime]]|}} | ||
+ | {{TableRowKeyValueList|[[GetAllResultsAndClear]]|}} | ||
+ | {{TableRowKeyValueList|[[SetParameterValue]]|}} | ||
+ | {{TableRowKeyValueList|[[SetParameterValueBySemantic]]|}} | ||
+ | {{TableRowKeyValueList|[[SetPdu]]|}} | ||
|} | |} | ||
Revision as of 23:30, 9 July 2014
Contents
Classification
Name | {{{1}}} |
Short Description | {{{2}}} |
Class | {{{3}}} |
Base Extension | {{{4}}} |
Pre-Conditions | {{{5}}} |
Specified by | ISO 13209-3 |
Introduction
The purpose of the OTX DiagCom extension is to provide the necessary OTX elements for performing diagnostic vehicle communication. Specifically, the following diagnostic use cases have been considered:
- Handling of ECU communication channels
- Execution of a diagnostic service
- Setting of service request parameters and evaluation of service response parameters
- Dealing with positive or various negative responses of a diagnostic service
- Handling of communication channel protocol parameters
- Performing variant identification of an ECU
- Functionally addressed diagnostic services: more than one ECU will respond to a request
- Repeated/cyclic execution of diagnostic services: a single request will result in multiple responses from the same ECU
- A potential combination of functional addressing and cyclic service execution: multiple ECUs responding multiple times to one request
- Complex data structures within the requests and responses of diagnostic services: structures of parameters, lists of parameters, lists containing structures of parameters
Actions
ComChannel related actions | |
IdentifyAndSelectVariant | |
CloseComChannel | |
ComParameter related actions | |
SetComParameter | |
SetComplexComParameter | |
DiagService related actions | |
ExecuteDiagService | Sending a diagnostic services to the ECU. |
ExecuteHexDiagService | |
StartRepeatedExecution | |
StopRepeatedExecution | |
SetRepetitionTime | |
GetAllResultsAndClear | |
SetParameterValue | |
SetParameterValueBySemantic | |
SetPdu |
Terms
Data Types
ComChannel | |
DiagService | |
Result | |
ParameterContainer | |
Parameter | |
Message | |
Response | |
Request | |
ResultState | |
ResponseState |
Exceptions
DiagComException | |
AmbiguousSemanticException | |
UnknownTargetException | |
LossOfComException | |
UnknownResponseException | |
UnknownComChannelException | |
InvalidStateException | |
IncompleteParameterizationException |
Checker Rules
DiagCom_Chk001 | No Path in ExecuteDiagService response parameter arguments |
DiagCom_Chk100 | Access path can not be determined |
DiagCom_Chk101 | Access path can not be resolved |
DiagCom_Chk102 | Targets of the access paths are not the same structure |