This Method is used to issue a command to the UA Server that can then be passed on to any other internal system as illustrated in Figure 19 or it can be used to pass information on to an upstream or downstream system as illustrated in Figure 20. In both cases, it is up to the UA Server and/or the underlying system to determine when the command is passed on.
Figure 19 - Remote Command and Internal systems
Figure 20 - Remote Command – Line and Upstream/Downstream systems
The RemoteCommand Method parameters are defined in Table 53
Signature
RemoteCommand(
[in] PackMLRemoteInterfaceDataType[] RemoteInterface);
Table 53 - RemoteCommand Method Parameters
|
Argument |
Description |
|
RemoteInterface |
This structure is an array of remote interface information which include Number, ControlCmdNumber, CmdValue and Parameter. Parameter itself is a structure formally defined in 6.5.4. The PackMLRemoteInterfaceDataType is formally defined in 6.5.7 |
|
|
|
Method result codes are defined in Table 54.
Table 54 - RemoteCommand Method result codes
|
Result Code |
Description |
|
Bad_MethodInvalid |
See OPC 10000-4 – Services for the description of this result code. (The Method id does not refer to a Method for the specified Object.) |
|
Bad_NotImplemented |
See OPC 10000-4 – Services for the description of this result code. (Requested operation is not implemented.) |
|
Bad_NodeIdUnknown |
See OPC 10000-4 – Services for the description of this result code. (Used to indicate that the specified Object is not valid) |
|
Bad_InvalidState |
See OPC 10000-4 – Services for the description of this result code. (The operation cannot be completed because the Object is closed, uninitialized or in some other invalid state.) |
|
Bad_MethodInvalid |
See OPC 10000-4 – Services for the description of this result code. (The Method id does not refer to a Method for the specified Object.) |
|
Bad_ArgumentsMissing |
See OPC 10000-4 – Services for the description of this result code (The Client did not specify all of the input arguments for the Method.) |
|
Bad_TooManyArguments |
See OPC 10000-4 – Services for the description of this result code (The Client specified more input arguments than defined for the Method.) |
|
Bad_InvalidArgument |
See OPC 10000-4 – Services for the description of this result code. (Used to indicate in the operation level results that one or more of the input arguments are invalid. The inputArgumentResults contain the specific status code for each invalid argument.) |
|
Bad_TypeMismatch |
See OPC 10000-4 – Services for the description of this result code. (Used to indicate that an input argument does not have the correct data type.) |
|
|
|
Table 55 specifies the AddressSpace representation for the RemoteCommand Method. RemoteCommand includes an array of InputArguments, where the input argument details are provided in Table 53.
Table 55 – RemoteCommand Method AddressSpace Definition
|
Attribute |
Value |
||||
|
BrowseName |
RemoteCommand |
||||
|
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
|
HasProperty |
Variable |
InputArguments |
Argument[] |
PropertyType |
Mandatory |
|
|
|
|
|
|
|