Post reply

Name:
Email:
Subject:
Message icon:
Verification:
Unregistered users must pass a verification:



Please enter the number from the picture above which is showing FM broadcast antenna:

shortcuts: hit alt+s to submit/post or alt+p to preview


Topic Summary

Posted by: Jan
« on: Yesterday at 11:13:27 am »

The settings related to UECP only take effect when UECP is the preferred communication protocol. You have all these settings in one place.
Unlike our hardware products, the READBEST is a UECP-based RDS encoder. Without enabling the UECP ('Encapsulate all Outgoing Data to UECP') some functions may not be available.
Any changes to the text settings will only take effect after sending a new message.

For loading data to external UECP encoder, you should use the Generic UECP model rather than the DEMO Encoder.
Posted by: chbroadcast
« on: Yesterday at 11:05:08 am »

Hello,

I have tried the latest version now. I see the new additional toggles, but they don't seem to do anything in Readbest.
With them enabled, the RT still gets padded up to 64 chars with spaces.
Am I forgetting something?
Posted by: Jan
« on: June 28, 2026, 09:38:01 pm »

I'm aware it's been a long time coming ;D
We've had a lot of requests and a lot of small bugs to fix. It's basically done now. I expect to release at least a beta version in the next few days.
Posted by: andrew01
« on: June 28, 2026, 09:23:58 pm »

Great! When could we see this next version launched?
Posted by: Jan
« on: June 28, 2026, 07:17:42 pm »

Gradually, everything will be unified to line breaks immediately after the last character of the text. In the UECP implementation this will happen in following Magic RDS 4 version.
Posted by: andrew01
« on: June 28, 2026, 06:52:55 pm »

Hi Jan, on the topic of 0x0D, will/can a switch be added between adding the CR character as the first one or last one for all connection modes (uecp, etc.) in the 2A group? Something like this  :)
Posted by: chbroadcast
« on: June 25, 2026, 03:37:02 pm »

Understood. Thank you!
Posted by: Jan
« on: June 25, 2026, 03:32:54 pm »

It does what it says - optionally inserts a CR after the last character of the text, so that the receiver can terminate it there.

A new version will be released soon, so I will add the option to control whether the rest is filled with spaces or sent truncated. Unfortunately, the standards are not specific enough in this regard and the CR termination was not included in first releases, so we preferred to use a safer method.
Posted by: chbroadcast
« on: June 25, 2026, 03:28:40 pm »

Thank you for the quick reply. So this toggle in the Extensions Tab doesn't do anything?
Posted by: Jan
« on: June 25, 2026, 03:02:55 pm »

Yes, that's correct. We use safe implementation and send the full 64 characters over UECP to completely overwrite the previous text. Some UECP-based encoders in past did not do this themselves. This does not affect the ability of the radio receiver to terminate the text after the CR character, nor the ability of the RDS encoder to start a new RT transmission cycle after the CR character is found in current segment.

There are no settings defined in the UECP specification for Radiotext termination. Everything must be encoded by the control software.
Posted by: chbroadcast
« on: June 25, 2026, 02:54:36 pm »

Hello,

I'm using Readbest with my custom UECP solution, and the CR termination does not work. Even though its enabled in the Readbest settings.
0x0D byte is also sent over UECP, but the Readbest encoder keeps sending blanks after the 0x0D char.

Sample RT UECP message for debugging, encoded in base64:
/gAAyyUKAQAhAVRpk3N0bzsgTWFiZWwgLSBHb2QgaXMgYSBkYW5jZXINx3P/