Search
13 result(s) for MDISDiscreteInstrumentObjectType
-
OPC-30020 – MDIS OPC UA Companion SpecificationMDISDiscreteInstrumentObjectType Definition Table 7 defines the structure of an MDISDiscreteInstrumentObjectType . Any vendor specified properties that have been implemented within a project should be documented within a similar format and supplied ... vendor. The addition of vendor specific properties will result in a subtype of the MDISDiscreteInstrumentObjectType . Table 7 - MDISDiscreteInstrumentObjectType Definition Attribute Value BrowseName MDISDiscreteInstrumentObjectType IsAbstract False References Node Class BrowseName DataType
-
OPC-30020 – MDIS OPC UA Companion SpecificationMDISDiscreteInstrumentObjectType The MDISDiscreteInstrumentObjectType (see 6.3 ) is a base type and can be subtyped or instances of it can be directly created. The Object can be used with multi-state type
-
OPC-30020 – MDIS OPC UA Companion SpecificationMDISDiscreteOutObjectType The MDISDiscreteOutObjectType (see 6.3.4 ) is a subtype of MDISDiscreteInstrumentObjectType and can be subtyped or instance of it can be directly created. The Object can be used for Tristate
-
OPC-30020 – MDIS OPC UA Companion SpecificationMDISDiscreteArbitrationObjectType The MDISDiscreteArbitrationObjectType (see 6.3.6 ) is a subtype of MDISDiscreteInstrumentObjectType and can be subtyped or instance of it can be directly created. It adds inputs that can be selected according
-
OPC-30020 – MDIS OPC UA Companion Specification6.3.1 IntroductionIntroduction The following section details the generic MDISDiscreteInstrumentObjectType structure and defines the properties associated with it. Additional sections define a subtype MDISDiscreteOutObjectType that allows updates to the discrete value. This ... general a vendor and operator independent description, but all users of the MDISDiscreteInstrumentObjectType or MDISDiscreteOutObjectType can add vendor specific data. The vendor specific data should be defined as part
-
OPC-30020 – MDIS OPC UA Companion Specification6.3.2 OverviewOverview The following section details the MDIS generic properties for the MDISDiscreteInstrumentObjectType . Implementation shall ensure adherence to Mandatory [M] aspects in order to comply with the MDIS interface standardisation. Optional ... implemented within a project. Figure 11 provides an overview of the MDISDiscreteInstrumentObjectType as defined by MDIS, including some nested types. This figure includes all items that are inherited from
-
OPC-30020 – MDIS OPC UA Companion SpecificationBrowseName MDISDiscreteArbitrationObjectType IsAbstract False References Node Class BrowseName DataType TypeDefinition Other Subtype of the MDISDiscreteInstrumentObjectType 0:HasComponent Variable SourceA 0:UInt32 0:BaseDataVariableType M, RO 0:HasComponent Variable SourceB ... value does not apply to this arbitration ObjectType . The MDISDiscreteArbitrationObjectType is a subtype of MDISDiscreteInstrumentObjectType and inherit the FaultCode Variable . The MDISDiscreteArbitrationObjectType defines the standard FaultCodes (for bits
-
OPC-30020 – MDIS OPC UA Companion SpecificationHasComponent Object <DigitalArbitrationPlaceholder> MDISDigitalArbitrationObjectType OP 0:HasComponent Object <DiscretePlaceholder> MDISDiscreteInstrumentObjectType OP 0:HasComponent Object <DiscreteOutPlaceholder> MDISDiscreteOutObjectType OP 0:HasComponent Object <DiscreteArbitrationPlaceholder> MDISDiscreteArbitrationObjectType ... subtype. Each object instance shall have a unique BrowseName and must be of MDISDiscreteInstrumentObjectType or a subtype of it. <DiscreteOutPlaceholder> denotes that a subtype of this ObjectType
-
OPC-30020 – MDIS OPC UA Companion Specificationmodels defined in section 6 and listed below: MDISInstrumentObjectType MDISInstrumentOutObjectType MDISInstrumentArbitrationObjectType MDISDigitalInstrumentObjectType MDISDigitalOutObjectType MDISDigitalArbitrationObjectType MDISDiscreteInstrumentObjectType MDISDiscreteOutObjectType MDISDiscreteArbitrationObjectType MDISValveObjectType MDISChokeObjectType MDISElectricChokeObjectType MDISCIMVObjectType MDISMotorObjectType Subtyping MDISBaseObjectType and MDISCounterObjectType is not allowed. Figure ... with any MDIS parent (subtyping MDIS ObjectTypes - MDISValveObjectType , MDISChokeObjectType , MDISElectricChokeObjectType, MDISMotorObjectType, MDISCIMVObjectType, MDISDigitalInstrumentObjectType , MDISInstrumentObjectType , MDISDiscreteInstrumentObjectType or any subtype of these types) No Yes 2) Define new ObjectType with MDISAggregateObjectType
-
OPC-30020 – MDIS OPC UA Companion Specification14.2.2 ServerDiscrete Instrument Server MDIS Discrete Instrument Base Supports the base required aspect of the MDISDiscreteInstrumentObjectType . This includes the State of the Object . Discrete Instrument Out Server MDIS Discrete Out Base ... defines new ObjectTypes that are extensions of the existing MDIS ObjectTypes ( MDISValveObjectType , MDISChokeObjectType , MDISDigitalInstrumentObjectType , MDISDiscreteInstrumentObjectType , MDISInstrumentObjectType or any subtype of these types
-
OPC-30020 – MDIS OPC UA Companion Specification14.2.3 ClientMDIS Discrete Instrument Client Base Makes use of the base required aspect of the MDISDiscreteInstrumentObjectType . This includes the State of the Object . Discrete Out Client MDIS Discrete Out Client Base
-
OPC-30020 – MDIS OPC UA Companion Specification14.3.2.6 MDIS Discrete Model Server Facetthat describes the base characteristics for an OPC UA Server that is exposing the MDISDiscreteInstrumentObjectType model. Table 137 - MDIS Discrete Model Server Facet Group Conformance Unit / Profile Title Optional MDIS
-
OPC-30020 – MDIS OPC UA Companion Specification14.3.3.6 MDIS Discrete Model Client FacetFacet that describes the base characteristics for an OPC UA Client using the MDISDiscreteInstrumentObjectType model. Table 157 - MDIS Discrete Model Client Facet Group Conformance Unit / Profile Title Optional MDIS Base