Difference between revisions of "Extensions.DiagCom.SetPdu"
Jump to navigation
Jump to search
m (Hb moved page SetPdu to Extensions.DiagCom.SetPdu: #3153) |
|
(No difference)
| |
Revision as of 07:02, 5 February 2016
Classification
| Name | SetPdu |
| Short Description | Set the PDU within a request |
| Class | Action |
| Extension | OTX DiagCom extension |
| Group | ComParameter related actions |
| Exceptions | - |
| Checker Rules | - |
| Standard Compliant | Yes |
OTL Syntax
DiagCom.SetPdu(Request, ByteFieldTerm);Description
With the SetPdu activity a request can be passed directly without further processing a byte stream. 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 |
| Request | Request | Term | - | [1] | Request object. |
| Pdu | ByteField | Term | - | [1] | PDU (z.B.: "18 00 FF FF"). |
OTL Examples
DiagCom.ComChannel myComCannel;
DiagCom.DiagService myDiagService;
DiagCom.Request req;
myComCannel = DiagCom.GetComChannel("LL_AllEmissRelatUDSSyste", null, false);
myDiagService = DiagCom.CreateDiagServiceByName(myComCannel, "DiagnServi_ReadDataByIdentASAMODXFileIdent");
req = DiagCom.GetRequest(myDiagService);
DiagCom.SetPdu(req, &1800FF);