For RDS/RBDS encoders we will see commands such as DPS=, TEXT= RT_TEXT=, etc. The actual command is based on the selected encoder. If using an FMB80 we will need to set the encoder itself. To do this we telnet into the encoder as these settings cannot be done in the web interface. Once Connected we issues the following commands:
UDP1.PORT=#### (selected port)
You will receive a + after each command and when completed close the Telnet session and CSRDS is good to go.
Depending on the selected options CSRDS will send up to 3 commands for every song. These are:
Dynamic PS (DPS) This is an 8 character display of the 64 character radio text. Some RDS Receivers do not display Radio Text or require the listener to press a button to see it. Selecting the Use Dynamic PS option in the Input Sources Tab will activate the DPS command. It is not as necessary on most newer receivers but for some receivers it may appear as RDS is not working if Dynamic PS is not used.
Radio Text (RT) This is the full 84 character message that will display differently on various receivers. Like DPS, newer receivers with large display area will display the full message while receivers with a single line display may show a 12-16 character scroll once then just display the first 12-16 characters. Again, this may require the listener to press a command button to see Radio Text.
Radio Text Plus (RT+) if supported on the selected encoder and RT+ is set to Yes, CSRDS will send a special command after the Radio Text command that tells RT+ devices where the artist and title information is located in the Radio Text message. For Example RTP=01,00,14,04,18,22 tells the receiver the title starts in position 0 and is 15 characters long (0-14) and the artist starts in position 18 and is 23 characters long. Devices may use this for Tagging to purchase and download the song or some receivers may use the RT+ data to display the artist and title in separate fields.
Depending on the enco0der CSRDS may also send the PI, PTY and other settings but this is normally done using the encoders software or web interface.
CSRDS uses a Port Aware function allowing other applications or instance of CSRDS to feed the same encoders. To do this CSRDS uses the Windows API to open the port, send the data and close the port. If we get an error on any of these processes we will need to check the communications (See FAQ). When CSRDS issues each command, CSRDS turns control over the Windows O/S and is locked until control is passed back. If control is not returned you will see the Not Responding message and CSRDS will be locked (hung) until control is returned or stopped using the Task Manager. This is a communication issue that will need to be resolved (See FAQ for suggestions)