Please enable JavaScript to view this site.

XStudio PostMajik

Navigation: Appendices

Supported RDS Encoders

Scroll Prev Top Next More

XStudio PostMajik supports a number of popular RDS encoders and includes a user-defined encoder. The list of supported encoders may change from time to time as new encoders are added to those currently supported.

Supported RDS Encoders

RDS encoders specifically supported as of 7/12/2024:

Audemat-Aztec Silver

FMB80 Audemat / Burk

FMB80 Audemat (Old Firmware)

Inovonics 711

Inovonics 712

Inovonics 713

Inovonics 720

Inovonics 730

PIRA32

User-Defined

If you have an encoder that emulates one of the supported encoders, use that encoder if yours does not appear on the list.

Notes on the User-Defined Encoder

When using this encoder type, you must place any required identifiers (i.e., "RT=" or other command text) in your RDS post item templates. Consult your encoder documentation for command identifiers and syntax to use for the type of message you wish to send to the encoder.

Note that only one message will be sent to the encoder per RDS post item as there is no provision for a Radio Text or PS designation. The message template itself must contain the identifiers and command text. plus the usual available post variables.

If you require more than one message and the target encoder supports TCP communications, you may be able use two post items (one for Radio Text and one for PS text, for instance). The encoder must support simultaneous TCP connections for this to work.

If the target encoder uses only a serial connection, only one message can be sent as each post item must have exclusive use of its COM port, thus preventing other post items from using that same COM port.

You may be able to use the user-defined encoder for other purposes, possibly an electronic billboard or similar device which can receive specially‑formatted text via TCP or serial connection.