|
FB-Name |
UA_Write |
|||
|
This Function Block is used to write a value to a single node. |
||||
|
VAR_INPUT |
||||
|
B |
Execute |
BOOL |
On rising edge node information will be written. |
|
|
B |
ConnectionHdl |
DWORD |
Connection handle. |
|
|
B |
NodeHdl |
DWORD |
Node handle. |
|
|
B |
NodeAddInfo |
STRUCT |
See UANodeAdditionalInfo. Specifies the attribute and IndexRange. This parameter is optional. If not existing the UAAI_Value (13) will be taken from internal implementation. |
|
|
B |
Timeout |
TIME |
Time to response. |
|
|
VAR_OUTPUT |
||||
|
B |
Done |
BOOL |
FB has completed its task. |
|
|
B |
Busy |
BOOL |
The FB is not finished and new output values are to be expected. |
|
|
B |
Error |
BOOL |
Signals that an error has occurred within the FB. |
|
|
B |
ErrorID |
DWORD |
Error code. |
|
|
VAR_IN_OUT |
||||
|
B |
Variable |
Vendor specific |
To be defined by vendor. |
|
|
Notes: Vendors can handle “Variable” in a vendor specific way. Independent of the vendor specific solution the mapping of the controller data type and OPC UA data type shall be handled in the function block. VAR_IN_OUT: “Variable” as would provide best type save solution for users: The client firmware is able to map the UA memory layout to the controller layout. The firmware client can receive the type definition from the OPC UA Server.Workaround would be to provide a byte array as “Variable” and the firmware client just provide the blob (UA memory layout – so called “raw data”) into that byte array. “Variable” could be the name of the variable so the internal firmware can get address, length, data type of variable. This FB is deprecated and just for backward compatibility – better use UA_WriteList |
||||
|
|
|
UA_Write |
|
|
||
|
BOOL |
|
Execute |
|
Done |
|
BOOL |
|
DWORD |
|
ConnectionHdl |
|
Busy |
|
BOOL |
|
DWORD |
|
NodeHdl |
|
Error |
|
BOOL |
|
STRUCT |
|
NodeAddInfo |
|
ErrorID |
|
DWORD |
|
TIME |
|
Timeout |
|
|
|
|
|
Vendor specific |
|
Variable |
|
Variable |
|
Vendor specific |
|
|
|
|
|
|
|
|