Difference between revisions of "Extensions.DiagCom.ExecuteHexDiagService"
Jump to navigation
Jump to search
m (Hb moved page ExecuteHexDiagService to Extensions.DiagCom.ExecuteHexDiagService: #3153) |
|
(No difference)
| |
Revision as of 07:01, 5 February 2016
Classification
| Name | ExecuteHexDiagService |
| Short Description | Direct send a diagnostic services as a byte stream. |
| Class | Action |
| Extension | OTX DiagCom extension |
| Group | DiagService related actions |
| Exceptions | LossOfComException |
| Checker Rules | - |
| Standard Compliant | Yes |
OTL Syntax
DiagCom.ExecuteHexDiagService(ByteFieldTerm, ByteFieldTerm, ComChannelTerm);Description
With the ExecuteHexDiagSevice activity a byte stream can be sent directly and without further processing to the control unit. The byte stream is referred to as PDU (Protocol Data Unit). The PDU contains the entire block starting with the service identifier (SID), but without header and checksum.
Properties
| Name | Data Type | Class | Default | Cardinality | Description |
| ComChannel | ComChannel | Term | - | [1] | Communication Channel (Control unit). |
| HexRequest | ByteField | Term | - | [1] | Request PDU (z.B.: "18 00 FF FF"). |
| HexResponse | ByteField | Variable | - | [0..1] | Request PDU (zB "FF 58 01 01 08"). |
OTL Examples
DiagCom.ComChannel myComCannel;
ByteField HexResponse1;
myComCannel = DiagCom.GetComChannel("LL_AllEmissRelatUDSSyste", "", false);
DiagCom.ExecuteHexDiagService(&1800FFF0, HexResponse1, myComCannel);