Golden Eagle

Managing
Open Data Applications

messages
Advanced configuration
Date : 2011/05/03
audemat WorldCast Systems Group

web: www.audemat.com - e-mail: contact@audemat.com
ODA Advanced Configuration – 05/2011
CONTENTS
1. INTRODUCTION ..................................................................................................................................3
2. PRIORITY TRANSMISSION ................................................................................................................4
3. OUTSIDE OF THE GROUP SEQUENCE: THE GROUP 3A ..............................................................5
3.1. The Application Group type code ................................................................................................5
3.2. 16 message bits for the actual ODA ............................................................................................6
3.3. The Applications Identification (AID) code...................................................................................6
4. ODA FREE FORMAT GROUP (MESSAGE BITS)............................................................................10
4.1. MEC 42: What is the priority of the message? ..........................................................................10
4.2. MEC 42: What is the transmission mode for this message? .....................................................11
4.2.1. Burst mode ...........................................................................................................................11
4.2.2. Spinning Wheel mode ..........................................................................................................12
4.3. MEC 42: Which buffer should be used? ....................................................................................13
5. MEC 43 RELATIVE PRIORITY GROUP SEQUENCE ......................................................................14
6. DO YOU STILL NEED MORE INFORMATION? ...............................................................................15
6.1. Example 1: Transmission of TMC information with an FMB80 - configuration with ASCII
commands .................................................................................................................................15
6.2. Example 2: Transmission of RT+ information with an FMB80 - configuration with UECP ........17
7. REFERENCES ...................................................................................................................................19
Page 2
Head Office : Parc d’activites Kennedy - 20, avenue Neil Armstrong – F-33700 Bordeaux-Merignac (France)
Tel +33 (0)5 57 928 928 – Fax +33 (0)5 57 928 929 – contact@audemat.com – www.audemat.com
1. INTRODUCTION
Open Data Applications are a very effective and flexible way for adding additional applications to an
RDS service. A number of different ODAs may exist on any service, subject to capacity. ODAs may be
transmitted constantly, or only when required (e.g. an application which provides an alert in the case of
extreme weather etc.). The Open Data Applications feature is conveyed in a number of allocated
groups in an RDS transmission. The groups allocated are indicated by the use of type 3A group which
is used to identify to a receiver the data application in use in accordance with the registration details in
the Open Data Applications Directory.
The UECP defines, for Open Data Application (ODA) messages, different settings that can be
combined in order to transmit the data of your ODA as needed.
The procedures describes in this document are applicable to all Audemat RDS encoders with ODA
capabilities.
Page 3
2. PRIORITY TRANSMISSION
Whether using an Audemat FMB80, FMX480, Digiplexer (Full RDS) or NEXT FM (Full RDS) it is
mandatory to use UECP to send dynamic data for your ODA.
The ODA configuration can be done via UECP and / or ASCII commands or using the remote RDS
application depending on the equipment used.
Audemat encoders organize the transmission of the data according to the priorities defined in the RDS
standard IEC EN 62106:2000.
Higher Priority transmission
Group 4A
Group 1A
Group 13A
Group 14B
Group 15B
ODA Groups with Immediate priority
Group sequence (Group sequence can include ODA groups with priority)
ODA groups with Extremely Urgent priority
ODA groups with Normal priority Spinning wheel
Queued data Burst Mode
Cyclic data
Lower priority transmission

4A groups (Clock Time) have the highest priority in the RDS system as they are used to synchronize
other data. Groups defined in the group sequence containing cyclic data will have the lowest priority in
transmission.
A group sent with normal priority will be added to the specified free-format group buffer for
transmission according to the group sequence and allocation of RDS resources. A group sent with
"extremely urgent" priority will bypass the free-format buffer and will be sent as soon as possible
according to the group sequence and resource allocation. A group sent for "immediate" transmission is
transmitted immediately regardless of the group sequence, but will not interrupt the higher priority
groups (1A, 4A…).
The relative priority setting for different groups can also be configured in order to explicitly define the
relative priority for groups competing to be transmitted
Page 4
3. OUTSIDE OF THE GROUP SEQUENCE: THE GROUP 3A
To work properly, an ODA must be defined in the encoder and the receiver. This means that it is
necessary for an RDS group to transmit one and only one application, as defined by its Application
Identifier (AID). An ODA may use type A and/or type B groups, however it cannot be designed to
operate with a specific group type. The specific group type used by the ODA in any particular
transmission is indicated in the AID, carried in type 3A groups. This group sends information to the
receiver about which ODAs are carried on a particular signal, and in which groups they will be found.
Type 3A groups includes three elements:
The Application Group type code used by that application,
16 message bits for the actual ODA
The Applications Identification (AID) code.
Applications which actively utilize both, type A and B groups are signaled using two type 3A groups.
3.1. The Application Group type code

