OPC Client to ArchestrA – Write Errors
- Last UpdatedMar 31, 2017
- 1 minute read
In the case of an OPC Client, the following error code support is used:
|
Return Code |
Description |
|
S_OK |
The corresponding item handle was valid. The write will be attempted and the results will be returned on OnWriteComplete. |
|
E_FAIL |
The function was unsuccessful. |
|
OPC_E_BADRIGHTS |
The item is not writeable. |
|
OPC_E_INVALIDHANDLE |
The passed item handle was invalid. |
|
OPC_E_UNKNOWNITEMID |
The item is no longer available in the data source’s address space. |
|
E_xxx S_xxx |
Vendor specific errors may also be returned. Descriptive information for such errors can be obtained from GetErrorString. |
A failed write to an ArchestrA data source is handled as follows:
-
If ArchestrA responds with Nak, FSGateway sends an E_FAIL error code to the OPC Client.
-
If FSGateway cannot successfully convert the requested OPC data, this maps to a new vendor specific error for OPC indicating "Conversion Error" (OPC_E_BADTYPE).
-
If the item handle is unknown to FSGateway or ArchestrA, the OPC_E_INVALIDHANDLE error code is sent.
-
If the item name is not valid in FSGateway or ArchestrA, the OPC_E_UNKNOWNITEMID error code is sent.