Search
27 result(s) for ExtensionObject
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model8.48 StructureDefinitionDataType is only used inside nested Structures and is not directly contained in an ExtensionObject , the DefaultEncodingId is allowed to be null. If the DataType is abstract the DefaultEncodingId shall
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.38.2 Common StatusCodesrequested operation. Bad_CommunicationError A low level communication error occurred. Bad_DataTypeIdUnknown The ExtensionObject cannot be (de)serialized because the data type id is not recognized. Bad_DecodingError Decoding halted
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services7.40.2.3 EncryptedSecret FormatTypeId of a DataType Node as a prefix as defined for the ExtensionObject encoding in OPC 10000-6 . The general layout of the EncryptedSecret is shown in Figure 39 . Figure ... Table 183 . The first three fields TypeId , EncodingMask and Length belong to the ExtensionObject encoding defined in OPC 10000-6 . Table 183 - EncryptedSecret layout Name Type Description TypeId NodeId
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model12.34 EnumDescriptionDataType is an Enumeration . If the builtInType is one of the UInteger DataTypes or ExtensionObject , the DataType is an OptionSet . Its representation in the AddressSpace is defined in Table
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model12.36 UABinaryFileDataTypeBinary encoded file. The content of the file is the UABinaryFileDataType encoded as ExtensionObject . The file-specific metadata is provided by the DataTypeSchemaHeader which is the base type
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.1.2 Built-in Typesfields set to default. Human readable text with an optional locale identifier. 22 ExtensionObject Yes All fields set to default. A structure that contains an application specific data type that ... abstract types defined in OPC 10000-3 and OPC 10000-4 . However, the ExtensionObject and Variant types are defined in this document. In addition, this document defines a representation
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.1.7 Structures and Unionspresent in the field. In these cases, the values are serialized as an ExtensionObject. If IsOptional =FALSE then the field value is encoded directly according to the rules ... IsOptional field is to be interpreted. A field is serialized as an ExtensionObject if a field has a DataType set explicitly to Structure. Unions are special subtypes of Structure where
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.1.8 ExtensionObjectExtensionObject An ExtensionObject is a container for any Structure and Union DataTypes . The ExtensionObject contains a complex value serialized as a sequence of other DataTypes. It also contains an identifier ... Structure where AllowSubTypes =TRUE (see F.12 ). In all of these cases, the ExtensionObject provides an identifier that allows a decoder to know if it understands the Structure contained with
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.1.9 VariantVariant A Variant is a union of all built-in data types including an ExtensionObject . Variants can also contain arrays of any of these built-in types. Variants are used
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.1.10 DecimalDecimal is encoded in a Variant the built-in type is set to ExtensionObject . Decoders that do not understand the Decimal type shall treat it like any other unknown Structure ... Structure then the type description shall set the DataType for the field to ExtensionObject
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.2.1 Generaladvance knowledge of the services and structures that they support. An exception is an ExtensionObject which provides an identifier and a size for the Structured DataType structure it represents. This
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.2.2.15 ExtensionObjectExtensionObject An ExtensionObject is encoded as sequence of bytes prefixed by the NodeId of its DataTypeEncoding , the DataEncoding used and the number of bytes encoded. An ExtensionObject may be serialized ... number of bytes in the object before it encodes the bytes. However, an ExtensionObject knows how to encode/decode itself which means the encoder shall calculate the number of bytes before
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.2.6 Structuresencoded as 28-byte sequence. If the instance of Type1 was encoded in an ExtensionObject it would have an additional prefix shown in Table 29 which would make the total ... length 101 bytes. The TypeId , Encoding and the Length are fields defined by the ExtensionObject . The encoding of the Type2 instances do not include any type identifier because
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappingsbyte sequence. If the instance of TypeA was encoded in an ExtensionObject it would have the encoded form shown in Table 32 and have a total length of 22 bytes ... length of the TypeId , Encoding and the Length are fields defined by the ExtensionObject . Table 32 - Sample OPC UA Binary Encoded Structure with optional fields Field Bytes Value Type
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.2.8 Unionsbyte sequence. If the instance of Type 1 was encoded in an ExtensionObject it would have the encoded form shown in Table 33 and it would have a total length ... bytes. The TypeId , Encoding and the Length are fields defined by the ExtensionObject . Table 33 - Sample OPC UA Binary Encoded Structure Field Bytes Value Type Id 4 The identifier
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.3.1.9 XmlElement (Deprecated)sequence> </xs:complexType> XmlElements may only be used inside Variant or ExtensionObject values
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.3.1.16 ExtensionObjectExtensionObject An ExtensionObject value is encoded as an xs:complexType with the following XML schema: <xs:complexType name="ExtensionObject"> <xs:sequence> <xs:element ... element> </xs:sequence> </xs:complexType> The body of the ExtensionObject contains a single element which is either a ByteString or XML encoded Structure . A decoder
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.3.2 DecimalDecimal DataType . When encoded in a Variant the Decimal is encoded as an ExtensionObject . Arrays of Decimals are Arrays of ExtensionObjects . The Value is a base-10 signed integer with
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.4.1 GeneralThese fields are not omitted when serialization uses abstract DataTypes such as Structure (i.e. ExtensionObject ) or BaseDataType (i.e. Variant ). OPC 10000-14 specifies the behaviour if a Publisher is misconfigured
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.4.2.16 ExtensionObjectExtensionObject The ExtensionObject is encoded as a JSON object as described in: Structure (see 5.4.6 ); Structure with optional fields (see 5.4.7 ); Union (see 5.4.8 ); with the UaTypeId field inserted into ... present if these fields are used. The JSON object fields used for an ExtensionObject are in Table 40 . Table 40 - JSON Object Fields used for an ExtensionObject Name Description UaTypeId
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.4.3 Decimalfields. When encoding in a Variant , a Decimal value shall be encoded as an ExtensionObject with the JSON object in Table 43 as the Body . The TypeId shall
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings7.4.4 Binary EncodingLength: nnnn The Message body is the request or response structure encoded as an ExtensionObject in OPC UA Binary. The Authorization header is only used for Session-less Service calls
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.13 DataTypeFieldsubtypes of the DataType . If TRUE, all subtypes of Structure are encoded as an ExtensionObject (see 5.1.6 ) and all DataTypes that are not subtypes of Structure are encoded
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsH.7 ExtensionObjectExtensionObject For the ReversibleEncoding , ExtensionObject values shall be encoded as a JSON object with the fields shown in Table H.6 . Table H.6 - JSON Object Definition for an ExtensionObject Name Description ... string. This field is omitted if the value is 0. Body Body of the ExtensionObject . The type of this field is specified by the Encoding field. If the Body
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services7.8.2.1 TrustListTypeinstance of TrustListDataType (see 7.8.2.8 ). The encoded structure is not wrapped in an ExtensionObject . The Size Property inherited from FileType has no meaning for TrustList and returns the error code
-
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub6.2.3.2.4 FieldMetaDataDataType referenced through the dataType field. (3) Structure and Union DataTypes are encoded as ExtensionObject . The encoding rules are defined through a DataType referenced through the dataType field. (4) DataTypes ... concrete UInteger DataTypes or as an instance of an OptionSetType in an ExtensionObject . DataType NodeId The NodeId of the DataType of this field. If the DataType is an Enumeration
-
OPC-10030 – OPC Unified Architecture - Common Object Model: ISA-957.5.4 ISA95TestResultTypebefore it is transmitted on the wire. The generic Structure DataType results in an ExtensionObject being placed on the wire. The default defined sub-type is either ISA95TestResultDataType or ISA95TestResultMeasurementDataType