Recent Posts

Pages: [1] 2 3 ... 10
1
P132, P164, P232(U) and P332 RDS Encoders / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by Jan on Yesterday at 06:42:59 pm »
Thanks, now everything is clear. This is not a P232 chip. I already had a feeling from the previous description that there was something completely different inside. If the board is from 2014, as can be assumed based on the label, then at that time we were still developing the P232 and it was not offered.

Unfortunately, I have no idea who made this board and what is actually inside. Based on the number of I/O connectors, I would guess that this is a multi function board and therefore there may not be a full-featured RDS encoder, but only a software component. It will be quite a problem to find some documentation and support for this.
2
P132, P164, P232(U) and P332 RDS Encoders / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by andrew01 on Yesterday at 05:48:16 pm »
I was thinking that most encoders (like DEVA Broadcast, 2wcom, etc.) have exact group sequence changing options and PIRA doesn't, in my eyes it would give a "nicer touch" for those who want to customise the encoder to their most desire, and with the current legacy optimised mode and with a separate mode to change the exact group sequence, it would've been some "nice-to-haves", but that is just my 2 cents.  :D

Coming back on topic, my colleague replaced the 3V battery, we think this is what is causing the group losses and probably all other problems, BUT we haven't tested it, in the evening probably we will see if it works. Can you confirm if this is the P232 chip?
3
P132, P164, P232(U) and P332 RDS Encoders / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by Jan on August 27, 2026, 10:41:06 pm »
It is pointless to insist on the exact group sequence. As the RDS standard says, the decoder must be able to process any stream regardless of the order of the groups anyway. The only thing that matters is the ratio of groups of a certain type. So whether you have 4x 0A and 4x 2A or 0A 2A at the output, there is no difference at all. The first case only has the specific advantage that you can rewrite the entire PS faster. For reasons of maintaining compatibility, no further changes are possible in existing system.
4
P132, P164, P232(U) and P332 RDS Encoders / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by andrew01 on August 27, 2026, 10:27:57 pm »
It is probably a encoder from PIRA, the old sequence had 4x 0A 2x 1A 2x 2A and that 13B ODA, plus some random 0B groups, but just to be sure we will open the transmitter, when my colleague has time  :)

Unrelated to the issue we are having, but is it possible to add a option in Magic RDS to make your own RDS sequence (like 0A,2A,0A,10A,2A,etc.) aswell as PIRA's 022R... modes in the P132,232,332, etc. pages? I have only seen 0 which is 4 0As sent, we want to send something more refined, (we would like to put the sequence as 0A 2A for now) if we can finally find a way to properly send info.  ;D
5
P132, P164, P232(U) and P332 RDS Encoders / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by Jan on August 27, 2026, 07:23:16 pm »
From what you say, I get the feeling that there is no P232 inside the device at all, but a different encoder. I probably wouldn't rely on what they have in the documentation.

I'll tell you a trick on how to find out with a relatively high degree of reliability whether the RDS encoder is from Pira.cz. If you have the opportunity to view the output RDS data in the RDS Spy program, our encoders were optimized for transmitting dynamic PS and therefore groups 0A are always transmitted in fours, and the first group always contains the first PS segment.

2A 2A 0A 0A 0A 0A 2A 2A 0A 0A 0A 0A <- this may be PIRA
2A 0A 0A 2A 0A 0A 2A 0A 0A <- this is not PIRA

If you can access the board under cover, it is possible to say more precisely what is actually inside.
6
P132, P164, P232(U) and P332 RDS Encoders / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by andrew01 on August 27, 2026, 02:36:39 pm »
Hi Jan,

As far as our tests that we have done, only via the SERVICE/RDS port we could send PI and Radiotext commands via UECP only as mentioned, I have looked in the manual and attached a picture of the setup embedded in the transmitter. Before sending UECP, we looked at the RDS sequence that the former station had, and we observed a lot of interesting stuff, such as : Slow Labelling Codes found on Group 1A: Specific application developed by the broadcaster + Unassigned SLC + Language Identification Code + Paging identification + TMC identification + Extended Country Code + EWS channel identification , and a 13B ODA, we have also observed losses of the groups. After a successful attempt to connect, we could send a proper sequence, but we still have group losses.

