6.7.15 RemoteCommand Method

This Method is used to issue a command to the UA Server that can then be passed on to either other internal system as illustrated in Figure 19

Figure 19 - Remote Command and Internal systems

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 actually passed on.

Figure 20 - Remote Command and Upstream/Downstream systems

The RemoteCommand Method parameters are defined in Table 55

Signature

RemoteCommand(

[in] Int32 Number,
[in] Int32 ControlCmdNumber,
[in] Int32 CmdValue,
[in] PackMLDescriptorDataType [] Parameter
);


Table 55 - RemoteCommand Method Parameters

Argument Description
Number This is the unique number for the downstream/upstream unit machine using a common tag structure as the unit machine. The number should correspond to a number on the communication network, such as network ID, or IP address identifier. This number corresponds to the “information sender” that is setting the command data in the RemoteInterface[#] structure of the unit machine.
ControlCmdNumber A user defined command number associated with coded value from a remote unit. This number is a coded value sent from one node on the network to another. The value can be associated with a unit mode change request, speed change request, a state change request, etc.
CmdValue This is the command value associated with the ControlCmdNumber above. The command value may be the speed requested, state change, etc.
Example:
For an upstream machine designated as #2 a control command number of 5 may be related to the speed setting value for the machine. A value of 400 can be used to modify the remote machine setpoint.
Command.RemoteInterface[1].Number = 2
Command.RemoteInterface[1].ControlCmdNumber = 5
Command.RemoteInterface[1].CmdValue = 400
Parameter The parameter tags associated to commanded remote interface are typically used for command parameters that are given to the unit machine from remote machines. The parameters are typically needed for coordinating the unit machine or production with other machines. The parameter value may be anything from machine limit parameters to temperatures and counter presets. The parameters are typically limited to machine parameters as product and process parameters are described in later tags.

Method result codes are defined in Table 56.

Table 56 - 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 57 specifies the AddressSpace representation for the RemoteCommand Method. RemoteCommand includes an array of InputArguments, where the input argument details are provided in Table 55.

Table 57 – RemoteCommand Method AddressSpace Definition

Attribute Value
BrowseName RemoteCommand
References NodeClass BrowseName DataType TypeDefinition ModellingRule
HasProperty Variable InputArguments Argument[] PropertyType Mandatory