OTX Reference  
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:
Inheritance graph

Public Attributes

StringTerm identifier
 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
 Store additional 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.UnknownTargetExceptionIf the identifier does not exist or is invalid
Syntax
ListTerm = DiagDataBrowsingPlus.GetDbEcuVariantList(StringTerm identifier);
StringTerm identifier
Communication channels (logical link) to be constructed. The communication channels must have been co...
Definition: DiagDataBrowsingPlus.cs:1875
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

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.