Difference between revisions of "Extensions.DiagCom"
Jump to navigation
Jump to search
Line 1: | Line 1: | ||
+ | == Classification == | ||
+ | {| border="0" cellpadding="5" cellspacing="0" | ||
+ | |- style="background: whitesmoke; vertical-align:top;" | ||
+ | |'''Name''' || '''DiagCom''' | ||
+ | |- style="vertical-align:top;" | ||
+ | |'''Short Description''' || Diagnostic vehicle communication | ||
+ | |- style="background: whitesmoke; vertical-align:top;" | ||
+ | |'''Type''' || [[OTX Extension]] | ||
+ | |- style="vertical-align:top;" | ||
+ | |'''Base Extension''' || - | ||
+ | |- style="background: whitesmoke; vertical-align:top;" | ||
+ | |'''Pre-Conditions''' || [[Diagnostic Communication Kernel (MVCI ISO 22900)]] | ||
+ | |} | ||
+ | |||
== Introduction == | == 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: | 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: | ||
Line 115: | Line 129: | ||
| Request related terms | | Request related terms | ||
|- | |- | ||
− | |[[ | + | |[[GetRequest]] || |
|- | |- | ||
− | |[[ | + | |[[GetPdu]] || |
− | |||
− | |||
|- style="font-size:x-small; color:gray" | |- style="font-size:x-small; color:gray" | ||
Line 233: | Line 245: | ||
|- | |- | ||
|[[IncompleteParameterizationException]] || | |[[IncompleteParameterizationException]] || | ||
+ | |||
+ | |} | ||
+ | |||
+ | == Checker Rules == | ||
+ | {| border="0" cellpadding="5" cellspacing="0" | ||
+ | |||
+ | |- | ||
+ | |[[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 | ||
|} | |} |
Revision as of 19:10, 9 July 2014
Contents
Classification
Name | DiagCom |
Short Description | Diagnostic vehicle communication |
Type | OTX Extension |
Base Extension | - |
Pre-Conditions | Diagnostic Communication Kernel (MVCI ISO 22900) |
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 |