DRS05# Configuration Radar Sensor Firmware - TB - en - 059101937A

Configuration of the radar sensor firmware
Technical description
Doc.No.: 4AB1937/A-en
EDP No.: 059101937A
Created: 16/12/2019 - GMA/VD
Checked: 16/12/2019 - ANI/PM
Date of issue: 20/12/2019
Applies to
Applies to
This document applies to:
DRS05/# all variants
4AB1937/A-en Technical description 20/12/2019

059101937A Configuration of the radar sensor firmware Page 2 of 29
Revision index
Revision index
Version Date Change Chapter No.1
A 16.12.2019 GMA/VD: all

First compiled
1
: The chapter numbers specified in this table always refer to the preceding
document.

Table of contents
Table of contents
Applies to ................................................................. 2
Revision index ......................................................... 3
1 General ..................................................................... 6
1.1 About this description .............................................................................. 6
2 Ancillary documents ............................................... 7

2.1 Reference documents ............................................................................... 7
3 General description of the radar sensor ............... 8

3.1 Measuring principle ................................................................................... 8
3.2 Housing variants ......................................................................................... 8
3.3 Radar sensor as a measuring device ................................................... 9
3.4 Signal processing ........................................................................................ 11
3.4.1 States ............................................................................................................... 11
4 Technical Data ......................................................... 14

4.1 Antenna modules........................................................................................ 14
4.2 Interfaces ........................................................................................................ 14
4.2.1 Serial interface ............................................................................................. 15
4.2.1.1 Serial transmission...................................................................................... 15
4.2.1.2 Protocol .......................................................................................................... 15
4.2.1.3 Status-Byte .................................................................................................... 18
4.2.2 Pulse output .................................................................................................. 20
4.2.2.1 Variant 1 ......................................................................................................... 21
4.2.2.2 Variant 2 ......................................................................................................... 22
4.2.2.3 Variant 3 ......................................................................................................... 22
4.2.2.4 Variant 4 ......................................................................................................... 22
4.2.2.5 Variant 5 ......................................................................................................... 22
4.2.2.6 Variant 6 Traditional .................................................................................. 22
4.2.2.7 Electric ............................................................................................................. 22
4.3 Power supply ................................................................................................ 22
4.3.1 Service interface RS232 ............................................................................ 23

Table of contents
5 DEUTA service concept........................................... 24
6 Appendix .................................................................. 25
6.1 Configuration options through customer-specific adaptation 25
of the firmware ............................................................................................
6.2 Protocol configuration of the serial interface.................................. 26
List of keywords ...................................................... 29

General
1 General
1.1 About this description

Copyright
This document is protected by copyright and may not be reproduced,

translated, nor stored, processed, duplicated or circulated under utilisation of
electronic systems without prior consent.
The information contained therein is confidential and may only be used to
fulfil the contractually planned purpose.
The names DEUTA REDBOX®, IconTrust®, SelectTrust®, SignalTrust® and
TouchTrust® are registered trademarks of DEUTA-WERKE GmbH. IconTrust®
and SelectTrust® are patented inventions of DEUTA-WERKE GmbH. The use
of trademarks and patents without the previous written permission of
DEUTA-WERKE GmbH is prohibited.

Ancillary documents
2 Ancillary documents
INFO
Complete documentation
The complete documentation of this product includes the following
documents:
DRS05/# all variants:
Documents No.
Instruction Handbook 4AB1771
DRS05/1#, DRS05/1S1#
Instruction Handbook 4AB1772
DRS05/2#, DRS05/2S1#
accompanying project configuration description project-

DRS05/# with SW51-### specific
EU Declaration of Conformity DRS05/1#

(included in Instruction Handbook))
EU Declaration of Conformity DRS05/2#
Installation requirements DRS05/1# Zu1376

Installation requirements DRS05/2# Zu1031
Additional documents
Abnahmeprüfzeugnis 3.1 nach EN10204 at customer´s

request
IMPORTANT
Observe ancillary documents!
To ensure smooth and safe operation, the instructions and information in
all ancillary documents must be observed!
2.1 Reference documents

The following reference documents belong to the content of this document:
DRS05-Firmware-Update-User-Guide_GB_20111130

