In some cases we may see error 10046 or a Time Out error on an IP post. This can be caused if the IP is on a separate subnet that cannot be accessed from the CSRDS computer, but is more often the port. This error occurs on a TCP/IP connection request and the connection is denied or cannot be completed. Possible causes are: the port is already in use by another application, blocked by a security setting, or the device we are trying to connect to is not monitoring that port.

Common Communication Issues

  1. IP 
  • Verify the correct IP is used especially if a new device has been added.              Eg: is now
  • If the devices are on different networks you will need a second NIC or Port Forwarding. Eg. CSRDS on needs to post to
  • The correct protocol is selected. The default for Input Sources is for CSRDS to be the TCP/IP client and the input devices to the TCP/IP Server. However RCS systems link NextGen is the client so set the “Input Source is the Client” in the Other Tab and CSRDS will be the TCP/IP server.
  • 10046, Time Out and Forcefully Rejected errors are caused when CSRDS tries to make a TCP/IP connection request to the device and the request is not accepted. If the IP is correct and we can Ping the device using the IP in CSRDS then it is a port issue which can be: 
  • a.      The port on this pc is in use by another application. If nothing is running                   check Services as some applications using a port will run as a service and               not show as a running application.
  • b.      Verify the port on CSRDS and device are the same.
  • c.      Firewall/AntiVirus/Network Policy may be blocking the Port especially on                Automation Systems that tend to have restricted access. This can be the                hardest to find as the block could be on the CSRDS PC, the Device we trying          to connect to, a router/switch setting or a Network Policy.
  • Hardware or Driver issues may cause CSRDS to “Lock Up”. Since CSRDS is receiving and sending to multiple devices we can use the Event Log to narrow down the cause. Since CSRDS no longer has control the Event Log will not be updated so you will need to check the Event Log on the main window before clicking on CSRDS and the window shows as Not Responding. Generally, it will be the event after the one in the CSRDS event log that will be the issue.

2. Serial

  • Verify the correct serial cable is used and the pin outs are correct. Some Encoders require a cross-over while others are a standard RS-232/
  • The Serial Cable is in the correct Serial Port.
  • If using a USB to Serial or IP to Serial connector ensure the correct driver for the Windows O/S is installed.
  • The Comm Port settings are correct. BAUD Rate, Stop Bits, Parity, Flow Control

Note: CSRDS is designed to run unattended and “self correct” as much as possible and will ignore some error messages that may be shown in a TelNet application like HyperTerminal, Putty, Hercules, etc. As such, exiting CSRDS and using these applications may provide more information as to the connection issue.

As always, intermittent issues can be the hardest to find as CSRDS is accessing the devices every few minutes, 24x7 and may experience error that these or other less active applications may not experience.

Did this answer your question?