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 September 29, 2026, 09:30:38 pm »
Hi Jan, OK, it works. Two pins on the PIRA processor were out of the socket; everything is working now and there are no communication errors. Thanks, and have a good evening. :) :) :) ;D ;D
42
Configuration Options and Possibilities / Re: Version 4 help (reading XML file)
« Last post by Jan on September 29, 2026, 08:52:33 pm »
The version released today includes expanded error messages for broken XML file processing. This might help you identify where the problem lies.
43
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on September 29, 2026, 08:35:23 pm »
Version 4.3.2 (build 2026-10-10)

https://magicrds.com/download/MagicRDS_Setup.exe

  • New add-on: Network adapter assign. Please read Help - netadapt.pdf for details.
  • All HTTP/HTTPS client operations now use latest libcurl library rather than WinINet API
  • Legacy HTTP client removed
  • Simple HTTP and XML Template models: test button and adjustable distribution delay added
  • Bug fix: Simple HTTP model sometimes indicated trial in paid licenses
  • Bug fix: Access violation if XML file was corrupted

Network adapter assign: Professional multi-network operation

Many general-purpose applications leave all network selection entirely to the operating system. That approach is convenient, but it may not provide sufficient control for demanding installations. Assign Network Adapter add-on gives Magic RDS 4 explicit control over how individual connections and services access the network. This improves predictability, separation of network traffic and operational reliability — exactly the kind of control expected from professional RDS and broadcast automation software.

We have modified a significant portion of the code related to network operations. Although we have made every effort to test everything thoroughly, it is still possible that we have not covered every real-world scenario. Please report any potential issues to us, and we will resolve them as quickly as possible.

Legacy HTTP client removed

In this version, the implementation of a modern interface for HTTP/HTTPS communication necessitated the removal of the legacy HTTP client. This step had been announced in advance via a notice within the program itself. The simplest replacement is to create a new Connection with the "Hybrid radio" kind and "Simple HTTP" model (see the image). Current solution now supports:
  • Latest secure https protocols
  • Selectable GET or POST or combined method
  • Multiple instances (can feed any number of websites or devices with different data)
  • XML/JSON elements in separate variables (for example artist and title)
  • Adjustable distribution delay
Alternatively, use the Connection kind Bridge and appropriate "Internal channel" commands.
Please note that sending text to the website works under all licenses but in the "Basic" and "Activated" license it operates in trial mode.

We continue to maintain the application so that it remains runnable on old versions of Windows, such as XP and Vista. However, some modern network features and secure protocols depend on capabilities provided by the operating system and may be unavailable or limited.
44
PIRA32 RDS Encoder / Re: Firmware update fail 1.6a PIRA 32 anno 2006
« Last post by Jan on September 27, 2026, 10:36:53 pm »
That’s unfortunate. A third attempt is pointless as there is clearly another fault somewhere. We could check and repair the board if you sent it to us, but when you factor in the time and several shipping costs, it doesn't make economic sense for a 20-year-old board. It will be more advantageous for you to purchase a module from our current offer. You get incomparably greater value for similar cost.

I advised you to check the supply voltage before the replacement. You didn't mention whether you did so. From experience, I can tell you that the cause of most inexplicable faults lies in the power adapter, while the device itself is fine.
45
PIRA32 RDS Encoder / Re: Firmware update fail 1.6a PIRA 32 anno 2006
« Last post by radiosiciliaexpress on September 27, 2026, 10:16:58 pm »
Hi Jan, after some time I tried replacing the PIRA32 PIC microcontroller you sent me, but it doesn't work: both LED 1 and LED 2 remain off, and there is no RDS signal output. So, I put the old PIC back in; at least that one works, even though I can't program it with new messages—it always gives the same "communication error"!
If you could send another microcontroller, I would be grateful—I'm even willing to pay for it again—but please test it before shipping it to me. Thanks.
46
Configuration Options and Possibilities / Re: Version 4 help (reading XML file)
« Last post by Jan on September 27, 2026, 03:27:59 am »
It has nothing to do with the device. Simply attach the original XML file to an email and send it to me, or attach it here to the post. There is likely something in the file that is causing the XML parser to reject it as invalid.

Please send the actual file rather than copying and pasting its contents. Copied text may not preserve the original data exactly — for example, the character encoding or special characters may be altered or lost.

You could also try an online XML validator, but that would not provide me with the information I need to determine whether the application needs to be modified.

Judging by the declared character encoding (ISO-8859-1), I suspect that the application generating this XML file may be relatively old. This legacy 8-bit encoding is still valid, but UTF-8 has long been the standard choice for modern XML applications. This is precisely where a potential source of problems may lie: if the application indicates the now less common ISO-8859-1 encoding but actually uses a different character set.

You should double-check that you are using the current version of Magic RDS — currently 4.3.1, which is displayed after pressing the Home button on the top bar.
47
Configuration Options and Possibilities / Re: Version 4 help (reading XML file)
« Last post by dennism on September 27, 2026, 02:28:32 am »
I've tried running version 4 on three different computers but none will display anything in the Find Element window. I'm sure there's an incompatibility somewhere. This is trying to use version 4 with a P332. I also have a 232U being fed from PlayoneONE and it works fine.

I'm going to go back to Version 3 and try again.
48
P132, P164, P232(U) and P332 RDS Encoders / Re: FCC Cybersecurity Rules
« Last post by Bob Crittenden on September 25, 2026, 04:54:20 pm »
Thanks for your prompt response!  I don't use Magic RDS, but I probably need to start using it.  Is there a link to a tutorial that is available?
Bob
49
P132, P164, P232(U) and P332 RDS Encoders / Re: FCC Cybersecurity Rules
« Last post by Jan on September 25, 2026, 04:12:25 pm »
We are preparing an update to the internal website that will allow you to set a longer password than is currently possible. While this will not affect security in any way, it will ensure formal compliance with an FCC requirement.

If you do not want to wait, you can set a 15-character password right now. Use the Magic RDS 4 program's GUI to do so.
50
P132, P164, P232(U) and P332 RDS Encoders / P132/P332 - FCC Cybersecurity Rules
« Last post by bobcvols on September 25, 2026, 03:44:54 pm »
Good morning, Jan -

We have 3 P332's that we use on three facilities - extremely dependent!

We are staring down new U.S. FCC cybersecurity rules which require enhanced security measures for our EAS system and devices that are connected to it through our program chain.  RDS units have been mentioned in some of the discussion that I have seen, although that may refer to RDS that is generated by transmitters.  Here is a set of FCC FAQ's that it released earlier this week:
https://www.fcc.gov/faqs-EAS-Cybersecurity-Requirements

Do the Pira boxes qualify, in your estimation?  If so, with our exposure to the Internet, I wanted to change our password on these units to a 15-character, randomly-generated password.  But, the Pira interface only allows me to insert 10 characters. What would you suggest?

Thanks!
Pages: 1 ... 3 4 [5] 6 7 ... 10