Search

167 result(s) for StatusCode

• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.2.7 WriteMask
  called on the Attribute , the Server should transfer this request and return the corresponding StatusCode if such a request is rejected. StatusCodes are defined in OPC 10000-4 . The AttributeWriteMask
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.6.2 Variable NodeClass
  Variable then the Server should transfer this request and return the corresponding StatusCode even if such a request is rejected. StatusCodes are defined in OPC 10000-4 . The SemanticChange flag ... Subscription and the Property value changes, then the SemanticsChanged bit of the StatusCode shall be set as defined in OPC 10000-4 . Clients subscribing to a Variable should look
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  5.7.1 Method NodeClass
  Method is called then the Server should transfer this request and return the corresponding StatusCode even if such a request is rejected. StatusCodes are defined
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.40 OptionSet
  value representing the valid bits in the value parameter. A Server shall return the StatusCode BadOutOfRange if it receives a different array size. When the Server returns the value ... reject any attempt to write to an invalid bit. A Server shall return the StatusCode BadOutOfRange if it receives validBits with a bit set to 1 which it does
• OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model
  8.57 AccessLevelType
  semantic, 1 means is a semantic). StatusWrite 5 Indicates if the current StatusCode of the value is writeable (0 means only StatusCode Good is writeable, 1 means any StatusCode
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.3 Service results
  status of each operation requested by the Service . Service results are defined via the StatusCode (see 7.38 ). The status of the Service call is represented by the serviceResult contained ... status of individual operations in a request is represented by individual StatusCode s. The following cases define the use of these parameters. A bad code is returned in serviceResult
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.7.3.2 Parameters
  prove possession of its ApplicationInstanceCertificate in the next call to ActivateSession request. results [] StatusCode List of validation results for the SoftwareCertificates (see 7.38 for StatusCode definition). diagnosticInfos [] DiagnosticInfo List
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.7.4.1 Description
  subsequent requests received for the Session are discarded. It returns negative responses with the StatusCode Bad_SessionClosed to all requests that are currently outstanding to provide for the timely return
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.2 Parameters
  nodesToAdd request parameter. This structure is defined in-line with the following indented items. statusCode StatusCode StatusCode for the Node to add (see 7.38 for StatusCode definition). addedNodeId NodeId Server
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.2.4 StatusCodes
  StatusCodes Table 24 defines values for the operation level statusCode parameter that are specific to this Service . Common StatusCodes are defined in Table 179 . Table 24 - AddNodes Operation Level Result
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.3.2 Parameters
  Server . Response responseHeader Response Header Common response parameters (see 7.33 for ResponseHeader definition). results [] StatusCode List of StatusCodes for the References to add (see 7.38 for StatusCode definition). The size
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.4.2 Parameters
  TRUE. Response responseHeader Response Header Common response parameters (see 7.33 for ResponseHeader definition). results [] StatusCode List of StatusCodes for the Nodes to delete (see 7.38 for StatusCode definition). The size
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.8.5.1 Description
  specified Reference . Response responseHeader ResponseHeader Common response parameters (see 7.33 for ResponseHeader definition). results [] StatusCode List of StatusCodes for the References to delete (see 7.38 for StatusCode definition). The size
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.4.2 Parameters
  browsePaths request parameter. This structure is defined in-line with the following indented items. statusCode StatusCode StatusCode for the browse path (see 7.38 for StatusCode definition). targets [] BrowsePathTarget List
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.9.4.4 StatusCodes
  StatusCodes Table 42 defines values for the operation level statusCode parameters that are specific to this Service . Common StatusCodes are defined in Table 179 . Table 42 - TranslateBrowsePathsToNodeIds Operation Level Result
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.2.2 Parameters
  Nodes and their Attributes to read. For each entry in this list, a StatusCode is returned, and if it indicates success, the Attribute Value is also returned. The ReadValueId parameter
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.2.4 StatusCodes
  StatusCodes Table 49 defines values for the operation level statusCode contained in the DataValue structure of each results element. Common StatusCodes are defined in Table 179 . Table 49 - Read Operation
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.3.2 Parameters
  TimestampsToReturn of NEITHER is not valid. A Server shall return a Bad_TimestampsToReturnInvalid StatusCode in this case. OPC 10000-11 defines exceptions where this parameter shall be ignored. releaseContinuation Points ... nodesToRead request parameter. This structure is defined in-line with the following indented items. statusCode StatusCode StatusCode for the NodesToRead item (see 7.38 for StatusCode definition). continuationPoint ContinuationPoint This parameter
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.3.4 StatusCodes
  StatusCodes Table 52 defines values for the operation level statusCode parameter that are specific to this Service . Common StatusCodes are defined in Table 179 . History access specific StatusCodes are defined
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.4.2 Parameters
  validation fails. Response responseHeader ResponseHeader Common response parameters (see 7.33 for ResponseHeader definition). results [] StatusCode List of results for the Nodes to write (see 7.38 for StatusCode definition). The size
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.4.4 StatusCodes
  Server shall not perform any write on this Node and shall return this StatusCode for this Node . It is also used if writing of IndexRanges is not supported ... contained in the enumeration data type of the Node , the Server shall return this StatusCode for this Node . This result code can be returned for any value that
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.5.2 Parameters
  request. This structure is defined in-line with the following indented items. statusCode StatusCode StatusCode for the update of the Node (see 7.38 for StatusCode definition). operationResults [] StatusCode List
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.11.5.4 StatusCodes
  StatusCodes Table 58 defines values for the statusCode and operationResults parameters that are specific to this Service . Common StatusCodes are defined in Table 179 . History access specific StatusCodes are defined
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.12.2.2 Parameters
  Method calls. This structure is defined in-line with the following indented items. statusCode StatusCode StatusCode of the Method executed in the Server . This StatusCode ... InvalidArgument StatusCode if at least one input argument broke a constraint (e.g. wrong data type, value out of range). This StatusCode is set to a bad StatusCode if the Method
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.12.2.4 StatusCodes
  StatusCodes Table 61 defines values for the statusCode parameter and Table 62 defines values for the inputArgumentResults parameter that are specific to this Service . Common StatusCodes are defined in Table ... specific error information. This is valid as long as the canonical description of the StatusCode does not have a different meaning than the application specific description. To eliminate any vagueness
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.5 Queue parameters
  than one, then the Overflow bit (flag) in the InfoBits portion of the DataValue statusCode is set. If discardOldest is TRUE, the oldest value gets deleted from the queue
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.1.6 Triggering model
  contains the Attribute being monitored is deleted, the MonitoredItem generates a Notification with a StatusCode Bad_NodeIdUnknown that indicates the deletion, but the MonitoredItem is not deleted
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.2.1 Description
  Server may allow the creation of a MonitoredItem and return an appropriate Bad StatusCode in the Publish response. The return diagnostic info setting in the request header of the CreateMonitoredItems
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.2.2 Parameters
  itemsToCreate request parameter. This structure is defined in-line with the following indented items. statusCode StatusCode StatusCode for the MonitoredItem to create (see 7.38 for StatusCode definition). monitoredItemId IntegerId Server ... unique within the Server or Session . This parameter is present only if the statusCode indicates that the MonitoredItem was successfully created. revisedSampling Interval Duration The actual sampling interval that
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.2.4 StatusCodes
  StatusCodes Table 65 defines values for the operation level statusCode parameter that are specific to this Service . Common StatusCodes are defined in Table 179 . Table 65 - CreateMonitoredItems Operation Level Result
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.3.2 Parameters
  itemsToModify request parameter. This structure is defined in-line with the following indented items. statusCode StatusCode StatusCode for the MonitoredItem to be modified (see 7.38 for StatusCode definition). revisedSampling Interval
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.3.4 StatusCodes
  StatusCodes Table 68 defines values for the operation level statusCode parameter that are specific to this Service . Common StatusCodes are defined in Table 179 . Table 68 - ModifyMonitoredItems Operation Level Result
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.4.2 Parameters
  MonitoredItems . Response responseHeader Response Header Common response parameters (see 7.33 for ResponseHeader definition). results [] StatusCode List of StatusCodes for the MonitoredItems to enable/disable (see 7.38 for StatusCode definition). The size
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.5.2 Parameters
  linksToAdd . Response responseHeader Response Header Common response parameters (see 7.33 for ResponseHeader definition). addResults [] StatusCode List of StatusCodes for the items to add (see 7.38 for StatusCode definition). The size ... header or if no diagnostic information was encountered in processing of the request. removeResults [] StatusCode List of StatusCodes for the items to delete. The size and order of the list
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.13.6.2 Parameters
  deleted. Response responseHeader Response Header Common response parameters (see 7.33 for ResponseHeader definition). results [] StatusCode List of StatusCodes for the MonitoredItems to delete (see 7.38 for StatusCode definition). The size
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.1.4 Functions
  error. No parameters are returned other than the responseHeader that contains the Service level StatusCode . ReturnNotifications() CreateNotificationMsg() ReturnResponse() If (MoreNotifications == TRUE) && (PublishingReqQueued == TRUE) { DequeuePublishReq() Loop through this function
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.4.2 Parameters
  IntegerId definition). Response responseHeader ResponseHeader Common response parameters (see 7.33 for ResponseHeader definition). results [] StatusCode List of StatusCodes for the Subscriptions to enable/disable (see 7.38 for StatusCode definition). The size
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.5.2 Parameters
  contains the list of Notifications . The NotificationMessage parameter type is specified in 7.26 . results [] StatusCode List of results for the acknowledgements (see 7.38 for StatusCode definition). The size and order
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.7.2 Parameters
  subscriptionIds request parameter. This structure is defined in-line with the following indented items. statusCode StatusCode StatusCode for each Subscription to be transferred (see 7.38 for StatusCode definition). availableSequence Numbers
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.7.4 StatusCodes
  StatusCodes Table 96 defines values for the operation level statusCode parameter that are specific to this Service . Common StatusCodes are defined in Table 179 . Table 96 - TransferSubscriptions Operation Level Result
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  5.14.8.2 Parameters
  IntegerId definition). Response responseHeader ResponseHeader Common response parameters (see 7.33 for ResponseHeader definition). results [] StatusCode List of StatusCodes for the Subscriptions to delete (see 7.38 for StatusCode definition). The size
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.2 ContentFilterResult
  ContentFilter parameter. This structure is defined in-line with the following indented items. statusCode StatusCode The status code for a single element. operandStatusCodes [] StatusCode A list of status codes ... information was encountered in processing of the elements. Table 116 defines values for the StatusCode parameter that are specific to this structure. Common StatusCodes are defined in Table 179 . Table
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.7.3 FilterOperator
  null value. TRUE If the value in operand[0] is a StatusCode instead of the field DataType . GreaterThan 2 2 TRUE if operand[0] is greater than operand ... From) Boolean Byte ByteString DateTime Double ExpandedNodeId Float Guid Int16 Int32 Int64 NodeId SByte StatusCode String LocalizedText QualifiedName UInt16 UInt32 UInt64 XmlElement Boolean
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.10 DataChangeTrigger
  DataChangeTrigger values Name Value Description STATUS 0 Report a notification ONLY if the StatusCode associated with the value changes. See Table 179 for StatusCodes defined in this document ... particular for device data. STATUS_VALUE 1 Report a notification if either the StatusCode or the value change. The Deadband filter can be used in addition for filtering value changes
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.11.1 General
  DataValue structure The value and associated information. value BaseDataType The data value. If the StatusCode indicates an error then the value is to be ignored and the Server shall ... null. statusCode StatusCode The StatusCode that defines the Server 's ability to access/provide the value. The StatusCode type is defined in 7.38 sourceTimestamp UtcTime The source timestamp for the value
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.11.3 SourceTimestamp
  time and should indicate the time of the last change of the value or statusCode . The sourceTimestamp should be generated as close as possible to the source of the value
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.11.5 StatusCode assigned to a value
  StatusCode assigned to a value The StatusCode is used to indicate the conditions under which a Variable value was generated, and thereby can be used as an indicator ... usability of the value. The StatusCode is defined in 7.38 . Overall condition (severity) A StatusCode with severity Good means that the value is of good quality. A StatusCode with severity
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.12 DiagnosticInfo
  contain StatusCodes . If the localizedText contains a translation for the description of a StatusCode , the symbolicId is -1. locale Int32 The locale part of the vendor-specific localized text describing ... localizedText refers to the symbolicId if present or the string that describes the standard StatusCode if the Server provides translations. If the index is -1, the Server has no translation
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.21 MonitoringParameters
  queue overflow, the Overflow bit (flag) in the InfoBits portion of the DataValue statusCode is set in the new value. The following values have special meaning for event monitored items
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.22.3 EventFilter
  available at the time of the event notification, the event field shall contain a StatusCode that indicates the reason for the unavailability. For example, the Server shall set the event ... user associated with the Session . If a Value Attribute has an uncertain or bad StatusCode associated with it then the Server shall provide the StatusCode instead of the Value Attribute
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.22.4 AggregateFilter
  support the ability to override the Aggregate configuration settings it shall return a StatusCode of Bad_AggregateListMismatch. This structure is defined in-line with the following indented items. useServerCapabilities Defaults
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.25.2 DataChangeNotification parameter
  REPORTING and a change in value or its status (represented by its StatusCode ) is detected; if the MonitoringMode is set to SAMPLING, the MonitoredItem is linked to a triggering item ... handle for the MonitoredItem . The IntegerId type is defined in 7.19 Value DataValue The StatusCode , value and timestamp(s) of the monitored Attribute depending on the sampling and queuing configuration
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.25.4 StatusChangeNotification parameter
  Subscription . Table 163 - StatusChangeNotification Name Type Description StatusChangeNotification structure Event Notification data status StatusCode The StatusCode that indicates the status change. diagnosticInfo DiagnosticInfo Diagnostic information for the status change
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.32 RequestHeader
  ServiceLevel / SymbolicId 0x0000 0002 ServiceLevel / LocalizedText 0x0000 0004 ServiceLevel / AdditionalInfo 0x0000 0008 ServiceLevel / Inner StatusCode 0x0000 0010 ServiceLevel / Inner Diagnostics 0x0000 0020 OperationLevel / SymbolicId 0x0000 0040 OperationLevel / LocalizedText 0x0000 ... OperationLevel / AdditionalInfo 0x0000 0100 OperationLevel / Inner StatusCode 0x0000 0200 OperationLevel / Inner Diagnostics Each of these values is composed of two components, level and type , as described below. If none
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.33 ResponseHeader
  response. requestHandle IntegerId The requestHandle given by the Client to the request. serviceResult StatusCode OPC UA-defined result of the Service invocation. The StatusCode type is defined in 7.38 . serviceDiagnostics
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.34 ServiceFault
  shall be returned instead of the Service response message when the serviceResult is a StatusCode with Severity Bad . The requestHandle in the ResponseHeader should be set to what was provided
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  7.38.1 General
  General A StatusCode in OPC UA is numerical value that is used to report the outcome of an operation performed by an OPC UA Server . This code may have associated ... make decisions on how to process the results of an OPC UA Service . The StatusCode is a 32-bit unsigned integer. The top 16 bits represent the numeric value
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.3 QueryFirst
  node type encountered an error all node types should have an associated status code. statusCode StatusCode Parsing result for the requested NodeTypeDescription . dataStatusCodes [] StatusCode List of results for dataToReturn ... result set may be incomplete. Table B.6 defines values for the parsingResults statusCode parameter that are specific to this Service . Common StatusCodes are defined in Table 179 . Table B.6 - QueryFirst
