OpenTestSystem.Otx.Extensions.DiagCom.DataTypes Namespace Reference

Data types, see also Core data types. More...

Classes
class	ComChannel
	Communication Channel More...
class	DiagService
	Diagnostic Service More...
class	Message
	ECU messages More...
class	Parameter
	A handle to a parameter object More...
class	ParameterContainer
	The ParameterContainer is an abstract data type which subsumes all data types that contain parameters, i.e. Parameter and Message handles. More...
class	Request
	A handle to a request More...
class	Response
	A handle to a response object More...
class	ResponseState
	ResponseState is an enumeration type describing the state of a Response. More...
class	Result
	A handle to the result More...
class	ResultState
	ResultState is an enumeration type describing the state of a Result. More...

Enumerations
enum class	ResponseStates { FAILED , INVALID , POSITIVE , NEGATIVE }
	ResponseState is an enumeration type describing the state of a Response. More...
enum class	ResultStates {   ALL_INVALID , ALL_NEGATIVE , ALL_POSITIVE , ALL_FAILED ,   FAILED , INVALID , NEGATIVE , POSITIVE }
	ResultState is an enumeration type describing the state of a Result. More...

Detailed Description

Data types, see also Core data types.

Enumeration Type Documentation

ResponseStates

enum OpenTestSystem.Otx.Extensions.DiagCom.DataTypes.ResponseStates

strong

ResponseState is an enumeration type describing the state of a Response.

Enumerator
FAILED	It refers the case when the ECU failed to answer.
INVALID	It refers the case when the ECUs returned an invalid response.
POSITIVE	It refers the case when the ECUs returned a positive response.
NEGATIVE	It refers the case when the ECUs returned a negative response.

ResultStates

enum OpenTestSystem.Otx.Extensions.DiagCom.DataTypes.ResultStates

strong

ResultState is an enumeration type describing the state of a Result.

Enumerator
ALL_INVALID	All ECUs in a functional group (listening to the same functional address) returned an invalid answer, in case of physical addressing: the one requested ECU returned an invalid response. In case of a MVCIServer, it will be mapped with MCDExecutationState: eALL_INVALID_RESPONSE.
ALL_NEGATIVE	All ECUs in a functional group (listening to the same functional address) returned a negative response, in case of physical addressing: the one requested ECU returned a negative response. In case of a MVCIServer, it will be mapped with MCDExecutationState: eALL_NEGATIVE.
ALL_POSITIVE	All ECUs in a functional group (listening to the same functional address) returned a positive response, in case of physical addressing: the one requested ECU returned a positive response. In case of a MVCIServer, it will be mapped with MCDExecutationState: eALL_POSITIVE.
ALL_FAILED	All ECUs in a functional group (listening to the same functional address) failed to answer, in case of physical addressing: the one requested ECU failed to answer. In case of a MVCIServer, it will be mapped with MCDExecutationState: eALL_FAILED.
FAILED	Some of the ECUs in a functional group (listening to the same functional address) failed to answer. In case of a MVCIServer, it will be mapped with MCDExecutationState: eCANCELED_DURING_EXECUTION or eCANCELED_FROM_QUEUE or eFAILED.
INVALID	Some of the ECUs in a functional group (listening to the same functional address) returned an invalid response. In case of a MVCIServer, it will be mapped with MCDExecutationState: eINVALID_RESPONSE.
NEGATIVE	Some of the ECUs in a functional group (listening to the same functional address) returned a negative response. In case of a MVCIServer, it will be mapped with MCDExecutationState: eNEGATIVE.
POSITIVE	It refers the case when some of the ECUs in a functional group (listening to the same functional address) returned a positive response. The POSITIVE value will never occur.