General description of the radar sensor
3 General description of the radar sensor
3.1 Measuring principle
Two-channel Doppler radar sensors of the DRS05 series measure the vehicle
speed over ground by utilizing the Doppler effect. A Doppler radar sensor
directs a continuous microwave of fixed frequency (here: 24 GHz, 5 mW) at a
certain angle to the ground, which ideally diffusely scatters the wave. The
backscattered wave which is frequency shifted by the motion is multiplied by
the transmitted signal to form the Doppler signal corresponding to the
differential frequencies. Its spectrum contains frequencies that are
proportional to the velocity. The width of the frequency range depends on
the lobe width of the antenna, the proportionality factor on the inclination of
the lobe and also on the angular dependence of the backscattering on the
ground. With the DRS05, this influence is greatly reduced by evaluating the
Doppler signals of two antenna modules with a patented algorithm. This
improves the accuracy on changing ground conditions, while the comparison
of the Doppler signals, which are also evaluated individually at the same
time, contributes to safety.
If a microwave module fails or one of the two antennas receives a weaker
signal, the firmware (FW) switches to a special „Single-Mode-Algorithm“. This
method increases the availability of the speed signal. By the way, each
antenna module, like a two-channel incremental encoder, provides a signal
pair for determining the direction of travel (DOT).

3.2 Housing variants

The radar is available in two housing variants:
In the standard housing
Fig. 3/1: DRS05/# (example)
and in an extended housing with horizontal radome (Antenna cover: Area

through which the microwave radiation passes), so it is less affected by snow
accumulation and stone impact:
Fig. 3/2: DRS05/#S1 (example)
The beam geometry and thus the field of vision to be kept clear from
obstacles are identical. Dimensions and recommended mounting positions
can be found in the accompanying Instruction Handbook.

3.3 Radar sensor as a measuring device

Precision und correctness
The DRS05 is not an officially certified measurement device. The factory
calibration on a special moving belt results in a very small deviation between
the individual sensor devices (precision), which allows a trouble-free
exchange in case of repair. However, the correctness (trueness) in use
depends on other factors:
▪ The greatest influence has the dependency of the mounting angle. It
causes a deviation of the measured speed of 1.8 % per degree inclination
from the parallel to the rails (sign: a steeper beam leads to
underestimation).
▪ Up to 100 km/h the noise (1-σ-uncertainty) is 0,4 km/h. Beyond 100 km/h
the noise is ±0.4 %.
▪ The effect of different grounds (ballast, gravel, concrete, snow ...) is
typically <1 %.
▪ On some roads and at low speeds, a different direction of travel can cause
more than 1 % deviation, typically 0.2 %.
▪ Variations of lateral distance from the rail fastening clamps while driving
has an effect of 1 %.
One initial calibration run per project or per mounting position, respectively,
is recommended to be conducted on a representative track in order to get
the typical speed deviation that depends on the conditions mentioned
above. Precise alignment of the mounting surface parallel to the rails or,
optionally, measurement of the inclination of the mounting surface and the
corresponding correction in the superordinate system is sufficient to achieve
the same correctness of the speed estimation for every train in the same
project.
Availability:
The Doppler radar sensor sends telegrams as soon as it is switched on. In this
sense, it is available without restriction.
At standstill, the Doppler frequency reflected from the ground is 0 Hz and,
therefore, the signal is suppressed by the AC coupling in the input circuits of
the radar sensor. In the absence of a Doppler signal, the "validity bit" (Bit1,
DOTV) in the status byte is then set to zero. However, in this state the radar
sensor is sensitive to motions of even small or distant objects, who´s speed
then may be displayed, even though the train does not move. Because the
Doppler-signal-amplitude (RMS) must exceed a certain threshold to set
DOTV = 1, DOTV usually remains = 0 (strong vibration of the mounting
platform of the radar, dense flying snow, fluorescent lamps in maintenance
pits, etc.) The useful signal already dominates at low speeds (exception: jet
water in car washes etc.)

