Search

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

25 result(s) for Status

OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model

6.4.3 AuditEventType

inherits the InstanceDeclarations of that Node. HasProperty Variable ActionTimeStamp UtcTime PropertyType Mandatory HasProperty Variable Status Boolean PropertyType Mandatory HasProperty Variable ServerId String PropertyType Mandatory HasProperty Variable ClientAuditEntryId String PropertyType Mandatory ... Property because this is the time the server generated the AuditEvent documenting the action. Status identifies whether the requested action could be performed (set Status to TRUE
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs

5.2.6 AuditProgramTransitionEventType

Properties of the AuditUpdateStateEventType defined in OPC 10000-5 , except as noted below. The Status Property, specified in OPC 10000-5 ,, identifies whether the state transition resulted from a Program ... Control Method call (set Status to TRUE) or not (set Status to FALSE). The SourceName specified in OPC 10000-5 , identifies the Method causing the Program transition when
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.4.2 DataSetFieldContentMask

consists of a value and related metadata. In most cases the value comes with status and timestamp information. This DataType defines flags to include DataSet field related information like status ... layout requirements. The DataSetFieldContentMask is formally defined in Table 32 . The handling of bad status for different field representations is defined in Figure 24 , Table 34 and Table 35 . Table
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.11.2.2 Action execution sequence

Action execution is still in progress. Responder sends Response Message with ActionState = Executing, Status = Good and the payload is empty. Executing Executing Action execution completed. Responder sends Response Message with ... ActionState = Done, Status = Action result and payload provided for Good and Uncertain Status and payload is empty for Bad Status. Done Done PublishingInterval expired and did not receive Idle from
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

6.2.12.1 PubSubConfigurationDataType

enabled state of the PubSub configuration. This Enable state corresponds to the PubSub Status of the PublishSubscribe Object . Its representation in the AddressSpace is defined in Table 87 . Table
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.4.5.4 DataSetMessage header

Variant The Variant can contain a StatusCode instead of the expected DataType if the status of the field is Bad. The Variant can contain a DataValue with the value ... statusCode if the status of the field is Uncertain. 01 RawData Field Encoding The RawData field encoding is defined in 7.2.4.5.11 . 10 DataValue Field Encoding The DataSet fields are encoded
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.4.2 VerboseEncoding

following example shows a DataSetMessage with VerboseEncoding and DataSet fields without field specific status and timestamps. { "PublisherId":"MyPublisher", "DataSetWriterId":102, "SequenceNumber ... following example shows a DataSetMessage with VerboseEncoding and DataSet fields with field specific status and timestamps. Status is omitted if the Code is 0. { "PublisherId":"MyPublisher
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.2.5.5.5 Status

Status A NetworkMessage with MessageType Status is a JSON object with the fields defined in Table 191 . Table 191 - JSON Status definition Name Type Description MessageId String A globally unique ... message. This value is mandatory. MessageType String This value shall be "ua-status". This value is mandatory. PublisherId String The Publisher that sent the message. This value
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

7.3.4.7.7 status Topic level

status Topic level The status Topic has the form: <Prefix>/<Encoding>/status/<PublisherId> The <PublisherId> Topic level is the PublisherId ... application sending the messages. The messages are instances of the Status MessageType (see 7.2.2 ). A Publisher that is exclusively using a PublisherId shall register a Status message as an MQTT
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

9.1.2 Configuration behaviours

allow changes through parameter write only when the related Object has the Status Disabled and to apply the new configuration settings when the Status is changed to Operational . Therefore write ... operations to configuration parameters should be rejected with Bad_InvalidState if the Status is not Disabled
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.1.7 Header layout for DataSetMessages

header shall consist of the following fields according to this header layout: DataSetFlags1 DataSetMessageSequenceNumber Status Additional restrictions: Fields within the payload use RawData Field Encoding Only data key frame DataSetMessages ... Field Encoding 01 RawData Field Encoding Bit 3: DataSetMessageSequenceNumber enabled = 1 Bit 4: Status enabled Bit 5: ConfigurationVersionMajorVersion enabled = 0 Bit 6: ConfigurationVersionMinorVersion enabled = 0 Bit 7: DataSetFlags2 enabled
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.2.2.7 Header layout for DataSetMessages

consist of the following fields according to this header layout: DataSetFlags1 DataSetFlags2 DataSetMessageSequenceNumber Timestamp Status MinorVersion Additional remarks: Fields can use any encoding All types of DataSetMessages (Data Key Frame ... Field Encoding <anything> Bit 3: DataSetMessageSequenceNumber enabled = 1 Bit 4: Status enabled = 1 Bit 5: ConfigurationVersionMajorVersion enabled = 0 Bit 6: ConfigurationVersionMinorVersion enabled = 1 Bit 7: DataSetFlags2 enabled
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.3.3.5 Examples

Timestamp":"2021-09-27T18:45:19.555Z", "Status":{"Code":1073741824}, "MessageType":"ua-keyframe", "WriterGroupName":"WriterGroup1 ... false and with SourceTimestamp and StatusCode flags set in the DataSetFieldContentMask . The Status is omitted if the Code is 0. { "PublisherId":"MyPublisher", "DataSetWriterId
OPC-10000-14 – OPC Unified Architecture - Part 14: PubSub

A.3.4.4 Configuration parameters

SequenceNumber is always omitted for Action messages. Bit 3: Timestamp = 1 Bit 4: Status = 1 The Status is omitted for ActionRequest messages. Bit 5: MessageType configurable (default
OPC-10000-17 – OPC Unified Architecture - Part 17: Alias Names

D.3.4 Header layout for DataSetMessages

range 1-2: Field Encoding 00 - Variant Bit 3: DataSetMessageSequenceNumber enabled = 1 Bit 4: Status enabled = 0 Bit 5: ConfigurationVersionMajorVersion enabled = 0 Bit 6: ConfigurationVersionMinorVersion enabled = 0 Bit 7: DataSetFlags2
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

5.5.4.2 Operation

lifetime of a logical connection on an AutomationComponent can be tied to its Status (see 6.6.2 ), which is, in turn, tied to the reception of data or heartbeat messages ... allows the deletion of all resources allocated to a specific ConnectionEndpoint once its status indicates loss of data reception. This revision of the specification supports logical connections that utilise
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.2.4.2 EstablishConnections signature

AssetVerificationResults VerificationStatus are formally defined in Table 10 . Table 10 - AssetVerificationResults VerificationStatus Status Codes Result Code Description Bad_NodeIdUnknown AssetToVerify does not exist in the Server address space. Bad_NodeIdInvalid ... StatusCodes for the ConnectionEndpointConfigurationResults FunctionalEntityNodeResult are formally defined in Table 11 . Table 11 - FunctionalEntityNodeResult Status Codes Result Code Description Bad_NodeIdUnknown The NodeId for FunctionalEntityNode does not exist
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.2 FunctionalEntityType definition

HasComponent Object 3:OperationalHealthAlarms 0:FolderType O 0:HasComponent Object 5:Status 5:FunctionalGroupType O 0:HasComponent Object 5:Diagnostics 5:FunctionalGroupType O 0:HasComponent Object 5:Operational 5:FunctionalGroupType ... during normal operation, like process data (see OPC 10000-100 Recommended FunctionalGroup BrowseNames ). The Status FunctionalGroup contains Variables which describe the general health of the FunctionalEntity
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.4.8 ConnectionEndpointsFolderType

CommHealthOptionSet 0:BaseDataVariableType O, RO ConformanceUnits UAFX FunctionalEntity Base The optional CommHealth aggregates the Status of all ConnectionEndpoints contained in the Folder . The aggregation rules are defined as follows ... least one ConnectionEndpoint established at this FunctionalEntity has its Status set to Error , the CommHealth CommError bit shall be set. If at least one ConnectionEndpoint established at this FunctionalEntity
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.5.2 ControlGroupType definition

UAFX". The Locks are automatically renewed as long as the Status of the ConnectionEndpoint is different from Error . A Controls Reference (see OPC 10000-23 ) shall be added with
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.2 ConnectionEndpointType definition

Subtype of the 0:BaseObjectType defined in OPC 10000-5 0:HasComponent Variable 3:Status 3:ConnectionEndpointStatusEnum 0:BaseDataVariableType M, RO 0:HasComponent Variable 3:RelatedEndpoint 2:RelatedEndpointDataType 0:BaseDataVariableType ... Diagnostics 0:HasComponent Variable 3:ModificationTime 0:DateTime 0:BaseDataVariableType O The Status describes the current status of a ConnectionEndpoint . This status is illustrated by the state machine in Figure
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

6.6.3 PubSubConnectionEndpointType definition

referenced DataSetWriter shall be associated with a null DataSet to publish the heartbeat. The Status is determined based on the Status of the referenced DataSetReader and DataSetWriter . If a required ... Reference (see Mode ) to a DataSetReader or DataSetWriter is missing, the Status shall be Initial . For PubSubConnectionEndpoints with the Mode value of PublisherSubscriber , the Status shall be determined
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.9 CommHealthOptionSet

Value Bit No. Description CommInitial 0 At least one of the ConnectionEndpoints has its Status set to Initial . CommPreOperational 1 At least one of the ConnectionEndpoints has its Status ... PreOperational . CommError 2 At least one of the ConnectionEndpoints has its Status set to Error . Bits 3:15 are reserved for future use. The CommHealthOptionSet representation in the AddressSpace
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.17 ConnectionEndpointStatusEnum

ConnectionEndpointStatusEnum This enumeration defines the values of the Status of a ConnectionEndpointType . The enumeration is formally defined in Table 156 . Table 156 - ConnectionEndpointStatusEnum items Name Value Description Initial 0 Initial ... status of the logical connection. No communication-model o bjects referenced. Ready 1 Logical connection is ready to operate; communication-model objects are referenced but not enabled. PreOperational 2 PreOperational
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model

10.20 ConnectionStateEnum

removed (e.g., due to ConnectionEndpoint auto-cleanup or AutomationComponent power-cycle). ConnectionStateEnum combines the Status of all ConnectionEndpoints participating in a Connection (see 10.20 ). For Connection types bidirectional, unidirectional ... unidirectional with heartbeat, the value is calculated according to Figure 58 . Endpoint1 Status Endpoint2 Status Initial Ready PreOperational Operational Error Initial ConnectionInitial ConnectionInitial ConnectionInitial ConnectionInitial ConnectionInitial Ready ConnectionInitial ConnectionReady ConnectionReady