• OPC-10000-4 – OPC Unified Architecture - Part 4: Services
  B.2.5 QueryDataSet
  value is returned for that item. If a value has a bad status, the StatusCode is returned instead of the value. If multiple values exist for a requested item then
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.2 BaseEventType
  always be returned as value and the Server is not allowed to return a StatusCode for the EventId indicating an error. EventType describes the specific type of Event . The EventType ... always be returned as value and the Server is not allowed to return a StatusCode for the EventType indicating an error. The SourceNode Property identifies the Node that the Event
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  6.4.27 AuditUpdateMethodEventType
  InstanceDeclarations of that Node. HasProperty Variable MethodId NodeId PropertyType Mandatory HasProperty Variable StatusCodeId StatusCode PropertyType Optional HasProperty Variable InputArguments BaseDataType[] PropertyType Mandatory HasProperty Variable OutputArguments BaseDataType[] PropertyType Optional Conformance Units ... triggered by the method. MethodId identifies the method that was called. StatusCodeId identifies the StatusCode of the Method executed by the Server . Note: This Property is optional for backward compatibility
• OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model
  12.14 StatusResult
  StatusResult This structure combines a StatusCode and diagnostic information and can, for example, be used by Methods to return several StatusCodes and the corresponding diagnostic information that are not handled ... setting of the Service calls. Table 250 - StatusResult Structure Name Type Description StatusResult structure statusCode StatusCode The StatusCode. diagnosticInfo DiagnosticInfo The diagnostic information for the statusCode. Its representation
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.1.9 Variant
  DiagnosticInfo types only have meaning when returned in a response message with an associated StatusCode and table of strings. As a result, Variants cannot contain instances of DiagnosticInfo. Values
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.2.8 XmlElement (Deprecated)
  then this error can be reported by setting value of the Variant to the StatusCode Bad_DecodingError
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.2.11 StatusCode
  StatusCode A StatusCode is encoded as a UInt32
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.2.2.15 ExtensionObject
  this error can be reported by setting the value of the Variant to the StatusCode Bad_DecodingError. A null value for an ExtensionObject is encoded with a TypeId
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.3.1.12 StatusCode
  StatusCode A StatusCode is encoded as an xs:unsignedInt with the following XML schema: <xs:complexType name="StatusCode"> <xs:sequence> <xs:element name
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  5.4.2.12 StatusCode
  StatusCode StatusCode values shall be encoded as a JSON object with the fields defined in Table 37 . Table 37 - JSON Object Definition for a StatusCode Name Description Code The numeric ... string. e.g. 0x80AB0000 has the associated literal "BadInvalidArgument". Any InfoBits in the StatusCode are ignored when looking up the symbol. If the string literal is not known
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.7.3 MessageChunks and error handling
  close the SecureChannel . The Client shall report the error back to the application as StatusCode for the request. If the Client is the sender, then it shall report the error
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  6.8.2 UserIdentityToken Encryption
  ECDHKey EphemeralKeyType Specifies an EphemeralKey . If the EphemeralKey could not be created a StatusCode indicating the reason for the error is used instead of an instance of EphemeralKeyType
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  7.1.2.4 Acknowledge Message
  request Message . The Client shall abort the Message with a Bad_RequestTooLarge StatusCode if a request Message exceeds this value. The mechanism for aborting Messages is described fully
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  A.2 Status Codes
  that appears in the specification and the Code is the hexadecimal value for the StatusCode (see OPC 10000-4 ). The severity associated with a particular code is specified
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  F.8 UAVariable
  UANodeSet is used to initialize a Server AddressSpace then the Server shall report a StatusCode of Bad_NoValue or choose a default Value consistent with the DataType and ValueRank . Translation
