Recent Posts

Pages: [1] 2 3 ... 10
1
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 Logo
« Last post by Jan on Yesterday at 08:51:58 am »
Your questions are relevant and completely correct. Unfortunately, we are unable to give you a complete answer here. These questions need to be directed to car infotainment manufacturers, and also to the "RDS Forum" organization. In this regard, it is necessary to exert pressure so that the implementation of RDS in car radios is in accordance with the currently valid standard and the user is sufficiently informed about all features and standards supported by the equipment. I am not at all satisfied with how the implementation of the RDS2 standard in receivers is going, but we have done a lot of work on this matter and the ball is not in our court now.

To verify that all encoder settings have been made correctly, you don't need any equipment to receive and show the logo. Just click on the RDS Spy button and in the RDS Spy select View - RDS2 RFT File Receiver.

If you are looking for an RDS2 receiver, look for compliance with IEC 62106:2023 or later.
2
P175 FM Analyzer / Re: p175 problem
« Last post by Sandersona on Yesterday at 06:17:46 am »
Oh no, that sounds rough! Dropping sensitive equipment like that is always a gamble. While I'm not a repair expert, it does sound like the fall is the most likely culprit. Before you write it off completely, maybe check the obvious things like connections and power supply. Sometimes a simple reset can do wonders. Thinking outside the box, I wonder if simulating the problem helps identify it... Almost like how Crazy Cattle 3D helps visualize farm management! Hope you get it sorted!

3
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 Logo
« Last post by rogertee1966@gmail.com on Yesterday at 12:00:35 am »
Clearly I am missing something.  I have added a station logo and I thought I had all of the settings correct so that it should display, however, I am not seeing the logo on the radio.  The radio is in a 2025 Chevrolet Silverado.  Lots of conflicting info out there where one source says it will display another implies it might not.
I didn't find any information, again I may have overlooked it, in the manuals about setting up the logo but the error messages are very helpful.  I did have one of the logos that I resized etc. to meet the criteria of a 1:1 aspect ration and a file size of less that 6kB.  I believe I found where to turn on the additional subcarrier (again some conflicting info on the subject, is the additional carrier necessary?) but it would appear the receiver must be capable of receiving the addtional carrier...if it is indeed necessary.
Can you offer some clarity on proper setup and do you know what receivers will actually display the logo?

Thank you.
4
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on November 25, 2025, 10:55:07 pm »
Version 4.2.8

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

  • Added device websites for P232, P232U and PIRA32
  • The website now allows working with Bridges and Virtual ports
  • Scripts now support Virtual port add/edit/delete/enable/disable and partial edit of Connection parameters
  • Improved help: multilingual introduction document and hints in the website
  • Bug fix: application deadlock after closing the Preferences dialogue box if web server was serving a page at the same moment
  • Bug fix: P232 and P232U models were sometimes confused
  • Bug fix: 'insufficient system resources' when reading an application title via the External Text Sources
  • Bug fix: P164 device website: Radiotext manual update fix and some more
  • Bug fix: UDP connect/disconnect when editing the connection from the web
5
Free Topic / Personal Routes: Experiencing dreadhead parkour with Patience
« Last post by Billyhan on November 25, 2025, 08:19:24 am »
Diving into a game experience that feels both fresh and unpretentious can be a rare treat. If you’re craving something that blends velocity, creativity, and a touch of mystery, dreadhead parkour offers a compelling invitation into its world. While it isn’t about flashy marketing or grandiose promises, it provides a straightforward promise: a meaningful moment of movement and exploration. Here’s a friendly, down-to-earth guide to how to play and what to expect when you immerse yourself in this intriguing title.
Introduction
What makes dreadhead parkour stand out is its focus on motion as a core language. The game isn’t chasing hyper-realistic visuals or relentless competition; instead, it leans into the simple, satisfying ritual of moving through space with intention. Think of it as a playground where your choices—how you sprint, jump, and weave around obstacles—shape the pace and vibe of your session. You’ll encounter tight corridors, sweeping platforms, and occasional sections that nudge you toward experimentation rather than perfection. The experience invites patience, curiosity, and a willingness to map out your own rhythm.
Gameplay
At its heart, dreadhead parkour emphasizes momentum and control. You’ll typically navigate a sequence of rooms or outdoor sections filled with ramps, ledges, and gaps that demand precise timing. The controls are designed to feel responsive without being punishing, so you can explore different routes without constantly reloading or restarting. The game rewards players who take a moment to read the space: where a platform angles upward, where a wall offers a chance for a wall-run, or where a jump’s arc hides a smoother landing.
One of the appealing aspects is the game’s emphasis on flow. When you find a line—an uninterrupted path that carries you from start to finish with minimal stumbles—you get a small rush that’s hard to describe: a sense of carving through air and space with intention. The levels often present multiple ways to progress, so you’re encouraged to test paths, switch approaches, and learn from missteps. If you enjoy a “design your own route” mindset, you’ll likely spend time tracing alternative lines, noting which moves yield cleaner landings or cooler transitions.
From a player’s perspective, expect moments that lean into puzzle-like thinking. Some sections require you to time a jump to coincide with a gust of wind, to bounce between narrow ledges, or to stack a sequence of moves (a sprint, a precise jump, then a quick wall-run) to reach a higher platform. These moments aren’t about sheer speed alone; they’re about controlling your momentum and choosing the safest, most graceful path through a space.
6
General Discussion about the RDS / Re: Brand new to all this
« Last post by DaveS on November 19, 2025, 12:42:45 pm »
I am not too clear what you are asking for.  If you want to convert your call of KFII to a PI code, that would be 1E0C.
7
RDS Spy / Re: Request for lager font of PI code in RDSSpy
« Last post by Andreas Mikula on November 17, 2025, 06:22:29 pm »
Additional comment: when I use 125 or even 150% zoom, the font is not sharp.
8
General Discussion about the RDS / Brand new to all this
« Last post by 92.3 KFII on November 15, 2025, 04:11:44 am »
So here I am. Starting a new rural FM station. While my life has been surrounded by music and sitting in a station as my father DJ'd in the 70's-80's, this piece is completely new to me. I am not technologically incompetent, I have learned over the years every new piece is a new experience. We just changed from a tube setup to a fancy new, less than 260 pound, Bext XL 3000. I joined here to read and learn from your knowledge, and, occasionally pester with stupid questions. At this point, We just want the script to Read our call letters. I have no doubt I'll get some guidance here. Thanks in advance for your patience.
9
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 - EAS/EASTIME Protocol
« Last post by Jan on November 14, 2025, 08:18:29 pm »
Yes, I think it is working now. You can see in the video that the Virtual port receives the EAS commands. At the same time, these commands should appear in the Communication Monitor in Overview, which is a monitor of the data going to the encoder.
10
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 - EAS/EASTIME Protocol
« Last post by mendotatech on November 14, 2025, 07:48:54 pm »
It looks like I misunderstood the error. Still, I think being that I'm sending a Weekly Test, that's less than 10 seconds total (yes, I see the data has it pegged at 30 seconds). I may stand a better chance waiting for the Monthly Test or an actual alert since those messages are usually 90 seconds in length.

That all said, I think we may have found a way to get this working. Thanks!
Pages: [1] 2 3 ... 10