Wet ballast does not falsify the measurement results or restrict availability.
Puddles on poorly drained slab track disturb in two ways: On the one hand,
the useful signal decreases due to reduced backscattering of the microwave
(forward scattering predominates on the surface, penetrating radiation is
absorbed), on the other hand, turbulent spray on the low-frequency side of
the useful signal can produce a broadband interference signal. This influence
can be reduced if the sensor is mounted under the train at the front.
However, even then the speed signal usually only breaks in for a short time,
very rarely undetected while still signalling DOTV = 1. The following
availability applies to a mounting behind the first bogie of an ICE
The DRS05 needs an unobstructed view of the track bed. Snow on the track
is harmless, snow on the radome can obstruct visibility: The availability
decreases. With firmware variants designed for this, undetected coarse
mismeasurement under snow conditions is very rare. The compilation and
parameterization of the various monitoring algorithms that can lead to
DOTV = 0 is customer-specific. Safer versions tend to show false alarms, i.e.
DOTV = 0 while the speed estimation is correct. With firmware variants
designed for maximum safety even under snow conditions, the availability -
defined as DOTV = 1 at speed over 10 km/h - on German main lines without
winter conditions is 99.9 %.
3.4 Signal processing

Reflections from different directions, i.e. with different Doppler frequencies,
overlap according to the beam width of the antennas. Currently, Deuta has
developed two firmware families which differ in terms of smoothing und
dynamics:
▪ The historically older one has an integration element for smoothing, which
implies "v = const." as motion model. At constant acceleration, there is a
dynamic deviation that can be interpreted as a delay of approx. 180 ms;
▪ The newer family assumes a motion model "a = const.", so at constant
acceleration no dynamic deviation occurs, at jerk (da/dt) however an
overshoot or undershoot.

3.4.1 States
The following figure shows a state diagram of the radar sensor firmware:
State diagram
After the initialization the radar sensor conducts an initial estimate of the
speed (acquisition, one second). The result of this estimate is then tested
(test mode, 0.5 sec.). If the signal quality is sufficient, one of the
measurement modes (SP – intersection mode, SM40 – Single mode 40°,
SM50 – Single mode 50°) is selected (Evaluate state, shown as yellow areas in
the diagram).
If it becomes necessary while driving, the algorithm dynamically switches
between the measurement modes. This is signalled by the status byte
(Mode1, Mode0).
If the signal suddenly disappears during operation at V > 5 km/h (open
bridge, long total reflective metal surface in the track bed, a long puddle),
the radar switches to BlackOut mode, waits for the signal and makes another
initial estimate of the speed (acquisition).

BlackOut-state can also be caused by progressive snowing of the radome

(antenna coverage).
Numerous algorithms continuously monitor the signal quality. Some cause
the deletion of DOTV bits („invalidation“ of the measurement). Others
terminate the measurement mode and start acquisition.

Technical Data
4 Technical Data
4.1 Antenna modules

The modules transmit a microwave continuously and unmodulated. Power
and frequency allow worldwide approval. For further information about
approved areas of application and usage in different regions of the world,
see accompanying Instruction Handbook. To prevent crosstalk between the
antennas of a radar sensor, those two antennas of a single radar sensor are
programmed to different transmission frequencies (channels). To prevent
crosstalk between antennas of different radar sensor units, several
frequencies within the (country-specific) allowed frequency bands are used
(within the K-Band).
Country from (GHz) to (GHz)
Australia 24.000 24.250
Canada 24.075 24.175
EU 24.000 24.250
UK 24.150 24.250
USA 24.075 24.175
China
Korea
India
Japan
Russia
NOTICE
Worldwide intersection
A possibly worldwide valid intersection of 24.150 to 24.175 GHz contains
to few channels to reduce the possibility of crosstalk between different
radar sensors effectively.

Technical Data
4.2 Interfaces
The superordinate system can receive the information of the radar sensor via
two different interfaces: Telegrams via the serial interface (RS485) and a
speed-proportional frequency at the pulse output. Both interfaces are
accessible via the device socket:
Bayonet plug-in connection, 14-pin, pins,

Order of the pins: 20-27
Pins labelled with "reserved" may not be connected!
4.2.1 Serial interface

The RS485 interface of the DRS05 radars only works as a transmitter (no
reception possible and no terminating resistor installed).
4.2.1.1 Serial transmission

