Author Topic: NexGen Export to P132 via IP  (Read 14911 times)

gully52

  • Newbie
  • *
  • Posts: 1
NexGen Export to P132 via IP
« on: April 16, 2015, 05:02:46 pm »
Searched the forums for NexGen, but only found instructions for the older Pira32 via remote COM port application.

How do I configure NexGen to output program titles to the P132 Encoder?

Also, what ports need to be forwarded through the transmitter site firewall in order for the P132 to successfully receive the exported data from NexGen at the studio?

Thanks!
Brian

Jan

  • Hero Member
  • *****
  • Posts: 1202
Re: NexGen Export to P132 via IP
« Reply #1 on: April 16, 2015, 05:45:27 pm »
The NexGen configuration for the P132 is exactly the same, these encoders are compatible.

On the P132 configure port 3 or port 4 as a server, select such TCP port number which is not blocked by firewall and equal to the TCP port number set in the NexGen.

k955backup

  • Newbie
  • *
  • Posts: 1
Re: NexGen Export to P164
« Reply #2 on: June 27, 2023, 10:39:00 pm »
1st time Pira user here and I Magic RDS 4 connected to the Pira 164, in Nexgen I have the RDS Export pointed at the Pira ip address and port that is open. Anyone be willing to share screen shots on how they were able to get Nexgen to send data to Pira 164?

Jan

  • Hero Member
  • *****
  • Posts: 1202
Re: NexGen Export to P132 via IP
« Reply #3 on: September 29, 2023, 08:59:31 pm »
If the P164 is connected to the Magic RDS 4, just create a new Virtual port in the Magic RDS 4 and setup the Nexgen to connect to this virtual port.
There are many other options available but this one is probably the simplest.

mikehagans

  • Newbie
  • *
  • Posts: 3
NexGen export to P164 via TCP direct (no magic4 software)
« Reply #4 on: April 29, 2025, 06:59:13 am »
I saw several posts implying that the P164 can work with NexGen for title and artist export, but no details.  I have a nexgen aserv on the same network as my P164.  Nexgen is set to export standard format to TCP, pointed at the IP address and port that the P164 is set up on as a TCP server.  In NexGen, my lead text on line1 is RT= with output field of Artist.  line 2's lead text is a dash and a single space, with output filed of Title.  The Field separator is set to other and I entered a space in the little box for the separator.  And record separator is CR/LF.  The bright white TCP light is lit up on my P164, but no joy as far as getting title and artist... So far I haven't found how to monitor what the P164 is receiving via TCP, and I've found no other forum posts (searching 'nexgen') that indicate a working export setup.  I could sure use any pointers or troubleshooting ideas.  I'll only be here for a couple of days and need to make this work... I do not want to add a PC to the mix for middleware.   Mike 

Jan

  • Hero Member
  • *****
  • Posts: 1202
Re: NexGen Export to P132 via IP
« Reply #5 on: April 29, 2025, 08:37:07 am »
You can send the song artist and title directly. I think you're almost done. On the other hand it is important to note that there are some given formats for sending data. If the broadcast automation software lacks quick presets for the most common RDS encoders, you can find correct format in the P164 manual or in this forum or at this link: https://pira.cz/rds/show.asp?art=linking_with_broadcast_automation_system

In short, the RT= prefix is incorrect. Use RT1= or TEXT= (they are equivalent). The software must provide single line of text, followed by CR:

TEXT=Artist - Title<CR>

As a next step, contact the RCS for correct setup for the X-Command, so you can send the RT+ as well.

mikehagans

  • Newbie
  • *
  • Posts: 3
Re: NexGen Export to P132 via IP
« Reply #6 on: April 29, 2025, 04:30:00 pm »
Thank you for the links and information Jan.  I will try these shortly.