Recent Posts

Pages: 1 ... 4 5 [6] 7 8 ... 10
51
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.
52
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.
53
P132, P164, P232(U) and P332 RDS Encoders / Re: P164 - EAS/EASTIME Protocol
« Last post by Jan on November 14, 2025, 09:35:41 am »
The Magic RDS 4 can provide an entry point to the RDS network for another device or application, to expand the range of other services broadcast.

If the device provides a data output which is compatible with the RDS encoder command set, use the setup as showed in Help - m4vp.pdf, section 'Data Splitter for RDS Encoders'.

If the device output uses incompatible data format, you still have the option to at least partially control the RDS encoder with it. Appropriate setup is showed in m4vp.pdf, section 'Redirecting to External Text Sources'. Then use the External Text Sources function called 'Text conditions' to send RDS commands, based on the occurrence of keywords or sequences in the text received from the device.

You should consult with the manufacturer of the SAGE Endec device to determine which method is suitable for your case.

The Magic RDS currently accepts input data via following interfaces: serial RS-232, TCP server, TCP client, UDP, HTTP server (GET method), HTTP client, FTP client, Windows file system.
54
P132, P164, P232(U) and P332 RDS Encoders / P164 - EAS/EASTIME Protocol
« Last post by mendotatech on November 14, 2025, 09:01:18 am »
Hi All,
So far, been having good results with the P164 with MagicRDS 4 as I'm tying Song Titles with Hourly Station Announcements and a Program Guide (Long Story, Neither here nor there.) . I have a SAGE EAS ENDEC 3644 and it appears to have a "Peripherals" section where I can select between a few devices. One of them happens to be a competing RDS encoder and only seems to ask for a URL to send data to.

In comparing what the P164 (Page 49, Manual) and the competitor protocol standard is, it appears similar. EAS/EASTIME.

Since I'm using MagicRDS 4, do I need to set it up to receive the commands from the SAGE Endec? If so, how would I go about doing that? I don't seem to find anything in the documentation except for possibly directly connecting with the P164. Again, I haven't the slightest clue.

Thanks in Advance.
55
Silence Detector / Re: %time value is wrong
« Last post by sphinx on November 08, 2025, 08:08:55 pm »
It was a faulty sound card, even if everything appeared to be functional.
Card replaced, problem solved.
56
Release News and Tutorials / Re: Release News and Change Log
« Last post by Jan on October 26, 2025, 12:27:32 am »
Version 4.2.7

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

  • Time sync: auto UTC offset option added
  • Captions and hints: Czech and Spanish language added
  • RTPRUN= command removed
  • If RTP= command is being used for the RT+, the RT+ is now correctly cleared if necessary
  • Bug fix: Previously, the text was sometimes sent again and again if the RT+ Running Bit control was enabled for the text source

Known issues: Handle leak - when using External Text Sources for Window Title reading, the application reports getting out of available resources and no I/O operation is possible until application restart. A solution is on the way.
57
Configuration Options and Possibilities / Re: Can’t get RT+ working with Deva DB6400 (via TCP User Defined 1)
« Last post by Marc1963 on October 21, 2025, 04:13:49 pm »
Thanks for the information. I sent an email to Deva support, and their response was: "The DB6400 does not support UECP and RT+."
58
Configuration Options and Possibilities / Re: Can’t get RT+ working with Deva DB6400 (via TCP User Defined 1)
« Last post by Jan on October 21, 2025, 03:33:10 pm »
There is no problem with the license. Some equipment does not support RT+ in any way. You need a full-featured RDS encoder.

The RT+ is a standard RDS service like PS or RT. The RT+ is practically essential for taking full advantage of the display capabilities of today's receivers. A component without RT+ support should not be referred to as an RDS encoder, but rather as an RDS generator.
59
Configuration Options and Possibilities / Re: Can’t get RT+ working with Deva DB6400 (via TCP User Defined 1)
« Last post by Marc1963 on October 21, 2025, 03:13:18 pm »
We currently have a standard key. Do we need a full license to use this, and can we upgrade?
60
Configuration Options and Possibilities / Re: Can’t get RT+ working with Deva DB6400 (via TCP User Defined 1)
« Last post by Jan on October 21, 2025, 02:41:23 pm »
I don't see the RT+ in the DB6400's list of available functions.

Please visit our website https://pira.cz/rds/ for current offer of full-featured RDS encoders. They can be attached to the DB6400 as well.
Pages: 1 ... 4 5 [6] 7 8 ... 10