The transmission rate is set to 19200 bit/s. Each byte is transmitted in the
format {1 start bit, 8 data bits, no parity, 1 stop bit, LSB first}.

Technical Data
4.2.1.2 Protocol
The customer can create a protocol himself or take over one recommended
by Deuta. A list of possible protocol contents can be found in the appendix
[➙ Page 25]. It must be noted that the transmission of one byte takes
10bit/19200bit/s = 0.521ms. The length of the protocol period should be
specified sufficiently.
The HEADER marks the beginning of the binary telegram. Occasionally a
value pattern appears within the telegram equal to the HEADER.
For example:
With a HEADER=0x0CFC the value 0x0CFC may also occur in the payload of a
telegram as coding of the speed V = 30.43259 km/h. The synchronization of
the receiver is supported by check sums, see below.
Using telegrams in ASCII format, the appearance of header patterns in the

telegram payload is prevented. The telegram starts with the character "#"
(0x23, start of message, SOM) and ends with "CR" (0x13, carriage return =
end of message, EOM). In between, the HEX digits corresponding to the
telegram bytes are transmitted in ASCII, high nibbles first. This guarantees
that neither SOM nor EOM can be found in the telegram data. Disadvantage
is a more than twice the telegram length, since two ASCII characters
represent one byte.
SEQ is a circular telegram counter with a width of 1 byte. Monitoring the SEQ
allows to detect telegram losses and calculate the real time interval between
the telegrams.
The speed V is internally always calculated in km/h and output as 2-byte
number (unsigned short int, uint16_t). A value of 0xFFFF equals
V = 600 km/h. Other scalings are possible, but undesirable. The conversion
to other desired units, such as mph, should take place in the superordinate
system.
The distance travelled, which is always initialized to zero after booting, can
be distributed between two counters: S1 and S2. Each counter can have its
own scaling and overflow value. Usually S1 and S2 are not synchronized:
Overflow of S1 and corresponding increment of S2 can take place
asynchronously, with a few milliseconds difference - they should be
considered as two independent, differently scaled linear encoders. If
necessary, they can also work synchronously.
A better solution, however, would be to have an extended distance counter
that only overflows at 0xFFFF or 0xFFFFFF. With a scaling of 1cm/bit, an
overflow would only occur after 655.35 or 167772.15 meters.

Technical Data
There are currently four options for replacing unsafe distance increments
with zero increments, so the distance counters will remain on their previous
values under following conditions:
1. If V < Vmin or Evaluate = 0
2. .like 1., but also if DOTVms = 0
3. like 1., but also if DOTVms = 0 and DOTV = 0 longer than approx. 0,3s
4. like 1., but also if DOTV = 0 longer than approx. 0,3s and DOTV = 0 longer
than approx. 5s
DOTV changes more slowly than DOTVms because it arises through an
exponentially smoothing of the DOTVms signal every millisecond followed
by a threshold comparison. The time intervals of approx. 0.3s and 5s given
above are rough values. These time intervals result from the time constant of
the exponential smoothing.
Acceleration ACC is output as a 2-byte signed value (short int, int16_t). The
conversion is carried out according to the formula: Acc[m/s2] = ACC * 2-
15*600/3,6/32. Other units should be converted in the superordinate system..
PWR40 and PWR50 show relative signal strength in the channel of the
40° antenna and 50° antenna, respectively. They are also called "drive" and
take values from 0 to 100%. At PWR values above approx. 50% the
Doppler signal is saturated, because the peaks of the sinusoidal signal
exceed the permissible electrical range. The algorithm of the radar allows
large overloads, but very high PWR values indicate directed reflection from
the ground, which can mean loss of accuracy. At very low values (threshold
configurable) the sensor warns of snow on the radome. In projects with a
closed route network and strong variation of the reflectivity of the ground, a
location-dependent evaluation may be useful.
The Direction Of Travel (DOT) is determined by a separately running sub
algorithm for each channel (40° and 50°) as an analogue quantity, from -1.0
(backward) to +1.0 (forward). DOT is an important quality characteristic of
the signal - magnitudes shall be close to 0 while standstill, or fluctuate close
to 1 while driving.
When using Version-FW and Index-FW in the RS485-protocol it has to be
considered that firmware-updates of the radar may result in an update of the
superordinate system, if the superordinate system does not accept a higher
firmware-index.
The protocol transmission from the radar sensor to the superordinate system
is secured by sending a checksum of the telegram. There are currently three
common checksums to secure the telegram content:
1. The least significant byte of the sum of all bytes of the telegram (so called
Frame Check Sum, FCS) is appended to the telegram.
2. The same as with 1 but the FCS is negated (nFCS), so the sum at the
receiver must be zero.
3. CRC16_CCITT_KERMIT,
Examples:
#0F4E3E42228D1F67E54151E07F00A7712EBAEOM (ASCII-telegram)
0F FC 2F 20 AB 50 DF 27 41 B9 9D 81 83 F6 34 4B (HEX-telegram)

