Contents

1.1. How to start

Note: Information about how to install and connect the RDS encoder are placed in the Technical manual.

First steps

1. In the case of USB connection install the USB driver first. Pure RS232 connection requires no driver.
2. Make sure the RDS encoder is connected and powered.
3. Run the Magic RDS application.
4. Open the Preferences and set up the connection parameters. If the RDS encoder is connected via USB and was recognized correctly in Windows, you may find/change the COM port number in Windows Control Panels - System - Hardware - Device Manager.
5. Close the Preferences. You should see "Connected" or "Opened" in the status bar. Now you are ready. The settings are saved automatically.
6. Configure the basic RDS settings like PI, PS etc. You will find them on the sheets Program and System. Then click Store. For beginners there's a very useful configuration wizard under menu item Help.
7. The status bar at the bottom of the window shows whether the data was sent successfully. If Communication Error! is shown, check the connection to the RDS encoder, its power supply and that the correct COM port is selected in the Preferences dialogue box.

When attempting to set-up a unit that was already placed in operation before, the user should apply the initialization first (Options - Special - Initialize) and if required, set the unit address to 0 (Options - Special - Assign unit address: Disable, Override).

Language selection

Several language files are distributed with the application. To select the language choose Options - Language. During first settings it's recommended to use original language (English).

Running in demo mode

The demo mode is useful when touching the application first time or for proper adjusting of external text sources before putting them on-air. It does not require the RDS encoder to be connected. To enter the demo mode, go to Options - Preferences - Connection type and select Demo only. The status bar will indicate "Not connected". To see an effect of any operation and for better understanding how the communication works open the Command window in Options - Special.

When attempting to control the RDS encoder, make sure the application is not running in demo mode! Otherwise any changes will take no effect on air. To check this, go to Options - Preferences - Connection type and select appropriate communication port.

Contents

1.1.1. System requirements

• Windows operating system, version 95 or later
• PIRA32-based RDS encoder
• One serial COM port or USB to serial adapter or ethernet connection to the remote site

Tip: In Windows Vista/Seven it is recommended to turn off UAC (User Account Control) in Windows Control panel.

Contents

1.2. Application main window

The application main window consists of

• Title bar - Shows application name and current RDS file name.
• Main menu
• Toolbar - Contains commonly used options, preset buttons and Store All / Send All / Receive All buttons.
• On Air display - Shows content of the most important text services currently on air from last operation. These services are: default PS name, Dynamic PS 1, Radiotext 1, RT+ indicator.
• RDS control sheets - Affect the RDS data content.
• Status bar

Generally said the RDS data are saved into RDS files (*.rds), the application settings are saved into the ini file placed in the application folder.

Tip: After setting basic static parameters, choose File - Save as Default. This "template" will be used always when you click File - New.

Control buttons:

Tip: Click on the Sheets button to show or hide RDS control sheets. Unused sheets may be hidden. You may also exclude them from data sending in Preferences - Buttons.

Contents

1.3. RDS control sheets

Note: Information about how to set basic RDS services are placed in the Technical manual.

1.3.1. Program

Contents

1.3.2. Dynamic PS

Dynamic PS is defined as a using of the PS name for showing of sequential information. Up to 255 characters long text message can be displayed on receiver instead of static PS name.
Dynamic PS 1 is typically used for commercials, news and "on-air" texts. Dynamic PS 2 is typically used for fixed texts from the Messages bank. For the first steps it's recommended to decide for either the DPS1 (permanent on-line connection to the RDS encoder) or the DPS2 (placing the RDS encoder on a site without on-line connection).
Four display modes (0-3) are available depending on configuration in Text Setup.

The user can insert the text directly from a keyboard or configure the External text source for Dynamic PS 1 or Message switching for Dynamic PS 2.

Tip: (for mode 0 or 2) Fill %HH-MM%% to show real time.
Tip: Fill %%TIME%% to show time of the text insert.

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/scrolling PS properly for reasons that lie entirely on their side.

Contents

1.3.3. Radiotext

Radiotext 1 is typically used for commercials, news and "on-air" texts. Radiotext 2 is typically used for fixed texts from the Messages bank. For the first steps it's recommended to decide for one of the RT1 or RT2.

The user can insert the text directly from a keyboard or configure the External text source for Radiotext 1 or Message switching for Radiotext 2.

Contents

1.3.4. Messages

