Search
53 result(s) for Values
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model3.1.7 DataVariableDataVariable Variables that represent values of Objects , either directly or indirectly for complex Variables , where the Variables are always the TargetNode of a HasComponent Reference
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model4.5.1 GeneralGeneral Variables are used to represent values . Two types of Variables are defined, Properties and DataVariables . They differ in the kind of data that they represent and whether they
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.2.5 QueryDataSetNode description. typeDefinitionNode ExpandedNodeId The NodeId for the type definition for this Node description. values [] BaseDataType Values for the selected Attributes. The order of returned items matches the order ... were specified using a relative path from the selected instance's TypeDefinitionNode . If no values where found for a given requested item a null value is returned for that item
-
OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings5.1.9 VariantStatusCode and table of strings. As a result, Variants cannot contain instances of DiagnosticInfo. Values of Attributes are always returned in instances of DataValues . Therefore, the DataType of an Attribute
-
OPC-10000-6 – OPC Unified Architecture - Part 6: MappingsF.15 Exampleused for any NodeId value in the document except for NodeIds that appear in Values of Variables or VariableTypes . <Aliases> <Alias Alias="HasComponent
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.2 AlarmConditionTypeprovided. In some systems, an Alarm may be calculated based on multiple Variables Values ; it is up to the system to determine which Variable's NodeId is used. SuppressedState , OutOfServiceState
-
OPC-10000-23 – OPC Unified Architecture - Part 23: Common ReferenceTypes5.1 OverviewReferences are described by a ReferenceDescription , that is, the Variables SomeReferenceType1 and SomeReferenceType2. The Values of those Variables uniquely identify the References by providing SourceNode , TargetNode , ReferenceType and direction
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization3.1.5 SerializationValueSerializationValue the merged compact aggregation of the Values of all serialized Nodes belonging to the SerializationScope and is the Value of the SerializedData Variable
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization3.1.8 SerializationProcessSerializationProcess the mapping of the SerializationValue from and to the Values in the SerializationScope . Note 1 to entry: This can imply the creation or re-creation of the SerializationFieldDataType used
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object SerializationBasic Concept Object Serialization is understood in this specification as the aggregation of the Values of different Variables belonging to a subset of the Information Model ( SerializationScope ) into the Value ... SerializationValue) of a single Variable ( SerializedData ) . Clients gain access to all Values in the SerializationScope at once by accessing the SerializationValue
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object SerializationValue of the SerializedData Variable. The DataType of the SerializationValue maps all Values of the Variables in the SerializationScope (see Figure 3 ). The SerializationProperties are provided by the SerializationEntity ... referenced using certain ReferenceTypes , limiting the depth of the SerializationScope and settings which companion values like statusCodes shall be part of the SerializationFieldDataType of Variables is also possible
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization4.5 General Featurespreserved. Servers can provide different serializations by providing different SerializationEntities , e.g. for process values or for configuration data as shown in Figure 4 . Different SerializationScopes defined on the same data ... SerializationValue with NonatomicWrite flag set to 0, the update of the original Values in the SerializationScope is like a transaction. This means if update of one original Values fails
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serializationshows a Channel Group containing two output channel Objects , a configuration Object and Process Values . Figure 4 - RIO Channel Group From the Clients' perspective, certain use cases when accessing ... subtrees are supported by the Server . A Client might be interested in the Process Values provided in the "Values" array and the associated Process Value Qualifiers
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization6.1 OverviewOverview Object Serialization provides a consistent, compact representation of the Variable Values in the SerializationScope . Objects or Variables that are the root of such a serialization are called SerializationStartNodes ... this ObjectType. The DataType of the SerializedData Variable is the SerializationValue DataType mapping all Values in the SerializationScope . It is the serialization DataType of the SerializationStartNode . The Values themselves each
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object SerializationDataSetMetaData (see OPC 10000-14 ). The field names from the structures containing the Values the semantic Properties belong to are qualified with the OPC UA Namespace . This allows the encoder ... CustomMetaDataProperties Property of the SerializedData Variable describes the semantic Properties for all Values mapped into the SerializationValue DataType of the SerializedData . It is used as Properties field of the FieldMetaData
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serializationthis DataType is serialized by the JSON encoder. If the SerializationProperties have default values, the Properties of the ChannelGroupConfig Object (see OPC RIO) are mapped into fields of the SerializationValue ... JSON encoding of this structure only contains the field names as keys and the Values of the serialized fields as JSON literals when using VerboseEncoding
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object SerializationChannel Process Values Figure A.3 shows how Process Values (see OPC RIO) belonging to RioChannelType Objects are mapped into the SerializationValue DataType . The "SerializationEntity" referenced by the SerializationStartNode ... subtrees originating from the Channel Objects . The JSON snipped shows how the Values in the SerializationScope are serialized using VerboseEncoding (see OPC 10000-6 ) and RawData field encoding
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object SerializationEnergy Measurement Values Figure A.4 shows a SerializationScope configured to exclude the metadata Properties of the Objects and Variables reachable from the SerializationStartNode . The EnergyMeasurementType Object has a mandatory PeObjectNumber ... MeasurementValueType Variables (see OPC PE ) The SerializationValue DataType structure contains only fields for the Values of the MeasurementValueType Variables . The JSON snipped shows how the energy data in the SerializationScope
-
OPC-10000-25 – OPC Unified Architecture - Part 25: Object SerializationStatusCode of the "MeasurementX1", "MeasurementX2" and "MeasurementXn" Variable Values is never encoded into JSON. Figure A.7 - Combining Serialization Scopes
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelE.4.7 PubSub DataSetshave a value that is returned in every message. The message only contains the values, so the Subscriber has to be aware of the order/mapping of Variables in the DataSet ... delta frame, which is very similar to Client Server communication, and only changed values are sent. In this type of DataSetMessage , an index and the value are packaged into
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devicesmanufacturer point of view. They can be used as part of the identification. The Values of these Properties are typically provided by the component vendor. The VendorNameplate Interface is illustrated
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devices8.7.3 Package metadatasoftware package False PackageType 2:PackageType Type of the Software Package . Other values are reserved for future use. False SoftwareSubClass 0:String Name of the application (in case of SoftwareClass ... Identification functional group or its parent device or an application on that device… False Values[] 0:BaseDataType Comparison values (zero, one or more values depending on the comparison operator
-
OPC-10000-110 – OPC Unified Architecture - Part 110: Asset Management Basics13.3.1 Overviewboth information sources in sync, especially when the Property is writable. Servers may reject Values not represented by Objects or may extend the Locations hierarchy
-
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices6.1.3.2 Object IODataVariable Value . OPC UA Clients can read and write Variable Values depending on the AccessLevel of the Variable . Values can also be monitored for changes. The FunctionalGroupType is defined
-
OPC-30010 – OPC UA for AutoId Devices - AutoID: OPC UA for AutoId Devices6.1.3.3 Object Diagnosticsrepresented by an OPC UA Variable Value . OPC UA Clients can read the Variable Values . Values can also be monitored for changes. The FunctionalGroupType is defined ... concrete number of AutoID Identifiers. The Logbook FunctionalGroup shall be provided if Logging values are supported for diagnostic purposes. Its predefined parameters are defined in Table 8 and described
-
OPC-30142 – OPC UA for PROFINET Remote IOinto a PROFINET aspect offering detailed Telegram information and a functional aspect modelling Process Values as part of RIO Channel Objects . The two aspects offer different access paths for Clients
-
OPC-30142 – OPC UA for PROFINET Remote IOInput according to RIOforPA to illustrate the relationship between the different aspects. The Process Values and their qualifiers are transmitted consecutively and are available for the user program ... Value" and "03_AI_2_Value" representing the Process Values in the PnIoTelegramType Object "Input" connect to the "ProcessValue" Variables which are components
-
OPC-30142 – OPC UA for PROFINET Remote IOmodel and a Channel Group according to RIOforFA. The qualifiers of the Output Process Values are transferred as single bits packed into one byte in the Input section ... qualifiers of RIO Output Channels according to RIOforFA are transmitted separated from the values in an Input Signal since qualifiers of RIOforFA Output Channels are provided by the Channel
-
OPC-30142 – OPC UA for PROFINET Remote IOchannel encoded as RioSubstitutePolicyEnumeration . The PaDigitalSubstituteValue bit field Property contains the substitute values for the Process Value of the represented digital RIOforPA channels which shall be used if a failure ... actual value of the SubstitutePolicy Property . The FaDigitalSubstituteValue bit field Property contains the substitute values for the Process Value of the represented digital RIOforFA channels which shall be used
-
OPC-30142 – OPC UA for PROFINET Remote IOConformance Units PNRIO Channel Groups The InputImageValues array Variable contains the Input Process Values of the Input Channels the RIO Channel Group Object represents. The InputImageValues Variable is linked ... Object using a 0:RepresentsSameEntityAs Reference . The OutputImageValues array Variable contains the Output Process Values of the Output Channels the RIO Channel Group Object represents. The OutputImageValues Variable is linked
-
OPC-30142 – OPC UA for PROFINET Remote IOthis case and contain the start of the range the RioBitFieldVariableType Variable represents. Possible Values for Offset are 0, 32, 64, and so on. The Offset Value added
-
OPC-30142 – OPC UA for PROFINET Remote IO7.2.1 RioChannelTypeaggregated by a RIO Channel Group . The value range used for the RioChannelNumber Property Values shall be continuous and start with 0. The ApplicationTag Variable contains information determined by configuration
-
OPC-30142 – OPC UA for PROFINET Remote IO10.2.5 RioAnalogDataTypeRioAnalogDataType This union contains fields of the data types used for analog Values in analog RIO Channels . Table 101 - RioAnalogDataType Union Name Type Description RioAnalogDataType union Float_32 0:Float
-
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>relationship of the Signal Objects in the PROFINET aspect with the Variables providing concrete Values in the functional aspect. The figure shall give a basic understanding by demonstrating the model ... Position" and "Velocity" 0:AnalogUnitRangeType Variables in the "Measurement / Actual Values" sub-aspect contain the numeric representation of the "speed" and "position
-
OPC-30143 – OPC UA for PROFINET Encoder - Part <mm>: <Part Name>delivered by the sensor. The following table specifies the meaning of the possible Values of the Variable in dependence of the sensor type (See [ PDP ] Table 105 Subindex ... Sensors Linear Sensors 0 The sensor has no absolute information or may only display values less than one absolute revolution. The sensor has no absolute information (for example standard incremental
-
OPC-30144 – OPC UA for PROFINET GSD Generic Model - Part 30144: PROFINET GSD Generic Model7.1.1 SetApplicationTag MethodSubmoduleState.IdentInfo block encoded as GsdGenIoConfigurationStatusEnumeration . If the CommunicationStatus Property contains INDATA, possible Values are OK or SUBSTITUTE. If the CommunicationStatus Property contains OFFLINE (see above) for configured Submodules , the Value ... Server shall obtain the current value of the BMP and set the Boolean values in the BitMask array Property , starting with Bit 0 (LSB) of the sequence for the array
-
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drivespart of the four different sub-aspects "Signals", "Actual and Command Values", "Diagnosis" and "Axis Properties". The concrete ObjectTypes representing Axis type ... Axis Objects . Within the Axis Object , the mandatory "Actual and Command Values" sub-aspect is mainly consisting of Variables which contain the setpoint and measurement values
-
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives7.1 DriveAxisTypeFloat 0:AnalogUnitType M, RO The child Nodes of the DriveAxisType have additional Attribute values defined in Table 17 . Table 17 - DriveAxisType Attribute values for child Nodes BrowsePath Value Attribute ... Int16 and 0:Int32 shall be provided. Monitoring folder in Actual and Command Values sub-aspect The Monitoring folder contains Monitoring Variables describing measurements of the Axis/DO which
-
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drivestraversing task is executed ( TraversingTaskNumber >=0), the AxisState Variable contains one of the values belonging to the S45 sub state machine (see [ PI 3172 PDP ], Figure 35 also ... their EnumStrings lookup table Properties is defined in Table 29 . Table 29 - TraversingTaskType Attribute values for child Nodes BrowsePath Value Attribute PositioningMode 0:EnumStrings INACTIVE RELATIVE_POSITIONING ABSOLUTE_SHORTEST_PATH
-
OPC-30145 – OPC UA for PROFINET Drives - Part 30145: UA CS for PROFINET Drives8.1 AxisEventTypeMonitoring" folder (for a description see Table 33 section for Monitoring folder). The Values of these properties shall constitute a snapshot of the Axis/DO state when the Event
-
OPC-40001-2 – OPC UA for Machinery - Part 2: Process ValuesHasComponent Variable AlarmSuppression 0:UInt16 0:MultiStateValueDiscreteType O Conformance Units Machinery Process Values Base Types This ObjectType inherits the InstanceDeclarations defined on its supertypes, including the mandatory 3: SignalTag ... www.opcfoundation.org/UA/units/un/cefact ). This Variable is especially useful when the ranges for calculating the percentage values are dynamic, so that the client cannot calculate the percentage based on the 0: EURange
-
OPC-40001-2 – OPC UA for Machinery - Part 2: Process ValuesVariable it belongs to. The 0: EngineeringUnits , of that Variable shall have the same Values as defined on the Variable it belongs to. The 0: EURange shall be the same ... HasComponent Variable DeviationSensitivity 0:UInt16 0:MultiStateValueDiscreteType O Conformance Units Machinery Process Values Base Types Machinery Process Values Base SetpointType The optional SubstituteValue Variable provides a value that should
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumpsoffered control modes supported by the manufacturer of a Pump in Table 122 . The Values and the associated Descriptions are based on the standard VDMA 24223. Table 122 - OfferedControlModesOptionSet Values
-
OPC-40223 – OPC UA for Pumps and Vacuum PumpsDistributionTypeEnum The enumeration DistributionTypeEnum defines possible Pump distributions in Table 130 . The Values and the associated Descriptions are based on the standard VDMA 24223. Table 130 - DistributionTypeEnum Items Name Value
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumps8.10 ExchangeModeEnumExchangeModeEnum The enumeration ExchangeModeEnum defines possible Pump exchange modes in Table 132 . The Values and the associated Descriptions are based on the standard VDMA 24223. Table 132 - ExchangeModeEnum Items Name
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumps8.12 MaintenanceLevelEnumMaintenanceLevelEnum The enumeration MaintenanceLevelEnum defines possible Pump maintenance levels in Table 136 . The Values and the associated Descriptions are based on the standard DIN EN 13306. Table 136 - MaintenanceLevelEnum Items
-
OPC-40223 – OPC UA for Pumps and Vacuum PumpsMultiPumpOperationModeEnum The enumeration MultiPumpOperationModeEnum defines possible multi Pump operation modes in Table 138 . The Values and the associated Descriptions are based on the standard VDMA 24223. Table 138 - MultiPumpOperationModeEnum Items
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumps8.15 OperationModeEnumOperationModeEnum The enumeration OperationModeEnum defines possible Pump operation modes in Table 142 . The Values and the associated Descriptions are based on the standard VDMA 24223. Table 142 - OperationModeEnum Items Name
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumps8.16 PortDirectionEnumPortDirectionEnum The enumeration PortDirectionEnum defines possible Port directions in Table 144 . The Values and the associated Descriptions are based on the AutomationML semantic. Table 144 - PortDirectionEnum Items Name Value Description
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumps8.17 PumpKickModeEnumPumpKickModeEnum The enumeration PumpKickModeEnum defines possible Pump kick modes in Table 146 . The Values and the associated Descriptions are based on the standard VDMA 24223. Table 146 - PumpKickModeEnum Items Name
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumps8.18 PumpRoleEnumPumpRoleEnum The enumeration PumpRoleEnum defines possible Pump roles in Table 148 . The Values and the associated Descriptions are based on the standard VDMA 24223. Table 148 - PumpRoleEnum Items Name Value
-
OPC-40223 – OPC UA for Pumps and Vacuum Pumps8.19 StateOfTheItemEnumStateOfTheItemEnum The enumeration StateOfTheItemEnum defines possible Pump states in Table 150 . The Values and the associated Descriptions are based on the standard DIN EN 13306. Table 150 - StateOfTheItemEnum Items Name
-
OPC-40550-1 – OPC UA for Woodworking Machines - Part 1: Vertical InterfaceOverview 0:BaseObjectType M 0:HasComponent Object Flags 0:BaseObjectType O 0:HasComponent Object Values 0:BaseObjectType O Conformance Units Woodworking Machine Monitoring Woodworking SubUnits Monitoring Woodworking Unit State ... overview of the unit. The Flags Object provides the flags of the unit. The Values Object provides the counters and values of the unit. The components of the IWwBaseStateType have