1
Configuration Options and Possibilities / Re: MagicRDS 4 to send text file HTTP POST request?
« Last post by lorde on May 08, 2025, 03:20:45 am »Thank you
News:
Thank you for using this forum as the technical support base for your device.
● You can format the text and attach screenshots, photos and RDS Spy records
● Faster reply: 50 % of questions are answered within 30 minutes
● You don't need to register (but registration is possible)
● The members represent a wide range of experts
● The resolution will be helpful to other users
● You'll be notified by email about new post
Recent Posts
2
P275 FM Analyzer / Cable & antenna.
« Last post by AUROVAL on May 05, 2025, 04:41:51 pm »Hello, If I'm using an outdoor antenna at a distance of 15 or 18 meters, which cable do you suggest I use?
And what type of antenna or features should it have?
Thank you.
Auroval
And what type of antenna or features should it have?
Thank you.
Auroval
3
PIRA75 FM Analyzer / Re: Firmware upgrade error
« Last post by Jan on May 02, 2025, 09:50:56 pm »The problem is not caused by the device itself. Maybe ten years ago we had similar issue with some low cost Chinese USB to serial adapter.
4
PIRA75 FM Analyzer / Firmware upgrade error
« Last post by niwreg on May 02, 2025, 08:38:34 am »Hi,
I tried to upgrade an i think p75 (comport version) to the latest version, however i get an error: update failed at 9800 bytes - CRC error try again, tried it again and then it goes in 13400 bytes
i tried a few times with switching the unit off, start the upgrade application and let it run etc. but it seems not to work, it also doesnt seem to boot, display stays blank.
Any help? Maybe some older firmware versions i can try?
edit: tried a few more times, display is now displaying a bit of garabe but readable string here and there. and update failed at 38000 bytes
Fixed it by running the updater a lot of times and eventually it came through 100%
I tried to upgrade an i think p75 (comport version) to the latest version, however i get an error: update failed at 9800 bytes - CRC error try again, tried it again and then it goes in 13400 bytes
i tried a few times with switching the unit off, start the upgrade application and let it run etc. but it seems not to work, it also doesnt seem to boot, display stays blank.
Any help? Maybe some older firmware versions i can try?
edit: tried a few more times, display is now displaying a bit of garabe but readable string here and there. and update failed at 38000 bytes
Fixed it by running the updater a lot of times and eventually it came through 100%
5
P132, P164, P232(U) and P332 RDS Encoders / Re: Enabling RDS+ and station logo p232u
« Last post by drivenmedia on April 30, 2025, 01:49:00 am »my apologies.. never been a big fan of reading a manual...
6
P132, P164, P232(U) and P332 RDS Encoders / Re: NexGen Export to P132 via IP
« Last post by mikehagans on April 29, 2025, 04:30:00 pm »Thank you for the links and information Jan. I will try these shortly.
7
P132, P164, P232(U) and P332 RDS Encoders / Re: NexGen Export to P132 via IP
« Last post by Jan on April 29, 2025, 08:37:07 am »You can send the song artist and title directly. I think you're almost done. On the other hand it is important to note that there are some given formats for sending data. If the broadcast automation software lacks quick presets for the most common RDS encoders, you can find correct format in the P164 manual or in this forum or at this link: https://pira.cz/rds/show.asp?art=linking_with_broadcast_automation_system
In short, the RT= prefix is incorrect. Use RT1= or TEXT= (they are equivalent). The software must provide single line of text, followed by CR:
TEXT=Artist - Title<CR>
As a next step, contact the RCS for correct setup for the X-Command, so you can send the RT+ as well.
In short, the RT= prefix is incorrect. Use RT1= or TEXT= (they are equivalent). The software must provide single line of text, followed by CR:
TEXT=Artist - Title<CR>
As a next step, contact the RCS for correct setup for the X-Command, so you can send the RT+ as well.
8
P132, P164, P232(U) and P332 RDS Encoders / NexGen export to P164 via TCP direct (no magic4 software)
« Last post by mikehagans on April 29, 2025, 06:59:13 am »I saw several posts implying that the P164 can work with NexGen for title and artist export, but no details. I have a nexgen aserv on the same network as my P164. Nexgen is set to export standard format to TCP, pointed at the IP address and port that the P164 is set up on as a TCP server. In NexGen, my lead text on line1 is RT= with output field of Artist. line 2's lead text is a dash and a single space, with output filed of Title. The Field separator is set to other and I entered a space in the little box for the separator. And record separator is CR/LF. The bright white TCP light is lit up on my P164, but no joy as far as getting title and artist... So far I haven't found how to monitor what the P164 is receiving via TCP, and I've found no other forum posts (searching 'nexgen') that indicate a working export setup. I could sure use any pointers or troubleshooting ideas. I'll only be here for a couple of days and need to make this work... I do not want to add a PC to the mix for middleware. Mike
9
Bug Reports / Re: XCMD over UDP with PIRA332
« Last post by metro187 on April 28, 2025, 08:42:59 pm »Hi Jan,
Thanks for the quick clarification!
Thanks for the quick clarification!
10
Bug Reports / Re: XCMD over UDP with PIRA332
« Last post by Jan on April 28, 2025, 08:05:14 pm »Following bugs exist in the P132/P332 (other models are ok):
- All firmware versions: UDP communication mode supports 90 bytes of data at maximum per packet
- Firmware version 2.2i and 2.2j: Ethernet setup does not work using the embedded website