Posted by: metro187
« on: April 28, 2025, 08:42:59 pm »Hi Jan,
Thanks for the quick clarification!
Thanks for the quick clarification!
News:
Thank you for using this forum as the technical support base for your device.
● You can format the text and attach screenshots, photos and RDS Spy records
● Faster reply: 50 % of questions are answered within 30 minutes
● You don't need to register (but registration is possible)
● The members represent a wide range of experts
● The resolution will be helpful to other users
● You'll be notified by email about new post
Posted 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
Posted 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:
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:
Is this a known issue? Am I doing something wrong?
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?