Recent Posts

Pages: [1] 2 3 ... 10
1
PIRA32 RDS Encoder / Re: Firmware update fail 1.6a PIRA 32 anno 2006
« Last post by Jan on Yesterday at 10:36:53 pm »
That’s unfortunate. A third attempt is pointless if there is clearly another fault with the board. We could repair it if you sent us the entire unit, but when you factor in the time and 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.
2
PIRA32 RDS Encoder / Re: Firmware update fail 1.6a PIRA 32 anno 2006
« Last post by radiosiciliaexpress on Yesterday at 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.
3
Configuration Options and Possibilities / Re: Version 4 help (reading XML file)
« Last post by Jan on Yesterday at 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.
4
Configuration Options and Possibilities / Re: Version 4 help (reading XML file)
« Last post by dennism on Yesterday at 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.
5
Free Topic / Custom Embroidery Patches In Gulf
« Last post by noahadam on September 26, 2026, 09:09:29 am »
Greetings from Gulf Patches, the leading patch maker in the Gulf region. We create unique patches in a number of styles, including morale, PVC, iron-on, custom embroidered patches Yemen, and many more. Enhance your new appearance with our personalized patches. Buy now.
6
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
7
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.
8
P132, P164, P232(U) and P332 RDS Encoders / 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!
9
General Discussion about the RDS / Re: Windows 11 Pro Insider Preview + vpn
« Last post by Jan on September 24, 2026, 03:54:31 pm »
I understand your frustration, but I think there are two important points that need to be clarified.

First, the Magic RDS license is a lifetime license. You do NOT need to purchase Magic RDS 4 again when the license becomes invalid due to system change. Your existing User ID remains valid, and if the Installation ID changes, a new license key can be generated for the new Installation ID. I also reset your account in June specifically to allow further key generation.

So please do not purchase another license. If you have any problem generating a replacement key for your existing license, contact me and we will solve it.

Second, we need to find out why the license becomes invalid. When this happens and Magic RDS falls back to Basic, please go to:
Help - License Manager - Diagnose

Please save this diagnostic information each time the problem occurs. By comparing it with the previous one, we can determine whether Windows is changing the system identifiers used by the licensing system.

However, I also have to point out that you are running a Windows 11 Insider Preview / Evaluation build. Preview versions of Windows are development and testing versions and make changes to the operating system that do not occur on regular released versions. We cannot guarantee correct operation or license persistence on such Windows builds, because Microsoft may any time change system components or identifiers on which applications rely.

In previous posts, I explained how and where the problem arises, how to work with the purchased license, and also how to determine in advance that a specific system is unsuitable for installing the application.

If the diagnostic data shows that the Installation ID changes after an Insider Preview update, there is probably nothing that we can do to prevent this. In that case, the appropriate solution would be to use a regular released version of Windows for a system where stable Magic RDS operation is required.
10
General Discussion about the RDS / Re: Windows 11 Pro Insider Preview + vpn
« Last post by delta67 on September 24, 2026, 03:23:03 pm »
I've absolutely had it with this! for 3 time i'll payed for Magic rds! It's that windows 11 Pro Inside preview Evaluatie-exemplaar. Build 29671.1000.rs_prorelease.260911-1426 that changing Magicrds from Standard to Basic ... within a half year several times! Now i'm don with it!!!!

Pages: [1] 2 3 ... 10