OpenTestSystem.Otx.Extensions.DiagDataBrowsingPlus.Terms.GetDbEcuVariantList Class Reference

Returns a list of strings which represents the names of all ECU variants for a given logical link More...

Inheritance diagram for OpenTestSystem.Otx.Extensions.DiagDataBrowsingPlus.Terms.GetDbEcuVariantList:

Public Attributes
StringTerm	identifier
	Cardinality [1] Communication channels (logical link) to be constructed. The communication channels must have been configured within the settings for the diagnostic run-time system, see the settings of the document / project. More...
Public Attributes inherited from OpenTestSystem.Otx.Core.Terms.Term
MetaData	metaData
	Cardinality [0..1] The MetaData type allows tools to store additional, mainly tool-specific data. More...

Detailed Description

Returns a list of strings which represents the names of all ECU variants for a given logical link

The GetDbEcuVariantList activity which returns a list of strings which represents the names of all ECU variants for a given logical link. The identifier shall point to a base variant. If a base variant has no associated ECU variants, an empty list shall be returned. Furthermore, in case the communication channel points to a protocol or functional group, an exception shall be thrown.

Note: The appropriate MVCI system operation is MCDDbLogicalLink::getDbLocation::getDbECU::getDbEcuVariants.

Exceptions

DiagCom.Exceptions.UnknownTargetException	If the identifier does not exist or is invalid
Core.Exceptions.TypeMismatchException	This exception is thrown if the communication channel belongs to the category PROTOCOL or FUNCTIONAL_GROUP.

Syntax

ListTerm = DiagDataBrowsingPlus.GetDbEcuVariantList(StringTerm identifier);

Examples

// Local Declarations
List<String> List_String;
 
// Flow
List_String = DiagDataBrowsingPlus.GetDbEcuVariantList("LL_CentrElectUDS");

Member Data Documentation

identifier

StringTerm OpenTestSystem.Otx.Extensions.DiagDataBrowsingPlus.Terms.GetDbEcuVariantList.identifier

Cardinality [1]
Communication channels (logical link) to be constructed. The communication channels must have been configured within the settings for the diagnostic run-time system, see the settings of the document / project.