Difference between revisions of "Extensions.DiagCom.Result"

From emotive
Jump to navigation Jump to search
Line 1: Line 1:
 
{{DISPLAYTITLE:Data Type '''Result'''}}[[Category:DataType]][[Category:DiagCom]]
 
{{DISPLAYTITLE:Data Type '''Result'''}}[[Category:DataType]][[Category:DiagCom]]
 
== Classification ==
 
== Classification ==
{{ClassificationDataType | Result | A handle to the result | [[Core.DataTypes.SimpleDataType|Simple Data Type]] | - | - }}
+
{{ClassificationDataType | Result | A handle to the result | [[Core.DataTypes.SimpleDataType|Simple Data Type]] | [[Core.DataTypes.ComplexDataType.ComplexType|ComplexType]] | - }}
  
 
== Description ==
 
== Description ==

Revision as of 02:30, 24 September 2018

Classification

Name Result
Short Description A handle to the result
Class Simple Data Type
Base Data Type ComplexType
Default Value Empty
Provide a Literal No
SpecifiedBy ISO 13209-3
Standard Compliant Yes

Description

A Result is a handle tothe result of a diagnostic service object.

Icons Note.png In case of a MVCI/ODX based system a Result handle represents a MCDResultobject.

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 Result object String s = ToString(resultVariable); // Returns "1 response(s)"
ToByteField Undefined (should not be used)