The communications to the automations system or satellite service is incorrect, the link is blocked. When an event is received by CSRDS, it will be logged in its raw form in the Event Viewer – Captured Event. This can be used to verify a lack of communications or a format issue.

Resolution - No Entries in the Event Viewer Captured Tab

IP Connections

The first item to check is to ensure the automation system is configured to send to the CSRDS computer on the same network, the port is correct and not used by another application and the protocol is correct UDP/TCP/IP. If another RDS application was used, check the Services to ensure the application was not running as a service and if so, stop the service. 

If CSRDS is trying to connect and receiving the Forcefully Rejected or Time Out error, the IP or Port may not be correct but more likely a Firewall, Anti-Virus on the PC, or Router but may also be, a group policy or router configuration blocking the port. This may require contacting the Corporate IT department to open the port.


Ensure the correct RS-232 cable is used. This will normally be a Null Modem and not a cross over cable. Use the device manager to ensure a Com port is shown and is the COM port defined in CSRDS Input Sources Tab. In the Input Sources Tab, ensure the com port and settings are correct. If using a USB to Serial connector, you may need to install the drivers for that device and Windows O/S.

File Monitor 

When CSRDS is monitoring a file, it must have the correct path, filename and “Read” access to the path where the file is created. If drive mapping are used, make sure it is pointing to the correct drive and this user has the necessary rights. CSRDS may have configured as an administrator with rights and running as a user without rights. Also make sure it is the correct file. The file date and time should change when a new event is played.

Receiving Data from Automation System but not Posting

 Most Now Playing feeds include events such as Jingles, Legal IDs, Voice Tracks or other events we do not want to post. To filter out these events, CSRDS uses the Categories information included in the feed to limit processing to Music and Commercial events. Music and Commercials will be used by CSRDS but are treated differently. Music events will be posted to all devices while commercial events may be ignored or posted to specific devices or services such as the streaming service for commercial substitution. 

Another cause may be the Music Format selected in the Input Sources Tab. The Music Format option is used to select the parsing routine used to extract the information from the feed. CSRDS will verify the format and if the data is not received in the select format the entry will be ignored.


Select the Event Viewer from the View Menu and select the Captured Tab. Verify the information is in the correct format. (See Supported Automation System Formats) While checking the Format, look for the Categories tag and verify Music and Commercial Categories. Some stations use multiple categories for different types of music so we need to verify with the PD what categories are used. 

Once the format and categories are verified, in CSRDS select Properties from the Tools Menu and select the Input Sources Tab. Ensure the correct Music format is selected and if a Categories Command is available, use it to add the missing categories. 

If using a serial connection and the information in the Capture Tab displays garbage characters, check the Baud Rate, Stop Bits, Parity and Flow Control.

Did this answer your question?