The Messages bank can contain up to 99 text messages, each up to 255 characters long, stored in the RDS encoder. The messages are numbered for use as Dynamic PS 2 or Radiotext 2 source.
Messages with Dynamic PS 2 or Radiotext 2 box checked will be cyclically used if corresponding text service source is set to Automatic Message Switching. This feature works stand-alone without no more support from PC and it's recommended especially when the RDS encoder will be placed on a site without online connection. Where on-line connection is available, it's preferred to use the external text sources for inserting and rotating any text messages like commercials etc.

Tip: By clicking on Load button you may load the messages from a text file. Each line will represent one message.

Important! The messages are called by their number, their text must be stored before.

Contents

1.3.5. Enhanced other networks information (EON)

The EON feature is used to update the information stored in a receiver about program services other than the one received. Alternative frequencies, the PS name, Traffic Program and Traffic Announcement identification as well as Program Type and Program Item Number information can be transmitted for each other service. The relation to the corresponding program is established by means of the relevant Program Identification.
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 PIRA32 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. See the Technical manual for more details.

Contents

1.3.6. Data groups

You may add up to 16 RDS groups with any content to the RDS stream. This block is repeatedly transmitted as UDG1 (symbol X) or UDG2 (symbol Y).
Choose RDS Group type and insert the content using any coding you like (HEX, DEC, BIN or ASCII). Then click on Insert button.
This feature is intended mainly for advanced users or development purposes. This way you may simply insert user defined groups with fixed content, typically 3A (AID for ODA). See the Technical manual for more details.

Contents

1.3.7. System

Contents

2.1. Preferences

Tip: Why two types of "frames" are used in Preferences dialog window? The flat frames contain general settings, the "3D" frames contain settings assigned to currently opened RDS file.

Contents

2.1.1. General

Contents

2.1.2. Local settings

Contents

2.1.3. Buttons

Contents

2.1.4. Misc.

Contents

2.1.5. Task scheduler

Simple task scheduler that allows to run applications, open rds files, exit the Magic RDS and reboot/shutdown the PC in weekly program. The local PC time is decisive.
Please follow the differences between the Task scheduler and the RDS scheduling. Each of these two scheduling features has specific purpose.

These keywords are also accepted in the task line:

Contents

2.2.  Text Setup

Configures the Dynamic PS and Radiotext features. Open this dialogue window before using these services. Confirm the settings by Store button to take effect.

Contents

2.2.1. Dynamic PS Setup

Contents

2.2.2. Dynamic PS Mode

Contents

2.2.3. Radiotext Setup

Contents

2.3.  External Text

The External Text is one of the main features making the Magic RDS unrivalled among others. It allows complete dynamic control of the RDS encoder from external text sources (mainly broadcast automation text output, HTML and RSS content etc.). Up to 16 text sources may be defined. Each text source can be assigned to some RDS service.

Important: Before attempting to use the External text tool consider which RDS service you will use for showing the text (Dynamic PS or Radiotext or both). Configure the Dynamic PS 1 and/or Radiotext 1 and confirm the settings by Store button.
Using the dynamic (scrolling) PS is restricted in some countries. The manufacturer is not responsible for incompetent use of this feature.

Tip: Why two types of "frames" are used in External Text dialog window? The flat frames contain general settings, the "3D" frames contain settings assigned to currently opened RDS file.

Contents

2.3.1. Dynamic PS 1, Radiotext 1

Contents

2.3.2. Text sources

* marked items are obligatory

Note: Leave unused fields empty.

Important: One text source may be assigned to more services (like Dynamic PS 1, Radiotext 1, Text conditions etc.). But if there are more text sources in use, it's preferred to establish a separate set of text sources for each service (even though there will be more text sources reading the same file or location). This way allows to control additional differences between the services and ensures that values like 'Keep in cache for' will work exactly as expected.

Contents

2.3.3. Text replacing

A strong tool supporting basic scripting elements. May be used for simple characters, words and sentences replacing or for text filtering. See Examples. Click on right mouse button to insert or delete a row and to insert or delete a command.

Text processing scheme:
Reading from the source -> Text cutting -> Text replacing -> (Adding prefix/suffix)

Contents

2.3.4. Text conditions

A great tool which allows to control any RDS service (for example TA) using the "now-playing" file produced by your broadcast automation system. If any pre-defined keyword is found in the file, corresponding command is sent to the RDS encoder. See Examples. Assign a text source first. A source that reads "all lines" in sequence cannot be assigned for the Text conditions tool.

The Text replacing is not used for this feature (the comparison is made before the Text replacing).

It is preferable to use separate text source for this feature rather than share it with Dynamic PS or Radiotext. This allows to set individual properties although the source file or location may be the same. Especially the 'Keep in cache for' value should be set to 0 when used with the Text conditions to allow immediate response when the source file changes.