The Application Group type code indicates the group type used on a particular signal, to carry the
specified ODA. Group types not shown are not available for ODA use.
Group Application Group

Description
Type Type Code
00000 Special meaning, not carried in associated group
3B 00111 Available unconditionally
5A 01010 Available when not used for Transparent Data Channels
5B 01011 Available when not used for Transparent Data Channels
6A 01100 Available when not used for In House applications
6B 01101 Available when not used for In House applications
7A 01110 Available when not used for Radio Paging
8A 10000 Available when not used for Traffic Message Channel
9A 10010 Available when not used for Emergency Warning System
11A 10110 Available unconditionally
12A 11000 Available unconditionally
13A 11010 Available when not used for Enhanced Radio Paging
11111 Special meaning, temporary data fault (Encoder status)
This supplements information carried in the type 1A group and permits groups specified in this
standard for EWS, TDC, IH, RP and TMC to be re-allocated when these features are not used.
Page 5
For each group type indicated by the Application Group Type codes of a particular transmission, only
one application may be identified as the current user of the channel.
3.2. 16 message bits for the actual ODA

The message bits can be used by the application to transmit information. This is totally dependent on
the transmitted application itself.
For example:
TMC (the Traffic Message Channel), which is actually an ODA, utilizes this part of the 3A group to
transmit information (LTN; AFI; M; I; N; R; U; or SID, etc.)
Block 2
B0
Block 1 TP Block 3 Block 4

Y15 Y14 Y13 Y12 Y11‐Y06 Y05 Y04 Y03 Y02 Y01 Y00
0 0 X X LTN AFI M I N R U
Variant MGS
code

2 bit 2 bit 6 bit 2 bit 2 bit 2 bit

Y15 Y14 Y13‐ Y12 Y11‐Y06 Y05‐Y04 Y03‐Y02 Y01‐Y00
Where M = 0 :
0 1 G SID rfu rfu rfu
Where M = 1 : Y15 Y14 Y13‐ Y12 Y11‐Y06 Y05‐Y04 Y03‐Y02 Y01‐Y00
0 1 G SID Ta Tw Td
Diagram: RDS type 3a group structure, RDS-TMC carrying system information
Likewise RT+ (Radiotext Plus), another ODA, uses this part of the message to transmit the CB flag,
SCB and template number.
Diagram: Bit allocation for group 3A (message bits and AID)
The information that will be transmitted using these 16 message bits in the type 3A groups can be
found in the definition (standard) for the ODA.
3.3. The Applications Identification (AID) code

The AID feature indicates that a particular ODA is being carried in a transmission. It determines which
software handler a receiver needs to use to decode the information.
Each application can have unique requirements for transmission of its associated AID, in terms of
repetition rate and timing. These requirements must be detailed in the respective ODA specification.
The specification must also detail the AID signaling requirements for the times when an application
assumes or loses the use of a group type. Some applications may not allow reconfiguration in this
way.
Page 6
Using UECP this information is configured with a MEC (Message Element Code) – specifically, MEC
40.
MEC 40 enables to configure the group type used for a specific AID and in the same time it enables
data transmissions for Group 3A
Message Name: ODA Configuration and Short Message Command
Message Element Code: 40
Function: to set the ODA Application Group Type Code and AID, in type 3A groups. The command
also edits the Type 3A group message bits in Block 3. The command also initializes (by disabling)
ODA Data access rights on all ports for the configured AID (see MEC 47).
Format:
MSB LSB
MEC 40
MED 00...1B Application Group Type Code
MED 00..FF AID (MSB)
MED 00..FF AID (LSB)
MED 00..03 Bits 1..0 Buffer configuration
MED 20..FF Message (MSB)
MED 20..FF Message (LSB)
MED 20..FF ODA data input timeout, where: 0=off and