Technical Data
4.2.1.3 Status-Byte
The status byte is set up as follows:
Bit Variable Conten Description

ts
7 Mode1 1 40° antenna used

0 40° antenna not used
6 Mode0 1 50° antenna used

0 50° antenna not used
5 Evaluate 1 Evaluation state

0 No Evaluation state
4 Quality 1 High Quality

0 Low Quality
3 BlackOut 1 BlackOut detected

0 no BlackOut
2 TUV 1 Antenna module operational

0 Hardware failure of a transceiver
1 DOTV 1 Measurement valid

0 Measurement not valid
0 DOT 1 Forward direction of travel

0 Backward direction of travel

Technical Data
Here follows a short description of the meaning of each bit of the status
byte:
Bit 0 – Direction of travel

If bit 1 = 0 or bit 5 = 0, bit 0 has no valid information.
Direction of movement related to the direction of view of the radar. Bit 0
may flicker at standstill.
Bit 1 – Validity of the measurement

Bit 1 = 0 means that the measurement has failed, i.e. the output speed (V)
and the distance (S1, S2) must not be used. It should be emphasized that the
validity statement refers only to the last measurement in a series of
measurements within the protocol period, i.e. it is quite possible that several
or even most of the measurements were invalid and by chance the
measurement sent just then to the protocol was "valid". The internal update
of the measurement results takes place in the software every millisecond,
while the protocol period is at least 10 ms. Not only the speed, but also the
distance increment ΔS within the protocol period can be wrong. Incorrect
path increments are not treated separately in the firmware.
Modern firmware variants delete DOTV even if less than half of the
measurements between the protocols were successful (recommended for
protocol periods of more than 100ms).
Bit 2 – Hardware diagnostic

Bit 2 = 0 means that one of the two radar antennas has reported a hardware
failure. The algorithm periodically (every millisecond) monitors both TUV
signals of the antennas (Transceiver Unit Validity). Which of the two antennas
has failed can be determined from the behaviour of bits 6 and 7 - one of the
bits 6 or 7 is also deleted synchronously with the deletion of bit 2 and the
algorithm switches to the SM40° or SM50° mode (see state diagram).
States with TUV = 0 should be considered as a pre-failure state by the
superordinate system, the appropriate actions should be initiated (For
example: Replace the sensor at the next opportunity).
If two antennas fail, the radar sensor changes to "mute mode", i.e. all
interfaces stop transmitting.
Bit 3 – BlackOut
Bit 3 = 1 means that the algorithm receives too weak signals from both
antennas at an estimated speed of V > 5 km/h.
Bit 4 – Quality
Bit 4 = 1 means that the speed is obtained from strong signal of both
antennas.

Technical Data
Bit 5 – Evaluate
Bit 5 = 1 means that the algorithm evaluates the signals from the antennas
and calculates the speed estimation. If bit 5 = 0, the V and S1, S2 values are
invalid.
Bit 6 und Bit 7 – measurement mode

State Bit 6 = 0 and Bit 7 = 0 does not mean failure of the radar, but only that
none of the two antennas delivers a qualitatively sufficient signal. In this state
the measurements are not valid.
Single bits of the status byte present only eight of 24 internal status bits to
the user. Logical correlations and dynamic development of the algorithm-
internal quality features can lead to apparently absurd bit combinations in
the status byte (e.g. BlackOut and High-Quality, or Evaluate with Mode1 = 0
and Mode 0 = 0, etc.). For the developer, however, they are not absurd, but
carry valuable information. For an automatic generation of the decision
"valid - invalid" we recommend the implementation of the following decision
rule:
Logic for the validity of the signals