Contents

2.3.5. RSS support

Contents

2.3.6. Send HTTP query

Delighted with the text processing features and want to use it also for web publishing? This is a bonus feature which allows you to put the text from any text source to your web site. It uses the GET method. Consult this feature with your web admin.

Contents

2.3.7. RT+ (Radiotext Plus)

The RT+ 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. The RT+ module implemented in this application supports song artist and song title elements. These elements anyway carried in the Radiotext, are identified by their class code, length and location within the Radiotext. The receiver must be equipped with the RT+ function (also called "tagging") to take advantage of this feature.

Before attempting to use this feature make sure the Radiotext 1 is properly read from an external text source, showed on the receiver's display and contains the song information expected.

Contents

2.4.  RDS scheduling

There are two methods of RDS Scheduling implemented in the system: Stand-alone and PC-dependent.
The Stand-alone scheduling is provided directly by the PIRA32 unit. Once set, it works with no more support from the MagicRDS control application. It's recommended only for RDS units with battery included for real time clock backup.
The PC-dependent scheduling implementation is older, provided mainly for backward compatibility. It requires the PC to be connected and MagicRDS running. The Task scheduler may be used instead.
Both methods are provided for use (choose preferred method in Preferences - General). It's recommended to disable the unused method.

Contents

Stand-alone method

One of the strong tools that doesn't have any equivalent in competitive products. Allows you to schedule text messages, program type names and any other RDS services and settings in a weekly program. The RDS encoder's internal time is decisive.

Individual scheduled items are listed on the left. You may insert or edit the item using the tools on the right. You may choose between Messages scheduling or any other command.

Important! The text messages are called by their number only, their text must be stored before. Use the Store button in the Messages sheet.

Contents

PC-dependent method

Allows you to schedule text messages and program type names in weekly program.

Individual scheduled items are listed on the left. You may insert or edit the item using the tools on the right.

Important! The text messages are called by their number only, their text must be stored before. Use the Store button on the Messages sheet.

Contents

2.5. COM port speed change

Specifies the COM port speed. When changed, a store command is sent to the RDS encoder on the new speed immediately to test if the communication is running OK. Otherwise the speed will be set back to its previous value during following minute. This prevents setting an incorrect speed not supported by the communication channel that can result in connection lost.

Note: If you wish to drive the RDS encoder directly from a broadcast automation system, find out the baudrate that is used by the broadcast automation system for communicating with the RDS encoder. If this parameter is not clear from the documentation and no baudrate control is provided in the broadcast automation system, configure the RDS encoder for the default value (2400 bps). Then exit the Magic RDS application. If you use the Magic RDS and External Text feature, you may choose any speed. The PIRA32 ASCII control protocol is as tiny as possible so you may choose some of the lower speed options.

Contents

3.1. Program set change

Specifies the program set. RDS services in selected program set are transmitted by the RDS encoder and can be modified and stored into EEPROM memory. If external program switch selects the program, most of store operations are not allowed. For advanced users only. Default value is Program set 1.

Contents

3.2. Special settings

Menu: Options - Special...

Contents

3.2.1. Group sequence

Defines the RDS group sequence. Allows the user to control the group order and adjust repetition rate of individual RDS services. Max. 24 items are allowed. The Group statistics indicates a percentage share in the RDS data stream.

Services, which are not placed in the sequence, are disabled regardless of their individual settings. Services, which are placed in the sequence and are disabled by their individual settings, are ignored (skipped).

It's a good practice to assure that at least one '0' is present in each consecutive 6 symbols. Take into consideration that RDS does not know anything like empty groups or delays between groups. There must be still some groups sent to the output. The Group sequence does not affect: group 4A (CT), groups inserted using the G command, groups inserted using the UECP free format and TMC elements.

Contents

3.2.2. Addressing

The Addressing feature allows connecting more units to one COM port and controlling them independently. See the Technical manual for more details. RDS encoder with an address in range of 1 to 254 is not active after reset and can be controlled only if it’s selected in Preferences - Misc. - Address. Only selected units accept commands. If a unit is selected, other units are unselected immediately. Unselected units "listen" on the port for selection of their address.

Note: If only one unit is connected to the port and has address 0 or 255 (default), there is no need to take the addressing into consideration and user may simply ignore it.

Note: The Magic RDS application is not intended for driving large networks containing a lot of different locations. Thus only the Encoder address is applied when communicating with the RDS encoders. The Site address is always 0 (any site will respond).

Contents

3.2.3. Import/Export

File - Import... / File - Export...

