Search

Scope: Core (OPC-10000-*) All specs

26 result(s) for Type

OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model

9.11 AuditUrlMismatchEventType

does not match the Server 's HostNames (see OPC 10000-4 for details). This Type has been deprecated and will be removed in a future version
OPC-10000-4 – OPC Unified Architecture - Part 4: Services

7.32 RequestHeader

components of this parameter are defined in Table 171 . Table 171 - RequestHeader Name Type Description RequestHeader structure Common parameters for all requests submitted on a Session . authenticationToken Session AuthenticationToken ... identifier used to verify that the request is associated with the Session. The SessionAuthenticationToken type is defined in 7.35 . timestamp UtcTime The time the Client sent the request. The parameter
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.3.15 NonTransparentBackupRedundancyType

backup redundancy. It is formally defined in Table 24 . A Server represented by this Type shall use the Warm Failover mode defined in OPC 10000-4 . Table 24 - NonTransparentBackupRedundancyType definition
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.4.9 AuditUrlMismatchEventType

representation in the AddressSpace is formally defined in Table 32 . This Type has been deprecated and will be removed in a future version. Table 32 - AuditUrlMismatchEventType definition Attribute Value BrowseName
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

12.45 BitFieldDefinition

VariableType . The BitFieldDefinition is formally defined in Table 308 . Table 308 - BitFieldDefinition Structure Name Type Description BitFieldDefinition Structure Name String A name for the field that is unique within ... BitFieldType shall include, in its BitFieldDefinition all the field definitions of the parent Type . A Subtype of a BitFieldType shall not reallocate bits defined in the parent Type unless they
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.2.17 Variant

Table 41 - JSON Object Definition for a Variant Name Description UaType The built-in type for the value contained in the Body (see Table 1 ) encoded as JSON number. Value ... value is a scalar, it is encoded using the rules for type specified for the Type . If the value is a one-dimensional array it is encoded as JSON array
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.4.1 Compact

encoded as a JSON number. When an Enumeration is encoded in a Variant the Type field is Int32
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

5.4.4.2 Verbose

encoded as a JSON string. When an Enumeration is encoded in a Variant the Type field is a Int32 and the value is encoded as a JSON number
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings

H.8 Variant