Technical Data
4.2.2 Pulse output

Some of our customers use only the pulse output, some use only the serial
interface and some both. Thus it is recommended by Deuta to not use the
pulse output, but the serial interface instead, since detailed information
about the condition of the radar sensor is transmitted here.
If nevertheless the pulse output is to be used, it can be configured at the
factory. It should be noted that the output frequency at the project-specific
maximum speed is not too high, because the rising edge of a pulse depends
on the cable length and the design of the customer interface.
For example:
15 kHz at 300 km/h result in a scaling of 50 Hz per km/h as
SpeedResolution corresponding to 5.56 mm per pulse as
DistanceResolution.
Therefore:
▪ SpeedResolution = 1000 / 3.6 / DistanceResolution
The scaling also determines the at low speeds relevant pulse period (= delay
at the customer´s frequency acquisition), in the example above 100 ms at the
bottom radar acquisition limit of Vmin = 0,2 km/h.
The absolute lowest signal frequency is Fmin ≈ 1.2 Hz. Of course 0 Hz
(constant level) can be used for signalling particular states.
Customers who only use the pulse output of the radar miss important
information which is transmitted in telegrams (see appendix [➙ Page 25]):
▪ RMS values and their changes allow at least a rough monitoring of the
road: If it is known for a given road that the mean RMS values do not fall
below e.g. 7% anywhere, then vDRS should be used with caution for
significantly lower values, even if the radar sensor signals "Valid" and
"High Quality";
▪ Direction (DOTH and DOTL). The drop below certain specified thresholds
is signalled by the deletion of DOTV in the status byte.
▪ The status-Byte (see chapter configuration [➙ Page 18]) contains eight
binary signals.
Some customers have recognized this and requested signalling of some

events/states via the pulse output. This has resulted in 6 configuration
variants of the pulse output so far:

Technical Data
4.2.2.1 Variant 1
At V < Vmin 0 Hz is output. If Evaluate = 0, the frequency is held for
Tfreez milliseconds, then (regardless of validity) it is proportional to the speed
again.
4.2.2.2 Variant 2
If Evaluate = 0, in TEST-mode (see State Machine), at V < Vslow or if bit DOTV
is longer than approx. 300 ms Null, FNOK (VNOK) is output. Otherwise, the
frequency is proportional to the speed. If VNOK is defined as < Vmin,
FNOK (VNOK) = 0 Hz will be output.
4.2.2.3 Variant 3
Like variant 2 with the following addition: If an antenna reports hardware
failure (TUV =0 in status-byte), Fimp = 0 Hz will be output every minute for
one second („silence second“). During this VNOK should be > Vmin.
4.2.2.4 Variant 4
Very similar to variant 3, only the "silence second" is started after reaching
the state {V < Vmin, RmsH und RmsL < BlackOut threshold, smoothing value
of bit DOTV < DOTV-threshold}. This means that at standstill FNOK is replaced
by 0 Hz for one second.
4.2.2.5 Variant 5
V < Vslow (configurable) outputs 0 Hz. If Evaluate = 0 a fixed frequency
FNOK (VNOK) is output. Otherwise, the frequency is proportional to the speed.
4.2.2.6 Variant 6 Traditional

At V < Vmin = 0.2 km/h 0 Hz is output. If Evaluate = 0, Fmax is output.
Otherwise, the frequency is proportional to the speed.
4.2.2.7 Electric
The user can decide whether a pull-up resistor is mounted in the radar
housing or in the customer interface (see accompanying Instruction
Handbook).

Technical Data
4.3 Power supply

DEUTA radar sensors contain a wide range power supply
(Ub = 15 bis 150 VDC). Since all interfaces are galvanically isolated from Ub,
a direct supply from the vehicle battery is permitted.
4.3.1 Service interface RS232
IMPORTANT
The RS232 interface must not be connected during regular operation of the
vehicle! This interface is used exclusively for service purposes for personnel
specially trained and certified by DEUTA.

DEUTA service concept
5 DEUTA service concept

