Error codes display in the Power Tool’s statistics display and in Mission Control’s DRVST fields. The following table lists the errors that appear in the statistics display. To view an error, select an item from the Tree Browser and select Stats Mode from the Display Mode menu. The error appears in the Last Error field of the selected item. To learn more about Mission Control errors, refer to one of the following:
Item Last Error Field
|
Error |
Description |
Possible Cause |
|
0x0000 |
No error |
N/A |
|
0x0001 |
Generic error |
Any error that does not fall into any other category. |
|
0x0002 |
Unable to copy to common memory |
The item cannot copy its data, timestamp, or quality to memory for access for iFIX NIO applications. Process Database and your operator displays may show old data. |
|
0x0003 |
Unable to set active state |
The driver cannot change the active state of the item in the OPC server. Typically, this error occurs when you select the item’s Enable check box and the server rejects the request. |
|
0x0004 |
Unable to set client handle |
The server cannot change the client handle for the item. |
|
0x0005 |
Unable to set data type |
The server cannot handle or does not support the requested data type. |
|
0x0006 |
Unable to read |
The OPC server for this item’s group rejected a read request. Typically, this error occurs when you attempt to read data from a write-only OPC item. |
|
0x0007 |
Unable to write |
The OPC server rejected a write request for this item. Typically, this error occurs when you attempt to write data to a read-only OPC item. |
|
0x0008 |
Bad handle |
The OPC server sent an asynchronous callback containing a bad or unknown handle. |
|
0x0009 |
Unable to advise |
The driver attempted to establish an asynchronous connection with the OPC server, but the request failed. Verify that your server supports asynchronous communications. |
|
0x000A |
Unable to unadvise |
The driver attempted to break an asynchronous connection with the OPC server, but the request failed. |
|
0x000B |
Exception generated |
An exception was generated based on a call to the OPC server. Refer to the driver’s Event window for a more detailed explanation. |
|
0x000C |
Invalid Item ID |
The specified item ID is invalid or unknown by the OPC server. |
|
0x000D |
Invalid Access Path |
The specified access path is invalid or unknown by the OPC server. |
|
0x000E |
Bad Item Quality |
The quality of the item is no longer Good. |
|
0x000F |
Advise not received |
The driver made an asynchronous connection to the OPC server; however, server did not return data for the item. Examine the item to ensure the item ID and the access path are valid. Also verify that the item is enabled and communicating. |
|
0x0010 |
Write clamped |
The OPC server accepted the data you are writing, but then clamped its value. |
|
0x0011 |
Write value out of range |
The data you are writing is out of range. |
|
0x0012 |
Bad type for write value |
The OPC server cannot accept the data type of the item you are writing to. |
|
0x0013 |
Insufficient access rights |
The item does not have sufficient access rights. Typically, this error occurs when you write to a read-only item. |
|
0x0014 |
Unable to block write |
The OPC Client could not process the block write. |
|
0x0015 |
Block writes disabled |
Block writes are disabled; however, a database block attempted to execute a !SEND command. |
|
0x0016 |
No data to read for block write |
The block write failed because there was no data to read in common memory. |
|
0x0017 |
Duplicate block write |
A duplicate block write was detected. The previous block write request will be discarded. |
|
0x0018 |
Error reading data |
The OPC Client could not read the necessary data. |
|
0x0019 |
Unknown Item ID |
While adding or validating an Item, the server returned an error indicating that the requested Item ID does not exist in it’s address space. This error may also indicate that the Item is defined in the server as read-only or write-only. |
The following errors are combined with the errors listed above. For example, if you receive error 1516, this is a combination of error 1500, Error reading from common memory, and Error 16, No data to read for block write. From this error, you can determine that the OPC Client was reading from common memory when it found no data for the pending block write.
|
Error |
Description |
Possible Cause |
|
0x1000 |
Driver not running |
The Start button on the Run-time toolbar has not been selected. Select the Start button to start the OPC Client. |
|
0x1100 |
Not connected to the server |
The OPC Client is not connected to the OPC server. Make sure all servers, groups, and items in the OPC Client are enabled. |
|
0x1200 |
Common memory allocation failed |
The OPC Client failed to allocate common memory. |
|
0x1300 |
Local memory allocation failed |
The OPC Client failed to allocate a temporary local memory buffer. |
|
0x1400 |
Error accessing common memory |
The OPC Client could not access common memory. |
|
0x1500 |
Error reading data from common memory |
The OPC Client could not read data from common memory. |
|
0x1600 |
Error adjusting common memory data size |
The OPC Client could not resize the memory needed for an item. |
|
0x1700 |
Out of local memory |
The temporary local memory buffer allocated by the OPC Client is full; consequently, the operation in progress cannot be completed. |
|
0x1800 |
Queue Empty |
One of the queues used by the OPC Client is empty; consequently, the driver found nothing to process. |
|
0x1900 |
Error accessing data |
The OPC Client cannot access the data it needs. |
|
0x2000 |
Item not added to server |
The item being processed does not exist on the OPC server because it was never added to the server’s configuration. |
|
0x2100 |
Outputs disabled |
Outputs for the item being processed are disabled; however, a write from the item was attempted using a database block. |
|
0x2200 |
Not setup as array |
The item being processed uses data array syntax in its item ID; however, the item is not configured as an array. To configure the item as a data array, select the Array check box. |
|
0x2300 |
Setup as an array |
The item being processed does not use data array syntax in its item ID; however, the item is configured as an array. To correct the error, clear the Array check box. |
|
0x2400 |
Address out of bounds |
The specified item ID does not exist on the OPC server. |
|
0x2500 |
Data size out of bounds |
The specified array length is larger than is supported on the OPC server or the size of the data returned by the OPC server does not match the size of the array configured in the Power Tool. |
|
0x2600 |
Data type mismatch |
The item’s specified data type does not match the data type specified by the OPC server. |
|
0x2700 |
Data type invalid |
The OPC server or OPC Client does not support the item’s specified data type. |
|
0x2800 |
Database block type invalid |
The database block you configured cannot be used with the command entered in the I/O Address field. Refer to Specifying I/O Addresses in iFIX Process Database to determine the correct block to use. |
|
0x2900 |
Data type is empty |
No data type has been selected for the item being processed. |
|
0x2A00 |
Invalid floating point value |
The server processed an IEEE floating point value that was found to have an invalid format. |
Mission Control DRVST Errors
|
Field |
Contains the... |
|
DRVSTA |
Number of the last error caused by an item. Refer to the previous tables for information on the error. |
|
DRVSTB |
Group number contains the erroneous OPC item. |
|
DRVSTC |
Item number causing the error. |
