Recent Posts

Pages: 1 ... 8 9 [10]
91
P132, P164, P232(U) and P332 RDS Encoders / Can't get RDS RT to display
« Last post by wyosmith on June 29, 2025, 08:06:05 pm »
I have have two 164 setup both were working three days ago, then suddenly one would not display any messages etc.
they are both setup the same way, i have checked and compared settings. i have restarted the computer etc and restarted
the magic rds. it's says its connected and below giving song titles etc but still nothing on the rds radio. the only
thing i have not tried it unplugging the receiving end of the rds from the processor 12 miles away. was hoping to save a trip
if there is something i am missing on this. 
92
Configuration Options and Possibilities / Re: Setting up DJB Zones automation with a Pira P164 and Magic RDS4
« Last post by Jan on June 27, 2025, 12:14:08 pm »
In remote locations where TCP/IP link is not available, the P164 cannot be used directly. There are two options:
1) Use the P232U model instead, which is equipped with RS-232 interface so can be fed directly from a satellite link or another serial data source,
2) or add any commercially available serial to Ethernet adapter between the serial data source and the P164.

In the Magic RDS 4, the serial connection can be created similar way like existing TCP/IP links. Just select 'serial' instead of the 'TCP', then select the COM port and correct communication speed which must be equal on all devices across the serial channel (usually 9600 bps). Refer to the serial channel specification for details.

When you have several connections established in the Magic RDS 4, you may feed them using a single connection from the broadcast automation system (m4vp.pdf section 'Data Splitter for RDS Encoders') or using the External Text tool.
93
Configuration Options and Possibilities / Re: Setting up DJB Zones automation with a Pira P164 and Magic RDS4
« Last post by Tom McGinley on June 27, 2025, 12:05:57 am »
Hello Jan. Thanks for your reply and assistance. We have one Pira P164 connected via IP from our DJB automation Air server on the same protected subnet. The P164 output is connected directly to a Nautel VS1 transmitter SCA/RDS BNC input. We are getting DJB ASCII metadata and default dynamic PS and RT rotating messages programmed into the P164. We have a Nautel V10 transmitter at a remote site that we need to send the DJB metadata to another P164 encoder there. A separate TCP/IP connection is not available so we presume an RS232 serial connection conveyed via a Comrex or Barix link may work. In order to do that, I presume we need to deploy the Magic RDS4 app on a DJB LAN connected machine to receive the DJB metadata and then feed both a TCP/IP connection from there to the VS1 transmitter and a serial connection to the V10 transmitter.  The manual shows a block diagram in section 6.3 of multiple transmitters connected from a PC running Magic RDS4 via TCP ethernet ports. But I do see any descriptions of how remote transmitters with a local P164 can be fed with serial data from Magic RDS4 running on a PC. Can you provide the detail on setting up that connection?
94
PIRA32 RDS Encoder / Re: RDS RT Jazler SOHO
« Last post by Ivan on June 26, 2025, 03:45:18 pm »
Hello, you need to install the Universal Driver UP Universal, it will display the artist and song!
95
P132, P164, P232(U) and P332 RDS Encoders / Re: ' character doesn't appear on RT - P132
« Last post by Lucas G on June 09, 2025, 06:23:21 pm »
Thank you Jan for the reply.
My friend has moved to Magic RDS in order to manage the data, the issue is fixed!

I didn't know that firmware version he used. I will tell him anyway.
96
P132, P164, P232(U) and P332 RDS Encoders / Re: ' character doesn't appear on RT - P132
« Last post by Jan on June 09, 2025, 06:02:38 pm »
This issue did exist in the first firmware versions, but that was about 10 years ago. In current versions, this has long been fixed.
Please update the firmware and the embedded website to current version. The product site can be found in Support section.
97
P132, P164, P232(U) and P332 RDS Encoders / ' character doesn't appear on RT - P132
« Last post by Lucas G on June 09, 2025, 04:27:48 pm »
Hello,

A friend of mine has an issue with a ' character that doesn't appear on the RT of his station. He uses a P132 encoder and manages it directly from the web interface.
The "À" character works very well for example, but ' doesn't appear on the slogan.

The RT contains the slogan (sent "locally" from the encoder configuration) and the current song title (sent remotely).
The ' character seems to be displayed correctly on the current song title.

I've tried to find a solution on the manual and on the forum, without success.

Thanks in advance for your reply,
Lucas G.
98
Configuration Options and Possibilities / Re: Text Campaigns and Expire After
« Last post by radiosavage on June 06, 2025, 07:59:38 pm »
Thank you.  I did have it misconfigured with the text sources.  I made the change, and it is working as expected.  I was under the impression when using the instructions that you only added an internal channel if you did not have one.  This makes a lot more sense.  Thank you.
99
Configuration Options and Possibilities / Re: Text Campaigns and Expire After
« Last post by Jan on June 05, 2025, 08:10:26 am »
Yes, what you're doing now is telling the application "stop sending the song name after 3 minutes".
A second step is missing, telling "what to display instead of that".

Put both Sources to the Output, the song, as well as the text campaign loop.

For the song, set 'Go to next after' to 99999 or something similar
For the TC, set 'Go to next after' to 30.

That's one of the approaches possible.
100
Configuration Options and Possibilities / Text Campaigns and Expire After
« Last post by radiosavage on June 05, 2025, 02:50:21 am »
I just upgraded to the latest version with Text Campaigns, and it works great except for one issue that may be a misconfiguration on my end but not sure how to track it down or what I am doing wrong.

I have one text source at a time.  I enabled a text campaign and set the main text source so that it expires after 180 seconds since they want the text campaign to be the standard message when the "Expires After" times out.  However, I am finding that it will continue to display the text source song well after the 180 seconds.  I know the documentation says that when using a single source that the "Expires After" setting has little effect.  Is this the correct behavior?  Thoughts on how to make this work.  I was thinking the Text Campaign becomes the second source. 

Thank you!



Pages: 1 ... 8 9 [10]