Recent Posts

Pages: 1 ... 6 7 [8] 9 10
71
P132, P164, P232(U) and P332 RDS Encoders / Re: NexGen Export to P132 via IP
« Last post by Jan 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.
72
P132, P164, P232(U) and P332 RDS Encoders / NexGen export to P164 via TCP direct (no magic4 software)
« Last post by mikehagans 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 
73
Bug Reports / Re: XCMD over UDP with PIRA332
« Last post by metro187 on April 28, 2025, 08:42:59 pm »
Hi Jan,
Thanks for the quick clarification!
74
Bug Reports / Re: XCMD over UDP with PIRA332
« Last post by Jan on April 28, 2025, 08:05:14 pm »
Following bugs exist in the P132/P332 (other models are ok):
  • All firmware versions: UDP communication mode supports 90 bytes of data at maximum per packet
  • Firmware version 2.2i and 2.2j: Ethernet setup does not work using the embedded website
Before we release a fix, I would recommend to use TCP mode which is safe.
75
Bug Reports / Re: MagicRDS4, wrongly set TATMOUT parameter
« Last post by metro187 on April 28, 2025, 07:13:59 pm »
Got it, thanks for the correction.
76
Bug Reports / XCMD over UDP with PIRA332
« Last post by metro187 on April 28, 2025, 07:03:43 pm »
Hi,

I'm facing the following issue with a PIRA332 running firmware version 2.1g

I'm trying to control the RT1/RT+ messages using the X-Command interface.
As a test, I set up Port3 for TCP and Port4 for UDP.
To test, I set up two connections in MagicRDS4 and using the terminal to send the commands.

When using the UDP connection, the messages have severe limitations:
Code: [Select]
XCMD=<rds><item><dest>3</dest><text><title>1234567890123456</title></text></item></rds>
+

XCMD=<rds><item><dest>3</dest><text><title>12345678901234567</title></text></item></rds>
Operation timed out

XCMD=<rds><item><dest>3</dest><text>123456789_123456789_123456789_1</text></item></rds>
+

XCMD=<rds><item><dest>3</dest><text>123456789_123456789_123456789_12</text></item></rds>
Operation timed out

XCMD=<rds><item><dest>3</dest><text><title>1</title><artist>2</artist></text></item></rds>
Operation timed out

XCMD=<rds><item><dest>3</dest><text><artist>12345678901234</artist></text></item></rds>
+

XCMD=<rds><item><dest>3</dest><text><artist>123456789012345</artist></text></item></rds>
Operation timed out

So, title is supported up to 16 chars, artist is supported up to 14 chars, text without tags is supported up to 31 chars and title+artist is not supported.

If I send the "same" (even longer) updates through the TCP connection, all of them are successful, no length limitations:
Code: [Select]
XCMD=<rds><item><dest>3</dest><text><title>1234567890123456</title></text></item></rds>
+

XCMD=<rds><item><dest>3</dest><text><title>123456789_123456789_123456789_123456789_123456789_123456789_1234</title></text></item></rds>
+

XCMD=<rds><item><dest>3</dest><text><artist>123456789_123456789_123456789_123456789_123456789_123456789_1234</artist></text></item></rds>
+

XCMD=<rds><item><dest>3</dest><text><title>123456789_123456789_123456789_12</title><artist>123456789_123456789_123456789_1</artist></text></item></rds>
+

XCMD=<rds><item><dest>3</dest><text><title>123456789_123456789_123456789_12</title><artist>123456789_123456789_123456789_1</artist></text></item></rds>
+


Is this a known issue? Am I doing something wrong?
77
Bug Reports / Re: MagicRDS4, wrongly set TATMOUT parameter
« Last post by Jan on April 28, 2025, 07:02:51 pm »
TATMOUT=131
*TATMOUT
78
Bug Reports / Re: MagicRDS4, wrongly set TATMOUT parameter
« Last post by metro187 on April 28, 2025, 06:27:36 pm »
Thanks, Jan!

For now, we saved the config in the terminal, using:
*TATMOUT=131
79
Bug Reports / Re: MagicRDS4, wrongly set TATMOUT parameter
« Last post by Jan on April 25, 2025, 08:55:05 pm »
Yes, when sending 'level controlled' using the Magic RDS 4 form, it adds 1 instead of 128. It will be fixed in upcoming version.

Thx.
80
P132, P164, P232(U) and P332 RDS Encoders / Re: LIC code to P164
« Last post by Jan on April 25, 2025, 06:37:17 pm »
According to latest RDS standard release, the LIC service becomes deprecated. Regardless of that fact, we will keep it in the P164 also in future firmware versions.
If the LIC feature is not applicable or not required, set the value to 00.
Pages: 1 ... 6 7 [8] 9 10