The MultiStateDiscreteControlFunctionType describes a discrete control function (using more than two discrete values). It is formally defined in Table 109.
Table 109 – MultiStateDiscreteControlFunctionType Definition
Attribute |
Value |
||||
BrowseName |
MultiStateDiscreteControlFunctionType |
||||
IsAbstract |
False |
||||
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
Other |
Subtype of the DiscreteControlFunctionType defined in 7.6.1 |
|||||
0:HasComponent |
Variable |
CurrentValue |
UInt32 |
MultiStateDiscreteType |
M |
0:HasComponent |
Variable |
TargetValue |
UInt32 |
MultiStateDiscreteType |
M |
Conformance Units |
|||||
LADS MultiStateDiscreteControlFunctionType |
|||||
|
Table 110 – MultiStateDiscreteControlFunctionType AdditionalSubcomponents
BrowsePath |
References |
NodeClass |
BrowseName |
DataType |
TypeDefinition |
Others |
ControlFunctionState |
HasComponent |
Method |
StartWithTargetValue |
|
|
O |
The StartWithTargetValue Method starts a Function on the LADS Device with the target value as an argument.
The signature of this Method is specified below. Table 91 and Note: The optional TargetValue can be also empty. In this case it should be handled as it not exiting.Note: The optional TargetValue can be also empty. In this case it should be handled as it not exiting.
Table 92 specify the Arguments and AddressSpace representation, respectively.
Signature
StartWithTargetValue (
[in]UInt32TargetValue)
Table 111 – StartWithTargetValue Method Arguments
Argument |
Description |
TargetValue |
(Optional) This value can be used to set the target value parallel with the start method. |
Note: The optional TargetValue can be also empty. In this case it should be handled as it not exiting.
Table 112 – StartWithTargetValue Method AddressSpace Definition
Attribute |
Value |
||||
BrowseName |
StartWithTargetValue |
||||
References |
Node Class |
BrowseName |
DataType |
TypeDefinition |
ModellingRule |
0:HasProperty |
Variable |
0:InputArguments |
0:Argument[] |
0:PropertyType |
M |