[re location of RDS scrolling information]:
Depends on what you mean by
scroll. RDS works by multiplexing many different types of data (PS, RT, CT, etc.) into one ~1200 bps serial stream. The order and rate-of-repetition of each type of data depends both on RDS standards and the individual station's choice to prioritize one type of data over the other.
The net result is that receivers cannot depend on a specific character to always be in the same place (time slice), and thus do not directly display the information as it comes in. Instead, the receiver dumps each data stream of the type that it wishes to display into a buffer, and then displays those buffers according to pre-set characteristics.
As the PS was originally designed to be a quickly-accumulated static display of the name of the current program (
Program
Service), the receiver's PS buffer gathers eight characters -- often multiple times to insure good data -- then displays those eight characters as a block. What is now called Scrolling PS is done by the station's RDS encoder changing the eight character display every three seconds or so (if done quicker the receiver may interpret it as bad data and reject the display). The 64-total-character limit gives enough space for a rotating display of artist, title and call letters without the information taking forever to complete.
There is an encoder setting which outputs the 8-character PS string shifted one character to the left every few seconds for an appearance of true scrolling, but be advised that I have seen many RDS receivers say "nuh uh" and reject the whole thing if you try to speed it up past "painfully slow". Plus holding each display for three seconds allows a car-located user to occasionally look at the road
The same buffer concept is used for the RT radiotext stream. RT was originally designed for background or informational displays; the RT display is often found under a button called "info". For display, the assumption was that the 64-character buffer could be more slowly filled (RT data transmitted at a slower rate) and could be read at a time when the user could watch the display for whole display of the scroll ("Road? What road?"). Thus RT is sometimes - but not always - presented as a truly scrolling display. It's not the station doing that -- it's the receiver.
I've seen a lot of stations put their song/artist info on both the PS and RT. I feel that is a lost opportunity to push other station info: on my network's stations I try to display web sites and request numbers as well as the slogan or calls on the RT.
Way more information than you wanted to know.
Paul E. Burt, VP Broadcast Opns
Global Security Systems, an RDS-alerting company