I was hoping you would have their WINRDS+ software that the manual advises for this exact model with UECP, the other module that they offer advises Magic RDS 3 to be used. Sadly, their support team is not exactly useful, as my colleague contacted them in the past for another issue and they spoke a very broken english, they didn't understand what he wanted from them.
7
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on August 27, 2026, 01:27:36 pm »
Version 4.3.1

http://pira.cz/rds/magicrds/MagicRDS_Setup.exe

External Text Sources:
  • Text replacing: New RegEx library supports lookahead and further features
  • Text replacing: New Filter column added
  • Text replacing bug fix: The %CLEAR% command finally works same way like in versions 4.2.x
  • Text replacing bug fix: %TERMINATE% keyword sometimes did not work for case-insensitive match
  • Test button now fills the RT+ preview
  • XML/JSON RT+: The "assign" setting now has priority over the "template"

We are constantly working to improve the program for you. We welcome your feedback.
8
Release News and Tutorials / Re: External Text Sources: Get "now-playing" information from RadioBOSS via HTTP API
« Last post by Jan on August 27, 2026, 12:48:07 pm »
ADVANCED TUTORIAL

The previous example was simple, because we only read simple information about the currently playing song. This information was compiled for us by RadioBOSS based on the name of the music file or the included tags.

Sometimes it can be useful to compile the text information according to your own criteria directly in the Magic RDS. However, this cannot be taken as a general recommendation, because it all depends on how carefully the songs are named in the music file database.

The following example reads the song title and the artist name separately. If these fields are empty, the name compiled in RadioBOSS is used (usually the file name). Next, we read the playback status. If playback is paused or stopped, the song title will not be displayed. Instead, a fixed text will be displayed. But it is possible to add the %GOTONEXT% command instead of this text and the text Source will be skipped in the Output loop until the music starts playing again.

Please note that this example requires the latest version of Magic RDS 4.
9
Release News and Tutorials / External Text Sources: Get "now-playing" information from RadioBOSS via HTTP API
« Last post by Jan on August 27, 2026, 12:24:49 pm »
SIMPLE TUTORIAL

In this tutorial, we'll look at how easy it is to use a broadcast automation system's HTTP API to retrieve information about the song currently playing. This is a more modern and secure method than sharing information via a text file.

The condition is that the broadcast automation system allows this option. We will demonstrate this on the RadioBOSS system, which returns an XML structure containing all the necessary information about the current song via the API.

We will assume that you have already made the basic settings in the Magic RDS 4. In particular, a working connection to the RDS encoder or encoders is required. It is necessary to create a new Output, a new text Source, and assign (insert) this Source to the Output. Select the Radiotext destination. See other tutorials for details.

Now we can proceed as follows:

  • Enable the HTTP API in RadioBOSS. Note the port and password.
  • Try the API output in any web browser. Yes, it's really so easy. On the same PC the API address is usually localhost:<port>/? followed by password and keywords, as described in the API documentation. In this case the full URL is
    http://localhost:9000/?pass=1234&action=playbackinfo
    The API commands may be different for each broadcast automation system. For access from another PC, type its IP address instead of localhost.
  • Configure the Magic RDS text Source as showed on the picture below.
  • Don't forget to turn on the RT+, as every station should be using this feature these days.

This was a simple example. For most cases this will suffice. In the next post, we will show an advanced usage.
10
RDS Spy / Re: Request for lager font of PI code in RDSSpy
« Last post by SWL Tobias on August 27, 2026, 11:23:23 am »
This is another try to attach the screenshot I had referred to in my earlier post.

Best Regards
SWL Tobias
Pages: [1] 2 3 ... 10