P164 RDS Encoder User Manual: Firmware Version 2.2
P164 RDS Encoder User Manual: Firmware Version 2.2
P164 RDS Encoder User Manual: Firmware Version 2.2
User Manual
Firmware version 2.2
https://www.pira.cz/rds/
2
Table of Contents
1 Introduction ...............................................................................................................................................................................3
1.1 Main Highlights ....................................................................................................................................................................3
1.2 Other Features .......................................................................................................................................................................3
2 Technical Specifications ..........................................................................................................................................................4
2.1 Block Diagram .......................................................................................................................................................................5
3 Physical Description .................................................................................................................................................................6
3.1 Front Panel .............................................................................................................................................................................6
3.2 Rear Panel ..............................................................................................................................................................................6
3.3 Board Layout .........................................................................................................................................................................7
4 Installation and Setting-up .....................................................................................................................................................8
4.1 Connection .............................................................................................................................................................................8
4.2 On-board Controls ................................................................................................................................................................9
4.3 Power Supply ........................................................................................................................................................................9
4.4 Windows Control Software - First Steps ..........................................................................................................................10
4.5 Level and Phase Adjustment .............................................................................................................................................11
4.6 Setting Basic RDS Data .......................................................................................................................................................13
5 RDS Services and Features ....................................................................................................................................................15
5.1 Broadcast Automation System Link-up ...........................................................................................................................15
5.2 Dynamic PS ..........................................................................................................................................................................17
5.3 Alternative Frequencies .....................................................................................................................................................18
5.4 Enhanced Other Networks Information (EON) Setup ...................................................................................................20
5.5 Weekly Scheduling .............................................................................................................................................................21
5.6 RDS2 Subcarrier Configuration .........................................................................................................................................22
6 Communication Ports .............................................................................................................................................................23
6.1 Overview ..............................................................................................................................................................................23
6.2 USB Connection...................................................................................................................................................................23
6.3 Ethernet Connection ...........................................................................................................................................................24
6.4 Port Access Control.............................................................................................................................................................28
6.5 Working with a Terminal Application .............................................................................................................................29
6.6 Command Interpreter.........................................................................................................................................................30
6.7 Additional Information ......................................................................................................................................................31
7 List of Commands ...................................................................................................................................................................33
7.1 Command Summary ..........................................................................................................................................................33
7.2 Basic Commands .................................................................................................................................................................36
7.3 EON Commands .................................................................................................................................................................42
7.4 Messages Commands .........................................................................................................................................................43
7.5 Scheduling Commands ......................................................................................................................................................44
7.6 System Commands .............................................................................................................................................................45
7.7 Ethernet Configuration Commands .................................................................................................................................47
7.8 Advanced Commands ........................................................................................................................................................48
7.9 Memory Organization ........................................................................................................................................................53
7.10 Dynamic PS 1 and Dynamic PS 2 Summary ....................................................................................................................53
8 Further Features.......................................................................................................................................................................54
8.1 Bypass Relay ........................................................................................................................................................................54
8.2 On-board Program Set Switch ...........................................................................................................................................54
8.3 On-board TA/EON1TA Switch ........................................................................................................................................54
8.4 Showing Real Time in Dynamic PS ..................................................................................................................................54
8.5 Real-Time Backup ...............................................................................................................................................................54
8.6 Firmware Upgrade..............................................................................................................................................................54
8.7 RDS Output Monitoring.....................................................................................................................................................55
8.8 On-line Support ...................................................................................................................................................................55
9 Universal Encoder Communication Protocol (UECP).......................................................................................................56
9.1 UECP Implementation .......................................................................................................................................................56
9.2 Traffic Message Channel (TMC) Application Notes ......................................................................................................59
10 Annexes.....................................................................................................................................................................................60
10.1 Character Set and Code-Table Conversions ....................................................................................................................60
10.2 RDS Group Format .............................................................................................................................................................61
10.3 Troubleshooting ..................................................................................................................................................................64
3
1 Introduction
The P164 RDS Encoder is an attractive choice to all radio stations which don't want to burden their budget but still
need a flexible RDS encoder with support of all common data formats and RDS services. Effective design based on
DSP technology ensures high reliability and gives the user many advanced features while maintaining low
acquisition costs. The system is scalable from small local stations to large broadcast networks.
Some features are unique: remote output monitoring down to the bit level, direct conversion of XML tagging data to
Radiotext Plus, port multiplication thru Windows control software and several others. Due to native RDS2 support,
the P164 is future-proof equipment, ready for further enhancements of the FM broadcasting.
*) Note: In the meantime, the station logo is not supported by consumer FM receivers.
CE conformance notice:
This device complies with the requirements of the EEC Council CE marking and EMC directives.
Harmonized standards applied: EN 55032 (B ITE class), EN 55024, EN 50082-1.
Please read this manual and familiarize yourself with the controls before attempting to use this equipment.
Where not otherwise indicated, any information mentioned in relation to the RDS (Radio Data System) applies in full
also to the RBDS (Radio Broadcast Data System).
The equipment has been thoroughly tested and found to be in proper operating condition when shipped. The
manufacturer is not liable for any damages, including but not limited to, lost profits, lost savings, or other incidental or
consequential damages arising out of the use of this product.
No part of this manual may be reproduced or transmitted in any form or by any means, electronic or mechanical,
including photocopying, recording or information storage and retrieval systems, for any purpose other than the
purchaser's personal use.
Information in this document is subject to change without notice.
If you have any questions or comments regarding this document, please contact us via email.
We welcome your feedback.
Revision 2020-05-17
Copyright © 2020 PlRA DigitaI s.r.o.
4
2 Technical Specifications
General
RDS signal
RDS 57 kHz
Subcarrier configuration (switchable)
RDS2 57 kHz and 66.5 kHz
Subcarrier bandwidth ± 2.4 kHz (50 dBc)
Output level adjust 0.0 to 4.0 V p-p in 256 steps
Phase shift adjust stereo broadcast Full range, in 9.5 deg. steps
Audio/MPX/Pilot input
mono < 10 kΩ
Recommended load impedance
stereo MPX < 2 kΩ
Recommended MPX voltage 1.3 - 8.0 V p-p
Passthrough voltage gain 2 Hz - 100 kHz 1 (0 dB)
Pilot tone level min. 120 mV p-p
- recommended FM deviation 6.8 kHz
Pilot PLL capture range 8 Hz
Pilot frequency required stereo broadcast 19000 Hz ± 2 Hz
Output
Input J1
Output
SIDE/LOOP
Relay
RTC
Digital output
level control
D
EEPROM
I2C
Pilot/MPX
P164
Microcontroller
Port 2 Port 1
Optional
Program
Ethernet USB
Socket Socket
LED Indicators TA
Analogue Part
Power
Supply
5V Digital Part
3 Physical Description
3.1 Front Panel
USB
TA
RDS2 PILOT OPERATION TCP
ETHERNET
DEFAULTS
PORT 2
LOOP SIDE
3.3.1 Connectors
J10 – LCD (optional) display output
J2 – 12 V power supply connector (2.1 mm) 1 +5V 8 GND
Central pin is positive (+) 2 GND 9 GND
3 V0 10 GND
J3 – Output 4 RS 11 DB4
5 GND 12 DB5
J8 – Ethernet socket 6 E 13 DB6
7 GND 14 DB7
J5 – USB socket (standard B type) The LCD is HD44780 compatible, 16x2.
J19 – 5 V Output for LCD (optional) backlight D1 – Pilot tone indication / Firmware update
1: +5V D2 – Operation / Receive data / Error
2: Ground D9 – TA (blinking) / RDS2
D10 – TCP connected
B1 – Lithium battery 3 V for real time backup. Estimated endurance is 10 years. Replace by CR2032 type.
Note: EEPROM memory which is used for RDS data storage does not require any voltage to hold the data.
8
ETHERNET
DEFAULTS
PORT 2
LOOP SIDE
ETHERNET
DEFAULTS
PORT 2
LOOP SIDE
ETHERNET
DEFAULTS
PORT 2
LOOP SIDE
ETHERNET
DEFAULTS
PORT 2
LOOP SIDE
Both the audio processor and the FM transmitter have only one MPX connector provided - loopthrough mode.
It is preferred not to use this mode if another kind of connection is applicable.
ETHERNET
DEFAULTS
PORT 2
LOOP SIDE
FM Transmitter with
integrated audio processor RDS/SCA/MPX input Pilot/MPX output
In case of mono transmission (no stereo encoder used) the RDS encoder input may be left unconnected (since there is
no need of external synchronization) or it may be used for the audio signal injection in the case that the FM
transmitter has only one input connector.
Due to completely DSP-based solution there’s no adjustable element on the board affecting the RDS or MPX signal.
Set the switch to LOOP position only if you want to pass the input signal to the output of the RDS encoder
(loopthrough mode). In all other cases the switch must be set to the SIDE position!
Note: After first power-up the RDS encoder will start to generate the RDS signal with factory default values
(PS: * RDS *, PI: FFFF, output level 2 Vpp). There is no need to configure anything to turn on the RDS subcarrier.
10
Note: The RDS encoder contains two types of memory. These are marked as RAM and EEPROM. Like any other
computing system the RAM holds all operational data which are also used for transmission whilst the EEPROM is
used for the data storage during power-off. By default the button Test will fill the RAM only. The button Apply or
Store saves the data into EEPROM.
If the user forgets to store the data into EEPROM, that settings will be lost when the power is disconnected.
11
Important note: There is no universal setting for the RDS level. Due to different input sensitivity of different FM
broadcast equipment it is preferred always to check and adjust the RDS level.
The correct level should be between 2 and 11 % of the audio multiplex signal, measured by oscilloscope in peak-to-
peak values on the modulator input. Recommended value is such that results in 3.4 kHz deviation of the FM carrier.
Don’t forget that the maximum total FM carrier deviation with RDS and MPX signal is 75 kHz. It is much easier to
use any FM broadcast analyzer for setting the RDS level precisely.
Adjusting higher RDS level results in better RDS reception in areas covered with weak signal. This is especially
important if using scrolling PS or sending a lot of text information. However consider following aspects before
adjusting higher RDS level:
- the MPX (audio) level must be decreased a little to meet the overall FM deviation limit,
- automatic tuning using alternative frequencies (AF) will appear slower – the receiver will rate the signal
reception to be good although there may be a reason to tune to another frequency.
The deviation range of the FM carrier caused by RDS/RBDS is 1.0 to 7.5 kHz.
The deviation range of the FM carrier caused by stereo pilot tone is 6.0 to 7.5 kHz.
The overall peak frequency deviation shall not exceed 75 kHz.
The RDS level can be adjusted after establishing a connection to the encoder, using one of these two methods:
Enter the RDS level directly in mV p-p unit or check the ‘Track’ box and adjust the level as desired. Finally confirm
by the Apply button.
The P164 RDS encoder allows direct adjusting of the RDS level in 256 steps, in range 0 to 255, by assigning a
corresponding value to the LEVEL parameter. Each step represents approx. 15.6 mV increase.
LEVEL 1
Output RDS level 4000
256
12
The RDS level adjustment is valid for both the RDS and RDS2 subcarrier configurations.
In the RDS2 configuration, the output level value is a sum of two subcarriers, 57 kHz and 66.5 kHz. Amplitude ratio
between these subcarriers is 10:11.
Thus, when enabling the RDS2, signal level of stream 0 (57 kHz) drops to approx. a half of the original (RDS) level.
The phase adjustment between RDS subcarrier 57 kHz and pilot tone is an optional procedure applicable for stereo
broadcast (for mono there’s nothing to adjust). The adjustment is made using the Windows control software or using
the PHASE= command. Make sure the external synchronization is enabled (check the command EXTSYNC or the item
‘Subcarrier reference source’ on the Analog Control card in the Windows control software, it must be set to Auto).
From factory the phase shift is already adjusted so user may skip this chapter.
1. Fetch pilot or MPX signal to the RDS encoder. The PILOT LED will indicate that the pilot tone is present.
2. Adjust correct phase shift (0 or 90 degrees phase shift between 19 kHz pilot tone and 57 kHz RDS subcarrier,
measured on transmitter input, see the oscillograms). The phase adjustment would be difficult without an
oscilloscope or specialized measuring instrument.
Note: The phase adjustment is only optional. In all cases make sure the pilot tone is indicated on the RDS
encoder by the PILOT LED.
Oscillograms
Measuring conditions: Two-channel analogue oscilloscope, CH1: pilot (or MPX without audio), CH2: RDS
output, trigger source: CH1, vertical function: CH1+CH2, horizontal: 5 µs/div.
13
Note: When attempting to set-up a unit that was already placed in operation before, the user should clear the
encoder first. In the Windows control software, go to Device Setup – Special – Initialize.
This is very important information that enables the receiver to distinguish between countries, areas in which the
same program is transmitted, and the identification of the program itself. The code is not intended for direct display
and is assigned to each individual radio program, to enable it to be distinguished from all other programs.
The PI code consists of four characters (hexadecimal numbers).
The third and fourth characters are used to clearly identify different stations within the area of coverage.
Important note: If the station has only one transmitter, second PI digit must be zero (x0xx).
Important note: Factory default PI value is FFFF and it's needed to change it as soon as possible to avoid the
situation that two different stations with common area of coverage have the same PI. For each station in the same
location the unique PI must be assigned. Stations that carry different program must be unambiguously identified by
the last two PI digits. In other case they are recognized as one station by car radios, regardless of any other service
settings. If the broadcaster hasn't received the 4-digit PI from authority, he must choose such number that is not in
conflict with other stations in the location.
14
The PS name is max. 8 character long radio station name that will be shown most of the time on the radio display.
Advanced use of the PS (Dynamic/Scrolling PS) is discussed later.
The PTY code defines the type of the programme broadcast within 31 possibilities. See chapter 7.2 for a complete list.
This code could be used for search tuning.
Important note: PTY number 1 (News) should never be left on all the time. Use PTY number 3 (Info) for this purpose.
This is a flag to indicate that the tuned program carries traffic announcements. The TP flag should only be set on
programs which dynamically switch on the TA identification during traffic announcements. The flag shall be taken
into account during automatic search tuning.
4.6.5 MS (Music/Speech)
This is a two-state signal to provide information on whether music or speech is being broadcast. The signal would
permit receivers to be equipped with two separate volume controls, one for music and one for speech, so that the
listener could adjust the balance between them to suit his individual listening habits.
The Alternative Frequencies are used to tell receivers what frequencies they can receive the radio station on. This
facility is particularly useful in the case of car and portable radios. For this to work, each transmitter must have RDS
with the same PI code.
Important note: If second PI digit is set to zero (x0xx), this indicates that the station has only one transmitter and
the AF list is ignored on most receivers.
For complete RDS service description visit the website, section Support.
15
In this configuration, the broadcast automation system does not communicate directly in the RDS encoder’s language
but rather it updates the text information in a specific file on the disk. That file is periodically read and processed by
the RDS encoder’s control software.
Text
output LO O P SID E
Default Windows control software for the P164 RDS encoder is the Magic RDS 4. This application including
documentation, tutorials and examples of use can be downloaded from the Website, at the product page. The text
processing is accessible through menu item Tools – External text sources.
Since probably hundreds of automation systems are used around the world and new versions are released often,
information in this manual cannot be full-scale. For information about how to configure the broadcast automation
system text output please follow its documentation or contact the software vendor.
In this configuration, the broadcast automation system drives the RDS encoder directly via its communication port,
either physical or virtual.
RDS Encoder
RDS
12V D C ETH ER N ET R S-232 O U TPU T IN PU T G PIO
plugin LO O P SID E
Since some situations require more communications ports or there may be a need to address more RDS encoders in
larger networks, the P164 RDS Encoder’s control software provides a unique port multiplication features, called
Bridges and Virtual Ports. In such case the broadcast automation system connects to the Windows control software.
1. In the Magic RDS 4, click on the Virtual Ports icon and then on Add Virtual Port button.
In case of driving more RDS encoders, create a new Bridge first (Add new connection – kind: Bridge, type:
Internal Feed ).
2. Configure the connection parameters of the Virtual Port so that the broadcast automation system can connect to
it.
3. Configure the broadcast automation system, according to step 2.
For detailed information about how to control the RDS encoder contact your broadcast software vendor.
16
The P164 RDS encoder supports several formats (protocols) for input data and it’s designed to be compatible with all
broadcast automation software.
• ASCII commands
• UECP protocol (format given by UECP specification)
• X-Command (described later in this chapter)
Example:
RT1=Now Playing: Julia Michaels - Issues
Compatibility commands
To reach the best possible compatibility with broadcast automation systems, the P164 includes a special set of
compatibility commands. In the systems where the P164 is not directly supported (or the system is older version) the
user may try to select another RDS encoder model to send text messages. Where possible, set the communication as
unidirectional.
Command Translated to
TEXT= RT1=
DPS= DPS1=
PS_SCROLL= DPS1ENQ=
The RT+ feature is designed to let the listener take additional benefit from the Radiotext service by enabling receivers
to offer direct access to specific elements of Radiotext. Typically the RT+ feature supports song artist and song title
elements. These elements anyway carried in the Radiotext, are identified by their class type, length and location
within the Radiotext. The receiver must be equipped with the RT+ function (also called "tagging") to take advantage
of this feature.
The RDS encoder includes full support for the RT+ and its handling is highly automated. For direct use your
broadcast automation system must support X-Command or the RT+ function either by means of user defined groups
or by the command RTP= (see section 7.8 for more details). In other cases the Windows control software used in the
indirect link configuration can provide the RT+ service.
The X-Command is the newest and preferred method how to forward text information (incl. tagging) from the
broadcast automation system to the RDS encoder. It is based on simplified markup language. The X-Command is
fully supported by the P164 RDS Encoder.
Example:
XCMD=<rds><item><dest>3</dest><text>Now Playing: <artist>Julia Michaels</artist> -
<title>Issues</title></text></item></rds>
For more details follow the information in the document ‘X-Command for RDS Encoders’.
17
5.2 Dynamic PS
Standard RDS enabled receiver disposes of 8-character LCD display but we usually need to show pile of information
and commercials. So small display on the one hand and so much demands on the other hand. The P164 solves it by
unique system of text messages showing. Although Radiotext service is defined in the RDS standard, this service is
not present some receivers (especially older car radios) and has some other limitations. According to the broadcasters
needs, the PS service - one of the basic RDS services supported by all receivers - can be usually used to give
sequential information. This has become known as ‘Dynamic PS’ or ‘Scrolling PS’.
Note: Using the dynamic PS is restricted in some countries and it's fully prohibited by the RDS standard!
The manufacturer is not responsible for incompetent use of this feature. Some receivers may not display the dynamic
PS properly for reasons that lie entirely on their side. Never provide traffic information inside the Dynamic PS text!
The P164 RDS encoder offers advanced implementation of the Dynamic PS service. Basic text message length is up to
255 characters (mode independent). Two varieties of the Dynamic PS are present: Dynamic PS 1 (DPS1) and Dynamic
PS 2 (DPS2). Both varieties are configurable independently from each other.
Basic configurable parameters are:
Text content/text source
Display mode
Label period or scrolling speed
Number of transmissions
The number of transmissions is specified for each Dynamic PS text. The Static PS period (delay between text loops)
specifies the time between two repeats of the Dynamic PS text loops. Default PS is displayed during this time.
Four display modes are provided. The mode is switchable ‘on the fly’, without need to re-enter the text message.
Mode 0 - Scrolling by 8 characters
Mode 1 - Scrolling by 1 character
Mode 2 - Word alignment scrolling
Mode 3 - Scrolling by 1 character, text separated by spaces at begin and end
Additional differences exist between Dynamic PS 1 and Dynamic PS 2 (see sections 7.2 and 7.10). In general the DPS1
should be used if on-line connection is available between your studio and the RDS encoder while the DPS2 should be
used if the RDS encoder is placed on a site without on-line connection providing set of fixed messages.
18
Important note: If second PI digit is set to zero (x0xx), this indicates that the station has only one transmitter and
the AF list is ignored on most receivers.
Ideally the AF list should only comprise frequencies of neighboring transmitters or repeaters. Entire AF set should be
as tiny as possible to allow the receiver to find the strongest frequency quickly. This will improve the listener's
experience. Thus there should be more RDS encoders using individual AF sets within larger networks.
94.3 MHz
95.8 MHz
91.2 MHz
5.3.1 Method A
Note: Requires only one RDS encoder for entire network (common STL or one main transmitter and two
repeaters). The list must contain all frequencies on which the signal from the RDS encoder is carried.
91.2 MHz:
AF=94.3 Enter the list
*AF Store the list
94.3 MHz:
AF=95.8,91.2 Enter the list
*AF Store the list
95.8 MHz:
AF=94.3 Enter the list
*AF Store the list
19
5.3.2 Method B
Method B AF coding is a more complex method that is used where the number of AFs used by a transmitter and its
associated repeater stations exceed 25, or where it is required to indicate frequencies which belong to different
regions which at times carry different programs.
More than one transmitter or associated repeaters of the station broadcast the same set of different AF lists in
sequence. Total number of AF lists used within entire network is in general identical to the number of transmitters
and repeater stations in the network so as to provide a unique list for each transmitting station. In this method the
alternative frequencies are individually addressed by transmitting the tuning frequency paired with one alternative
frequency. Each list starts with the tuning frequency for which the list is valid, e.g. 94.3. All remaining pairs (up to
12) give the tuning frequency together with a valid AF.
For the transmission of the frequency pairs within one block the following convention is used. They are generally
transmitted in ascending order (F1 < F2), e.g. 94.3,95.8 or 91.2,94.3. In special cases they are transmitted in
descending order, if they belong to different regions, or carry from time to time different programs. If you use the
Windows control software, this assures right order automatically.
Note: For illustration purpose only. If the network contains only a few frequencies like in this example, the
method A is more effective.
Notes:
If the number of AFs of a station is larger than 12, the list must be split into two or more lists. These lists are
transmitted directly one after the other.
Broadcasters using splitting of a network during certain hours of the day should use AF method B, and not AF
method A. The lists should be static, i.e. the AFs included in the list, carrying a different program during certain
hours of the day, shall be signaled by transmitting in the descending order (F1 > F2). Their PI shall differ in the
second digit of the code (using regional variant 4 to F) and may also be static. Switching the second digit of the PI to
1, 2 or 3 informs the receiver that now even AFs transmitted in descending order carry the same program and the
receiver may use them for switching.
20
The EON is especially useful for linking two or more stations of the same owner. Most of EON featured receivers
gives priority to stations linked by EON when seek function is activated. Since the P164 can store four EON links, up
to 5 stations can be linked together.
Station that doesn’t carry traffic announcements can refer to a station that does. This situation is described below. For
more information see appropriate section in the List of Commands or in the Magic RDS control software help.
Station which uses the code TP=0, TA=1 must refer to at least one program service which carries traffic information,
and has the flag TP=1. When a particular program service begins a traffic announcement, the station that cross-
references this service via the EON feature will broadcast a switch signal by setting the appropriate EON TA flag to 1.
The EON TA flags can be controlled by software for all four EON links in the P164. The first EON link TA flag can be
also controlled by external TA/EON1TA switch.
The situation described is illustrated on the example below:
5.4.2 Example
Kiss FM is a small station that doesn’t carry traffic announcements but refers via EON to City Radio, which is
regional station of the same owner that carries the traffic announcements. If the Kiss FM listener has activated the
EON feature on his receiver, he will be automatically tuned to City Radio for the duration of traffic announcements.
PI=20F1 PI=2501
PS=KISS FM PS=CITY
TP=0, TA=1 TP=1, TA=(controlled by external switch)
Frequency: 90.2 MHz Frequencies: 93.7 and 106.2 MHz
(only 93.7 can be received in the area covered by Kiss FM)
Station 1 EON Data:
EON1PI=2501
EON1PS=CITY
EON1TA=(controlled by external switch)
EON1AF=93.7
Both TA/EON1TA switch connectors can be wired together and controlled by only one switch or device if the
transmitters of 90.2 and 93.7 MHz are placed on the same site.
21
The scheduling feature is fully implemented in the P164 unit and works independently
Almost any RDS service or control command can be scheduled
Up to 48 scheduling items
Each item may contain any combination of days in week, up to 12 times (a wildcard is supported on the hour
place), program type (PTY) information and any from more than 60 commands
Let’s say that our radio station called ‘PRO 88’ broadcasts news from Monday to Friday at midday. The news
duration is 40 minutes. During the news the PS is set to ‘HOT NEWS’ and the PTY is set to 1 (News). In common
program the PTY is set to 3 (Info).
Although it’s possible to change directly the Dynamic PS and Radiotext (using an appropriate command, for example
RT2=The best music in the city), the maximum text length is limited since maximum command length in
each Scheduling item is 35 characters. For longer texts you may use indirect method based on the bank of Messages:
1. Store the text as a Message, for example Message 01.
2. In the Scheduling call the message number, for example RT2MSG=1 or DPS2MSG=1
or XCMD=<rds><msg>1</msg></rds>.
The Windows control application provides easy GUI for this case.
5.5.4 Troubleshooting
The subcarrier configuration is controlled by ASCII command RDSGEN= (see section 7).
In the Window control software, the RDS2 subcarrier configuration can be enabled in Device Setup – Analog Control
– RDS Generator.
When the RDS2 is enabled, an additional stream 1 will appear in the MPX spectrum at 66.5 kHz subcarrier. Content
of the basic stream 0 at 57 kHz subcarrier remains unchanged, providing all original RDS features and full backward
compatibility.
Note: In the meantime, the RDS2 services are not supported by consumer FM receivers. Enabling the RDS2 may
violate with your broadcast license specifications!
The RDS2 mode of operation is controlled by ASCII command RDS2MOD= (see section 7).
In the Window control software, the RDS2 mode of operation can be changed in RDS Content – System –
Miscellaneous.
Content of the stream 1 is partially or fully controlled by external applications, which provide the data coded into the
RDS2 group format. There are no restrictions in the RDS2 services support.
All modes of operation allow external applications to send the RDS2 content using the ASCII command G=. The
mode of operation effectively determines a default (idle state) content of stream 1:
0 Tunneling The stream 1 is effectively a duplicate of the basic stream 0. This is a default setting.
RDS2 Buffer /
1 RDS2 Buffer (see the command STORE) is periodically sent in stream 1.
Station Logo
The modes of operation may be enhanced in future, depending on the RDS2 expansion.
23
6 Communication Ports
6.1 Overview
For configuration and control requirements the RDS encoder is equipped with two communication ports. These ports
include individual buffers and work in complete independence, i.e. both ports can be used at one time by different
applications.
Port
Physical plug Port type Description and purpose
reference
All ports are universal so they accept complete set of ASCII commands, a connection from the Windows control
software and UECP records (depending on setup).
Individual access limitations can be configured for each port using the Port Access Control (PAC).
This method uses the Windows control software for Ethernet configuration. A working connection to the encoder
must already be established, either via Ethernet or USB.
25
1. Establish a connection to the RDS encoder, either via Ethernet or USB (see section 4.4).
2. In the Windows control software, select Device Setup and then go to the LAN Settings tab.
3. Configure the fields and finally click on the Apply button.
4. The settings will take effect in 10 seconds. The RDS encoder does not require to be restarted.
Use DHCP Embedded DHCP client allows for automated configuration of the Ethernet parameters
like IP address or DNS server.
This option should be Enabled. Choose Disabled if you want to enter the parameters
manually or if there’s no DHCP function contained in your network.
Work As: TCP For TCP protocol, the user may specify if the RDS encoder is a server (waiting for a client
Server/Client application connection) or a client (actively connects to the specified RDS data providing
server).
Hint: If host name or IP address needs to be specified in the RDS data providing
application, the RDS encoder will be a server (most frequent option).
The server side must be visible in the network. In internet that means the server requires
public IP address and/or correct port forwarding setting on router (if present).
Port Number Fill the port number in range 1 to 65535. It must match the port number of the RDS data
providing application.
Connect To Available only if the encoder is configured as a client. Specifies the remote server the
encoder will connect to.
Password The password is required in order to enable access to the Ethernet configuration website.
Default password is admin.
26
This method uses the ConfigTool desktop application for Ethernet configuration and getting its status (for example
current IP address). Data are carried by UDP broadcast feature so the process is independent of network
configuration and initial state of the device.
Note: The simple configuration cannot be applied if Alternative configuration switch was previously enabled in the
Windows control software.
27
The RDS encoder includes HTTP server and web-based user interface. An internet browser may be directed to the
encoder’s IP address to bring up the Ethernet configuration website. RDS content cannot be changed this way.
Note: The embedded website cannot be used for changing the configuration if Alternative configuration switch was
previously enabled in the Windows control software.
28
Use DHCP No
IP Address 192.168.1.88
Subnet Mask 255.255.255.0
Gateway 192.168.1.1
DNS Server 114.114.114.114
Work As TCP Server
TCP Port 5000
The default configuration can be recalled any time by pressing the Ethernet defaults button:
Hint: In the factory default configuration, the encoder is directly accessible in networks which use IP addresses in
format 192.168.1.xxx. Connection is instantly possible to IP address 192.168.1.88, port 5000.
The port is identified by its number (1 or 2). The command is identified by its code (see the document ‘P132 RDS
Encoder – Communication Ports and Internet Functions’). The RDS encoder is set from factory so that all commands
are accepted (enabled) on all ports.
The PAC feature applies to both the ASCII commands and the UECP commands on all ports. An exception from this
rule exists for USB port: ASCII commands on this port cannot be disabled so local configuration is always possible.
If the UECP commands are completely disabled by ASCII command UECP=0, the PAC has no effect on UECP
commands.
The Port Access Control feature can be easily configured in the Windows control software (Device Setup –
Communication) or via ASCII command PAC.
Commands executed using internal scheduler, are never restricted by the PAC.
The PAC does not affect transmission of any service. For example, if Radiotext is being transmitted,
disabling the Radiotext command (code AB) does not stop its transmission. Use appropriate commands for
that purpose.
29
All RDS encoder’s settings and configuration incl. text messages etc. can be made from a terminal using a set of
ASCII commands. (The Windows GUI based application effectively does the same; it translates the user’s data into
the ASCII commands.)
Note: If the RDS encoder was previously in use, there may remain any speed from 1200, 2400, 4800, 9600 or
19200 bps. The Magic RDS 4 detects the speed automatically.
5. For TCP connection, fill the encoder’s IP address and network port number on which the encoder listens for the
connection. The RDS encoder must be configured before using the TCP connection.
Once configured, the terminal can be used. To check if the hardware and logic configuration work as planned, type
for example HELP and press <Enter> to display the list of all commands. If no or unknown characters are displayed
on the screen, try again a second time, otherwise, check the following points:
To display the commands entered at the keyboard on the screen, type the command ECHO=1 followed by <Enter>. If
all characters written are displayed twice, type ECHO=0 and press <Enter>.
To store this parameter into a non-volatile EEPROM memory, type *ECHO and press <Enter>.
To display actual parameter value, type ECHO and press <Enter>.
Now you made first steps with the RDS encoder command interpreter.
30
Not all methods are available for all commands, see Command Summary, section 7.1.
Depending on the command processing success, several characters (followed by two pairs of carriage return and line
feed characters) can be returned by the RDS encoder:
The command interpreter is not case sensitive for the portion before the ‘=’. The value portion is case sensitive,
hexadecimal values, if contain letters, must be typed in upper case.
If you wish to retain change of any parameter value during power off, don’t forget to store it into EEPROM memory!
The P164 supports both unidirectional and bidirectional communication modes. Nothing is required to be set, the
mode of operation results only from the method of communication.
Unidirectional
(backward channel from the RDS encoder is not Very simple to implement
present or the data from this channel is ignored) Low cost data link
Unidirectional communication:
If sending more commands in sequence, the execution times must be sometimes taken into consideration;
otherwise some commands may be discarded after internal buffer filling:
The RX buffer size is 90 bytes for each port. For commands with 0 ms execution time, as well as for command
batches whose length is shorter than the RX buffer size, there’s no need to pay attention for timing.
The execution times result from the EEPROM write cycle duration or from the requirement of internal
synchronization with RDS data group order. Most of commands require no perceptible delay.
Legend:
TX – data sent to the RDS encoder, ← - CR (char. 13, <Enter>)
32
Bidirectional communication:
Next command can be sent after receiving confirm sequence from previous command. This ensures right timing
and optimal channel usage in all cases. There is no need to consider any timing or delays.
Legend:
TX – data sent to the RDS encoder, RX – data read from the RDS encoder, ← - CR (char. 13), ↓ - LF (char. 10)
7 List of Commands
7.1 Command Summary
Basic:
AF AF= *AF *AF= Alternative Frequencies
AFCH AFCH= *AFCH Alternative Frequency Channels
DI DI= *DI Decoder Identification
DPS1 DPS1= *DPS1 Dynamic PS 1
DPS1ENQ= Dynamic PS 1 Enqueue
DPS2 DPS2= *DPS2 Dynamic PS 2
DPS1EN DPS1EN= *DPS1EN Dynamic PS 1 Enable
DPS2EN DPS2EN= *DPS2EN Dynamic PS 2 Enable
DPS1MOD DPS1MOD= *DPS1MOD Dynamic PS 1 Mode
DPS2MOD DPS2MOD= *DPS2MOD Dynamic PS 2 Mode
DPS1REP DPS1REP= *DPS1REP Dynamic PS 1 Number of Repeating
DPS2REP DPS2REP= *DPS2REP Dynamic PS 2 Number of Repeating
DTTMOUT DTTMOUT= *DTTMOUT Default Text Timeout
EQTEXT1 EQTEXT1= *EQTEXT1 Equal Text 1
LABPER LABPER= *LABPER Label Period
MS MS= *MS Music/Speech
PI PI= *PI Program Identification
PS PS= *PS Program Service name
PTY PTY= *PTY Program Type number
PTYN PTYN= *PTYN Program Type Name
PTYNEN PTYNEN= *PTYNEN PTYN Enable
RT1 RT1= *RT1 Radiotext 1
RT1EN RT1EN= *RT1EN RT1 Enable
RT2 RT2= *RT2 Radiotext 2
RT2EN RT2EN= *RT2EN RT2 Enable
RTPER RTPER= *RTPER Radiotext Switching Period
RTTYPE RTTYPE= *RTTYPE Radiotext Type
RSTDPS RSTDPS= *RSTDPS Restart Dynamic PS
SCRLSPD SCRLSPD= *SCRLSPD Scrolling PS Speed
SPSPER SPSPER= *SPSPER Static PS Period
TA TA= *TA Traffic Announcement
TATMOUT TATMOUT= *TATMOUT TA Timeout
TP TP= *TP Traffic Program
TPS TPS= *TPS Traffic PS
INIT Initialization
*ALL Store All
HELP Help
EON:
EONxAF EONxAF= EON x Frequencies
EONxAFCH EONxAFCH= EON x Frequency channels
EONxEN EONxEN= EON x Enable
EONxPI EONxPI= EON x Program Identification
EONxPS EONxPS= EON x Program Service name
EONxPSN EONxPSN= EON x Program Service Number
EONxPTY EONxPTY= EON x Program Type number
EONxTA EONxTA= EON x Traffic Announcement
EONxTP EONxTP= EON x Traffic Program
*EON Store all EON data into EEPROM
x is in range 1-4
Note: Almost all commands have their equivalent in the Windows control software, accessible through its GUI.
34
Messages:
MSGxx *MSGxx= Text Message
MSGxxD *MSGxxD= Message Destination
MSGLIST List of Messages
DPS2MSG DPS2MSG= *DPS2MSG Dynamic PS 2 Message Number
RT2MSG RT2MSG= *RT2MSG Radiotext 2 Message Number
xx is in decimal range 01-99
Scheduling:
SLIST List of Scheduling Items
SxxC *SxxC= Scheduling Item Command
SxxD *SxxD= Scheduling Item Days
SxxP *SxxP= Scheduling Item PTY
SxxT *SxxT= Scheduling Item Times
SEN SEN= *SEN Scheduling Enable
xx is in decimal range 01-48
System:
COMSPD COMSPD= *COMSPD Port 1 Speed
CT CT= *CT Clock Time and Date
DATE DATE= Date
ECHO ECHO= *ECHO Terminal Echo
EXTSYNC EXTSYNC= *EXTSYNC External Pilot Synchronization
LEVEL LEVEL= *LEVEL RDS Signal Level
LTO LTO= *LTO Local Time Offset
MJD MJD= Modified Julian Day
PHASE PHASE= *PHASE RDS Signal Phase
PILOT Pilot Tone Present
RDS2MOD RDS2MOD= *RDS2MOD RDS2 Mode of Operation
RDSGEN RDSGEN= *RDSGEN RDS Generator
RESET Reset
SETFEAT *SETFEAT= Special Features
SPEED SPEED= *SPEED Port 1 Speed
STATUS RDS Encoder Status
TIME TIME= Time
VER Firmware Version
Ethernet configuration:
SETCTS *SETCTS= Port 2 Configuration Switching Timeout
SETLAN *SETLAN= LAN Setup
SETPORT2 *SETPORT2= Port 2 Main Configuration
SETPORTA *SETPORTA= Port 2 Alternative Configuration
35
Advanced:
ADR *ADR= Encoder Address List
CC *CC= Conditional Command
EAS= Send EAS Text Message
EASTIME= Set EAS Timer
ECC ECC= *ECC Extended Country Code
ECCEN ECCEN= *ECCEN ECC and LIC Enable
G= Send RDS or RDS2 Group
GRPSEQ GRPSEQ= *GRPSEQ Group Sequence
LIC LIC= *LIC Language Identification Code
PAC y,zz PAC y,zz= *PAC Port Access Control
PROGRAM PROGRAM= *PROGRAM Program Set Selection
PSNx *PSNx= Program 1/2 Service Number
PSW PS Window
RTP RTP= Radiotext Plus Tagging Data
RTPRUN RTPRUN= Radiotext Plus Running Bit
SETSPY= Set RDS Monitoring Counter
SHORTRT SHORTRT= *SHORTRT Short Radiotext
SITE *SITE= Site Address List
*STORE= Write to the non-volatile RDS2 Buffer
UDG1 UDG1= *UDG1 User Defined Groups 1
UDG2 UDG2= *UDG2 User Defined Groups 2
UECP UECP= *UECP General UECP Enable
XCMD= X-Command for RDS encoders
x is in range 1 to 2
y is in range 0 to 4
zz is in range 00 to FF (hex)
36
DPS1 Dynamic PS 1
Up to 255 characters long text message to be displayed on receiver instead of static PS name. Primarily used
for song titles streaming etc.
DPS1=Hello World Sets the DPS1 text
DPS1= Clears the DPS1
DPS2 Dynamic PS 2
Up to 255 characters long text message to be displayed on receiver instead of static PS name. Alternatively
used in conjunction with Messages Commands.
DPS2=Hello World Sets the DPS2 text
DPS2= Clears the DPS2
MS Music/Speech (0, 1)
Music/Speech switch.
MS=0 Speech program
MS=1 Music program
RT1 Radiotext 1
Up to 64 characters long text message to be displayed on receiver in Radiotext format. Primarily used for song
titles streaming, commercials etc.
RT1=Hello World
RT2 Radiotext 2
Up to 64 characters long text message to be displayed on receiver in Radiotext format. Alternatively used in
conjunction with Messages Commands.
RT2=Hello World
TPS Traffic PS
Static text displayed on receiver during traffic announcements. Max. 8 characters long.
The TPS= command requires additional processing time of up to 400 ms for internal synchronisation with
RDS group order.
TPS=TRAFFIC
TPS= Disables the Traffic PS
41
INIT Initialization
Sets most parameters and services in actually selected Program to their default values. Does not clear
Messages and Scheduling items. Does not clear port and network settings.
Apply for example if new blank EEPROM is placed on the board or if the RDS encoder was previously used
for another station.
INIT Initialize the program set that is actually selected.
*CC= Complete initialization procedure. Replace the HH:MM with actual time and the
PROGRAM=2 DD.MM.YY with actual date.
INIT Note: This initialization sequence must always be applied if new blank
*ALL EEPROM is placed on the board in production process. Alternatively use the
PROGRAM=1 Windows control software: Device Setup – Special – Initialize.
INIT
*ALL
TIME=HH:MM
DATE=DD.MM.YY
HELP Help
Shows all commands available.
HELP
42
x is in range 1-4
43
DATE Date
Specifies the actual date in DD.MM.YY format.
DATE=30.11.05 30th of November 2005
RESET Reset
Provokes a hardware reset of the RDS encoder and is equivalent to an "off-on" cycle of the RDS encoder.
RESET
CC Conditional Command
Executes specified command when specified condition occurs. Optional ELSE command supported.
Syntax:
*CC=[aa]bcc:dddddddd
*CC=ELSE:eeeeeeee
where is:
aa - memory address pointer (00-FFF)
b - condition operator
< - lower than
> - greater than
= - equal
! - not equal
B - bit cc of [aa] is set (numbered from LSB to MSB)
cc - value to compare (00-FF) or bit number (00-07)
dddddddd - the command executed if the condition is matched
eeeeeeee - the command executed if the condition is not matched (optional)
Max. command length is 31 characters. Once the command is executed, next execution is stopped until the
condition matching changes. In other words, the command is executed only at the condition matching change. Both
numbers aa and cc are in hexadecimal representation. Only one CC item is allowed. Only commands from the
second column of the Command Summary are allowed.
To check visually what value is on each address, type MEM xx where xx is the address desired.
49
Important note: The CC is a very “strong” command. Due to a theoretical possibility of bad setting that may cause
the unit stop responding (please don’t ask for an example) the Conditional Command is not active after power-up
for up to 30 seconds. This gives the user a time to type *CC= to disable the Conditional Command before it
becomes active.
*CC=[CC]B03:PS=RADIO Periodically switches the PS between ‘RADIO’ and ‘PRO 88’.
*CC=ELSE:PS=PRO 88
PTYN=Football Sets PTYN name to ‘Football’. When PTY code ‘Sport’ is on-air,
*CC=[13]=04:PTYNEN=1 additional PTYN name is included.
*CC=ELSE:PTYNEN=0
*CC=[E9]!01:COMSPD=1 Does not allow to set port 1 speed other than 2400 bps.
*CC=[E4]>0B:DPS2=Good afternoon Different DPS2 text for hours in range 0-11 and 12-23. Scheduling
*CC=ELSE:DPS2=Good morning feature can be used as well.
*CC=[71]<20:DPS1MOD=1 Shows first part of DPS1 in mode 1, then switches to mode 2 for
*CC=ELSE:DPS1MOD=2 the rest of the text.
PSW PS Window
Returns actual Program Service name that is being sent by the RDS encoder. The value returned is an output of
internal real-time RDS decoder so it’s affected also by Dynamic PS and user defined groups.
PSW
RTP Radiotext Plus Tagging Data (00-31; 00-31; 00-31; 00-31; 00-31; 00-15)
Six 2-digit decimal numbers of RT+ tagging data in this order:
Tag 1 type, tag 1 start, tag 1 length, tag 2 type, tag 2 start, tag 2 length.
Start marker 00 means the first character in the Radiotext. Length marker gives the number of characters
following the first character at the start position.
The tagging data must be associated with actual Radiotext 1.
The tagging data are transmitted as groups 3A (RT+ ODA AID) and 11A (RT+ Tagging Data).
On each enter of the tagging data internal Toggle bit automatically changes its state from 0 to 1 or from 1 to 0.
First entering of the tagging data automatically enables the internal RT+ feature until power off or reset.
The RT+ is active only if symbol ‘R’ is present in the Group sequence.
If both tag 1 type and tag 2 type are set to 00, internal RT+ running bit is temporarily hold low until at least one
valid tag type is entered.
RT1=Now playing: Novaspace – Time After Time
RTP=04,13,08,01,25,14
RDS2MOD
PI, PS, Dynamic PS, RT,
AF, Group Sequence, ... PSN
Port 1
EON UDG
Port 2
Command
Non-volatile Memory (EEPROM) Interpreter
Program Set 1
RDS2MOD
PI, PS, Dynamic PS, RT,
AF, Group Sequence, ... PSN1
EON UDG
Program Set 2
RDS2MOD
PI, PS, Dynamic PS, RT,
AF, Group Sequence, ... PSN2
EON UDG
Messages
01-99
Scheduling Items,
Conditional Command
Network Settings
Dynamic PS 1 Dynamic PS 2
Real time showing capability yes, in mode 0 and 2 yes, in mode 0 and 2
Display modes available 4 4
Text queue available yes no
Max. text length 255 255
Max. queued text length 127 N/A
Removing redundant spaces from the text end yes, in mode 2 and 3 no
Allows transmission of Messages no yes
Commercials, news and Fixed texts from the
Typically used for
"on-air" texts Messages bank
54
8 Further Features
8.1 Bypass Relay
The RDS encoder board includes a bypass relay providing an alternative way for the MPX signal on power supply
failure (applies to loopthrough connection mode only).
RDS data is provided as ASCII coded RDS groups in raw format at the RDS group rate (11.4 groups per second for
each stream). The group content provided is equal to the group content being sent to output of the RDS encoder and
being seen by listeners. This format of data is directly supported by some easy to use applications (for example
freeware RDS Spy).
RDS Spy - Real-time freeware Radio Data System decoder and analyzer for Windows.
1. For monitoring via Port 1, set the port speed to 19200 bps.
2. In the Windows control software, select the device (connection) of interest.
3. Click on the RDS Spy button:
Important note: Before sending an email please make sure you have read entire content of this manual (incl. section
10.3), control software help file and also forum, F.A.Q. and tips on the website. Your question may be already
answered in this extensive knowledge base.
56
Note: Read more information about the UECP in the document "SPB 490 Universal Encoder Communication
Protocol" (published by RDS Forum).
The address field of each UECP record comprises of two elements. These are:
The RDS encoder incorporates two address lists; one of acceptable Site addresses (SITE) and the other of acceptable
Encoder addresses (ADR). A UECP record is acceptable to a particular encoder only if the site address is contained
within its site address list and the encoder address is contained within its encoder address list.
It is expected that many UECP commands will be sent to all encoders. For this reason a “global” address of 0 is
defined for both the site and encoder addresses. Thus the address lists always consist of addresses defined by user
and the “global” address of 0. Messages bearing the site address of 0 are deemed to be acceptable at all sites in the
system. Messages bearing the encoder address of 0 are deemed to be acceptable by all encoders at sites specified by
the accompanying site address.
57
9.1.4 The UECP implementation in the P164, its characteristics and restrictions
Notes:
1) Supports RT buffering for up to two radiotexts – edits either the Radiotext 1 or Radiotext 2.
If using only one radiotext (most frequent case), at least the RT1 must be enabled (RT1EN=1). Beyond the UECP
specification, the radiotext may be optionally showed as Dynamic PS 1 (see the command EQTEXT1), in that
case the RT1 may be disabled.
If using two radiotext, both RT1 and RT2 must be enabled (RT1EN=1, RT2EN=1).
Control bits handling:
Bit 7 Ignored.
Bit 6 0: destination is RT1; 1: destination is RT2.
Bit 5 Ignored.
Bits 4..1 Ignored. The RDS encoder switches between two radiotexts using real-time base
(see the command RTPER) rather than using a number of transmissions for each radiotext.
Bit 0 0: do not toggle A/B flag; 1: toggle A/B flag.
2) The RDS encoder address list can contain up to three items for the Site address and up to three items for the
Encoder address. One of these items is always fixed to 0, the remaining two items can be changed using the
commands *SITE= and *ADR=.
3) Buffer size 16 groups (FIFO type), shared by all ODA, TMC and free-format Message elements. Number of
repeats is assigned to each group in the FIFO buffer so one group occupies one position in the buffer regardless
of number of repeats. See section 9.1.5.
4) Buffer configuration bit 5 ignored. Buffer configuration bit 6 meaning: 0 – no repeat, 1 – repeat the group one
time, then clear.
58
5) Full support except the priority and buffer configuration. The encoder automatically assures at least 3-group
long gap between any TMC groups in the data transmitted.
6) Timeout and buffer configuration ignored. Always inserts one group through the FIFO buffer.
7) Priority, mode and buffer configuration ignored. Always inserts one group through the FIFO buffer.
8) MEC's not included in the list above are ignored, incl. all possible Message elements that may follow within the
same Message field. Due to mistake in the UECP specification (unknown Message element length in general) it
may be impossible to detect following Message element within the same Message field. It's strongly
recommended for the UECP data providers not to insert more than one Message element inside each Message
field to maintain general compatibility and to keep the UECP really ‘universal’.
When the UECP is enabled, the RDS encoder accepts any mixture of ASCII commands and UECP records on the
same communication port. The UECP communication is always unidirectional. There are no responses sent to the
UECP records.
Any characters which follow the UECP start byte (0xFE) will be ignored by the ASCII command interpreter until one
of the following conditions occurs:
For this reason take care not to send the UECP start byte within an ASCII command when the UECP is enabled.
In order to simplify the RDS encoder’s control and fit it to current applications, the device incorporates one global
UECP buffer for all groups inserted via MEC 24, 30, 40 and 42. This buffer is a FIFO type and its capacity is 16
groups.
U EC P buffer
interpreter
...
O ther com m ands
Num ber G roup type and group content
of repeats (blocks 2, 3, 4)
Note: The UECP buffer applies only to user-defined RDS groups inserted via UECP protocol. The UECP buffer has no
meaning for other that those UECP MECs: 24, 30, 40 and 42.
59
The TMC service can work only if there is an application that we can call 'TMC data provider'. The TMC data
provider collects all related information and translates it into RDS groups 8A type. The output of the TMC data
provider must be either by means of ASCII command G= or (more often) coded as UECP command with MEC 30. We
will deal with the second case in following text.
Nowadays the TMC service is coded as an ODA application. Thus there must be ODA AID groups 3A transmitted in
addition to the 8A groups. This can be done for example using the UECP MEC 24. The 3A groups typically carry
fixed content so in some cases they can be inserted into the RDS encoder also one-time using the command UDG1= or
UDG2=.
The Address and Site fields are optional. When the TMC data provider drives one RDS encoder only, these fields are
usually set to zero. However there can be more RDS encoders connected with various Address and Site values. Each
encoder will accept only the UECP records that match the Address and Site criteria. This configuration has been
tested successfully simulating a network of more than 60 encoders (equivalent to full load of one 9600 bps channel).
1. Configure all static parameters of the RDS encoder (PI, PS, CT etc.). Enable the UECP (UECP=1 *UECP).
2. Where required, store the fixed 3A groups using the commands UDG1= or UDG2=
(for example: UDG1=30100646CD46,30104080CD46 *UDG1).
In this case make sure the UDG groups are included in the Group sequence (symbols X or Y).
3. Decide for the communication settings. Configure the RDS encoder and TMC data provider ports.
4. Configure the Site and Address values.
This application example shows TMC data and ODA AID information inserted by UECP commands 30 and 24.
Notes:
1) Any RDS group inserted using the UECP elements 24, 30, 40 or 42 is put into the UECP buffer. See section 9.1.5
for more details. For TMC transmission it is recommended to leave the UECP buffer as transparent so the TMC
data providing application has full control over the TMC transmission. The encoder automatically ensures at
least 3-groups long gap between TMC groups.
60
10 Annexes
10.1 Character Set and Code-Table Conversions
Original RDS system, as defined by the standards, does not support Unicode character set. Default character set (G0)
used within the RDS system is limited to the characters provided in following EBU Latin code-table.
Character 'é' can be found in the table on coordinates 8, 2. Thus it converts to ASCII character 0x82 (HEX) or 130.
A conversion is required for all characters outside the basic set region. If you use the Magic RDS control software, the
characters are converted automatically between Windows Unicode and RDS character set. Setting for that feature can
be made in Preferences - Local settings. Some functions are based on UTF-8 coding – conversion is made
automatically inside the RDS encoder.
Notes:
Many commercially available receivers use 14-segment LCD displays. These receivers are able to display only a
limited part of the basic character set (green framed) and do not support the extended set at all. All lower-case
characters are showed as upper-case.
The EBU Latin basic set is compatible with most of other systems so conversion is not required for this region.
Since many receivers contain no support for the extended character set, it is recommended to keep all characters
in all text messages in the basic set region.
61
The largest element in the RDS coding structure is called a "group" of 104 bits each. Each group comprises 4 blocks of
26 bits each. Each block comprises an information word and a checkword. Each information word comprises 16 bits.
Each checkword comprises 10 bits.
All information words, checkwords, binary numbers or binary address values have their most significant bit (MSB)
transmitted first.
The data transmission is fully synchronous and there are no gaps between the groups or blocks. The basic data-rate
of the system is 1187.5 bit/s. Thus transmission of one group takes about 87.6 ms and about 11.4 groups are
transmitted per one second.
The services which are to be repeated most frequently, and for which a short acquisition time is required (PI, TP,
PTY), in general occupy the same fixed positions within every group.
There is no fixed rhythm of repetition of the various types of group, i.e. there is ample flexibility to interleave the
various kinds of message to suit the needs of the users at any given time.
The first four bits of the second block of every group are allocated to a four-bit code which specifies the
application of the group - group type. Groups are referred to as types 0 to 15.
For each type (0 to 15) two "versions" can be defined. The "version" is specified by the fifth bit of block 2: 0 =
version A, 1 = version B.
For all groups of version B the PI is inserted also in block 3 so this block cannot carry any other information when
version B of the group is used.
10.2.2 Remarks
One complete PS label consists of 4 groups. So one PS takes 350 ms of the transmission time. It may be found from
experience that any RDS text should be transmitted at least twice to improve reception reliability. With regard to
other services included in the RDS the repetition rate of dynamic/scrolling PS usually cannot be lower than one
second.
Checkwords and offsets are always computed and inserted automatically by the RDS encoder.
PI is always inserted automatically by the RDS encoder in block 1, and also in block 3 for version B of the group.
Due to this the block 1 is never specified when inserting any user defined group.
TP and PTY are always inserted automatically by the RDS encoder using OR method (logical sum) on the
appropriate bit positions.
62
These groups are used to identify the Open Data Application in use, on an RDS transmission. The type 3A group
conveys, to a receiver, information about which Open Data Applications are carried on a particular transmission
(AID Code) and in which groups they will be found (Application group type code).
The Application group type code and the AID Code are obligatory, while the Message field is optional and should be
set to zeros if not used.
Since the 3A groups usually carry fixed static content, they may be inserted using either the UDG1= or UDG2=
command for automatic cyclic transmission while the ODA application groups may be inserted by any command or
method (G=, UDG1=, UDG2= or UECP MEC 24 or 42).
63
Let’s show the group coding example on the popular RT+ service. We need to insert group type 3A (Application
identification for ODA) to the RDS stream pointing to the RT+ service which is – in this example - carried in group
11A.
Group 3A
Group 11A
Note:
This example is for illustration only. The RT+ feature is directly supported by the RDS encoder (see section 5.1.2).
64
10.3 Troubleshooting
The RDS encoder has been designed to make its use as easy and painless as possible. However, success depends
upon a number of settings and things working together correctly. While correcting problems is usually quite simple,
the difficulty lays in knowing where to look.
Factory default settings assure right operation after first power-on. This section of the manual is designed to assist
you in determining the cause of problems that may occur so they can be fixed quickly.
Radiotext stopped working The RT service is not included in the Group sequence.
although I’m sure that it’s Initialize the Group sequence to its default value.
7.8
enabled and entered RDS Content – System – Group
correctly. GRPSEQ=
sequence – Default, Test, Apply.
Pilot tone is fed to the unit Device Setup – Analog Control –
4.1 EXTSYNC=1
but it is not indicated. Reference Source: Auto
The unit loses time and date
3.3 Replace the on-board battery.
after power off.
The unit is not connected in loopthrough mode but the
loopthrough switch is in the LOOP position. Switch to the SIDE
The audio is distorted. 4.1 position.
There is a whistling in the 4.2.2 The RDS level considerably exceeds maximum value allowed.
audio. 4.5.1 Adjust lower RDS level. Use an FM analyzer for the best result.
Applied input of the transmitter is not suitable for RDS. Follow
the transmitter’s documentation.
4.1 The unit is connected in loopthrough mode but the loopthrough
No audio on air
4.2.2 switch is in SIDE position. Switch to the LOOP position.