Recent Posts

Pages: 1 ... 3 4 [5] 6 7 ... 10
41
PIRA32 RDS Encoder / Re: Firmware update fail 1.6a PIRA 32 anno 2006
« Last post by radiosiciliaexpress on June 04, 2026, 07:38:37 pm »
Hi Jan, I ran the firmware update. The first time it gave me "failed at 47550 B-CRC error. Try again." I tried again and it updated with "Update OK." So far, so good...but Magic RDS isn't communicating. It keeps giving me a communication error!
I even did a RESET, but nothing works. I don't think it's a cable issue. I'll try again tonight. Any advice? Thanks, Francesco.
42
RDS Spy / Re: Enhanced RT ODA support?
« Last post by andrew01 on June 04, 2026, 07:12:01 pm »
The same abuse logic on DAB+... works on FM, I have seen here radios insert characters such as <,>,!,* and they are all shown on top of radio lists. Dynamic/Scrolling PS use is a problem everywhere , except in places where the use of such practices is banned by regulators (like France, Slovakia, and a few). Some tuners like the one I have, also memorise parts of dynamic PS's (like a frequency or a fragment of artist - title info), without it being updated unless the text is static for a period of time, it creates a huge mess when trying to find a station because of this.

Coming back on topic, is eRT/eRT+ confirmed to be implemented in the RDS2 capable encoders and RDS Spy?
43
PIRA32 RDS Encoder / Re: Firmware update fail 1.6a PIRA 32 anno 2006
« Last post by radiosiciliaexpress on June 04, 2026, 12:19:55 pm »
Good morning JAN, always kind and quick in responding, I'll try as soon as I get to the office. I'll let you know - always THANK YOU :D :D ;)
44
RDS Spy / Re: Enhanced RT ODA support?
« Last post by Jan on June 04, 2026, 11:14:57 am »
We have been trying for years to convince radio stations to stop using dynamic or scrolling PS. One reason is that car radios cannot correctly display the PS name in the list when scanning the band. Car radio manufacturers solved it in their own way and no longer display PS at all  :)

Another crazy thing is the abuse of station names in DAB, where stations insert various characters to appear at the beginning of the list. The resulting list sometimes looks terrible. It wouldn't surprise me if after some software update they end up at the bottom of the list or aren't shown at all.

45
RDS Spy / Re: Enhanced RT ODA support?
« Last post by andrew01 on June 04, 2026, 10:51:37 am »
RDS2 might never be of interest within car manufacturers because of very few users of RDS2 in general (at least that is how I see it, in my country we have only 3 STATIONS using RT+, and 2 using Long PS, which are part of RDS1). Many regulators do not agree with going over 75khz for extra RDS carriers. It is true that radio is not of interest for car manufacturers (the interest moved to streaming apps), for example new tuners from various brands, have a database based on the PI Code so they don't have to show the current RDS-PS (this way they can fit the full name and not be constrained to RDS-PS's 8 character capability), only if they don't have it in their database, then RDS-PS will be shown.

Still, coming back to eRT/eRT+, if it can be added to the existent RDS2-capable encoders, I don't see why it shouldn't be included, the few users who use RDS2 are users who would love having every single function available to be sent :)
46
RDS Spy / Re: Enhanced RT ODA support?
« Last post by Jan on June 04, 2026, 08:40:30 am »
As a manufacturer, we will not go against the currently valid standard. It would not even be technically possible if we want to maintain the quality level of the current functions. The encoders support the UECP ODA protocol, so developers have the opportunity to try it out.

IEC 62106-6

Coding of enhanced RadioText (eRT)

Broadcasting conventions

"The transmission capacity of RDS is not sufficient to use normally RT and eRT at the same time on stream 0, i.e. it shall be either one or the other RadioText mode. If RDS2 is used, eRT can be on the upper streams and RT can be at the same time on stream 0."


I understand your effort. This however needs to be directed at car radio manufacturers so that they finally implement RDS2.
47
PIRA32 RDS Encoder / Re: Firmware update fail 1.6a PIRA 32 anno 2006
« Last post by Jan on June 04, 2026, 05:28:04 am »
I remember you. It is definitely correct to use the latest firmware version. Current control software may not work properly with 20-year-old firmware, many functions have been added since then.

Updating the firmware is a completely seamless process, even for a 20-year-old piece. If the update process is interrupted unintentionally, it is always possible to start it again. The procedure is described in the instructions. Simply put, first run the update and then turn on the device. The bootloader is stored in a memory that cannot be overwritten, so an update can never cause a complete loss of communication.

If the process is still not successful, look for the problem elsewhere, in the power supply or communication cable. You are using a serial device on a new computer. Be aware that the most common source of problems are cheap USB to RS232 converters or their drivers. In any case you need a laplink cable for your unit (wiring 2-3, 3-2, 5-5).
48
RDS Spy / Re: Enhanced RT ODA support?
« Last post by andrew01 on June 04, 2026, 12:02:25 am »
It would be nice to have the eRT/eRT+ function available on the RDS encoders, maybe not everyone will use it, but if some receivers (2 car brands are a big thing/chunk of tuners, honestly) can support it, why not include it? Besides, 128 UTF-8 bytes are a big thing compared to normal RT's 64 characters.

Through RDS1, eRT/eRT+ seem to work fine (no issues with decoding on a external decoder application), with the only disadvantage being that it "eats" % of other groups.
49
PIRA32 RDS Encoder / Firmware update fail 1.6a PIRA 32 anno 2006
« Last post by radiosiciliaexpress on June 03, 2026, 11:33:25 pm »
Good evening, something strange happened to me after trying to update the PIRA 32 firmware with the latest 1.6a. Both the Magic 3 and Magic 4 software no longer communicate....it says "Communication Error!" It has worked perfectly for over twenty years, it was better if I didn't update..... Thank you if Jan replies. THANKS FRANCESCO
50
Control Software / Re: Setting up RDS with RadioDNS
« Last post by Jan on June 03, 2026, 08:43:10 am »
It's great that you provided pictures of your setup because the reason is now clearly visible.

To operate a hybrid radio, which includes RadioDNS, it is necessary to clearly tell the receiver which station it is currently tuned to. Since RadioDNS operates in many countries and on several continents, the PI alone (which works more or less only at the national level) is not enough for that identification, so the ECC byte must also be added. These two pieces of information (PI and ECC) must exactly match your settings on the hybrid radio server. RDS encoders that do not support ECC service can no longer be used and must be replaced.

PI and ECC codes are usually assigned by the national authority. Otherwise, you can use the built-in calculator (select Help and PI Calculator from the menu).

So now to your case. You have set ECC to A0, but you are using the UECP model. It is specific for it that individual RDS services are turned on by inserting the appropriate group type designation into the Group Sequence. In your case, for ECC to actually be transmitted, you have to insert 1A into the Group Sequence. It is there by default, but you probably deleted it thinking that it was not needed.

For the BW V3 the 'READBEST' model may be a better choice, however, this has no effect on the case described above.
Pages: 1 ... 3 4 [5] 6 7 ... 10