Search
12 result(s) for QueryDataSet
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.2.5 QueryDataSetB.2.5 QueryDataSet The components of this parameter are defined in Table B.9 . Table B.9 - QueryDataSet Name Type Description QueryDataSet structure Data related to a Node returned in a Query response ... then a ReferenceDescription or array of ReferenceDescription is returned for that item. If the QueryDataSet is returned in a QueryNext to continue a list of ReferenceDescription , the values array will
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.2.1 Overviewform of an array of QueryDataSets . The selected Attribute values in each QueryDataSet come from the definition of the selected TypeDefinitionNodes or related TypeDefinitionNodes and appear in results
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.2.3 QueryFirstReferences that the Client wants the Server to return in the response for each QueryDataSet and on each subsequent continuation call response. The Server is allowed to further limit ... Type Description Response responseHeader ResponseHeader Common response parameters (see 7.33 for ResponseHeader definition). queryDataSets [] QueryDataSet The array of QueryDataSets . This array is empty if no Nodes or References
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.2.4 QueryNextResponse responseHeader Response Header Common response parameters (see 7.33 for ResponseHeader definition). queryDataSets [] QueryDataSet The array of QueryDataSets . The QueryDataSet type is defined in B.2.5 . revisedContinuationPoint ContinuationPoint Server -defined opaque
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.3.4 Example 1AttributeOperand = NodeId: HasSchedule, BrowsePath ".", Attribute: NodeId LiteralOperand= '1' Table B.12 describes the QueryDataSet that results from this query if it were executed against the instances described in Figure ... column and browse name (in parentheses in the NodeId column) are not in the QueryDataSet and are only shown here for clarity. The TypeDefinition NodeId would be an integer
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.3.5 Example 2column and browse name (in parentheses in the NodeId column) are not in the QueryDataSet and are only shown here for clarity. The TypeDefinition NodeId would be a NodeId
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.3.6 Example 3column and browse name (in parentheses in the NodeId column) are not in the QueryDataSet and are only shown here for clarity. The TypeDefinition NodeId would be an integer
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.3.7 Example 4column and browse name (in parentheses in the NodeId column) are not in the QueryDataSet and are only shown here for clarity. The TypeDefinition NodeId would be an integer
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.3.8 Example 5column and browse name (in parentheses in the NodeId column) are not in the QueryDataSet and are only shown here for clarity. The TypeDefinition NodeId would be an integer
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.3.9 Example 6HasPet ReferenceDescription NOTE The RelativePath and browse name (in parentheses) is not in the QueryDataSet and is only shown here for clarity and the TypeDefinition NodeId would be an integer ... ReferenceDescription which are described in 7.29 . Table B.28 provides an example of the same QueryDataSet as shown in Table B.27 without any additional fields and minimal symbolic Ids. There
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.3.10 Example 7HasFarmAnimal ReferenceDescription NOTE The RelativePath and browse name (in parentheses) is not in the QueryDataSet and is only shown here for clarity and the TypeDefinition NodeId would be an integer
-
OPC-10000-4 – OPC Unified Architecture - Part 4: ServicesB.3.11 Example 8column and browse name (in parentheses in the NodeId column) are not in the QueryDataSet and are only shown here for clarity. The TypeDefinition NodeId would be an integer