This option allows to share Text Sources and Text Replacing settings between the users or to make templates for these features.

For example, to send the Text Replacing settings to your friend, choose File - Export, select the Text Replacing in the dialogue box, type the file name and click Save.

Contents

3.2.4. Online PS Window

Read - Online PS Window

Shows actual Program Service name that is being sent by the RDS encoder. The PS showed is an output of internal real-time RDS decoder so it shows also Dynamic PS and may be affected also by user defined groups.

Note: Depending on the data connection baudrate and workload the online PS viewer may sometimes freeze for a short time. This behaviour does not affect the real data sent to your listerens. Remember that your RDS encoder always sends PS strings correctly and continuously to your listeners.

Contents

3.3. Advanced usage

Launching from command line

These examples illustrate use of the command line option. Launching some of the line runs the program (if it is not already running) and opens the filename.rds file:
magicrds.exe filename.rds
magicrds.exe C:\Magicrds\filename.rds
magicrds.exe "C:\Program Files\Magicrds\filename.rds"
Similar sequence is also launched when you directly execute the *.rds file or if you drag the *.rds file and drop it on the magicrds.exe program file.

If the Magic RDS is already running, you may send any command to the RDS encoder using the command line, for example:
magicrds.exe send:TA=1
magicrds.exe send:PS=TOP FM

RDS files specification

For advanced users only. Understanding of the RDS files specification allows you to use extended functions of this program, but it is not needed for common use. The RDS file (*.rds) structure is very flexible and it is open for adding new features in future. The structure stems from INI files. You will see it well if you open some RDS file in Windows Notepad (for example, select File - Edit RDS file from the main menu).
When the RDS file is opened in the Magic RDS, the "Clear" key is important. If the Clear value is 1 (Clear=1), all RDS services are cleared (set to their default values) before reading the RDS file. If the Clear value is 0 (Clear=0), only the RDS services mentioned in the file are changed.
Opening customised RDS files using the Task Scheduler may make amazing automation effects.

Multiple instances

The Magic RDS can be launched in multiple instances. Following rules must be met:
1. Each instance must be placed in another folder on the disk.
2. Each folder must contain a file multi.set. Length and content of this file is optional and has no effect.

Contents

3.4. Examples

Text replacing

For example, set Dynamic PS or Radiotext to be read from text file generated by your broadcast system. Fill the following to the Text replacing grid:

Characters "é" and "&" can't be displayed on most receivers, so we replace them by characters, that can be displayed.
In normal conditions currently playing song title is showed as Dynamic PS or Radiotext. If a jingle is playing and its name starts with "jingle", no text is showed. If a speaker is on air and background sound name starts with "Background 1", corresponding text is showed.

%C% command means that the replacing will be case-sensitive.
%S% command means that the text must start with expression filled.
%SC% command means that the text must start with expression filled. The matching will be case-sensitive.
Commands %C%, %S% and %SC% cannot be used together.

%CLEAR% command means that whole text (not only the expression found) will be deleted and replaced by the text written behind the command. No prefix is added in this case.
%TERMINATE% command terminates the text on a first occurrence position of the expression. Any text behind the expression found (and including it) will be deleted.

%END% command means that next rows are ignored if the expression is found.

Text Conditions

Check corresponding text source file/window, fill the following to the Text Conditions grid and enable the feature:

Any item from the 'If found' column must be a part of the audio file name/tag in your broadcast automation system.

The matching is not case-sensitive.

How to change the Text sources in a predefined day and time?

Showing the example for Dynamic PS 1. Switching off Source 1 and switching on Source 2.

1. Create a text (in Notepad or similar) with the following content:
   
   [DPS1]
   Src1Enabled=0
   Src2Enabled=1
     
2. Save it to a file named switch.rds (any name is possible).
     
3. Open the Task Scheduler card and add the file to any task line. Specify the Times.

Contents

3.5. Related documents

Contents

3.6. Contact and support

E-mail: mail@pira.cz
Website: http://www.pira.cz/rds/

Some RDS related feature is missing? Please send your suggestions or bug reports. It will help us to create new improved version of this application!
Check the website from time to time for the software and firmware updates.

Warranty and restrictions

The software is provided as is, without warranty of any kind. The author shall not be liable for damages of any kind. Use of the software indicates you agree to this. You are prohibited from renting, modifying or reverse engineering of the software. The software can only be used to drive the "PIRA32" based RDS encoders, including 3rd party products that may carry another brand name. Using the application to drive any other equipment is illegal. The software may be distributed in original form with no more restrictions.

Contents

Revision 2011-10-18
Copyright (C) Pira CZ 1999-2011