1-255 minutes can be signaled
The data is divided into several units; each called a MED (Message Element Data).
Bits 1 and 0 of the fourth MED control the buffer configuration.
Bits 1 and 0 of the 4th MED are coded as follows:
Bit 1 Bit 0 Buffer configuration
0 0 Information transmitted once only and removed after transmission
0 1 Reserved
1 0 For cyclic transmission, type 3A groups are added to the specified
buffer
1 1 Remove all type 3A groups from the specified Application Group type
buffer
Page 7
L With the FMB80 / FMX480, an AID can also be modified using the console or Telnet mode with
the command “ODA.gv.AID=”, “ODA.gv.MSG=” and “ODA.gv.MSG2=” where gv is the group
value (3A, etc)
With the Digiplexer or NEXT FM the AIDs are configured using the remote application software or
the front panel application.
Type 3A Group will use all non-null AIDs to transmit data (AID and group type) alternatively
In the case of multiple ODAs that must be transmitted by the encoder, it may be necessary to indicate
the groups (or applications) to send and to set a rate proportion, to allocate the RDS resources as
needed to the different applications. This can be handled with the ODA identification group usage
sequence.
Type 3A groups are transmitted according to the group sequence.
Within the group sequence the Application Group Type code to be transmitted is determined by the
usage sequence.
If no usage sequence is used, each programmed Application Group Type code is transmitted
once.
Page 8
This information is configured using UECP, with MEC 41.
MSB LSB
MEC 41
DSN 00...FF
MEL 00..FC
MED 00..1B First Application Group Type code

Bits 7..5: Set to 0
Bits 4..1: Group type
Bit 0: Group version, 0=A, 1=B
.
.
.
MED 00..1B nth Application Group Type code
L With the FMB80 / FMX480, this can also be modified in the console or telnet mode with the
command “SEQ3A=”.
With the Digiplexer or NEXT FM, use the remote application software or the front panel
application.
We have seen here how to set up the encoder to transmit an Open Data Application (ODA). Now it is
necessary to receive the data to be transmitted and place it in the associated encoder buffers.
Page 9
4. ODA FREE FORMAT GROUP (MESSAGE BITS)
RDS encoders provide various data buffer to store the data to be transmitted. It is necessary to
indicate to the encoder where and how to transmit data for each specific group type (ODA).
The only way to configure the information is with UECP commands.
Using UECP this information is configured with MEC 41
Message Name: ODA Free-format group (Message bits)
Message Element Code: 42
Function: to add a group to the free-format buffer for that Application Group Type Code
Format:
MSB LSB
MEC 42
MED 00..7F Configuration

Bits 7..6: Set to 0
Bits 5..4: Priority setting
Bits 3..2: Mode selection
Bit 1..0: Buffer configuration
MED 00..1F Block 2, 5 bits
MED 00..FF Block 3 MSB
MED 00..FF Block 3 LSB
MED 00..FF Block 4 MSB
MED 00..FF Block 4 LSB
The second MED of this message contains the instructions for the encoder.
What is the priority of the message?
What is the transmission mode to use for this message?
Which buffer should be used?
4.1. MEC 42: What is the priority of the message?

A message sent with “Normal” priority will be inserted into the data stream according to the group
sequence and its position in the buffer (FIFO).
A group sent with “Extremely urgent” priority will be inserted as soon as possible according to the
group sequence. (First out position in the buffer).
A group with “immediate” priority will be transmitted immediately, regardless of the group sequence,
but respecting the priorities set in the encoder, unless the ODA priority group sequence has been
configured.
Page 10
The relative priority setting for different groups can also be configured in order to explicitly define the
relative priority for groups competing to be transmitted outside of the group sequence (See MEC 43).
In MEC 42, bits 4 and 5 of the second MED carry the priority setting.
Bit 1 Bit 0 Priority setting

