Recent Posts

Pages: 1 2 [3] 4 5 ... 10
21
I am asking a very basic setup question here. I have a brand new PIRA P164 encoder that can receive RDS data via serial or TCP/IP. I have it connected to receive RDS data from our DJB Air server via an ethernet switch that handles our DJB subnet. The Magic RDS4 app is loaded for now on a separate DJB file server. The P164 pulled a DHCP IP on the DJB subnet at 192.168.91.211.  I've tried to get it configured to receive the RDS text data being generated from the DJB Air server which we see scrolling on the Hercules data capture app on a connected DJB production machine. I added the PIRA P164 IP as the target device in the DJB Air server Metadata setup screen: 192.64.91.211:10001. The Magic RDS4 tool allows setting up the P164 encoder as either a TCP client or TCP server. I have it set as a TCP server.  I presume other DJB machines with the Magic RDS4 app loaded and running will be TCP clients and can show the RDS scrolling data as air events change. The P164 shows as connected to the Magic RDS4 Tool but I am not seeing any text data coming into that app's Viewer from DJB. Perhaps I don't have the TCP setup or ports assigned correctly.

I am quite familiar with the older PIRA RDS ethernet connected encoders without any middleware with good success. Those models had a much easier web UI to do the IP setup plus static PS and RT messages with windows that scrolled the RDS PS and RT data as it updated from the automation. It didn't need the Magic RDS4 tool. The P164 web UI (port 80) does not offer that and only shows the static ethernet setup parameters.   What am I missing to get this configuration corrected before I try connecting the P164 to my transmitters SCA input to see RDS texting on car radios?
22
Release News and Tutorials / Automatically save playlist to different file each day
« Last post by Jan on May 29, 2025, 08:08:25 pm »
Once you successfuly configured the artist and title publishing for currently playing song, you may follow these simple steps to save daily playlists.

  • Add a new Connection of kind 'Bridge', named 'Save Playlist'.
    Select Connection Type: Internal Channel.
    Fill the Data Distribution box as follows:
    saveto prefix:"%DATETIME:hh:nn:ss%; " file:"C:\yourfolder\Playlist %DATETIME:yyyy-mm-dd%.txt" mode:"append"
       
  • In the External Text Sources, add a new Output.
    Move existing source to the Output.
    As the Destination, fill sendto "Save Playlist"
23
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on May 29, 2025, 07:34:27 pm »
Version 4.2.5

http://pira.cz/rds/magicrds/MagicRDS_Setup.exe

  • External Text Sources: New text processing preset added: ARTIST (in uppercase) - Title (in titlecase)
  • External Text Sources: The Window Title source now allows filtering based on the process exe file name
  • saveto command now accepts dynamic elements in the file name parameter, for example %DATETIME:dd-mm-yy%.txt
  • sendhttp command now supports %1% to %4% dynamic elements for use with XML/JSON source
  • sendhttp command now fully supports Unicode
  • Configuration: Auto Save options added to Preferences
  • Bug fix: TA timeout setting
  • Bug fix: UDP communication with P132/P332
  • Bug fix: The titlecase text processing preset has unexpectedly applied to %GOTONEXT% and other commands
24
PIRA32 RDS Encoder / Re: Firmware update fail. Help
« Last post by Jan on May 28, 2025, 03:33:03 pm »
Please download again: https://pira.cz/rds/rdsup.zip

If the update fails, save the log and post it to me.
25
PIRA32 RDS Encoder / Re: Firmware update fail. Help
« Last post by Jan on May 28, 2025, 08:12:52 am »
This is not a firmware issue. Old Chinese USB to RS232 adapters, like Prolific, may fail on new PC because they do not flush the buffer correctly. Today I'll recompile the update utility exe file. I'll be back soon.
26
PIRA32 RDS Encoder / Re: Firmware update fail. Help
« Last post by smattingly on May 28, 2025, 04:38:56 am »
Hi,

I am having the same issue.  I'm attempting to upgrade firmware on 2 units today.

My serial cable will control the unit via Magic RDS3 no problem.  But if I try and run the firmware update, I see this...
"Update failed at 300 bytes - connection lost. Try again."

I have tried the suggestion of powering it up at different times during the update process, no luck.

See my attached screenshot.

Is there a prior firmware I can try?  Such as a version 1.5?
27
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  :)
28
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.
29
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%
30
my apologies.. never been a big fan of reading a manual...
Pages: 1 2 [3] 4 5 ... 10