The following errors are low-level errors which are generic to evry driver. These errors are mapped to Generic errors so that CitectSCADA can recognize them. Most drivers also have a set of driver specific errors in addition to these errors.
|
Error |
Description |
|---|---|
|
0 (0x00000000) NO_ERROR |
No error condition exists. |
|
1 (0x00000001) DRIVER_CHAR_OVERRUN |
Transmitted characters could not be received fast enough. This error mapped to Generic Error GENERIC_INVALID_RESPONSE. |
|
2 (0x00000002) DRIVER_CHAR_PARITY |
Parity error in received characters. This error mapped to Generic Error GENERIC_INVALID_RESPONSE. |
|
3 (0x00000003) DRIVER_CHAR_BREAK |
A break was detected in the receive line. This error mapped to Generic Error GENERIC_INVALID_RESPONSE. |
|
4 (0x00000004) DRIVER_CHAR_FRAMING |
Framing error. Check the baud rate. This error mapped to Generic Error GENERIC_INVALID_RESPONSE. |
|
5 (0x00000005) DRIVER_MSG_OVERRUN |
The message received from the device was too long. This error mapped to Generic Error GENERIC_INVALID_RESPONSE. |
|
6 (0x00000006) DRIVER_BAD_CRC |
Checksum in received message does not match the calculated value. Error mapped to Generic Error GENERIC_INVALID_RESPONSE. |
|
7 (0x00000007) DRIVER_NO_STX |
Start of text character not present. Error is mapped to Generic Error GENERIC_INVALID_RESPONSE. |
|
8 (0x00000008) DRIVER_NO_ETX |
End of text character not present. Error is mapped to Generic Error GENERIC_INVALID_RESPONSE. |
|
9 (0x00000009) DRIVER_NOT_INIT |
Driver has not been initialized. This error is mapped to Generic Error GENERIC_UNIT_OFFLINE. |
|
10 (0x0000000A) DRIVER_BAD_TRANSMIT |
Cannot transmit message. This error is mapped to Generic Error GENERIC_UNIT_OFFLINE. |
|
11 (0X0000000B) DRIVER_CANNOT_RESET |
Cannot reset serial driver. This error is mapped to Generic Error GENERIC_CHANNEL_OFFLINE. |
|
12 (0X0000000C) DRIVER_BAD_LENGTH |
Response length is incorrect. This error is mapped to Generic Error GENERIC_GENERAL_ERROR. |
|
13 (0X0000000D) DRIVER_MSG_UNDERRUN |
Message length too short. This error is mapped to Generic Error GENERIC_INVALID_RESPONSE. |
|
15 (0X0000000F) DRIVER_INVALID_COMMAND |
The command from the server is invalid. This error is mapped to Generic Error GENERIC_INVALID_COMMAND. |
|
16 (0X00000010) DRIVER_NO_TIMER |
Cannot allocate timer resource for the driver. This error is mapped to Generic Error GENERIC_HARDWARE_ERROR. |
|
17 (0x00000011) DRIVER_NO_MORE_CHANNELS |
Too many channels specified for device. This error is mapped to Generic Error GENERIC_NO_MORE_CHANNELS. |
|
18 (0x00000012) DRIVER_BAD_CHANNEL |
The channel number from the server is not opened. This error is mapped to Generic Error GENERIC_BAD_CHANNEL. |
|
19 (0x00000013) DRIVER_CANNOT_CANCEL |
Command cannot be cancelled. This error is mapped to Generic Error GENERIC_CANNOT_CANCEL. |
|
20 (0x00000014) DRIVER_CHANNEL_OFFLINE |
The channel is not online. This error is mapped to Generic Error GENERIC_CHANNEL_OFFLINE. |
|
21 (0x00000015) DRIVER_TIMEOUT |
No response have been received within the user configure time. This error is mapped to Generic Error GENERIC_UNIT_TIMEOUT. |
|
22 (0x00000016) DRIVER_BAD_UNIT |
The unit number from the server is not active or is out of range. This error is mapped to Generic Error GENERIC_UNIT_OFFLINE. |
|
23 (0x00000017) DRIVER_UNIT_OFFLINE |
The unit is not online. This error is mapped to Generic Error GENERIC_UNIT_OFFLINE. |
|
24 (0x00000018) DRIVER_BAD_DATA_TYPE |
The data type from the server is unknown to the driver. This error is mapped to Generic Error GENERIC_INVALID_DATA_TYPE. |
|
25 (0x00000019) DRIVER_BAD_UNIT_TYPE |
The unit type from the server is unknown to the driver. This error is mapped to Generic Error GENERIC_INVALID_DATA_TYPE. |
|
26 (0x0000001A) DRIVER_TOO_MANY_UNITS |
Too many units specified for channel. This error is mapped to Generic Error GENERIC_TOO_MANY_UNITS. |
|
27 (0x0000001B) DRIVER_TOO_MANY_COMMANDS |
Too many commands have been issued to the driver. This error code can also occur if you are running a restricted version of a driver (i.e. one that will run for a limited time) for every issued read and write. This error is mapped to Generic Error GENERIC_TOO_MANY_COMMANDS. |
|
29 (0x0000001D) DRIVER_CMD_CANCELED |
Command is cancelled. This error is mapped to Generic Error GENERIC_COMMAND_CANCELLED. |
|
30 (0x0000001E) DRIVER_ADDRESS_RANGE_ERROR |
The address/length is out of range. This error is mapped to Generic Error GENERIC_ADDRESS_RANGE_ERROR. |
|
31 (0x0000001F) DRIVER_DATA_LENGTH_ERROR |
The data length from the server is wrong. This error is mapped to Generic Error GENERIC_INVALID_RESPONSE. |
|
32 (0x00000020) DRIVER_BAD_DATA |
Cannot read the data from the device. This error is mapped to Generic Error GENERIC_INVALID_DATA. |
|
33 (0x00000021) DRIVER_DEVICE_NOT_EXIST |
Device specified does not exists. This error is mapped to Generic Error GENERIC_HARDWARE_ERROR. |
|
34 (0x00000022) DRIVER_DEVICE_NO_INTERRUPT |
Device specified does not support interrupt. This error is mapped to Generic Error GENERIC_HARDWARE_ERROR. |
|
35 (0x00000023) DRIVER_BAD_SPECIAL |
Invalid special options in port database. This error is mapped to Generic Error GENERIC_BAD_PARAMETER. |
|
36 (0x00000024) DRIVER_CANNOT_WRITE |
Cannot write to variable. This error is mapped to Generic Error GENERIC_GENERAL_ERROR. |
|
37 (0x00000025) DRIVER_NO_MEMORY |
The driver has run out of memory and cannot continue execution. Minimize buffer and queue allocation or expand the computer's memory (physical or virtual memory). This error is mapped to Generic Error GENERIC_NO_MEMORY. |