0 0 Normal
0 1 Extremely urgent Valid only if the buffer
1 0 Immediate configuration is 00
1 1 Reserved
Bits 6 – 7 of the second MED are set to zero.
4.2. MEC 42: What is the transmission mode for this message?
RDS defines 2 methods of transmission for the data:
Burst mode
Spinning Wheel mode
One or the other mode is specified using Bits 2 and 3 of the second MED of MEC 42:
4.2.1. Burst mode
This mode enables ODA free-format groups to be transmitted with a predetermined number of
repetitions and inter-group spacing.
The number of repetitions ranges from 0 to 16 times (according to relative priority).
The spacing indicates the minimum number of other groups between two ODA free-format groups with
this Application Group Type code.
Using UECP this mode can be configured with MEC 44.
MSB LSB
MEC 44
MED 07...1B Bits 7..6: Application Group Type Code
MED 00..7F Bits 7..4: Number of repetitions

Bits 3..0: Spacing
L With the FMB80 / FMX480, this can also be modified in console or telnet mode with the command
“ODA.gv.REPEAT=” and “ODA.gv.SPACE=”.
With a Digiplexer or NEXT FM, use the remote application software or the front panel application.
(Repetition and Space settings)
Page 11
4.2.2. Spinning Wheel mode

The Spinning Wheel technique is based on the following concepts:
Divide the minute into a number (integer) of time slots.
Split each of these time slots into two parts. A first part (activity time, Ta), during which ODA
groups may be inserted into the data stream, and a second part (window time, Tw), during
which no ODA groups may be inserted into the data stream. Actually, only the Window time
(Tw) will be configured, this defines the activity time (Ta), by default.
Between the start of each minute (as indicated in the RDS-data stream by the appearance of
the type 4A group, which must be transmitted to use this technique) and the start of the first
time slot, a delay is possible (delay time, Td).
The insertion of ODA groups is governed by the following rules:

No ODA groups may start outside the activity window.
An ODA group may be completed outside the activity time.
Ta, Tw, Td have to be multiples of one second, with 60 s/(Ta + Tw) = n (where n: integer > 0).
The actual values of these parameters should be assumed to be either default values or be
coded into the system information.
Using UECP this mode can be configured with MEC 45.
MSB LSB
MEC 45
MED 01..3C Number of time slots
MED 00..3C Window time (in seconds)
MED 00..3B Delay time, relative to the beginning of the

minute (in seconds)
The number of time slots should be chosen so that each time slot can contain a number of seconds
that is a whole number, not a fraction.
command “ODA.gv.NB=”, “ODA.gv.WINDOW=” and “ODA.gv.DELAY=”.
With a Digiplexer or NEXT FM use the remote application software or the front panel application.
(Nb Time slot, Window (sec) and Delay (sec) settings)
Page 12
4.3. MEC 42: Which buffer should be used?

This depends on whether the information is to be repeated or not.
Bit 1 Bit 0 Buffer configuration
0 0 Information transmitted once only and removed
after transmission
0 1 Reserved
1 0 For cyclic transmission, free-format information
sets are added to the specified buffer
1 1 Remove all free-format information sets from the
specified free-format buffer
Note that if it is decided to save the data in a cyclic buffer it will be stored until a command has been
sent to clear all information. (Bit1=1 and Bit0=1)
Page 13
5. MEC 43 RELATIVE PRIORITY GROUP SEQUENCE
It sets the relative priority level for groups transmitted using the ODA free-format command with
“immediate” priority
If no ODA Relative Priority Group Sequence is specified, the priority of groups sent with the ODA free-
format command and “immediate” priority is lower than the priorities of other groups, specified in the
standard.
Setting the ODA Relative Priority Group Sequence enables the relative priority of groups to be
changed.
Using UECP this mode can be configured with MEC 43:
MSB LSB
MEC 43
MEL 00..FD
MED 00..1F Highest relative priority group