• OPC-10000-6 – OPC Unified Architecture - Part 6: Mappings
  H.4 StatusCode
  StatusCode StatusCode values shall be encoded as a JSON number for the ReversibleEncoding . If the StatusCode is Good (0) it is only encoded if it is an element ... JSON array. For the NonReversibleEncoding , StatusCode values shall be encoded as a JSON object with the fields defined in Table H.3 . Table H.3 - JSON Object Definition for a StatusCode Name
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.2 SemanticsChanged
  SemanticsChanged The StatusCode also contains an informational bit called SemanticsChanged . Servers that implement Data Access shall set this Bit in notifications if certain Property values defined in this standard change
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  5.5 Attributes of DataItems
  requests the Value Attribute for reading or monitoring, the Server will always return a StatusCode (the quality and the Server's ability to access/provide the value) and, optionally, a ServerTimestamp ... SourceTimestamp - based on the Client's request. See OPC 10000-4 for details on StatusCode and the meaning of the two timestamps. Specific status codes for Data Access are defined
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  7.2 PercentDeadband
  Specifying a deadbandValue outside of this range will be rejected and reported with the StatusCode Bad_DeadbandFilterInvalid (see Table 61 ). If the Value of the MonitoredItem is an array, then
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  7.3.1 Overview
  Overview Subclauses 7.3.2 and 7.3.3 define additional codes and rules that apply to the StatusCode when used for Data Access values. The general structure of the StatusCode is specified
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  7.3.3 LimitBits
  LimitBits The bottom 16 bits of the StatusCode are bit flags that contain additional information, but do not affect the meaning of the StatusCode . Of particular interest for DataItems
• OPC-10000-8 – OPC Unified Architecture - Part 8: Data Access
  A.4.2.3 Variable Nodes
  property. Details on Value mapping are in A.4.3.2 Item Quality (Property ID: 3): The StatusCode of the Value obtained for the node in the OPC UA Server is assigned
• OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions
  5.14.2 Communication problems
  Event field related information that is exposed in the address space, the Value/ StatusCode obtained when reading the Event fields that are associated with the communication failure shall have ... value of NULL and a StatusCode of Bad_CommunicationError. For Subscription s that contain Conditions for which the failure applies, the effected Conditions generate an Event, if the Retain field
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  4.6 Bounding Values and time domain
  tuple with a value of null, a timestamp of the specified StartTime , and a StatusCode of Bad_BoundNotFound. LAST stands for a tuple with a value of null, a timestamp ... specified EndTime , and a StatusCode of Bad_ BoundNotFound . In some cases, attempting to locate bounds, particularly FIRST or LAST points, can be resource intensive for Servers . Therefore, how far back
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.2.1 Overview
  Overview Subclause 6.2 defines additional codes and rules that apply to the StatusCode when used for HistoricalDataNodes . The general structure of the StatusCode is specified
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.2.2 Operation level result codes
  Operation level result codes In OPC UA Historical Access the StatusCode is used to indicate the conditions under which a Value or Event was stored, and thereby can be used
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.2.3 Semantics changed
  Semantics changed The StatusCode in addition contains an informational bit called Semantics Changed (see OPC 10000-4 ). UA Servers that implement OPC UA Historical Access should not set this ... rather they should propagate the StatusCode which has been stored in the data repository. The Client should be aware that the returned data values can have this
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.3 Continuation Points
  request. If the ContinuationPoint for an operation is missing or invalid then the StatusCode for the operation shall be Bad _ ContinuationPointInvalid
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.2.2 Read Event functionality
  data exists at the time specified then the Server shall return the Good_NoData StatusCode . The standard ContinuationPoint rules (see 6.3 ) apply. In addition, the following ContinuationPoint rule applies ... along with a ContinuationPoint . For an interval in which no data exists, the corresponding StatusCode shall be Good_NoData. The filter parameter is used to determine which historical Events
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.2.4 Read modified functionality
  Events exists at the time specified then the Server shall return the Good_NoData StatusCode . The standard ContinuationPoint rules (see 6.3 ) apply. In addition, the following ContinuationPoint rule applies ... along with a ContinuationPoint . For an interval in which no Events exists, the corresponding StatusCode shall be Good_NoData. The filter parameter is used to determine which historical Events
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.3.2 Read raw functionality
  forward. It is specifically not allowed for the Server to return a Bad_InvalidArgument StatusCode if the requested time domain is outside of the Server 's range. Such a case ... When Bounding Values are requested and no bounding value is found then the corresponding StatusCode entry will be set to Bad_BoundNotFound, a timestamp equal to the start
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.4.2 Read processed functionality
  Aggregates does not match the array of NodesToRead then the Server shall return a StatusCode of Bad_AggregateListMismatch. The aggregateConfiguration parameter allows a Client to override the Aggregate configuration settings ... support the ability to override the Aggregate configuration settings, then it shall return a StatusCode of Bad_ AggregateConfigurationRejected. If the Aggregate is not valid for the Node then the StatusCode
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.5.6.2 Read Annotation Data functionality
  request. If Annotation Data is not supported for a HistoricalDataNodes then the StatusCode shall be Bad_HistoryOperationUnsupported. The standard ContinuationPoint rules (see 6.3 ) apply
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.2.2 Insert data functionality
  specified timestamp, then the new entry shall not be inserted; instead the StatusCode shall indicate Bad_EntryExists . This function is intended to insert new entries at the specified timestamps
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.2.3 Replace data functionality
  specified timestamp, then the new entry shall not be inserted; otherwise, the StatusCode shall indicate Bad_NoEntryExists . This function is intended to replace existing entries at the specified timestamp
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.2.4 Update data functionality
  insert/replace values and qualities, e.g., correction of values for bad sensors. Good as a StatusCode for an individual entry is allowed when the Server is unable to say whether there
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.3.3 Insert functionality
  Properties of HistoricalDataNodes. If a StructuredHistoryData entry already exists at the specified parameters the StatusCode shall indicate Bad_EntryExists . If the Time does not fall within range that
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.3.4 Replace functionality
  StructuredHistoryData entry does not already exist at the specified parameters, then the StatusCode shall indicate Bad_NoEntryExists
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.3.5 Update functionality
  entry is inserted. If an existing entry was replaced successfully then the StatusCode shall be Good_EntryReplaced. If a new entry was created the StatusCode shall be Good_EntryInserted ... Server cannot determine whether it replaced or inserted an entry then the StatusCode shall be Good. If the Time does not fall within range that can be stored then
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.3.6 Remove functionality
  deleted. If StructuredHistoryData does not already exist at the specified parameters, then the StatusCode shall indicate Bad_NoEntryExists
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.4.2 Insert event functionality
  fields are provided. If one of the required fields is not provided then the statusCode shall indicate Bad_ArgumentsMissing . If the historian does not support archiving the specified EventType then ... statusCode shall indicate Bad_TypeDefinitionInvalid . If the SourceNode is not a valid source for Events then the related operationResults entry shall indicate Bad_SourceNodeIdInvalid. If the Time does not fall
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.5.2 Delete raw functionality
  data is found in the time range for a particular HistoricalDataNode , then the StatusCode for that item is Bad_NoData
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.5.3 Delete modified functionality
  data is found in the time range for a particular HistoricalDataNode , then the StatusCode for that item is Bad_NoData
• OPC-10000-11 – OPC Unified Architecture - Part 11: Historical Access
  6.9.7.2 Delete event functionality
  Events are found that match the specified filter for a HistoricalEventNode , then the StatusCode for that Node is Bad_NoData
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.5 CloseAndUpdate
  ignored; however, they may be logged as warnings. If the validation fails, the appropriate StatusCode defined in OPC 10000-4 shall be reported. For Purposes other than ApplicationCertificateType , the validation
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.8.2.6 AddCertificate
  ignored; however, they may be logged as warnings. If the validation fails, the appropriate StatusCode defined in OPC 10000-4 shall be reported. For Purposes other than ApplicationCertificateType , the validation
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.10.5 UpdateCertificate
  ignored; however, they may be logged as warnings. If the validation fails, the appropriate StatusCode defined in OPC 10000-4 shall be reported. The validation process requires that the TrustList
• OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services
  7.10.17 TransactionDiagnosticsType
  Variable 0:EndTime 0:UtcTime 0:PropertyType Mandatory 0:HasProperty Variable 0:Result 0:StatusCode 0:PropertyType Mandatory 0:HasProperty Variable 0:AffectedTrustLists 0:NodeId [] 0:PropertyType Mandatory 0:HasProperty ... transaction has completed the status is Good and the value is the StatusCode that was returned from the ApplyChanges Method . If the CancelChanges Method was called the value
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  3.1.8 interpolated bounding values
  timestamp associated with Vx. If no non-Bad values exist before the timestamp the StatusCode is Bad_NoData. The StatusCode is Uncertain_DataSubNormal if any Bad values exist between ... after value. If either the before value or the after value are Uncertain the StatusCode is Uncertain_DataSubNormal . If the after value does not exist the before value shall
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  3.1.9 simple bounding values
  SlopedInterpolation in Clause 3.1.5 . If a Raw value at the timestamp is Bad the StatusCode is Bad_NoData. If the value before the timestamp is Bad the StatusCode ... NoData. If the value before the timestamp is Uncertain the StatusCode is Uncertain_DataSubNormal . If the value after the timestamp is Bad or Uncertain the StatusCode is Uncertain_DataSubNormal . Simple
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  4.2.1.2 AggregateConfigurationType
  Master Configuration The TreatUncertainAsBad Variable indicates how the Server treats data returned with a StatusCode severity Uncertain with respect to Aggregate calculations. A value of True indicates the Server considers ... value is True. Note that the value is still treated as Uncertain when the StatusCode for the result is calculated. The PercentDataBad Variable indicates the minimum percentage of Bad data
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  4.2.2.2 AggregateFunctionType
  Retrieve the percentage of data (0 to 100) in the interval which has Good StatusCode . PercentBad Retrieve the percentage of data (0 to 100) in the interval which ... StatusCode . WorstQuality Retrieve the worst StatusCode of data in the interval. WorstQuality2 Retrieve the worst StatusCode of data in the interval including the Simple Bounding Values . AnnotationCount Retrieve the number
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.3.1 Overview
  Overview Subclause 5.3 defines additional codes and rules that apply to the StatusCode when used for Aggregates . The general structure of the StatusCode is specified
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.3.2 Operation level result codes
  Operation level result codes In OPC UA Aggregates the StatusCode is used to indicate the conditions under which a value or Event was stored, and thereby can be used
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.3.3.1 General
  result of data aggregation). These bits are mutually exclusive. Table 47 - Data location StatusCode Description Raw A Raw data value. Calculated A data value which was calculated. Interpolated A data ... value for that timestamp, the Server should set the 'Raw' bit in the StatusCode of that value. Table 48 lists the bit settings which indicate additional important information about
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.2.2 Generating intervals
  Time Interval Resulting intervals Start = End Int = Anything No intervals. Returns a Bad_InvalidArgument StatusCode , regardless of whether there is data at the specified time or not. Start
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.2.3 Data types
  DurationGood All Duration DurationBad All Duration PercentGood All Double PercentBad All Double WorstQuality All StatusCode WorstQuality2 All StatusCode Statistical Aggregates StandardDeviationSample Numeric Double VarianceSample Numeric Double StandardDeviationPopulation Numeric Double VariancePopulation
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.2.1 General
  Bounding Value then the Bounding Values are included in the count when computing the StatusCode . If an Aggregate does any sort of a time weighted calculation (e.g. TimeAverage or TimeAverage2 ... then the StatusCode calculation shall also be time weighted. For purposes of calculating time weighted StatusCodes each interval shall be divided into regions of Good or Bad data. Creating these
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.5 Average
  Good values. If any non-Good values are ignored in the computation, the Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ). This Aggregate is not time based ... summary Average Aggregate Characteristics Type Calculated Data Type Double Use Bounds None Timestamp StartTime StatusCode Calculations Calculation Method PercentValues Partial Not Set Calculated Set Always Interpolated
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.6 TimeAverage
  Values exist in the interval then they are omitted from the calculation and the StatusCode is set to Uncertain_DataSubNormal . Sloped lines are drawn between the Good values when calculating ... summary TimeAverage Aggregate Characteristics Type Calculated Data Type Double Use Bounds Interpolated Timestamp StartTime StatusCode Calculations Calculation Method Custom Good if no Bad values skipped and Good values are used
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.7 TimeAverage2
  used to calculate the area of sub-interval preceding the Bad value. The Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ). Table 55 - TimeAverage2 Aggregate summary TimeAverage2 ... Aggregate Characteristics Type Calculated Data Type Double Use Bounds Simple Timestamp StartTime StatusCode Calculations Calculation Method PercentTime Partial Set Sometimes If an interval is not a complete interval Calculated
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.8 Total
  resulting units would be normalized to seconds, i.e. [ TimeAverage Units] x seconds. The Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ). Note that this calculation always uses ... summary Total Aggregate Characteristics Type Calculated Data Type Double Use Bounds Interpolated Timestamp StartTime StatusCode Calculations Calculation Method Custom Good if no Bad values are skipped and Good values
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.9 Total2
  resulting units would be normalized to seconds, i.e. [ TimeAverage2 Units] x seconds. The Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ). Table 57 - Total2 Aggregate summary Total2 ... Aggregate Characteristics Type Calculated Data Type Double Use Bounds Simple Timestamp StartTime StatusCode Calculations Calculation Method PercentTime Partial Set Sometimes If an interval is not a complete interval Calculated
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.15 Minimum2
  Bounding Values (see 3.1.9 ). Any Bad values are ignored in the computation. The Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates ... Aggregate Characteristics Type Calculated Data Type Same as Source Use Bounds Simple Timestamp StartTime StatusCode Calculations Calculation Method PercentTime Partial Set Sometimes If an interval is not a complete interval
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.16 Maximum2
  Bounding Values (see 3.1.9 ). Any Bad values are ignored in the computation. The Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates ... Aggregate Characteristics Type Calculated Data Type Same as Source Use Bounds Simple Timestamp StartTime StatusCode Calculations Calculation Method PercentTime Partial Set Sometimes If an interval is not a complete interval
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.17 MinimumActualTime2
  Bounding Values (see 3.1.9 ). Any Bad values are ignored in the computation. The Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates ... Type Calculated Data Type Same as Source Use Bounds Simple Timestamp Time of minimum StatusCode Calculations Calculation Method PercentTime Partial Set Sometimes If an interval is not a complete interval
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.18 MaximumActualTime2
  Bounding Values (see 3.1.9 ). Any Bad values are ignored in the computation. The Aggregate StatusCode will be determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates ... Type Calculated Data Type Same as Source Use Bounds Simple Timestamp Time of maximum StatusCode Calculations Calculation Method PercentTime Partial Set Sometimes If an interval is not a complete interval
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.21 Count
  values are non-Good, they are not included in the count, and the Aggregate StatusCode is determined using the StatusCode Calculation (see 5.4.3 ) for non-time based Aggregates ... Calculated Data Type Int32 (negative values are not allowed) Use Bounds None Timestamp StartTime StatusCode Calculations Calculation Method PercentValues Partial Set Sometimes If an interval is not a complete interval
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.22 DurationInStateZero
  values are non-Good, they are not included in the Duration , and the Aggregate StatusCode is determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates . Duration ... summary DurationInStateZero Aggregate Characteristics Type Calculated Data Type Duration Use Bounds Simple Timestamp StartTime StatusCode Calculations Calculation Method PercentTime Partial Set Sometimes If an interval is not a complete interval
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.23 DurationInStateNonZero
  values are non-Good, they are not included in the Duration , and the Aggregate StatusCode is determined using the StatusCode Calculation (see 5.3 ) for time based Aggregates . Duration ... summary DurationInStateNonZero Aggregate Characteristics Type Calculated Data Type Duration Use Bounds Simple Timestamp StartTime StatusCode Calculations Calculation Method PercentTime Partial Set Sometimes If an interval is not a complete interval
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.24 NumberOfTransitions
  values are Bad, they are not included in the count, and the Aggregate StatusCode is determined using the StatusCode Calculation (see 5.3 ) for non-time based Aggregates . The earliest transition ... Bounds Custom, a non-Bad value prior to the interval is used Timestamp StartTime StatusCode Calculations Calculation Method PercentValues Partial Set Sometimes If an interval is not a complete interval
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.25 Start
  which that value occurs. If no values are in the interval then the StatusCode is Bad_NoData . Table 73 - Start Aggregate summary Start Aggregate Characteristics Type Calculated Data Type Same ... Source Use Bounds None Timestamp Time of Raw Value StatusCode Calculations Calculation Method Custom The raw value status is returned Partial Set Sometimes If an interval is not a complete
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.26 End
  which that value occurs. If no values are in the interval then the StatusCode is Bad_NoData . Table 74 - End Aggregate summary End Aggregate Characteristics Type Calculated Data Type Same ... Source Use Bounds None Timestamp Time of Raw Value StatusCode Calculations Calculation Method Custom The raw value status is returned Partial Set Sometimes If an interval is not a complete
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.31 DurationGood
  Type Calculated Data Type Duration Use Bounds Uses status of bounding value Timestamp StartTime StatusCode Calculations Calculation Method Custom StatusCode is always Good , Calculated Partial Set Sometimes If an interval ... interval Calculated Set Always Interpolated Not Set Raw Not Set Multi Value Not Set StatusCode Common Special Cases Before Start of Data Bad_NoData After End of Data Bad_NoData
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.32 DurationBad
  Type Calculated Data Type Duration Use Bounds Uses status of bounding value Timestamp StartTime StatusCode Calculations Calculation Method Custom StatusCode is always Good, Calculated Partial Set Sometimes If an interval ... interval Calculated Set Always Interpolated Not Set Raw Not Set Multi Value Not Set StatusCode Common Special Cases Before Start of Data Bad_NoData After End of Data Bad_NoData
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.35 WorstQuality
  multiple values exist with the worst quality but different StatusCodes then the StatusCode of the first value is returned. This Aggregate returns the worst StatusCode as the value ... Good, Calculated. Table 83 - WorstQuality Aggregate summary WorstQuality Aggregate Characteristics Type Calculated Data Type StatusCode Use Bounds None Timestamp StartTime StatusCode Calculations Calculation Method Custom Always Good Partial Set Sometimes
