Recent Posts

Pages: [1] 2 3 ... 10
1
Configuration Options and Possibilities / Re: Version 4 help (reading XML file)
« Last post by Jan on October 08, 2026, 03:36:08 am »
I don't quite understand how the unit can be sending nothing to the transmitter while you simultaneously report seeing static radiotext. In any case, I do spot a problem with your setup: RDS Spy could never have worked at a speed of 2400 baud, as it is impossible to provide decoded data at such a low rate — a fact actually noted in the manual. When using an external Ethernet-to-RS-232 converter, the software cannot technically detect or adjust the communication speed; you must configure this via the converter's control interface. You also need to ensure that the speed set on the converter matches the speed pre-configured on the encoder.
2
Configuration Options and Possibilities / Re: Version 4 help (reading XML file)
« Last post by dennism on October 08, 2026, 03:03:07 am »
I have another problem with Version 4 and my P232U. Yesterday evening it suddenly stopped sending data to the transmitter. I can read the settings from the unit but nothing shows on air or in RDS Spy. It worked fine until yesterday.

It's a remote setup, connected by vpn through a Lantronix UDS1100. Baud rate 2400, port 3001. It's difficult to get to the site so I did a reset and also initialize command. Nothing helped. I uninstalled Magic RDS 4 and reinstalled. Right now I do not have any dynamic data feeding it, only a static message in RadioText.

It's acting like the encoder is disabled. It's set to enable.

Any ideas on where to look would be appreciated. Thanks.
3
P132, P164, P232(U) and P332 RDS Encoders / Re: P132/P332 - FCC Cybersecurity Rules
« Last post by Jan on October 05, 2026, 03:06:32 am »
No, that's not how it works; this isn't an Android phone  :)
If the webpage did not upload correctly, simply upload it again. This process takes place solely between your browser and the ConnectOne network module, and this is one of its characteristics that we cannot influence.
4
P132, P164, P232(U) and P332 RDS Encoders / Re: P132/P332 - FCC Cybersecurity Rules
« Last post by kdincville on October 04, 2026, 10:15:43 pm »
Jan- Thanks for all the information and the super quick response.
I was able to unlock two of the three units, get their address changed, and get them back in service. Unfortunately, the third one isn't cooperating. After entering the password, it looks like it's unlocked, but after a second or two it reverts to the login screen. It does this using all three iterations of the logon addresses I have: the plain, bare, IP address; the http://<device IP address>/?RESP=secure logon; and http://<encoder’s IP address>/ichip login from the new software package instructions.
At this point I'm thinking that the path of least resistance is to just reset it back to the factory settings and start over. Can you tell me how to do that? Thanks in advance... k
5
P132, P164, P232(U) and P332 RDS Encoders / Re: P132/P332 - FCC Cybersecurity Rules
« Last post by Jan on October 03, 2026, 12:08:19 pm »
Version 2.2a of the embedded website:

https://pira.cz/rds/p132webu.zip
https://pira.cz/rds/p332webu.zip

Instructions included.

Release notes for the version 2.2a:
  • The password length restriction when setting it up via the website has been removed. It is now possible to enter a password of up to 15 characters.
  • Bug fix: If a password had been set, logging in via the standard URL sometimes failed on certain modern browsers.

If you are going to update the website, I also recommend updating the RDS firmware to prevent any potential incompatibility:
https://pira.cz/rds/p132fwup.zip (valid for entire RDS encoder's family)
6
P132, P164, P232(U) and P332 RDS Encoders / Re: FCC Cybersecurity Rules
« Last post by Jan on October 03, 2026, 12:05:19 am »
Yes, you are right. We discovered today that, due to timing issues, logging into the web interface of this old device from modern computers can indeed be hit-or-miss. It is possible to log in, but not always on the first attempt (you must press Reload before attempting to submit again). We have identified the cause in the internal website and are working on a solution. We will keep you updated over the coming days. In any case, by following the procedure described above, you have formally satisfied the FCC requirement.
As a temporary solution, use this URL to access password-protected internal website on modern browsers:
http://<device IP address>/?RESP=secure
7
P132, P164, P232(U) and P332 RDS Encoders / Re: FCC Cybersecurity Rules
« Last post by kdincville on October 02, 2026, 10:25:08 pm »
I am attempting to log in to my 3) P332 encoders after installing 15 character passwords as previously demonstrated. So far, I appear to be locked out. I am wondering if the message in front of the password box is telling me to add characters in front of the password, or what its purpose is. I'd also like to know how to reset to a zero password condition.
 
WEB password (AT+iWpwd):

Thanks.
kd
8
PIRA32 RDS Encoder / Re: Firmware update fail 1.6a PIRA 32 anno 2006
« Last post by Jan on September 29, 2026, 09:32:23 pm »
Great job ;D
9
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
10
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.
Pages: [1] 2 3 ... 10