Bits 7..5: Set to 0
Bits 4..1: Group type
Bit 0: Group version, 0=A, 1=B
.
.
.
MED 00..1F Lowest relative priority group
command “ODA.RPGS=”.
With a Digiplexer or NEXT FM use the remote application software or the front panel application.
Page 14
6. DO YOU STILL NEED MORE INFORMATION?
Let’s look at some examples.
6.1. Example 1: Transmission of TMC information with an FMB80 - configuration with

ASCII commands
As mentioned earlier only the ODA configuration can be done with ASCII commands.
The dynamic data for any ODA must be sent to the encoder using the appropriate UECP format frame
(MEC30 for TMC).
We will assume that the RDS signal generation and communication with the encoder are correctly
configured.
Enter the following commands in the console mode or with remote Telnet access.
GS=0a,0a,0a,3a,8a Transmits the 3A group and the predefined ODA group for TMC (8A)
ODA.8A.AID = CD46 Configures the AID for TMC (CD46)
ODA.8A.MSG=052F Defines the 16 bit message (i.e:052F) included in 3A group
SEQ3A=8A Sets the ODA group usage sequence
The encoder is now configured to transmit any valid TMC data (MEC 30) received on any
communication port. The UECP frame will also include priority and selection mode data, it is not
necessary to specify this in the encoder.
Example of a valid MEC 30 frame:
MSB LSB
MEC 30
MEL 01..FB
MED 00..FF Bits 7: 0=Normal, 1 =Extremely urgent

Bits 6..5: Buffer configuration
Bits 4..1: Number of transmission 1-15
Bit 0: Set to zero
MED 00..1F Block 2 5 bits of first TMC message
MED 00..FF Block 3 MSB of first TMC message
MED 00..FF Block 3 LSB of first TMC message
MED 00..FF Block 4 MSB of first TMC message
MED 00..FF Block 4 LSB of first TMC message
.
.
.
MED 00..FF Block 4 MSB of nth TMC message
Page 15
The complete frame (valid for all encoders) would look like this:
FE000000083006020A0AD430A549CBFF
This frame specifies that the information should be sent in normal mode (bit7=0).
This information is transmitted 3 times and then removed from the buffer (bit 6,5 =0 And bits 4-1
=0011).
It transmits the following information:
PTY T F DP
X04 X03 X02 X01 X00
0 A
0 1 0 1 0
0 1 2
D +/- Extent Event

Y15 Y14 Y13 Y12 Y11 Y10 Y09 Y08 Y07 Y06 Y05 Y04 Y03 Y02 Y01 Y00
0 A D 4
0 0 0 0 1 0 1 0 1 1 0 1 0 1 0 0
0 + 1 724
LOCATION
Z15 Z14 Z13 Z12 Z11 Z10 Z09 Z08 Z07 Z06 Z05 Z04 Z03 Z02 Z01 Z00
3 0 A 5
0 0 1 1 0 0 0 0 1 0 1 0 0 1 0 1
12453
Note this is only an example. Event and location numbers are generated randomly. Thus you can see
no results except on an authorized TMC receiver. But the raw data can be decoded and seen with an
RDS decoder (such as the Audemat Modulation Analyzer, Audemat FM-MC4, Audemat Navigator
100).
Page 16
6.2. Example 2: Transmission of RT+ information with an FMB80 - configuration with

UECP
We will assume that the RDS signal generation and communication with the encoder are correctly
configured.
Assign a group in the encoder for transmission of the RT+ ODA information.
Let’s choose group 11A to transmit the application. The RT+ AID is 4BD7, no message is necessary
(There is no specific template to download) this information is stored in the cyclic transmission buffer.
MEC 40
Group type code 16
AID 4B
AID D7
Buffer 02
Message 00
Message 00
Timeout 00
The complete UECP frame (valid for all encoders) would look like this:
FE0000000840164BD702000000269BFF
Define the ODA usage sequence to use only 11A groups.
MEC 41
DSN 00
MEL 01
1st group type 2C
UECP: FE000000044100012C8930FF
Set the burst mode configuration.
In this example, 3 repetitions, with no minimum spacing between repetitions.
MEC 44
Group type 16
MED 30
UECP: FE00000003441630CB06FF
Page 17
Send (cyclically) a message, with immediate priority, in burst mode:
MEC 42
Group Type 16
Buffer 26
MED 08
MED 24
MED 0C
MED 00
MED 00
UECP: FE0000000842162608240C00008FCBFF
The message received will be
Diagram: Coding of the message bits of the application group
Block B Block C Block D