shown in Table H.7 . Table H.7 - JSON Object Definition for a Variant Name Description Type The built-in type for the value contained in the Body (see Table 1 ) encoded ... JSON number. If type is 0 (NULL) the Variant contains a NULL value and the containing JSON object shall be omitted or replaced by the JSON literal 'null' (when
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.2 Two-state state machines

value True or False, respectively. Since the two Properties provide meta-data for the Type , Servers shall not allow these Properties to be selected in the Event filter
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.18 LimitAlarmType

used to group multiple states together. The LimitAlarmType is used to provide a base Type for AlarmConditionTypes with multiple limits. The LimitAlarmType is illustrated in Figure 18 . Figure 18 - LimitAlarmType
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.24.4 TripAlarmType

down due to an overload condition. It is formally defined in Table 108 . This Type is mainly used for categorization. Table 108 - TripAlarmType definition Attribute Value BrowseName TripAlarmType IsAbstract False
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.24.5 InstrumentDiagnosticAlarmType

fault such as a sensor failure. It is formally defined in Table 108 . This Type is mainly used for categorization. Table 109 - InstrumentDiagnosticAlarmType definition Attribute Value BrowseName InstrumentDiagnosticAlarmType IsAbstract False
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.8.24.6 SystemDiagnosticAlarmType

monitored system experiences a fault. It is formally defined in Table 108 . This Type is mainly used for categorization. Table 110 - SystemDiagnosticAlarmType definition Attribute Value BrowseName SystemDiagnosticAlarmType IsAbstract False References
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

5.12 HasCondition Reference type

HasCondition Reference type The HasCondition ReferenceType is a concrete ReferenceType and can be used directly. It is a subtype of NonHierarchicalReferences . The representation in the AddressSpace is specified in Table ... Conditions . Each ConditionSource shall be the target of a HasEventSource Reference or a sub type of HasEventSource . The AddressSpace organisation that shall be provided for Clients to detect Conditions
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

9.2 AlarmMetricsType

AlarmMetricsType This Object Type is used for metric information. The ObjectType is formally defined in Table 145 . Table 145 - AlarmMetricsType Definition Attribute Value BrowseName AlarmMetricsType IsAbstract False References NodeClass BrowseName
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions

B.2 AddressSpace examples

illustrated with the example in Figure B.6 . Figure B.6 - HasCondition reference to a Condition type Figure B.7 provides an example where the HasCondition Reference is already defined in the Type ... system. The Reference can point to a Condition Type or to an instance. Both variants are shown in this example. A Reference to a Condition Type in the Type system
OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access

5.4.3 HistoricalEventConfigurationType

HistoricalEventConfigurationType The Historical Access Event model extends the standard type model by defining the HistoricalEventConfigurationType. This Object defines the general characteristics of a Node that defines the historical configuration ... defined to contain history. It is formally defined in Table 11 . Instances of this type shall be referenced by a HistoricalEventNode using the HasHistoricalConfiguration ReferenceType where the source node
OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines

4.6.2 ChoiceStateType

BrowseName ChoiceStateType IsAbstract False References NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of the State Type defined in 4.4.9 Conformance Units Base Info Choice States
OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model

5.5.6 LldpPortInformationType definition

YANG list port in IEEE 802.1Abcu-2021 . IetfBaseNetworkInterfaceName points to an object of type IetfBaseNetworkInterfaceType organized in the NetworkInterfaces folder with the value of the String . This link ... visualizes this reference. DestMacAddress defines the MAC address of this network interface. PortIdSubtype defines type of encoding used to identify the associated PortId , as defined in clause 8.5.3.2 of IEEE
OPC-10000-22 – OPC Unified Architecture - Part 22: Base Network Model

5.5.7 LldpRemoteSystemType definition

defined in clause 11.5.1 of IEEE Std 802.1AB-2016 : lldpV2RemIndex. ChassisIdSubtype defines type of encoding used to identify the chassis associated with the remote system, as defined in clause ... system, as defined in clause 8.5.2.3 of IEEE Std 802.1AB-2016 . PortIdSubtype defines type of encoding used to identify the associated PortId , as defined in clause 8.5.3.2 of IEEE
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

7.4 IAssetExtensionsType Interface definition

Diagnostics 5:FunctionalGroupType O ConformanceUnits UAFX Asset Base The components of the IAssetExtensions Type have additional subcomponents, which are defined in Table 108 . Table 108 - IAssetExtensionsType additional subcomponents BrowsePath References
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

4.11 BlockType

instances of a BlockType itself, but there will be instances of subtypes of this Type . In this specification, the term Block generically refers to an instance of any subtype
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices

9.2.1 General pattern

SupportedTypes folder on the instance can be different to the one on the Type and can contain only a subset. It can be for example that only one instance ... each Type can be configured. In this case the list of supported Types will shrink with each configured component
OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping

3.3.1.1 Node definitions

only a Comment column is introduced to point to the Node definition. Each Type Node or well-known Instance Node defined shall have one or more ConformanceUnits defined ... DataTypeDefinition Attribute are also dependencies. For additional details see OPC 10000-5 . Table 2 - Type Definition Table Attribute Value Attribute name Attribute value. If it is an optional Attribute that
OPC-10000-211 – OPC Unified Architecture - Part 211: Global Positioning

3.4.1.1 Node definitions

only a Comment column is introduced to point to the Node definition. Each Type Node or well-known Instance Node defined shall have one or more ConformanceUnits defined ... DataTypeDefinition Attribute are also dependencies. For additional details see OPC 10000-5 . Table 2 - Type Definition Table Attribute Value Attribute name Attribute value. If it is an optional Attribute that