Recent Posts

Pages: [1] 2 3 ... 10
1
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.
2
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.
3
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.
4
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.
5
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!
6
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 - EAS/EASTIME Protocol
« Last post by mendotatech on November 14, 2025, 07:29:27 pm »
Here's what I have logged...
ASCII: EAS=Required Weekly Test
ASCII: EASTIME=30

I did perform a screen capture and here's that link - https://drive.google.com/file/d/1k_pSDOilZSn1CtSSz-l-bPmm8PpTdiDw/view?usp=sharing
7
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 - EAS/EASTIME Protocol
« Last post by Jan on November 14, 2025, 07:19:14 pm »
At the end of your efforts you should see the EAS= and EASTIME= commands in the Communication Monitor of each Connection feeding the P164. The commands are not sent to the encoders until they appear there.
8
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 - EAS/EASTIME Protocol
« Last post by mendotatech on November 14, 2025, 06:41:51 pm »
I'll have to pull from that log later...

But I did receive ASCII data from the EAS Encoder on the program.

And yes, we are using a P164 as the encoder.
9
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 - EAS/EASTIME Protocol
« Last post by Jan on November 14, 2025, 06:22:13 pm »
It doesn't look like there is any data sent from the SAGE ENDEC.
The XCMD and DPS1ENQ commands are generated by the Magic RDS 4 External Text Sources, the KMBY-FM connection is configured for some PIRA encoder but another device is connected. Inovonics and others do not support X-Command or Dynamic PS queue. For such encoders use the Lite ASCII model.

Anyway, there's no need to guess and hope, because the Magic RDS 4 allows you to track the data at any point, using the RX Monitor in the Virtual Port and Communication Monitor at each Connection output.

The SAGE ENDEC must be a Virtual port, as proposed before. It cannot be a Connection. In simple terms: Connection = DATA OUTPUT, Virtual port = DATA INPUT.
10
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 - EAS/EASTIME Protocol
« Last post by mendotatech on November 14, 2025, 06:11:54 pm »
So I did try that out using the competitor product standard on the SAGE EAS ENDEC connecting via TCP to Magic RDS 4 and this is what I was able to capture in the recent events.

25-11-14 09:04:33; SAGE ENDEC: Client 10.5.10.147 connected
25-11-14 09:04:35; Radiotext and Dynamic PS text:  MONTEREY BAY MORNING SHOW -  DON BROOKLYN
25-11-14 09:04:35; Radiotext and Dynamic PS Dynamic PS text:  MONTEREY BAY MORNING SHOW -  DON BROOKLYN
25-11-14 09:04:36; KMBY-FM: Command not accepted: XCMD=<rds><item><text> MONTEREY BAY MORNING SHOW -  DON BROOKLYN</text></item></rds>
25-11-14 09:04:36; KMBY-FM: Command not accepted: DPS1ENQ=
25-11-14 09:04:36; SAGE ENDEC: Client disconnected, 0 clients remaining

So far, I'm able to get TCP data through, but it looks like none of it is what the P164 is expecting for EAS. I'll reach out to them.
Pages: [1] 2 3 ... 10