ERROR CODES
|
Error Code |
Description |
|
-1 |
(UNKNOWN) |
|
2 |
(DRIVER) - Devices does not exist. In the case of a COM Port Driver, this error generally indicates an invalid port setting. In the case of a bus card such as a PKTX, this error indicates the card may already be in use by another service such as RSLinx. See Resolving Conflicts with RSLinx |
|
5 |
(DRIVER) - COM PORT Access is denied – COM Port is already in use |
|
6 |
(DRIVER) - COM PORT Handle is invalid – COM Port cannot be accessed |
|
260 |
(CONTROLLOGIX) - Server Tag has invalid CPU Tagname. The CPU Tagname specified in the Server Tag dialog is invalid. Verify the spelling of the Tagname, and if it is Controller Scope or Program Scope. |
|
511 |
(CONTROLLOGIX) – The Data Type in the Server Tag Dialog box, does not match the data type of the tag in the controller |
|
512 |
(DH+/DH485) - The PLC Node setting of in the Device dialog is using a non-existent DH+/DH-485 network address |
|
768 |
(DH+/DH485) - Duplicate token hold detected. |
|
1024 |
(DH+/DH485) - Local port is disconnected |
|
1280 |
(DH+/DH485) - Application layer timed out waiting for response |
|
1536 |
(DH+/DH485) - Duplicate node detected |
|
1792 |
(DH+/DH485) – Station is off-line |
|
2048 |
(DH+/DH485) – Hardware fault |
|
4096 |
(ENET/DH+/DH485/DF1) - Illegal command or format. The PLC does not recognize the File Element setting of the tag, or cannot execute the command |
|
8192 |
(ENET/DH+/DH485/DF1) - Host has problem and cannot communicate |
|
10004 |
(WINSOCK) - A blocking operation was interrupted by a call to WSACancelBlockingCall |
|
10013 |
(WINSOCK) - An attempt was made to access a socket in a way forbidden by its access permissions |
|
10014 |
(WINSOCK) - The system detected an invalid pointer address in attempting to use a pointer argument in a call |
|
10024 |
(WINSOCK) - Too many open sockets |
|
10035 |
(WINSOCK) - A non-blocking socket operation could not be completed immediately |
|
10036 |
(WINSOCK) - A blocking operation is currently executing. |
|
10037 |
(WINSOCK) - An operation was attempted on a non-blocking socket that already had an operation in progress. |
|
10038 |
(WINSOCK) - An operation was attempted on something that is not a socket |
|
10050 |
(WINSOCK) - A socket operation encountered a dead network |
|
10051 |
(WINSOCK) - A socket operation was attempted to an unreachable network. |
|
10052 |
(WINSOCK) - The connection has been broken due to keep-alive activity detecting a failure while the operation was in progress. |
|
10053 |
(WINSOCK) - An established connection was aborted by the software in your host machine |
|
10054 |
(WINSOCK) - An existing connection was forcibly closed by the remote host |
|
10055 |
(WINSOCK) - An operation on a socket could not be performed because the system lacked sufficient buffer space or because a queue was full. |
|
10056 |
(WINSOCK) - A connect request was made on an already connected socket. |
|
10057 |
(WINSOCK) - - A request to send or receive data was disallowed because the socket is not connected and (when sending on a datagram socket using a sendto call) no address was supplied |
|
10058 |
(WINSOCK) - A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous shutdown call. |
|
10059 |
(WINSOCK) - Too many references to some kernel object. |
|
10060 |
(WINSOCK) - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond. |
|
10061 |
(WINSOCK) - No connection could be made because the target machine actively refused it. |
|
10062 |
(WINSOCK) - Cannot translate name. |
|
10063 |
(WINSOCK) - Name component or name was too long. |
|
10064 |
(WINSOCK) - A socket operation failed because the destination host was down. |
|
10065 |
(WINSOCK) - A socket operation was attempted to an unreachable host |
|
10067 |
(WINSOCK) - A Windows Sockets implementation may have a limit on the number of applications that may use it simultaneously. |
|
12288 |
(ENET/DH+/DH485/DF1) - Remote node is missing, disconnected or shutdown |
|
16384 |
(ENET/DH+/DH485/DF1) - Host could not complete function due to hardware fault |
|
20480 |
(ENET/DH+/DH485/DF1) - Addressing problem |
|
24576 |
(ENET/DH+/DH485/DF1) - Function disallowed |
|
28672 |
(ENET/DH+/DH485/DF1) - Processor in program mode |
|
32768 |
(ENET/DH+/DH485/DF1) - Compatibility mode file missing |
|
36864 |
(ENET/DH+/DH485/DF1) - Remote node cannot buffer command |
|
45046 |
(ENET/DH+/DH485/DF1) - Remote node problem due to download |
|
49152 |
(ENET/DH+/DH485/DF1) - Cannot execute due to active IPBS |
|
61441 |
(ENET/DH+/DH485/DF1) - A field has an illegal value |
|
61442 |
(ENET/DH+/DH485/DF1) - Less levels specified in address than minimum for any address |
|
61443 |
(ENET/DH+/DH485/DF1) - More levels specified in address than system supports |
|
61444 |
(ENET/DH+/DH485/DF1) - Symbol not found |
|
61445 |
(ENET/DH+/DH485/DF1) - Symbol is not proper format |
|
61446 |
(ENET/DH+/DH485/DF1) - File address doesn't point to something useful |
|
61447 |
(ENET/DH+/DH485/DF1) - File is wrong size |
|
61448 |
(ENET/DH+/DH485/DF1) - Cannot complete request |
|
61449 |
(ENET/DH+/DH485/DF1) - Data or file is too large |
|
61450 |
(ENET/DH+/DH485/DF1) - Transaction plus word size is too large |
|
61451 |
(ENET/DH+/DH485/DF1) - Access denied |
|
61452 |
(ENET/DH+/DH485/DF1) - Condition cannot be generated |
|
61453 |
(ENET/DH+/DH485/DF1) - Condition already exists |
|
61454 |
(ENET/DH+/DH485/DF1) - Command cannot be executed |
|
61455 |
(ENET/DH+/DH485/DF1) - Histogram overflow |
|
61456 |
(ENET/DH+/DH485/DF1) - No access |
|
61457 |
(ENET/DH+/DH485/DF1) - Illegal data type |
|
61458 |
(ENET/DH+/DH485/DF1) - Invalid parameter or invalid data |
|
61459 |
(ENET/DH+/DH485/DF1) - Address reference exists to deleted area |
|
61460 |
(ENET/DH+/DH485/DF1) - Command execution failure for unknown reason |
|
61461 |
(ENET/DH+/DH485/DF1) - Data conversion error |