Recent Posts

Pages: 1 ... 5 6 [7] 8 9 10
61
General Discussion about the RDS / Re: RVR TEX300LCD built-in RDS encoder (P232) board setup
« Last post by Jan on August 27, 2026, 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). But it's quite possible that there's a completely different type of encoder inside that doesn't come from us.

See also Magic RDS 4 Help - devices.pdf
62
P132, P164, P232(U) and P332 RDS Encoders / zetta setup
« Last post by wyosmith on August 27, 2026, 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
63
General Discussion about the RDS / RVR TEX300LCD built-in RDS encoder board setup
« Last post by andrew01 on August 26, 2026, 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  :)
64
Control Software / Re: ORBAN 8600(Si)
« Last post by Jan on August 21, 2026, 05:11:59 pm »
Some users report that working prefix for the Radiotext is R=

If UECP option is available, the Generic UECP model should probably work. External RDS encoder can be connected as well.
65
Configuration Options and Possibilities / Re: PTY NEWS
« Last post by radioroccella on August 20, 2026, 12:37:54 pm »
 :DHallo Jan, today I inserted these two lines into the "Text Conditions" page and everything seems to work!

send command:"PTY=1"send command:"PAC 0,8E=0"
send command:"PAC 0,8E=1"send command:"PTY=11"
66
Bug Reports / Re: ON AIR
« Last post by Jan on August 18, 2026, 06:06:34 pm »
Thank you for your report, but we are not aware of this issue at this time. I will need more information.

Your text source is returning empty text. This may not be a bug. Perhaps the source text is actually empty, or you are using the Text Replacing tool to change it to empty.

If you are reading a text file, then the first step I would take is to locate the file in a file explorer (e.g. Total Commander or the obscure This PC) and open it. This will give you a pretty clear idea of ​​where the problem is.
67
Bug Reports / ON AIR
« Last post by radioroccella on August 18, 2026, 05:54:06 pm »
 :(As of today, the source that's supposed to read what's being broadcast no longer works.
After a few minutes, if I try to press "TEST," it always says "magicrds."
68
Configuration Options and Possibilities / Re: Skip source if some words is found at a specific xml element
« Last post by nuno on August 18, 2026, 01:11:31 am »
Hi Jan,

Works like expected!
The solution in near future will help a lot!
Thank you for your help :)
69
Configuration Options and Possibilities / Re: Skip source if some words is found at a specific xml element
« Last post by Jan on August 17, 2026, 06:28:46 pm »
Well, if you download current build (2026-08-17), you can do following:

  • Completely remove the workaround proposed in past. Also remove the reference to the link from the Output Template.
       
  • Type following line in the Text replacing:

    Change
    %REGEXP%(?i)www.*programs

    To
    %GOTONEXT%

Explanation:
In current build, the %GOTONEXT% and %CLEAR% commands still work as you are used to. This means that even in the case of an XML/JSON source, these commands will be reflected in the resulting text. Moreover, these command now work also if matching occurs on elements which are not included in the Output Template (so they are hidden to the listener). In near future the Text replacing will include a third 'Filter' column for optinal specification of Output/Source/Element the line will apply to, so that the behaviour can be changed by the user. If you have further questions, just let me know.
70
Configuration Options and Possibilities / Re: Skip source if some words is found at a specific xml element
« Last post by Jan on August 17, 2026, 07:52:06 am »
Yes, now, in the case of XML or JSON sources, each element is processed separately, as this better reflects the logic of working with these text sources. Therefore, text replacement is no longer applied to the resulting text composed of elements according to the template.

The proposed workaround will no longer work. We will find a better solution for your specific needs.
Pages: 1 ... 5 6 [7] 8 9 10