Difference between revisions of "Extensions.DiagCom.Response"
Jump to navigation
Jump to search
Line 11: | Line 11: | ||
String=Returns the value of the '''Response''' object | StringSample=<tt>Response response (51 01); String s = ToString(responseVariable); // Returns "51 01"</tt> | String=Returns the value of the '''Response''' object | StringSample=<tt>Response response (51 01); String s = ToString(responseVariable); // Returns "51 01"</tt> | ||
}} | }} | ||
+ | |||
+ | ==Sample== | ||
+ | <syntaxhighlight lang="java" enclose="div" style="font-size: medium;"> | ||
+ | DiagCom.Response ResponseVariable; | ||
+ | </syntaxhighlight> |
Latest revision as of 10:42, 22 October 2018
Classification
Name | Response |
Short Description | A handle to a response object |
Class | Complex Data Type |
Base Data Type | Message |
Default Value | Empty |
Provide a Literal | No |
SpecifiedBy | ISO 13209-3 |
Standard Compliant | Yes |
Description
A Response is a handle to a response object of a diagnostic service’s result.
In case of a MVCI/ODX based system a Response handle represents a MCDResponseobject.
Core Conversion
The following table shows the rules for conversion to another data type:
Conversion | Result | Sample |
ToBoolean | Undefined (should not be used) | |
ToInteger | Undefined (should not be used) | |
ToFloat | Undefined (should not be used) | |
ToString | Returns the value of the Response object | Response response (51 01); String s = ToString(responseVariable); // Returns "51 01" |
ToByteField | Undefined (should not be used) |
Sample
DiagCom.Response ResponseVariable;