For a customer firmware update the following is needed:
1. Programming adapter WK 1628-4 with cable
2. Service program for Laptop
3. New device dependent firmware binary files (LOD-files)
These items can be provided by DEUTA upon request.

To operate the service program a detailed description is provided
(see chapter Reference documents [➙ Page 7]).
NOTICE
Programming adapter WK 1628-4
The WK 1628-4 programming adapter must not be connected during
regular operation of the vehicle!
The WK1628-4 is a custom-built evaluation kit destined for professionals to

be used solely at research and development facilities for such purposes.
Due to international custom regulations the programming adapter

WK1628-4 is only within the EU provided with led-gel-batteries . Outside
the EU an external supply of 20 to 30 VDC maximum shall be connected to
the programming adapter (connections are provided).

Appendix
6 Appendix
6.1 Configuration options through customer-specific adaptation of the firmware

Selection of the firmware properties:
No. Property Example Choice
General:
1 FW-group 1 (availability, no snow, gravel…) ✓
2 FW group 2 (reliability, false alarms possible...)
3 FW family 1 (180ms delay in information propagation from antenna ✓

to interfaces)
4 FW family 2 (no delay, prediction of the measured value)
Pulse output:
5 Integrated pull-up resistor ✓
6 SpeedResolution, Hz/km/h 7,27
7 DistanceResolution,mm/pulse
8 Impulse behavior (1,2…6) 3
8.1 Vslow [km/h] 2.0
8.2 Vnok [km/h] 0.5
8.3 Tfreez [ms] n.a
Serial interface:
9 Protocol period, ms 50
10 protocol coding (HEX,ASCII) HEX
11 protocol protection (FCS,nFCS,CRC16) nFCS
Distance counter 1
12 Resolution, unit per bit 1 cm
13 Overflow at 1 km
Distance counter 2
14 Resolution, unit per bit 1 km
15 Overflow at 1000 km

Appendix
No. Property Example Choice
Distance counter 1 and 2
16 Increment synchronous/asynchronous to overflow of S1 asynchron
17 Increment control set (see chapter 4.3.2.2: 1, 2, 3 or 4) 1
Status-Byte
18 Bit DOTV = 0 if most measurements failed within protocol period ✓
Serially output speed during Evaluate = 0
19 V should be (Vmax, VNOK, 0,...) [km/h]. 0
Serially output speed during test mode
20 V should be (Vmax, VNOK, 0,…, V) [km/h] 0

Appendix
6.2 Protocol configuration of the serial interface

Variables available for output via serial interface:
Variable meaning Format
HEADER_H Number of following bytes uint8
HEADER_L Constant (traditional 0xFC) uint8
ID Project-specific identification of the telegram uint8
# SOM; Start of Message, 0x23 uint8
CR EOF, End of Message, 0x13 uint8
SEQ revolving telegram counter (0…255) uint8
V Speed, 2-byte value, scaled to 600 km/h, always positive uint16
S1 Distance counter S1, 2- or 3-byte value uint16

uint24
S2 Distance counter S2, 2- or 3-byte value uint16

uint24
Acc* Acceleration derived from V changes, m/s2, with sign int16
PWR40 Signal strength, 40° antenna uint8

uint16
f3.5
PWR50 Signal strength, 50° antenna uint8

uint16
f3.5
DOTH Analogue value Direction Of Travel, 40° antenna int8
DOTL Analogue value Direction Of Travel, 50° antenna int8
DOTHL Analog value of both DOTs in compressed form spez.
STATUS Status-Byte uint8
Version_FW FW-number uint8
Index_FW FW-index (ASCII-Code) uint8
FCS Frame Check Summ, Sum of all bytes in the telegram uint8
nFCS Negated FCS uint8
CRC16 Cyclic Redundancy Check, CCIT_Kermit uint16
*) only available for FW variants of the 2nd family

Appendix
Example of a protocol:
Byte-No. Symbol meaning coding
1 0D 0x0D bytes follow fixed, Header
2 FC Radar sensor identifier fixed, Header
3 SEQ protocol counter 0…255 revolving
4-5 V speed, km/h FFFF ≈ 600 km/h
6-7 S1 Distance counter S1 1 Bit ≈ 10 cm
8-9 S2 Distance counter S2 1 Bit ≈ 1 km
10 PWR40 Signal strength, 40° antenna FF ≈ 100% of range
11 PWR50 Signal strength, 50° antenna FF ≈ 100% of range
12 STATUS Status-Byte see table in chapter

