CSRDS has a number of built in error trapping routines and in most cases can self-correct most issues even if it needs to restart itself to clear an issue. CSRDS uses a “port aware” that does not lock or keep a port open allowing other application and instances of CSRDS to update the same device. To do this, the program will open the port, send the data, then close the port. The actual communication will be handled by the device driver for the output device and when CSRDS issues the command to the device driver, the device takes control of the program, process the command and returns control to CSRDS. If there are device issues, control is never returned to CSRDS and it is in a Not Responding state.


  • This is more common when using an IP to Serial device. These usually work very well when connecting via IP to a serial device, entering information then closing the connection. Unless the links are very good, these do not work as well for an application that is updating the devices every few minutes 24x7. If possible, look at a different communication link. 
  • When using a USB to serial adapter, verify the device drivers for the correct windows O/S has been installed and check for updates. Several devices are “plug & play” but may require the actual driver from the manufacturer. 
  • In some cases, rebooting the computer and serial device will correct the issue. 
  • IP Connections can be more difficult to trace and correct. The most common corrections would be to re-boot the computer and IP Device, check for updates to the NIC driver, check the Ethernet cable for bad connectors, bends or breaks in the line. We can also try using a different port on the router/switch. As a last restort, we can replace the NIC card.
Did this answer your question?