================================
Questionnaire on a RDS Project
================================
Thank you for your interest in our RDS products and services.
Esslinger has been providing qualified broadcast engineering support
since the mid 1990s, and has been able to help many reputated
companies in solving technical challenges.
So, why not benefit from our know-how?
Please consider this questionnaire as a simple instrument to start
the communication between you and us. We have introduced it to
learn more about your requirements, enabling us to propose an
efficient solution that is tailored for your needs.
If you are worried about disclosing details, just use the questions
as a guideline and get directly in touch with us. Contact addresses
are listed at the end of this document.
What you also should know:
* The questionnaire was designed to cover the requirements of
different RDS project types. Some of the questions may not
affect your specific project. Just leave them open.
* When you return this form you do so without entering any obligation.
Your feedback will solely be used by us for informational purposes
and does not start any contractual relationships.
* Esslinger Broadcast Engineering takes the protection of your personal
data very seriously. When we process the data that you supply with
this form, we always observe the rules laid down in the applicable
data protection laws. The information that you provide will be
treated confidentially. Neither part of your data will be disclosed
publicly by us, nor transferred to any third parties without your
consent.
* Following, both the "RDS" (IEC 62106) and the U.S. "RBDS" system
are referenced using the expression "RDS" for better legibility.
In cases where the differences between the two systems are
relevant we will point this out at the particular question.
==========================================================================
Here we go...
==========================================================================
1.) It would be helpful to us if you self-estimate your RDS knowledge.
(Of course, please feel free to skip this question.
Your responses help us in finding the right level of
technical communication. You may wish also to consider
the knowledge of your colleagues who might be involved
in your RDS project.)
Please rate like this: 1=poor, 2=quite okay, 3=good
If some questions are not relevant to your specific project,
leave them open.
a) Knowledge of the general features that RDS offers -->
b) How RDS basically works -->
c) Details of the different applications that RDS
offers (e.g. Alternative frequencies, EON, TMC) -->
d) The features a RDS receiver typically provides -->
e) The do's and dont's with RDS -->
f) Components required for an RDS receiver -->
g) Open Data Applications -->
h) Transmission errors and RDS error correction issues -->
i) The RDS bitstream structure -->
j) RDS encoders / transmission equipment -->
k) Other: __________________________ -->
--------------------------------------------------------------------------
2.) What is the current state of your project?
[ ] Brainstorming
[ ] Design
[ ] Implementation
[ ] Re-design
When would you need project support (date)?
______________________________________________
--------------------------------------------------------------------------
3.) Please outline your RDS project:
a) [ ] RDS development project, reception side
(e.g. receiver development)
b) [ ] We wish to add RDS functionality to an existing product
c) [ ] RDS proof of concept / RDS R+D
d) [ ] RDS development project, transmission side
e) [ ] RDS Open data application project
f) [ ] RDS business consulting project
Could you please describe your project
in a few words:
__________________________________________________
__________________________________________________
If you only ticked d-f above, please directly proceed
with question 8.
--------------------------------------------------------------------------
4.) For which RDS features do you need support?
[ ] Only for the basic ones (e.g. Programme service name, PI code, ...)
[ ] Simple data features (e.g. RadioText, Clock time and date, ...)
[ ] RDS features required for a fixed or portable receiver
[ ] RDS features required for an automotive receiver
[ ] RDS features required for a high-end device
[ ] Traffic message channel (TMC)
[ ] We consider special data features (e.g. open data applications
for closed user groups or for special receivers).
[ ] Other: _____________________________________________
--------------------------------------------------------------------------
5.) Only if your project has to do with RDS reception:
The overall RDS reception chain consists of several building blocks
(antenna, tuner, RDS demodulator, CPU, display, ...)
For which blocks did you already FIND a solution?
[ ] Tuner
[ ] RDS demodulator (chip)
[ ] CPU type that will perform RDS processing
[ ] The CPU will be used exclusively for RDS decoding
[ ] The CPU must perform further tasks besides decoding RDS
[ ] The general software architecture for the system
[ ] How the RDS part integrates into the system
[ ] Other: ___________________________________________
Are there any components (hardware, software) that definitely
MUST be used (e.g. a specific CPU type or a specific
RDS demodulator chip)?
[ ] No
[ ] Yes, the following one(s):
__________________________________________________________
--------------------------------------------------------------------------
6.) Only if your project has to do with RDS reception and you
consider to implement our RDS decoding software modules:
Please tell us something about your RDS target system.
a) [ ] Embedded system
(e.g. a CPU-equipped standalone receiver, an industrial system, ...)
b) [ ] Other
Please specify:
_____________________________________________________
c) [ ] PC (also: PC-based devices, Car PC, Handhelds, ...)
d) [ ] The receiver uses a dual-tuner concept
(two independent tuners, each one providing RDS data)
If you ticked a) or b), please estimate the approximate
free resources that can be used for RDS processing
(if the values are already known):
Amount of available RAM for RDS decoding: _______ kB
Amount of available program memory
(Flash, ROM) for RDS decoding: _______ kB
Maximum average CPU load that may be
caused by RDS processing: _______ %
CPU category [ ] 8 bit [ ] 16 bit [ ] 32 bit [ ] Yet unknown
CPU family: _________________________________
CPU speed: _____ MHz
Have you already tried a C compiler for this CPU? [ ] Yes [ ] No
--------------------------------------------------------------------------
7.) Did you already decode RDS data using our RDS decoder for Windows?
(The software can be downloaded from www.esslinger.de/downloads.
RDSDec is based upon our ANSI-C RDS decoder library, so by
trying RDSDec you will get a first imagination how the
RDS decoder library works and which features it provides.)
[ ] No
[ ] Yes
[ ] I tried but I could not make it work
--------------------------------------------------------------------------
8.) What do you have available for RDS works?
[ ] RDS signal on the air (from a radio station)
[ ] RDS signal generator
[ ] FM test transmitter
[ ] With RDS features
[ ] Without RDS features
[ ] RDS receiver
[ ] RDS "clock" and "data" signal is accessible (internally)
[ ] I don't know if the receiver provides RDS "clock" and "data"
[ ] Reference receivers / other RDS software products
[ ] We would be interested in lending these devices
from Esslinger:
_______________________________________________________
--------------------------------------------------------------------------
9.) In the USA, displaying the RDS logo on products is
subject to special certification.
[ ] We don't need support for U.S. certification
[ ] We would be interested in Esslinger's support
for U.S. certification
--------------------------------------------------------------------------
10.) Please feel free to let us know your specific questions
or your comments:
--------------------------------------------------------------------------
11.) (You've almost made it!)
Whom do you wish us to contact in response to your enquiry?
Name:
Company:
Position:
eMail address:
Phone aumber:
[ ] I think a meeting could be helpful to clear some questions.
==========================================================================
Please return the completed form to one of our contacts listed below.
==========================================================================
Esslinger Broadcast Engineering
Espenstrasse 20a 77656 Offenburg, Germany
Phone: +49-(0)781-990 79 79 Fax: +49-(0)781-990 79 85
rds@esslinger.de Internet: www.esslinger.de
RDS customer support engineer:
Mr. Michael Theben mt@esslinger.de
Direct phone: +49-(0)781-968 21 49
--------------------------------------------------------------------------
Form Rev. 1.7
(C) Copyright Esslinger Broadcast Engineering 1997-2008
--------------------------------------------------------------------------
END OF DOCUMENT