OTX Reference  
OpenTestSystem.Otx.Extensions.DiagComPlus.Actions.ExecuteHexDiagServiceFunctional Class Reference

Sending of diagnostic services More...

Inheritance diagram for OpenTestSystem.Otx.Extensions.DiagComPlus.Actions.ExecuteHexDiagServiceFunctional:
Inheritance graph

Public Attributes

ComChannelTerm comChannel
 This element shall reference the handle of the communication channel, which shall be used for communication with the functional (or physical) link. More...
 
ByteFieldTerm request
 This element shall contain the service request as a set of raw bytes. More...
 
MapVariable responses
 This element specifies the OTX Map[String,Bytefield] variable to which the combination of ComChannelIdentifier and raw response bytes of the service shall be assigned. The key of the map is the ComChannelIdentifier. The associated value is the hexadecimal response of the ECU. More...
 
- Public Attributes inherited from OpenTestSystem.Otx.Core.Actions.ActionRealisation
OtxLink validFor
 Validity of ActionRealisation. More...
 

Detailed Description

Sending of diagnostic services

The ExecuteHexDiagServiceFunctional action allows the sending of diagnostic services by directly entering the request byte stream. Unlike the diag:ExecuteHexDiagService action, it can receive responses from different ECUs.

Note
The time that the action will wait for responses is not specified in this action. It depends on the communication parameters of the given diag:ComChannel or the underlying system.
Exceptions
DiagCom.Exceptions.LossOfComExceptionIf communication was interrupted during diagnostic service execution.
Checker rules
CheckerRule.DiagComPlus_Chk001 - correct element types for responses map


Syntax
DiagComPlus.ExecuteHexDiagServiceFunctional(ComChannelTerm comChannel, ByteFieldTerm request, MapVariable responses);
ByteFieldTerm request
This element shall contain the service request as a set of raw bytes.
Definition: DiagComPlus.cs:555
ComChannelTerm comChannel
This element shall reference the handle of the communication channel, which shall be used for communi...
Definition: DiagComPlus.cs:545
MapVariable responses
This element specifies the OTX Map[String,Bytefield] variable to which the combination of ComChannelI...
Definition: DiagComPlus.cs:573
Examples
// Local Declarations
Exception Exception1;
DiagCom.ComChannel ComChannel1;
ByteField ByteField1 = &1122;
Map<String, ByteField> MapStringByteField1;
// Flow
ComChannel1 = DiagCom.GetComChannel("LL_GatewUDS", "EV_GatewLear_006", false);
try
{
[#DiagMetaData , <#Data>
<dmd:diagMetaData xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:dmd="http://iso.org/OTX/1.0.0/Auxiliaries/DiagMetaData">
<dmd:comChannelName value = "LL_GatewUDS" />
<dmd:ecuVariantName value = "EV_GatewLear_006" />
</dmd:diagMetaData></#Data>]
DiagComPlus.ExecuteHexDiagServiceFunctional(ComChannel1, ByteField1, MapStringByteField1);
}
catch (DiagCom.LossOfComException Exception1)
{
}

Member Data Documentation

◆ comChannel

ComChannelTerm OpenTestSystem.Otx.Extensions.DiagComPlus.Actions.ExecuteHexDiagServiceFunctional.comChannel

This element shall reference the handle of the communication channel, which shall be used for communication with the functional (or physical) link.

◆ request

ByteFieldTerm OpenTestSystem.Otx.Extensions.DiagComPlus.Actions.ExecuteHexDiagServiceFunctional.request

This element shall contain the service request as a set of raw bytes.

◆ responses

MapVariable OpenTestSystem.Otx.Extensions.DiagComPlus.Actions.ExecuteHexDiagServiceFunctional.responses

This element specifies the OTX Map[String,Bytefield] variable to which the combination of ComChannelIdentifier and raw response bytes of the service shall be assigned. The key of the map is the ComChannelIdentifier. The associated value is the hexadecimal response of the ECU.

Note
Important: If there is more than one ComChannelIdentifier with the same ECU short name, but a different baud rate value: the one that uses the baud rate that is currently being used will be returned.
Important: If there is more than one ComChannelIdentifier with the same communication ID (e.g. CAN ID) and same baud rate, but a different ECU short name only one (not specified which one) of them will be returned. The map will be empty. For example, if the hexadecimal service is configured to suppress positive responses and all connected ECUs respond positively.