• OPC-10000-13 – OPC Unified Architecture - Part 13: Aggregates
  5.4.3.36 WorstQuality2
  multiple values exist with the worst quality but different StatusCodes then the StatusCode of the first value is returned. This Aggregate returns the worst StatusCode as the value ... Good, Calculated. Table 84 - WorstQuality2 Aggregate summary WorstQuality2 Aggregate Characteristics Type Calculated Data Type StatusCode Use Bounds Simple Timestamp StartTime StatusCode Calculations Calculation Method Custom Always Good Partial Set Sometimes
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.3.7.1 PublishedData
  BaseDataType The SubstituteValue is the value that is included in the DataSet if the StatusCode of the DataValue is Bad. In this case the StatusCode is set to Uncertain_SubstituteValue ... with the right DataType that matches the ConfigurationVersion . If the SubstituteValue is Null, the StatusCode of the DataValue is processed. The handling of the SubstituteValue is defined in 6.2.11 . MetaDataProperties
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.3.8.2 SelectedFields
  DataSet field. Event fields can be null or the field value can be a StatusCode . The encoding of Event based DataSetMessages shall be able to handle these cases. ExtensionFields defined
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.4.2 DataSetFieldContentMask
  bits 0 to 4 is set, the fields are represented as DataValue . StatusCode 0 The DataValue structure field StatusCode is included in the DataSetMessage s. If this ... code in a fatal error situation. Bad_* Null Bad_* (a) If no specific StatusCode is used, the grouping into severity Good , Uncertain or Bad is used. In this case
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.10.2.3 FieldTargetDataType
  Operational or if the corresponding field in the DataSet contains a Bad StatusCode . The handling of the OverrideValue in different scenarios is defined in 6.2.11 . The OverrideValueHandling enumeration DataType ... Operational or if the corresponding field in the DataSet contains a Bad StatusCode . The handling of the OverrideValue in different scenarios is defined in 6.2.11 . This Value shall match
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  6.2.11.1 Published data items
  Value 1 Uncertain_* Value 1 Uncertain_* Ignored Bad_* Null Bad_* (a) If no specific StatusCode is used, the grouping into severity Good, Uncertain or Bad is used. In this case ... source value e.g. DataType does not match DataSetField should be treated like a Bad StatusCode received from the source. The mapping of the decoded DataSet on the Subscriber side
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  7.2.4.5.4 DataSetMessage header
  Encoding 00 The DataSet fields are encoded as Variant The Variant can contain a StatusCode instead of the expected DataType if the status of the field is Bad. The Variant ... contain a DataValue with the value and the statusCode if the status of the field is Uncertain. 01 RawData Field Encoding The RawData field encoding is defined
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.11.2 PubSubDiagnosticsType
  inactive nodes cannot be removed from the Address Space the Server shall set the StatusCode of the Variable Value to Bad_OutOfService
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  9.1.13.3 PubSubCommunicationFailureEventType
  NodeClass BrowseName DataType TypeDefinition ModellingRule Subtype of PubSubStatusEventType defined in 9.1.13.2 . HasProperty Variable Error StatusCode PropertyType Mandatory Conformance Units PubSub Model Diagnostics Events This EventType inherits all Properties ... from BaseEventType has a localized description of the error. The Error Property has the StatusCode associated with the error
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  A.2.1.7 Header layout for DataSetMessages
  ConfigurationVersionMinorVersion enabled = 0 Bit 7: DataSetFlags2 enabled = 0 DataSetMessageSequenceNumber UInt16 Defined by Table 162 . StatusCode UInt16 Defined by Table 162 . Table A.6 defines the values for the configuration parameters representing ... Value KeyFrameCount 1 UadpDataSetMessageContentMask 0x00000024 This value results of the following options: Bit 2: StatusCode enabled = 1 Bit 5: SequenceNumber enabled = 1 DataSetFieldContentMask 0x00000020 This value results of the following
• OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub
  A.3.3.5 Examples
  DataSet1 with all configurable JsonDataSetMessageContentMask flags set to false and with SourceTimestamp and StatusCode flags set in the DataSetFieldContentMask . The Status is omitted if the Code is 0. { "PublisherId
• OPC-10000-16 – OPC Unified Architecture - Part 16: State Machines
  4.5.2 StateMachineType with a SubStateMachine using inheritance
  MyStateMachine" is in "State1", a client would receive a Bad_StateNotActive StatusCode when reading the SubStateMachine CurrentState Variable if "MyStateMachine" is in a different State
• OPC-10000-20 – OPC Unified Architecture - Part 20: File Transfer
  4.2.1 General
  file, the Size Property shall be returned to a Client with a StatusCode of Bad_NotSupported . Writable indicates whether the file is writable. It does not take any user access
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.2 Limitations
  duplicate BrowseNames on the same hierarchy level) are encountered, the SerializationProcess fails and the StatusCode for access yields Bad_BrowseNameDuplicated
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.2 SerializedData Variable
  InstanceDeclaration , accessing the SerializedData Variable is not possible. Reading attempts are answered with the StatusCode Bad_NoValue. Note 1: It may be useful to use GUID NodeIds
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  6.3.9 IncludeStatus, IncludeSourceTimestamp, and IncludeDictionaryReference Properties
  Value of the Variable and a "Status" field for the statusCode . The DataType of the field shall be StatusCode . If False, the DataType representing the Variable shall contain