4.2.2.1
13-14 CRC16 CRC16 CCITT-Kermit

List of keywords
List of keywords
A N
Acquisition state 12 Noise 10
Areas of application 14
P
Availability 10
Precision 10
B
Programming adapter 24
BlackOut mode 12 Protocol 16
protocol transmission 17
C
pull-up resistor 22
configuration variants 21 Pulse output 21
Copyright 6
R
Correctness 10
Revision index 3
D
S
dependency of the mounting angle 10
device socket 15 serial interface 21
Dynamics 11 Service program 24
Single mode 12
E
Single-Mode-Algorithm 8
Evaluate state 12 smoothing 11
Status-Bytes 19
F
factory calibration 10 T
Firmware properties 25 transmission frequencies 14
Firmware update 24 Transmission rate 15
I W
initialization 12 wide range power supply 23
intersection mode 12
Invalidation 13
L
Led-gel-batteries 24
LOD-files 24
M
Measuring principle 8
Microwave module 8


DRS05# Configuration Radar Sensor Firmware - TB - en - 059101937A

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DRS05# Configuration Radar Sensor Firmware - TB - en - 059101937A

Uploaded by

Copyright:

Available Formats

Configuration of the radar sensor firmware

DRS05/# all variants

4AB1937/A-en Technical description 20/12/2019

A 16.12.2019 GMA/VD: all

4AB1937/A-en Technical description 20/12/2019

Revision index ......................................................... 3

2 Ancillary documents ............................................... 7

3 General description of the radar sensor ............... 8

4 Technical Data ......................................................... 14

4AB1937/A-en Technical description 20/12/2019

5 DEUTA service concept........................................... 24

List of keywords ...................................................... 29

4AB1937/A-en Technical description 20/12/2019

1.1 About this description

This document is protected by copyright and may not be reproduced,

4AB1937/A-en Technical description 20/12/2019

DRS05/# all variants:

accompanying project configuration description project-

EU Declaration of Conformity DRS05/1#

Installation requirements DRS05/1# Zu1376

Abnahmeprüfzeugnis 3.1 nach EN10204 at customer´s

2.1 Reference documents

4AB1937/A-en Technical description 20/12/2019

3 General description of the radar sensor

3.1 Measuring principle

4AB1937/A-en Technical description 20/12/2019

3.2 Housing variants

Fig. 3/1: DRS05/# (example)

and in an extended housing with horizontal radome (Antenna cover: Area

Fig. 3/2: DRS05/#S1 (example)

4AB1937/A-en Technical description 20/12/2019

3.3 Radar sensor as a measuring device

4AB1937/A-en Technical description 20/12/2019

3.4 Signal processing

4AB1937/A-en Technical description 20/12/2019

4AB1937/A-en Technical description 20/12/2019

BlackOut-state can also be caused by progressive snowing of the radome

4AB1937/A-en Technical description 20/12/2019

4.1 Antenna modules

Country from (GHz) to (GHz)

Australia 24.000 24.250

Canada 24.075 24.175

USA 24.075 24.175

4AB1937/A-en Technical description 20/12/2019

Bayonet plug-in connection, 14-pin, pins,

Pins labelled with "reserved" may not be connected!

4.2.1 Serial interface

4.2.1.1 Serial transmission

4AB1937/A-en Technical description 20/12/2019

Using telegrams in ASCII format, the appearance of header patterns in the

4AB1937/A-en Technical description 20/12/2019

4AB1937/A-en Technical description 20/12/2019

Bit Variable Conten Description

7 Mode1 1 40° antenna used

6 Mode0 1 50° antenna used

5 Evaluate 1 Evaluation state

4 Quality 1 High Quality

3 BlackOut 1 BlackOut detected

2 TUV 1 Antenna module operational

1 DOTV 1 Measurement valid

0 DOT 1 Forward direction of travel

4AB1937/A-en Technical description 20/12/2019

Bit 0 – Direction of travel