CR / 0x0D termination in Readbest

[chbroadcast]

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/

[Jan]

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.

[chbroadcast]

Thank you for the quick reply. So this toggle in the Extensions Tab doesn't do anything?

[Jan]

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.

[chbroadcast]

Understood. Thank you!