• OPC-10000-25 – OPC Unified Architecture - Part 25: Object Serialization
  A.7 Combining SerializationScopes
  SerializationScope . The IncludeStatus SerializationProperty of this second SerializationEntity is set to true, causing the StatusCode of the "MeasurementY1" Variable Value to be part of the SerializationValue DataType ... RawData field encoding (see OPC 10000-14 ) in a PubSub scenario. If the StatusCode of the "MeasurementY1" Variable Value is Good , an empty "Status" is generated
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.2 EstablishConnections signature
  Connections exceeded . See AutomationComponentCapabilityType MaxConnections in section 6.2.6 . An AutomationComponent may set this StatusCode , even if the optional AutomationComponentCapability MaxConnections does not exist. Bad_NothingToDo The operation was skipped. Creating
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.2 Command VerifyAssetCmd
  called on each AssetToVerify , supplying the VerificationMode , ExpectedVerificationVariables and ExpectedAdditionalVerificationVariables as Method Arguments . The StatusCode returned by the VerifyAsset Method and the values of its output Arguments VerificationResult , VerificationVariablesErrors
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.3 Command VerifyFunctionalEntityCmd
  called on the FunctionalEntity identified by FunctionalEntityNode , supplying the ExpectedVerificationVariables as Method Argument . The StatusCode returned by the Verify Method shall be stored in VerificationStatus, and the values
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.2.4.3.9.2 PubSub
  Node that is not accessible. If the Reference cannot be created, an appropriate StatusCode shall be set in the appropriate element in ConnectionEndpointConfigurationResults CommunicationLinksResult , and the EstablishConnections implementation shall abort
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.3.3 VerifyAsset method
  KeyValuePair[] ExpectedVerificationVariables, [in] 2:NodeIdValuePair[] ExpectedAdditionalVerificationVariables, [out] 2:AssetVerificationResultEnum VerificationResult, [out] 0:StatusCode[] VerificationVariablesErrors, [out] 0:StatusCode[] VerificationAdditionalVariablesErrors ); Table 31 - VerifyAsset Method arguments Argument Description VerificationMode Mode for Asset verification ... verification of AssetCompatibility or AssetIdentity or both results in Mismatch . VerificationVariablesErrors An array of StatusCode corresponding to the ExpectedVerificationVariables input argument that indicates any errors that occurred during the processing
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.2 FunctionalEntityType definition
  FunctionalEntity . The FailedVerificationCount provides the number of calls to Verify that returned a bad StatusCode in this FunctionalEntity
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.3 Verify method
  Table 43 . Signature Verify ( [in] 2:NodeIdValuePair[] ExpectedVerificationVariables, [out] 2:FunctionalEntityVerificationResultEnum VerificationResult, [out] 0:StatusCode[] VerificationVariablesErrors ); Table 43 - Verify Method arguments Argument Description ExpectedVerificationVariables An array of NodeIdValuePair containing verification ... null). If this value is set, VerificationVariablesErrors shall be populated. VerificationVariablesErrors An array of StatusCode corresponding to the ExpectedVerificationVariables input argument that indicates any errors (if VerificationResult equals NotSet
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.6.3 SetStoredVariables method
  arguments are defined in Table 50 . Signature SetStoredVariables ( [in] 0:NodeId[] VariablesToStore, [out] 0:StatusCode[] Results ); Table 50 - SetStoredVariables Method arguments Argument Description VariablesToStore An array of NodeIds containing configuration ... ConfigurationData of this FunctionalEntity or one of its SubFunctionalEntities. Results An array of StatusCode corresponding to the VariablesToStore input argument that indicates any errors that occurred during the processing
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.4.6.4 ClearStoredVariables Method
  arguments are defined in Table 54 . Signature ClearStoredVariables ( [in] 0:NodeId[] VariablesToClear, [out] 0:StatusCode[] Results ); Table 54 - ClearStoredVariables Method arguments Argument Description VariablesToClear An array of NodeId containing configuration ... data variables . Results An array of StatusCode corresponding to the VariablesToClear input argument that indicates any errors that occurred during the processing of VariablesToClear . If this array is populated
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.4 EditConnectionConfigurationSets method
  Table 80 . Signature EditConnectionConfigurationSets ( [in] 4:FxEditEnum Action, [in] 0:NodeId[] ConnectionConfigurationSets, [out] 0:StatusCode[] Results ); Table 80 - EditConnectionConfigurationSets Method arguments Argument Description Action Indicates whether to allow editing, commit ... ConnectionConfigurationSets A list of NodeIds of ConnectionConfigurationSets to be edited. Results A list of StatusCode corresponding to the ConnectionConfigurationSets input argument. The length of this array shall match the length
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  6.7.5.2 ProcessConnectionConfigurationSets signature
  Table 84 . Signature ProcessConnectionConfigurationSets ( [in] 4:FxProcessEnum Action, [in] 0:NodeId[] ConnectionConfigurationSets, [out] 0:StatusCode[] Results ); Table 84 - ProcessConnectionConfigurationSets Method arguments Argument Description Action The operation to be performed ... ConnectionConfigurationSets A list of NodeIds of ConnectionConfigurationSets to be processed. Results The array of StatusCode corresponding to the ConnectionConfigurationSets input argument. The length of this array shall match the length
• OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model
  10.19 ConnectionDiagnosticsDataType
  Endpoint1 in the Connection indicated by Name . FxErrorEnum is defined in 10.25 . Endpoint1Status 0:StatusCode A StatusCode associated with ErrorEndpoint1 . In some cases, this will just be a generic ... Endpoint2 in the Connection indicated by Name . FxErrorEnum is defined in 10.25 . Endpoint2Status 0:StatusCode A StatusCode associated with ErrorEndpoint2 . In some cases, this will just be a generic
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.4.2 TransferServices Type
  TransferFromDevice M 0:HasComponent Method 1:FetchTransferResultData M Conformance Units DI Offline The StatusCode Bad _ MethodInvalid shall be returned from the Call Service for Objects where locking is not supported
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  6.4.6 FetchTransferResultData Method
  last result set. The Server will return Bad_NothingToDo in the Method -specific StatusCode of the Call Service if the transfer is finished and no further result data are available ... TranslateBrowsePathsToNodeIds to retrieve the Parameter NodeId for the online or the offline representation. statusCode 0:StatusCode OPC UA StatusCode as defined
• OPC-10000-100 – OPC Unified Architecture - Part 100: Devices
  7.2 LockingServices Type
  HasProperty Variable 1:RemainingLockTime 0:Duration 0:PropertyType M Conformance Units DI Locking The StatusCode Bad _ MethodInvalid shall be returned from the Call Service for Objects where locking
• OPC-10000-120 – OPC Unified Architecture - Part 120: OPC UA and XML Data Type Mapping
  5.5 Handling of Errors
  fails because of limitations in the destination range. In an OPC UA context, the StatusCode Bad_OutOfRange should be returned (e.g. in the Value of a Variable ). Return an error ... when an incorrect syntax is encountered. In an OPC UA context, the StatusCode Bad_SyntaxError should be returned (e.g. in the Value of a Variable