2TVR was still using Dynamic PS when I passed through a few weeks ago.
I’m not sure if/how many characters the LPS field is limited to? But I can see that setting presets based on LPS could problematic for some radios in having to wait for the first few/most appropriate characters to appear.
Whilst I welcome LPS, I’m thinking a 12 character limit would have been a good idea, 8 characters is a bit short for some stations… Any longer description can always go in the RT field.
Stumbled upon an interesting bit about the nibbles & bytes that comprise the PI code in a very recent 2021 RDS specification document.
Apparently a PI code of: xx00 where x=any HEX number, is not to be used for fixed location radio transmitters, but rather the last two digits of a PI code, where the 3rd & 4th digits are both 00 is for exclusive use of low powered short range transmitting devices. I guess that could be for the low power mics & MP3 transmitters in vehicles etc.
So which broadcasters fall foul of that? Several Australian community radio stations & even a few commercial broadcasters here.
An example would be Radio 2MW Murwillumbah, NSW on 103.5MHz with a PI Code of: 5000
In tech jargon; nibbles 3 & 4 of the PI Code are not to be 00 for a radio broadcast station.
The RDS spec on pages 30 & 31 describe this.
The RDS spec for LPS maximum character length is: 32 bytes, UTF-8 coded characters.
To the best of my knowledge only RDS2 (not RDS1) supports UTF-8 coded characters.
I’m curious to know if anyone has been able to decode the Long PS (LPS) [Combined string of Station Name Frequency & Location is PS field] of the Rebel/The Breeze radio stations trailing the technology in any of their modern RDS capable vehicles over the past few days?
Apparently a small technical change has happened again to the two stations in just the Gold Coast region late today, so if no LPS received in past few days, it might be worth trying again now or tomorrow.
We’d all love to see any successful results.
BTW more updates to our RDS List over the weekend too.
No RDS on 92.3 3ZZZ tonight. This appears very recent.
Also another RDS change in Melbourne & I ask myself why o why did they do this? 3RRR have changed their PS from: 3RRR____ to: a centred ‘3RRR’ display.
(Re above; note to @melb_mateyy0 )
Bucketts Radio now added to the Google Worksheet (and thanks for the callsign info @TV-Expert ).
@ozbark I also managed to confirm the SKY Racing Taree (105.7) PI code and AF info whilst I was at the nearby Mograni Lookout as well. Have updated that on the worksheet too.
Yes I don’t think they could get away with no DAB in the UK. The majority of radio listening in the UK is now DAB even overtaking FM. I think DAB is also mandated for all new cars there now. I also recall RDS being in cars I drove over there long before it appeared here.
I collected this data as a bit of a test by using the ACMA transmitter spreadsheet and mapping the info from the RDS list along with station names from a list of callsigns (with a few manual fixes, and LPON data is missing). The end result is a CSV file which gets imported into the fmdx.pl site each week. It contains city/area, transmitter lat/lon, frequency, power, pol, station name, PI, PS and a couple of other details. This is the file - http://141.147.107.116:8080/ordb/AUS_FM.csv
It’s ended up working pretty well generally, but any changes going forward will have to be dealt with by a manual update each time. I’m wondering if there’s any feasible way of having another sheet in the Google Sheets RDS List with this transmitter data in, where updated RDS details could be mapped from the the other sheets, maybe even automatically? This might not be feasible or desirable for the list, but I just wanted to put the question out there. Also to say again that this project is totally open source, it’s purely for DXers using the webserver to be able to get a nice visualisation of transmitter/station identification.