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 Today at 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.
2
P132, P164, P232(U) and P332 RDS Encoders / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by andrew01 on Today at 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.
3
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on Today at 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.
4
Release News and Tutorials / Re: External Text Sources: Get "now-playing" information from RadioBOSS via HTTP API
« Last post by Jan on Today at 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.
5
Release News and Tutorials / External Text Sources: Get "now-playing" information from RadioBOSS via HTTP API
« Last post by Jan on Today at 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.
6
RDS Spy / Re: Request for lager font of PI code in RDSSpy
« Last post by SWL Tobias on Today at 11:23:23 am »
This is another try to attach the screenshot I had referred to in my earlier post.

Best Regards
SWL Tobias
7
P132, P164, P232(U) and P332 RDS Encoders / Re: zetta setup
« Last post by Jan on Today at 10:05:53 am »
Unless something has changed from previous versions, Zetta unfortunately does not provide any simple setup for RDS encoders. You need to create an appropriate .xslt file, as suggested for example in this discussion thread:
https://pira.cz/forum/index.php?topic=541.msg1689#msg1689

I definitely do not recommend this way for end users. Instead, make the information accessible so that Magic RDS 4 can read it. Not only will setup be easier, but you will also have many more options.
8
P132, P164, P232(U) and P332 RDS Encoders / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by Jan on Today at 09:57:33 am »
It is true that we have supplied a certain amount of P232 chips to R.V.R. in the past, but the cooperation was terminated because they violated the terms of business and subsequently stopped communicating.

Unfortunately, I do not know the technical details of their implementation. If your device really has a P232 chip and UECP communication works for you, then the P232 model must also work. Unless someone blocked ASCII commands using the PAC function. However, this is normally not possible to do from the port on which communication is being carried out, it would have to be done from the other communication port. Moreover, this blocking cannot be performed at all on one of the ports. I do not know which communication ports are accessible in this device.

Try both communication ports, if possible. Communication must always work on one of the ports, it cannot be blocked by any setting. If only one port is accessible on the panel and it is the blocked one, you can also solve the situation by replacing the EEPROM (24LC512/M24512).

See also Magic RDS 4 Help - devices.pdf
9
P132, P164, P232(U) and P332 RDS Encoders / zetta setup
« Last post by wyosmith on Today at 02:48:52 am »
trying to figure out Zetta, what would be a simple setup or directions for output for Zetta to read??? 
i have info going out on the RDS 164 except the song, artist etc.   
thanks
10
P132, P164, P232(U) and P332 RDS Encoders / RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by andrew01 on Yesterday at 10:43:51 pm »
Hi!
I have been recently helping a fellow colleague with his "new-old" secondhand RVR TEX300LCD (/RDS-TEX2HE) with a integrated P232 RDS Encoder (from the schematics)
We don't have the original WINRDS+ software CD, so we are using Magic RDS 4 configured as a Generic UECP encoder (as we have tried to set it up as an P232 and it would not send anything at all).

UECP communication is working. We can successfully read/write data, and any changes I make to the PI code and Radiotext update perfectly.
However, we cannot get rid of the old Dynamic PS.  :(

Whatever scrolling text was programmed into this board years ago (presumably using WINRDS+) from the old broadcaster is stuck looping. Even though Magic RDS 4 shows the new PS as being "sent", the board does not want to comply and just keeps on sending the old text that was programmed before...

Any help is appreciated, but mostly, is there any mode to fully flush the EEPROM from that old dynamic PS?
Thank you  :)
Pages: [1] 2 3 ... 10