|
<< Click to Display Table of Contents >> Error Codes - Protocol Specific |
  
|
|
<< Click to Display Table of Contents >> Error Codes - Protocol Specific |
|
Error codes in the range 18200 to 19103 are reserved for Protocol Specific errors returned by the equipment connected. Subtract 18200 to get the error code and then consult the Protocol or Instrument manual for details.
Modbus:
For example, a Modbus Instrument could return Error Code 18208. Thus, the Modbus error is 8, which is 'Parameter to be modified is write protected'.
For Instruments using the Modbus Protocol here is a list of the standard Modbus errors:
1 (18201) ILLEGAL FUNCTION - Indicates a driver problem, contact your SpecView Rep.
2 (18202) ILLEGAL DATA ADDRESS - Indicates either:
A. If using the Generic Modbus driver, then the address being used is invalid.
B. If using a Modbus driver written for a specific instrument, then it indicates a problem with the instrument definition file.
3 (18203) ILLEGAL DATA VALUE - The value being used is out of range for this parameter.
4 (18204) SLAVE DEVICE FAILURE - Contact your SpecView Representative.
5 (18205) ACKNOWLEDGE - Device is busy, setting the Driver Command: ECR=5 may help.
6 (18206) SLAVE DEVICE BUSY - Setting the Driver Command: ECR2=6 may help.
1460 standard timeout. If TCP connection then driver command TCPTOMS controls this timeout. If not TCP then the ordinary T driver command controls this timeout.
10004 is a TCP/IP error which Microsoft's documentation states "Interrupted function call.
10013 is a TCP/IP error which Microsoft's documentation states "Permission denied.
10014 is a TCP/IP error which Microsoft's documentation states "Bad address.
10022 is a TCP/IP error which Microsoft's documentation states "Invalid argument.
10024 is a TCP/IP error which Microsoft's documentation states "Too many open files.
10035 is a TCP/IP error which Microsoft's documentation states "Resource temporarily unavailable.
10036 is a TCP/IP error which Microsoft's documentation states "Operation now in progress.
10037 is a TCP/IP error which Microsoft's documentation states "Operation already in progress.
10038 is a TCP/IP error which Microsoft's documentation states "Socket operation on non-socket.
10039 is a TCP/IP error which Microsoft's documentation states "Destination address required.
10040 is a TCP/IP error which Microsoft's documentation states "Message too long.
10041 is a TCP/IP error which Microsoft's documentation states "Protocol wrong type for socket.
10042 is a TCP/IP error which Microsoft's documentation states "Bad protocol option.
10043 is a TCP/IP error which Microsoft's documentation states "Protocol not supported.
10044 is a TCP/IP error which Microsoft's documentation states "Socket type not supported.
10045 is a TCP/IP error which Microsoft's documentation states "Operation not supported.
10046 is a TCP/IP error which Microsoft's documentation states "Protocol family not supported.
10047 is a TCP/IP error which Microsoft's documentation states "Address family not supported by protocol family.
10048 is a TCP/IP error which Microsoft's documentation states "Address already in use.
10049 is a TCP/IP error generated when trying to talk to 0.0.0.0
10050 is a TCP/IP error which Microsoft's documentation states "Network is down.
10051 is a TCP/IP error which Microsoft's documentation states "Network is unreachable.
10052 is a TCP/IP error which Microsoft's documentation states "Network dropped connection on reset.
10053 is a TCP/IP error generated when Host Computer Software caused connection abort
10054 is a TCP/IP error generated as the Connection reset by peer
10055 is a TCP/IP error generated when the socket not found
10056 is a TCP/IP error which Microsoft's documentation states "Socket is already connected.
10057 is a TCP/IP error which Microsoft's documentation states "Socket is not connected.
10058 is a TCP/IP error which Microsoft's documentation states "Cannot send after socket shutdown.
10060 is a TCP/IP error generated when the socket connect timed out
10051 is a TCP/IP error generated when the socket was trying to connect to a turned off instrument when we got this error
10061 is a TCP/IP error generated when the socket connection was dropped by target device
10064 is a TCP/IP error which Microsoft's documentation states "Host is down.
10065 is a TCP/IP error generated when the socket was trying to reach and unreachable host
10067 is a TCP/IP error which Microsoft's documentation states "Too many processes.
10091 is a TCP/IP error which Microsoft's documentation states "Network subsystem is unavailable.
10092 is a TCP/IP error which Microsoft's documentation states "Winsock.dll version out of range.
10093 is a TCP/IP error which Microsoft's documentation states "Successful WSAStartup not yet performed.
10101 is a TCP/IP error which Microsoft's documentation states "Graceful shutdown in progress.
10109 is a TCP/IP error which Microsoft's documentation states "Class type not found.
11001 is a TCP/IP error which Microsoft's documentation states "Host not found.
11002 is a TCP/IP error which Microsoft's documentation states "Nonauthoritative host not found.
11003 is a TCP/IP error which Microsoft's documentation states "This is a nonrecoverable error.
11004 is a TCP/IP error which Microsoft's documentation states "Valid name, no data record of requested type
18036 Value Not Present warning. This is a warning, for example, if requesting a Ramp-Rate for a segment of type Dwell - use Modbus driver command NPV=-1 if this is occurring in error.
18210 With Barber-Colman Series 7 controllers first click the REM button on the Instrument View to enable writing to any variable.
18211 If using a Lantronix TCP to Serial converter then turn the following setting off inside the Lantronix: "Use MB/TCP 0x0B/0x0A Exception Responses (1=No 2=Yes)" as it is imposing a 5 second timeout above the actual devices
18517 FGH_Error_Block + 317 Phantom read error, see debug files
18625 Value Not Present error for a Scaling Of Numbers parameter
18858 ExtraData issue, check the MBI especially the enum values to see if they are correct!
18773 Code specified in codes box of config tool is illegal
18775 HoneyWell Sub Function 9 not returning the 9 so corrupt message or failed read!
18969 Block start address is wrong when used in "M" ModBus protocol as it is negative e.g. 1,1M where the parameters block is 0;12;0
18977 Failed to Tx via WriteFile. If USB COM Port then suspect faulty driver/hardware.
18979 BUFFER OVERFLOW - Over 750 bytes of data received over comms, which is likely to be caused by faulty wiring.
18991 Exception thrown from getOriginalTcpIpMode() as the slave address could not be found in the unique slave address table
19018 InitWinSock() WSAStartup() failed, Wrong COM Port selected ? e.g. IP address specified on COM1: Or resource limit reached e.g. out of memory or not able to create more threads
19037 is a TCP/IP transaction id mis-match i.e. the instrument did not return the same transaction id as the one we requested. Could be a firmware fault on the instrument
19089 is a TCP/IP error generated when GetLastError() returned -1 (0xFFFFFFFF) after read() failed on socket
19097 is a TCP/IP error generated when multiple requests are XXX'd back to SpecView because the socket has closed
19099 is a CRC low byte failure for serial comms
19100 is a CRC high byte failure for serial comms
19101 is a CRC failure when issuing a SetParam
19102 is a TCP/IP failure where the connect retries have exhausted
19103 is a TCP/IP failure where the read has had no data for 24 seconds or driver command TCPRTOMS
19104 is a TCP/IP failure to replace -2 when shutting down TCP/IP threads
19105 is a TCP/IP failure to replace -3 when closing the socket for shutting down TCP/IP threads
19106 is a TCP/IP failure where connect retries have been exhausted. Driver command TCPLCTOR has a default of 2 - actual number
19109 is a TCP/IP failure where a LAN device timed out on a read via a pended read. Driver command TCPLRTOMS has a default 5000 milli-seconds
19110 is a TCP/IP failure where a LAN device timed out on a read via a 0 on_read_complete. Driver command TCPLRTOMS has a default 5000 milli-seconds
19111 is a TCP/IP failure where the outstanding requests that could not be moved to the redundant IP address are error'd back to SV
19113 is a TCP/IP failure where the outstanding requests are XXX'd back if the they have exhausted the number of socket recreates
19114 is a TCP/IP NON failure where socket is being shut down, so this is a normal closure code NOT AN ERROR
19115 is a TCP/IP failure where the TcpIpThreadData->asyncSocketState does not match the asyncIoTimeoutActive
19116 is a TCP/IP failure where the TcpIpThreadData instance is not a valid address
19117 is a TCP/IP failure where the TcpIpProcessRequestObject::ProcessUidToIncludedRequestsList() fails to find the data in the TTL buffers via foundInTtlBuffersAndProcessedIt()
19118 is a TCP/IP Tx but no Rx and so has timed out controlled by TCPRTOMS driver command
19119 is a serial Read CRC low byte failure for serial comms
19120 is a serial Write CRC low byte failure for serial comms
19121 is a serial Read CRC high byte failure for serial comms
19122 is a serial Write CRC high byte failure for serial comms
19132 is a DateTime from IEEE that is NAN (Not A Number)
19139 is a DateTime from IEEE that is NAN (Not A Number)
19140 is a DateTime from IEEE that is NAN (Not A Number)
19141 is a DateTime from IEEE that is NAN (Not A Number)
19142 is a DateTime from IEEE that is NAN (Not A Number)
19143 is a DateTime from IEEE that is NAN (Not A Number)
19144 is a DateTime from IEEE that is NAN (Not A Number)
19154 Illegal time from device in 6 register Time Date type format
19156 is a TCP/IP failure where the connect() retries are exhausted
19157 is a TCP/IP failure where the read has had no data for 24 seconds or driver command TCPRTOMS
19158 is a TCP/IP failure where a LAN device timed out on a read via a 0 on_read_complete. Driver command TCPLRTOMS has a default 500 milli-seconds
19161 Logger host name lookup failures
19162 Logger host name lookup failures
19163 Logger host name lookup failures
19164 Logger host name lookup failures
19165 Logger host name lookup failures
19177 West ProVU parameter Wrong type specified in config tool for this West ProVU parameter check IDF/MBI
19178 West ProVU parameter Incorrect/unknown type from config tool for this West ProVU parameter check IDF/MBI compared to Driver
19244 West ProVU parameter Create Profile Next available profile number < 0
19245 West ProVU parameter Create Profile Next available profile number > 63
19246 West ProVU parameter Create Profile Profile name to create is empty
19247 West ProVU parameter Write to enum Write to read only
19248 West ProVU parameter Delete Profile Profile number to delete < 0
19249 West ProVU parameter Delete Profile Profile number to delete > 63
19255 West ProVU parameter Invalid Profile
19291 is a TCP/IP failure where a LAN device timed out on a read via a pended read. Driver command TCPLRTOMS has a default 5000 milli-seconds
19463 MBI error Missing the number after the POF in the config tool!
19476 is a TCP/IP failure where socket closed due to inactivity? Also device closed socket e.g. power off
19154 A problem with the Watlow F4T Time type
19156 is a TCP/IP failure where connect attempts to a socket are exhausted
19291 is a TCP/IP failure where connect attempts to a socket are exhausted
19309 West ProVu Send mode was set to Off when it should have been set to Send to issue the stored writes
19475 is a TCP/IP failure the socket is not up for the Tx to be issued
19476 is a TCP/IP failure the socket was closed, this is the default error code
19490 Invalid Time of Day parameter write value (SetParam)
19494 is a TCP/IP failure where the connect() has timed out
OPC:
84036 (and values above) These are OPC errors when the value being returned from the OPC server cannot be relied on. In this case please contact your OPC Server supplier.