Difference between revisions of "Extensions.DiagCom.SetComplexComParameter"

From emotive
Jump to navigation Jump to search
 
(8 intermediate revisions by 2 users not shown)
Line 1: Line 1:
−
[[Category:DiagCom]]
+
{{DISPLAYTITLE:OTX '''SetComplexComParameter'''}}[[Category:DiagCom]]
 
== Classification ==
 
== Classification ==
−
{{ClassificationActivity | SetComplexComParameter | Setting of complex communication parameters | [[Action]] | [[DiagCom|OTX DiagCom extension]] | [[ComParameter related actions]] | [[TypeMismatchException]] | - }}
+
{{ClassificationActivity | SetComplexComParameter | Setting of complex communication parameters | [[Action]] | [[Extensions.DiagCom|OTX DiagCom extension]] | [[Extensions.DiagCom#Actions|ComParameter related actions]] | [[Core.DataTypes.ComplexDataType.TypeMismatchException|TypeMismatchException]] | - }}
 +
 
 
== OTL Syntax ==
 
== OTL Syntax ==
 
<syntaxhighlight lang="java" enclose="div" style="font-size: medium;">
 
<syntaxhighlight lang="java" enclose="div" style="font-size: medium;">
−
DiagCom.SetComplexComParameter(ComChannelVariable, Parameter);
+
DiagCom.SetComplexComParameter(ComChannelValue comChannel, ParameterTerm parameter);
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 
== Description ==
 
== Description ==
−
The OTX '''SetComplexComParameter''' action is an enhanced variant of SetComParameter. The difference between these actions is that in this case complex data types can be used.  
+
The OTX '''SetComplexComParameter''' action is an enhanced variant of '''SetComParameter'''. The difference between these actions is that in this case complex data types can be used.  
−
{{Note|In an ODX/MVCI based '''Diagnostic Runtime System''' complex communication parameters to define lists of response IDs required for functional addressing.}}
+
{{Note|In an ODX/MVCI based system, complex communication parameter data types are used to define response ID lists for the functional addressing use case.}}
  
 
== Properties ==
 
== Properties ==
 
{| {{TableHeader}}
 
{| {{TableHeader}}
 
{{TableRowPropertiesHeader}}
 
{{TableRowPropertiesHeader}}
−
{{TableRowPropertie1| ComChannel | [[ComChannel]] | [[Variable]] | - | [1] | Communication Channel (Control unit).}}
+
{{TableRowPropertie1| ComChannel | [[Extensions.DiagCom.ComChannel|ComChannel]] | [[Value]] | - | [1] | This element comprises the communication channel where the communication parameter will be modified.}}
−
{{TableRowPropertie2| Parameter | [[Parameter]] | [[Term]] | - | [0..1] | Structure of the parameter to be changed Communication Saving Meters.}}
+
{{TableRowPropertie2| Parameter | [[Extensions.DiagCom.Parameter|Parameter]] | [[Term]] | - | [1] | This element comprises the parameter structure which will be set.}}
 
|}
 
|}
  
 
== OTL Examples ==
 
== OTL Examples ==
 
<syntaxhighlight lang="java" enclose="div" style="font-size: medium;">
 
<syntaxhighlight lang="java" enclose="div" style="font-size: medium;">
−
DiagCom.ComChannel myComCannel;
+
/// Local Declarations
−
DiagCom.Request req;
+
 
−
DiagCom.Parameter param;
+
DiagCom.ComChannel ComChannel1;
 +
DiagCom.Parameter Parameter1;
 +
 
 +
/// Flow
  
−
myComCannel = DiagCom.GetComChannel("LL_AllEmissRelatUDSSyste", null, false);
+
ComChannel1 = DiagCom.GetComChannel("LL_CentrElectUDS", "EV_BCMCONTI_009", false);
−
req = DiagCom.GetRequest(DiagCom.CreateDiagServiceByName(myComCannel, "DiagnServi_ReadDataByIdentActuaTestStatu"));
+
DiagCom.ExecuteDiagService(DiagCom.CreateDiagServiceByName(ComChannel1, "DiagnServi_ReadDataByIdentActuaTestStatu"), {}, {}, NULL, NULL, false, false);
−
param = DiagCom.GetParameterByPath(req, {"Param_RequeServiId"});
+
Parameter1 = DiagCom.GetComplexComParameter(ComChannel1, "CP_TesterPresentMessage");
−
DiagCom.SetComplexComParameter(myComCannel, param);
+
DiagCom.SetParameterValue(Parameter1, &AAAA);
 +
DiagCom.SetComplexComParameter(ComChannel1, Parameter1);
 
</syntaxhighlight>
 
</syntaxhighlight>
  
 
== See also ==
 
== See also ==
−
[[GetComChannel]] <br/>
+
[[Extensions.DiagCom.GetComChannel|GetComChannel]] <br/>
−
[[SetComParameter]]
+
[[Extensions.DiagCom.ExecuteDiagService|ExecuteDiagService]] <br/>
 +
[[Extensions.DiagCom.GetComplexComParameter|GetComplexComParameter]] <br/>
 +
[[Extensions.DiagCom.SetParameterValue|SetParameterValue]]

Latest revision as of 10:01, 12 September 2019

Classification

Name SetComplexComParameter
Short Description Setting of complex communication parameters
Class Action
Extension OTX DiagCom extension
Group ComParameter related actions
Exceptions TypeMismatchException
Checker Rules -
Standard Compliant Yes

OTL Syntax

DiagCom.SetComplexComParameter(ComChannelValue comChannel, ParameterTerm parameter);

Description

The OTX SetComplexComParameter action is an enhanced variant of SetComParameter. The difference between these actions is that in this case complex data types can be used.

Icons Note.png In an ODX/MVCI based system, complex communication parameter data types are used to define response ID lists for the functional addressing use case.

Properties

Name Data Type Class Default Cardinality Description
ComChannel ComChannel Value - [1] This element comprises the communication channel where the communication parameter will be modified.
Parameter Parameter Term - [1] This element comprises the parameter structure which will be set.

OTL Examples

/// Local Declarations

DiagCom.ComChannel ComChannel1;
DiagCom.Parameter Parameter1;

/// Flow

ComChannel1 = DiagCom.GetComChannel("LL_CentrElectUDS", "EV_BCMCONTI_009", false);
DiagCom.ExecuteDiagService(DiagCom.CreateDiagServiceByName(ComChannel1, "DiagnServi_ReadDataByIdentActuaTestStatu"), {}, {}, NULL, NULL, false, false);
Parameter1 = DiagCom.GetComplexComParameter(ComChannel1, "CP_TesterPresentMessage");
DiagCom.SetParameterValue(Parameter1, &AAAA);
DiagCom.SetComplexComParameter(ComChannel1, Parameter1);

See also

GetComChannel
ExecuteDiagService
GetComplexComParameter
SetParameterValue

Retrieved from "http://emotive.de/wiki/index.php?title=Extensions.DiagCom.SetComplexComParameter&oldid=9660"