08 24 0C 00 00
0 1 0 0 0 0 0 1 0 0 1 0 0 0 0 0 0 1 1 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
T R RT content RT content Length marker
Start marker 1 Length marker 1 Start marker 2
b b marker 1 marker 2 2
Item toggle Bit = 0

Item running bit=1
RT content Type 1= 000001 (Code 1= Title)
Start Marker 1= 001000 (8th Character)
Length marker 1 = 000110 (6 characters length)
Page 18
7. REFERENCES
Universal Encoder Communication Protocol version 7.5 - February 2010

The new RDS IEC 62106:2009 standard
EN ISO 14819-1:2002 RDS TMC
Radio text plus (RT+) Specification (Version2.1) RDS Forum document R06/040_1
Page 19

Golden Eagle

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Golden Eagle

Hochgeladen von

Copyright:

Verfügbare Formate

Managing

Open Data Applications

audemat WorldCast Systems Group

Lower priority transmission

3. OUTSIDE OF THE GROUP SEQUENCE: THE GROUP 3A

3.1. The Application Group type code

Group Application Group

3.2. 16 message bits for the actual ODA

2 bit 2 bit 6 bit 2 bit 2 bit 2 bit

Diagram: RDS type 3a group structure, RDS-TMC carrying system information

Diagram: Bit allocation for group 3A (message bits and AID)

3.3. The Applications Identification (AID) code

MED 00...1B Application Group Type Code

MED 00..FF AID (MSB)

MED 00..FF AID (LSB)

MED 00..03 Bits 1..0 Buffer configuration

MED 20..FF Message (MSB)

MED 20..FF Message (LSB)

MED 20..FF ODA data input timeout, where: 0=off and

This information is configured using UECP, with MEC 41.

MED 00..1B First Application Group Type code

MED 00..1B nth Application Group Type code

4. ODA FREE FORMAT GROUP (MESSAGE BITS)

MED 07...1B Application Group Type Code

MED 00..7F Configuration

MED 00..FF Block 3 MSB

MED 00..FF Block 3 LSB

MED 00..FF Block 4 MSB

MED 00..FF Block 4 LSB

4.1. MEC 42: What is the priority of the message?

Bit 1 Bit 0 Priority setting

MED 07...1B Bits 7..6: Application Group Type Code

MED 00..7F Bits 7..4: Number of repetitions

4.2.2. Spinning Wheel mode

The insertion of ODA groups is governed by the following rules:

MED 07...1B Application Group Type Code

MED 01..3C Number of time slots

MED 00..3C Window time (in seconds)

MED 00..3B Delay time, relative to the beginning of the

4.3. MEC 42: Which buffer should be used?

5. MEC 43 RELATIVE PRIORITY GROUP SEQUENCE

MED 00..1F Highest relative priority group

MED 00..1F Lowest relative priority group

6. DO YOU STILL NEED MORE INFORMATION?

Let’s look at some examples.

6.1. Example 1: Transmission of TMC information with an FMB80 - configuration with

MED 00..FF Bits 7: 0=Normal, 1 =Extremely urgent

MED 00..FF Block 3 MSB of first TMC message

MED 00..FF Block 3 LSB of first TMC message

MED 00..FF Block 4 MSB of first TMC message

MED 00..FF Block 4 LSB of first TMC message

MED 00..FF Block 4 MSB of nth TMC message

D +/- Extent Event

6.2. Example 2: Transmission of RT+ information with an FMB80 - configuration with

Send (cyclically) a message, with immediate priority, in burst mode:

Diagram: Coding of the message bits of the application group

Block B Block C Block D

Item toggle Bit = 0

Universal Encoder Communication Protocol version 7.5 - February 2010

Das könnte Ihnen auch gefallen