Search
50 result(s) for Call
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model5.7.1 Method NodeClassMethod NodeClass Methods define callable functions. Methods are invoked using the Call Service defined in OPC 10000-4 . Method invocations are not represented in the AddressSpace . Method invocations always ... Method. OutputArguments O Argument[] The OutputArguments Property specifies the result returned from the Method call. The Method NodeClass inherits the base Attributes from the Base NodeClass defined
-
OPC-10000-3 – OPC Unified Architecture - Part 3: Address Space Model8.55 PermissionTypeSourceNode field. This Permission is only valid for EventType Nodes or SourceNodes . Call 12 The Client is allowed to call the Method if this bit is set on the Object ... ObjectType Node passed in the Call request and the Method Instance associated with that Object or ObjectType . This bit affects the UserExecutable Attribute when set on Method Node . This Permission
-
OPC-10000-4 – OPC Unified Architecture - Part 4: Services6.3.1 DescriptionSession -less Service invocation is introduced for Services, such as Read , Write or Call , that do not require any caller specific state information. It is accessible through the SessionlessInvoke Service ... which provides the context information required to call Services without a Session . Session -less invocation is limited to Services of the View Service Set (with exception of RegisterNodes and UnregisterNodes
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Modelinstead of the ExpandedNodeId serverIndex . StatusCodeId identifies the overall status returned by the Method Call . InputArguments identifies the input arguments for the method. This parameter can be null
-
OPC-10000-5 – OPC Unified Architecture - Part 5: Information Model12.14 StatusResultreturn several StatusCodes and the corresponding diagnostic information that are not handled in the Call Service parameters. The elements of this DataType are defined in Table 250 . Whether the diagnosticInfo
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.5.6 AddComment MethodNormally, the NodeId of the Object instance is passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers ... shall also allow Clients to call the AddComment Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the ConditionType Node . Signature AddComment
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.7.3 Acknowledge MethodNormally, the NodeId of the object instance is passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall ... allow Clients to call the Acknowledge Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AcknowledgeableConditionType Node . Signature Acknowledge( [in] ByteString EventId
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.7.4 Confirm MethodNormally, the NodeId of the object instance is passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall ... allow Clients to call the Confirm Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AcknowledgeableConditionType Node. Signature Confirm( [in] ByteString EventId
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.5 Reset MethodNormally, the NodeId of the Object instance is passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall ... allow Clients to call the Reset Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature Reset(); This method
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.6 Reset2 Methodwith a locale shall be provided. Method result codes in Table 47 (defined in Call service) Table 47 - Reset2 result codes Result Code Description Bad_MethodInvalid The MethodId provided does
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.7 Silence MethodNormally, the NodeId of the Object instance is passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall ... allow Clients to call the Silence Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature Silence(); This method
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.8 Suppress MethodNormally, the NodeId of the object instance is passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall ... allow Clients to call the Suppress Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature Suppress(); Method Result Codes
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.10 Unsuppress MethodAlarm . Normally, the NodeId of the ObjectInstance is passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall ... allow Clients to call the Unsuppress Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature Unsuppress(); Method Result Codes
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.12 RemoveFromService MethodNormally, the NodeId of the object instance is passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall ... allow Clients to call the RemoveFromService Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature RemoveFromService(); Method result codes
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.13 RemoveFromService2 Methodwith a locale shall be provided. Method result codes in Table 64 (defined in Call Service ) Table 64 - RemoveFromService2 result codes Result Code Description Bad_MethodInvalid The MethodId provided does
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.14 PlaceInService MethodOutOfServiceState . Normally, the NodeId of the ObjectInstance is passed as the ObjectId to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, Servers shall ... allow Clients to call the PlaceInService Method by specifying ConditionId as the ObjectId. The Method cannot be called with an ObjectId of the AlarmConditionType Node . Signature PlaceInService(); Method result codes
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.15 PlaceInService2 Methodwith a locale shall be provided. Method result codes in Table 69 (defined in Call Service ) Table 69 - PlaceInService2 result codes Result Code Description Bad_MethodInvalid The MethodId provided does
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.16 GetGroupMemberships MethodSignature GetGroupMemberships( [out] NodeId[] Group ); Method result codes in Table 71 (defined in Call Service ) Table 71 - GetGroupMemberships result codes Result Code Description Bad_MethodInvalid The MethodId provided does
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.17.2 Unshelve MethodNodeId of the Shelving object as the ObjectId are passed to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall also ... allow Clients to call the Unshelve Method by specifying ConditionId as the ObjectId where the ConditionId is the Condition that has Shelving child . The Method cannot be called with
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.17.4 TimedShelve MethodNodeId of the Shelving object as the ObjectId are passed to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall also ... allow Clients to call the TimedShelve Method by specifying ConditionId as the ObjectId where the ConditionId is the Condition that has the Shelving child . The Method cannot be called with
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.17.6 OneShotShelve MethodNodeId of the Shelving object as the ObjectId are passed to the Call Service . However, some Servers do not expose Condition instances in the AddressSpace. Therefore, all Servers shall also ... allow Clients to call the OneShotShelve Method by specifying ConditionId as the ObjectId where the ConditionId is the Condition that has the Shelving child . The Method cannot be called with
-
OPC-10000-9 – OPC Unified Architecture - Part 9: Alarms & Conditions5.8.17.7 OneShotShelve2 MethodMethod Result Codes are defined in Table 90 (status code field is defined in Call Ser v ice) Table 90 - OneShotShelve2 result codes Result Code Description Bad_ConditionAlreadyShelved See Table
-
OPC-10000-10 – OPC Unified Architecture - Part 10: Programs4.2.7 Program Control Methodsoptions argument that specifies dynamic options used to determine some program behaviour. The Method Call service specified in OPC 10000-4 defines a return status. This return status indicates
-
OPC-10000-10 – OPC Unified Architecture - Part 10: ProgramsA.2.4.1 Generalcurrent state at the time the Method is called. If a Method Call is made when the DomainDownload is in a state for which that Method has no associated transition
-
OPC-10000-10 – OPC Unified Architecture - Part 10: ProgramsA.2.6.2 DomainDownloadTypecaused by the Start Method . The Start Method requires three input arguments. The Method Call service is used by the Client to invoke the Start Method and pass the arguments
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Services4.3.5 Global Discoverysearch for other applications (see 6 ). To access the GDS, the Client uses the Call service to invoke the QueryApplications Method (see 6.5.11 ) to retrieve a list of Servers that
-
OPC-10000-12 – OPC Unified Architecture - Part 12: Discovery and Global Servicessupport reverse connect within the administrative domain of the GDS. The SecurityAdmin uses the Call service to invoke the QueryApplications Method (see 6.5.11 ) with "RCP" as a ServerCapabilityFilter
-
OPC-10000-21 – OPC Unified Architecture - Part 21: Device Onboarding9.2.2 DeviceRegistrarTypeDevice using PullManagement . If an administration Client needs to register many Devices it can call the RegisterDeviceEndpoint Method multiple times in a single Call request. The GetManagers Method returns
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.2.4.3.1 Overviewrequired Arguments for each command. If multiple commands are provided in a single call, the individual commands shall be processed in the order VerifyAssetCmd , VerifyFunctionalEntityCmd , ReserveCommunicationIdsCmd , CreateConnectionEndpointCmd , EstablishControlCmd , SetConfigurationDataCmd , ReassignControlCmd ... shall be stopped at the command that caused the error, and the EstablishConnections Method Call shall be aborted, as described in 6.2.4.3.11 . An AutomationComponent may support individual commands in EstablishConnections
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.2.4.3.11 Abortbehaviour descriptions in Clauses 6.2.4.3.2 to 6.2.4.3.10 . No further commands requested for this Method Call shall be executed. The result of the commands executed with this Method Call shall ... None VerifyFunctionalEntityCmd None ReserveCommunicationIdsCmd None CreateConnectionEndpointCmd All ConnectionEndpoints in the context of this Method Call shall be deleted. EstablishControlCmd All requested ControlGroups requested in the context of this Method Call
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelindicates the maximum number of Connections that can be established in a single EstablishConnections Call (see 6.2.4 ). MaxConnectionsPerCall shall be less than or equal to MaxConnections (if both exist ... limit is specified. The optional CommandBundleRequired indicates whether this AutomationComponent requires a single Method Call for bundled commands when EstablishConnections is called (see 6.2.4.3.1 ). If the capability is not present
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modeluser or application different from the lock owner shall not be able to successfully call EstablishControl on another ControlGroup that references the same Variables or Methods in ListToBlock or ListToRestrict ... ControlGroup is assigned to a ConnectionEndpoint , only those having the rights to call EstablishConnections or CloseConnections can reassign or release control (i.e., the EstablishConnections and CloseConnections Methods
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.5.3 EstablishControl methodConnectionEndpoint or the ApplicationUri of a Client connection as provided in the CreateSession Service Call (see OPC 10000-4). If this parameter is a null string, it shall default
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.5.4 ReleaseControl methodReleaseControl method This Method Call shall release the ControlGroup and issue a Call to the Lock Objects in each Folder for the ExitLock Method (see OPC 10000-100 ). It shall
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.5.5 ReassignControl methodConnectionEndpoint or the ApplicationUri of a Client connection as provided in the CreateSession Service Call (see OPC 10000-4). It cannot be null. LockStatus 0 - OK -1 - E_NotLocked
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelzero indicates immediate clean-up. CleanupTimeout processing may be disabled by a CloseConnections Call (see 6.2.5 ). The ConnectionManagerApplicationUri can be used to identify the ConnectionManager that created this ConnectionEndpoint
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelalter the Edit Property of one or more ConnectionConfigurationSets in a single Call . ProcessConnectionConfigurationSets causes the ConnectionManager to manage Connections contained in one or more ConnectionConfigurationSets in a single Call ... reporting of all errors might result in multiple log records for a single call. For example, if there are multiple verification errors (e.g. Asset verification or FunctionalEntity verification), all would
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model6.7.3.2 Establishing ConnectionsAutomationComponent . The Method allows for the establishment of multiple Connections with a single Call . The number of Connections to be established with a single Call may be restricted ... AutomationComponent when calling the EstablishConnections Method . Figure 36 - Command sequence illustration A ConnectionManager shall call the EstablishConnections Method on the AutomationComponents , passing in one or several commands to be executed
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelMethod shall also set the Lock to the Client Session associated with this Method Call . The Lock shall behave as described in OPC 10000-100 , including the requirement to renew ... CommitUpdates or DiscardUpdates , but the Edit Property is FALSE, the Method shall ignore the Call for the ConnectionConfigurationSet . The signature of this Method is specified below. The Method parameters
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelNodeId array. Clients may inspect this list to determine the status of the individual Call to Trigger processing on each ConnectionConfigurationSet . For possible values for StatusCode , see Table
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelConnectionManager , and the user is set to "CM"). A Client can call the EditConnectionConfigurationSets Method on a ConnectionManager to release the Lock from the ConnectionManager and assign ... Client that issued the EditConnectionConfigurationSets Method Call (for additional details, see 6.7.4 ). SecurityKeyServerAddress defines the location of the SKS to be used for PubSub security configuration of this ConnectionConfigurationSet
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modeloccurred during Processing . ReadyToProcessing - This transition shall be initiated by the ProcessConnectionConfigurationSets Method Call . In addition, this state transition may also be initiated by vendor-specific means. While in State ... ProcessingResult Property in ConnectionConfigurationType . ErrorToProcessing - This transition shall be initiated by the ProcessConnectionConfigurationSets Method Call . In addition, this state transition may also be initiated by vendor-specific means
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelcontains information required for Asset verification to be used as arguments in a Method Call (e.g., EstablishConnections ). It is semantically equivalent to the AssetVerificationType as defined in 6.15.2 . The structure
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelAssetVerificationResultDataType This structure contains the result of Asset verification returned by the Method Call (e.g., EstablishConnections ). The structure is formally defined in Table 131 . Table 131 - AssetVerificationResultDataType structure Name Type
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information ModelThis element is used when calling EstablishConnections without the CreateConnectionEndpointCmd (e.g., in a subsequent Call ). False The ConnectionEndpointDefinitionDataType representation in the AddressSpace is formally defined in Table 155 . Table
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model10.23 FxCommandMaskFxCommandMask This OptionSet defines flags indicating the commands a ConnectionManager may use in its Call to the EstablishConnections Method . The FxCommandMask values are formally defined in Table 170 . Table
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modeltable in the temporary BrowsePath . This will convert the PortableRelativePath to a BrowsePath . Call the TranslateBrowsePathsToNodeIds Service with all of the BrowsePaths that are to be converted to NodeIds . Cache
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Model13.3.4 AliasName providedServers since the GDS also provides other functionality, such as certificate management or discovery. Call FindAlias with the provided AliasName(s) , which will return the target Server and the NodeId ... single Call to the GDS or AliasName Server can resolve all AliasNames in all records in the ConnectionConfigurationSet . The returned list of Servers ( Connection information) and NodeIds should be cached
-
OPC-10000-81 – OPC Unified Architecture - Part 81: UAFX Connecting Devices and Information Modelside (i.e., WriterGroups and DataSetWriters for AC1) and to retrieve the default PublisherId . This Call will typically contain the VerifyAssetCmd and the VerifyFunctionalEntityCmd if required; all further commands ... publishing side of the communication configuration and returns the information. This Call will typically contain all other required commands. The ConnectionManager updates the communication configuration for AC1 regarding the publishing
-
OPC-10000-100 – OPC Unified Architecture - Part 100: Devicesacknowledges that it received the result by passing the sequence number in the new call to this Method . The Server can delete the acknowledged result and will return the next ... result set with a new sequence number. Clients shall not call the Method before the previous one returned. If it returns with an error (e.g., Bad_Timeout), the Client