Display DDU 10
ManualVersion 1.1 09/09/2024

Content

Content
1 Preparation ......................................................................................................................................................................

5

2 Warnings and Safety Instructions .................................................................................................................................

6

3 Onboard Network Concept ............................................................................................................................................

7

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

8

4.1

Upgrades .................................................................................................................................................................................................................

12

5 Mechanical Drawing .......................................................................................................................................................

13

6 System Configuration Tool RaceCon ............................................................................................................................

14

7 First Steps.........................................................................................................................................................................

15

7.1

Starting the unit....................................................................................................................................................................................................

15

7.2

Connecting the unit to RaceCon....................................................................................................................................................................

15

7.3

Setting up a new RaceCon Project ................................................................................................................................................................

16

7.4

Feature activation.................................................................................................................................................................................................

21

7.5

First display configuration (Quick Start)......................................................................................................................................................

23

7.6

First recording (Quick Start) .............................................................................................................................................................................

25

7.7

Set date and time.................................................................................................................................................................................................

28

7.8

Color indication.....................................................................................................................................................................................................

29

7.9

Assign the Mounting Location........................................................................................................................................................................

31

8 Project Configuration .....................................................................................................................................................

33

8.1

Math Channels ......................................................................................................................................................................................................

33

8.2

Conditional Functions.........................................................................................................................................................................................

34

8.3

Conditional Channels..........................................................................................................................................................................................

36

8.4

Condition Combination .....................................................................................................................................................................................

38

8.5

Display Switch Module.......................................................................................................................................................................................

40

8.6

Timer Module ........................................................................................................................................................................................................

41

8.7

GPS Trigger Module............................................................................................................................................................................................

41

8.8

CPU Load Limits....................................................................................................................................................................................................

43

9 Display Configuration.....................................................................................................................................................

44

9.1

Display page setup ..............................................................................................................................................................................................

44

9.2

Element Configuration .......................................................................................................................................................................................

45

9.3

Types of display elements.................................................................................................................................................................................

50

9.4

Context menu ........................................................................................................................................................................................................

55

9.5

LEDs ...........................................................................................................................................................................................................................

56

9.6

Page select / Display brightness / LED brightness..................................................................................................................................

60

9.7

Alarms.......................................................................................................................................................................................................................

71

9.8

User Interface Menu UIM..................................................................................................................................................................................

79

9.9

ABS Diagnostic ......................................................................................................................................................................................................

81

10 CAN Configuration..........................................................................................................................................................

83

10.1 CAN Bus Trivia .......................................................................................................................................................................................................

83

10.2 CAN input................................................................................................................................................................................................................

84

10.3 CAN output.............................................................................................................................................................................................................

90

10.4 Multiplexer..............................................................................................................................................................................................................

93

11 Export and Import in RaceCon ......................................................................................................................................

96

11.1 Export in RaceCon................................................................................................................................................................................................

96

ii / cc

DDU_10_Manual

Bosch Motorsport

Content

11.2 Import in RaceCon ...............................................................................................................................................................................................

96

12 Analog and Frequency Inputs........................................................................................................................................

98

12.1 Analog inputs.........................................................................................................................................................................................................

98

12.2 Configuring inputs...............................................................................................................................................................................................

99

12.3 Configuring computed sources ......................................................................................................................................................................

112

12.4 Hysteresis ................................................................................................................................................................................................................

113

13 Online Measurement and Calibration...........................................................................................................................

117

13.1 Setting up an online measurement...............................................................................................................................................................

117

13.2 Online calibration of measurement channels ...........................................................................................................................................

122

13.3 Online calibration of multipoint adjustment channels..........................................................................................................................

124

14 Error Memory ..................................................................................................................................................................

126

14.1 Error memory representation in RaceCon..................................................................................................................................................

126

14.2 Information on errors available from the error memory ......................................................................................................................

128

14.3 Analog Input Diagnosis .....................................................................................................................................................................................

132

15 Recording .........................................................................................................................................................................

134

15.1 Features....................................................................................................................................................................................................................

134

15.2 Configuration of recordings.............................................................................................................................................................................

134

15.3 Event logging.........................................................................................................................................................................................................

141

15.4 Data Logger and USB recording ....................................................................................................................................................................

142

15.5 USB recording........................................................................................................................................................................................................

142

16 Ambient Light Sensor .....................................................................................................................................................

147

17 Lap Trigger.......................................................................................................................................................................

149

17.1 Lap trigger (timing beacon) .............................................................................................................................................................................

149

17.2 Counting outing/laps/fragments ...................................................................................................................................................................

155

17.3 Lap timing ...............................................................................................................................................................................................................

156

17.4 Segment timing ....................................................................................................................................................................................................

158

17.5 Countdown timer .................................................................................................................................................................................................

160

17.6 Automatic GPS Track Detection .....................................................................................................................................................................

161

17.7 Predicted Laptime ................................................................................................................................................................................................

162

18 GPS Sensor .......................................................................................................................................................................

164

18.1 GPS (Global Positioning System)....................................................................................................................................................................

164

18.2 Protocol....................................................................................................................................................................................................................

164

18.3 Sensor recommendation ...................................................................................................................................................................................

165

18.4 Measurement labels............................................................................................................................................................................................

167

18.5 GPS troubleshooting...........................................................................................................................................................................................

168

19 Telemetry System LTE 65 ...............................................................................................................................................

170

19.1 Software setup.......................................................................................................................................................................................................

170

19.2 Telemetry channels with special functionality ..........................................................................................................................................

171

19.3 Setting up car in WDServer ..............................................................................................................................................................................

172

19.4 Loading the telemetry data..............................................................................................................................................................................

176

20 Firmware ..........................................................................................................................................................................

177

20.1 Firmware and configuration.............................................................................................................................................................................

177

20.2 Firmware update...................................................................................................................................................................................................

177

Bosch Motorsport

iii / cc

DDU_10_ManualContent

21 Cloning the Unit ..............................................................................................................................................................

178

22 Fuel Consumption Calculation.......................................................................................................................................

179

22.1 Setting up fuel consumption calculation and tank management.....................................................................................................

179

22.2 Fuel consumption diagnosis/counter reset ...............................................................................................................................................

180

23 RaceCon Shortcuts ..........................................................................................................................................................

182

24 Legal .................................................................................................................................................................................

183

24.1 Legal Restrictions of Sale ..................................................................................................................................................................................

183

24.2 Open Source Software (OSS) Declaration for the Display....................................................................................................................

183

24.3 REACH Statement.................................................................................................................................................................................................

198

25 Disposal ............................................................................................................................................................................

199

iv / cc

DDU_10_Manual

Bosch MotorsportPreparation | 1

1 Preparation
Use the DDU 10 only as intended in this manual. Any maintenance or repair must be performed by authorized and qualified personnel approved by Bosch Motorsport.
Operation of the DDU 10 is only certified with the combinations and accessories that are
specified in this manual. The use of variant combinations, accessories and other devices
outside the scope of this manual are only permitted when they have been determined tobe compliant from a performance and safety standpoint by a representative from Bosch
Motorsport.
Read the manual carefully and follow the application hints step by step. Do not hesitate tocontact us, contact data can be found on the last page of this document.

Important information on Electromagnetic Conformity
To avoid unwanted interference with the environment (people, animals, electronic devices)or unwanted harm to the environment, it is mandatory that the user of the DDU 10 carries
out an appropriate analysis to determine the electromagnetic interaction the DDU 10 may
have with its individual installation environment.

Disclaimer
Due to continuous enhancements, we reserve the rights to change any illustrations, photos, and technical data within this manual.
Please retain this manual for your records.

Note
In this document, many screenshots are created by way of example for a display. Pleaseconsider this and replace the product names with the name of your device.

Bosch Motorsport

DDU_10_Manual

5 / 200

2 | Warnings and Safety Instructions

2 Warnings and Safety Instructions
The classification of the warnings and safety instructions is carried out by the respective
signal word (Danger, Warning, Caution) next to the warning symbol.

DangerDANGER

Nature and source of danger
Consequences
Warning of death or serious physical injury, which are sure to occur if ignored.

WarningWARNING

Nature and source of danger
Consequences
Warning of death or serious injury, which can occur if this is not observed.

CautionCAUTION

Nature and source of danger
Consequences
Warning of slight bodily injury in case of Disregard.

NoticeNOTICE

Nature and source of danger
Consequences
Warning of damage to equipment in case of ignoring.

6 / 200

DDU_10_Manual

Bosch Motorsport

Onboard Network Concept | 3

3 Onboard Network Concept
Please ensure that you have a good ground installation. That means:– A ground that has a solid, low resistance connection to the negative battery terminal– Connection should be free from dirt, grease, paint, anodizing, etc.
– Use large diameter wire
– More metal-to-metal contact is better!
The following notations for power signals are used:– KL 15 is a switched battery rail controlled by the IGN-switch– KL 30 is an unswitched battery positive rail (same as battery positive terminal)– KL 31 is an unswitched ground rail (same as battery negative terminal)
Be careful to observe current limits of wires and connector pins!

IGNSwitch
UBATStar connection(term30)

switched pos. terminal
positive terminal
Electric Loads
Main
Switch

KL15

PC

KL30

Bosch Motorsportdiagnosis connector

DeviceµC

LS_SWITCH1…4GKL31UBATT_FUSE
GND_Starpoint
ChassisSENSPWR10

Star connection
dig. sensors(e.g. wheelspeed)

As short as
possible

LS_GND_1
LS_GND_2

SENSPWR5

ANA_IN(xx)Engine_GND

activeSensor

ANA_IN(xy)SENSGND

NTC
Sensor

Note
This schematic is not device specific. Please see the section Technical Data for the specifications of your device.

Bosch Motorsport

DDU_10_Manual

7 / 200

4 | Technical Data

4 Technical Data
The Display DDU 10 integrates a programmable full colour dashboard display with a data
logging system for motorsport applications. Additional input devices can be connected
via Ethernet, CAN buses, and RS 232.
Data Analysis Software WinDarab is available free of charge as “WinDarab V7 free” on our
website. A basic logging function of 100 channels with recording of 50 ms (4 GB) is always
included. The logger can be upgraded to full logging performance (max. 1 ms). In addition, a 2nd logging partition of 4 GB can be activated.
With the DDU 10, a completely new library of graphical elements for the individual designof display pages was implemented and an all-new user interface menu has been developed for the device. A configurable input activates the menu structure and the user canreset for example laptime, fuel consumption and many more, without having to connect a
laptop to the DDU. The user can also install own graphics, pictures etc. on the 12 freely
configurable display pages. For quick data transfer from the car, e.g. during pit stop, data
copy to a USB stick is available as an option.
Display– 7” graphic color display– 12 user configurable display pages– 20 multicolor freely configurable (RGB) LEDs

Resolution

800 x 480 pixel

Supported image file formats

PNG, BMP, JPG, GIF

Processor

667 MHz Dual Core

Converters

10 kHz 12 bit AD converters with digital
low pass filter

Internal power source

Li/Ion capacitor

Configurable math channels
User configurable CAN in/out messages

Up to 256 IDs (128 in and out)

Online data compression
Internal logger– 4 GB memory on Recording 1 enabled– 100 channels enabled– 50 ms Sampling rate enabled– FULL_LOG_1 (1,500 channels/1 kHz sampling rate on Recording 1) optional– FULL_LOG_2 (4 GB memory on Recording 2) optional
Logging rates– Usage of all features: 600 kB/s
– Primary logging use case: 800 kB/s
– Logging data download rate: up to 4 MB/s
Ambient light sensor

Mechanical Data

8 / 200Size

198 x 134 x 35 mm

Weight875 g

Protection classification

IP67

DDU_10_Manual

Bosch MotorsportTechnical Data | 4

Operating temperature internal-20 to 85°C

Max. vibration

Vibration profile 1 (see Downloads orbosch-motorsport.com)

Electrical Data
Supply voltage

6 to 18 V

Current consumption (w/o sensor supply)

2 A (at 12 V)

Inputs4 x analog channels, plus 12 optional
0 to 5 V input range
12 bit resolution
Switchable pull up resistors for all analog inputs
4 x Hall-effect or DF11 wheel speed inputs, switchable

Sensor Supplies and Screens
2 x Sensor supply 5 V ± 1 % (250 mA)
1 x Sensor supply 10 V ± 1 % (250 mA)
1 x Sensor supply U_Bat (250 mA)
4 x Sensor ground

Environment
External switch for page selection, 12 steps

B 261 209 658-01

External switch for brightness adjustment or

B 261 209 659-01

page selection, 6 steps

Connectors and Wires
LIFE connector on display
AS216-35PN
Mating connector

F02U.000.466-01

AS616-35SN
Auxiliary connector on display
AS212-35PN
Mating connector

F02U.000.443-01

AS612-35SN

Pin Configuration
LIFE connector

Bosch Motorsport

Pin

Name

Comment

1

KL_31

Incl.

2

KL_15

Incl.

3

KL_30

Incl.

4

Rev_In_3

Hall or DF11 switchable

Incl.

5

Rev_In_1

Hall or DF11 switchable

Incl.

DDU_10_Manual

Status

9 / 200

4 | Technical Data

LIFE connector

10 / 200

6

KL_31

Incl.

7

CAN_2_L

8

Ethernet_2_TXP

Incl.

9

Ethernet_2_TXN

Incl.

10

Sens_Power_12V

over current protected

Incl.

11

Rev_In_4

Hall or DF11 switchable

Incl.

12

Rev_In_2

Hall or DF11 switchable

Incl.

13

Laptrigger_In

14

CAN_2_H

CAN speed selectable

Incl.

15

CAN_1_H

CAN speed selectable

Incl.

16

Ethernet_2_RXP

17

Sens_Gnd_4

fused

Incl.

18

Sens_Power 5V

over current protected

Incl.

19

ANA_IN_3

3.01 kOhm switchable

Incl.

20

ANA_IN_4

3.01 kOhm switchable

Incl.

21

Time_Sync

connection to Bosch ECU

Incl.

22

CAN_1_LCAN speed selectable

Incl.

23

Ethernet_screen

Incl.

24

Ethernet_2_RXN

Incl.

25

Sens_Gnd_3

fused

Incl.

26

Sens_Power 5V

over current protected

Incl.

27

ANA_IN_7

3.01 kOhm switchable

Opt.

28

ANA_IN_1

3.01 kOhm switchable

Incl.

29

USB_Device_DP

to Bosch USB stick

Opt.

30

RS232_TX_Telemetry

Transmit Telemetry data

Incl.

31

Ethernet_1_TXP

32

Sens_Gnd_2

fused

Incl.

33

Sens_Power_10V

over current protected

Incl.

34

ANA_IN_8

3.01 kOhm switchable

Opt.

35

ANA_IN_10

3.01 kOhm switchable

Opt.

36

USB_Device_Gnd

to Bosch USB stick

Opt.

37

USB_Device_DN

to Bosch USB stick

Opt.

38

RS232_RX_Telemetry

Receive Telemetry data

Incl.

39

Ethernet_1_TXN

40

Sens_Gnd_1

fused

Incl.

41

ANA_IN_11

3.01 kOhm switchable

Opt.

42

ANA_IN_9

3.01 kOhm switchable

Opt.

43

RS232_TX_GPS

Transmit GPS data

Incl.

44

ANA_IN_16

3.01 kOhm switchable

Opt.

45

USB_Device_Powerto Bosch USB stick

Opt.

46

Ethernet_1_RXP

47

ANA_IN_12

DDU_10_Manual

CAN speed selectable

Incl.

Incl.

Incl.

Incl.

Incl.

Incl.
3.01 kOhm switchable

Opt.

Bosch MotorsportTechnical Data | 4

LIFE connector
48

ANA_IN_6

3.01 kOhm switchable

Opt.

49

ANA_IN_2

3.01 kOhm switchable

Incl.

50

ANA_IN_13

3.01 kOhm switchable

Opt.

51

ANA_IN_15

3.01 kOhm switchable

Opt.

52

Ethernet_1_RXN

53

ANA_IN_5

3.01 kOhm switchable

Opt.

54

RS232_RX_GPS

Receive GPS data

Incl.

55

ANA_IN_14

3.01 kOhm switchable

Opt.

Comment

StatusIncl.

Auxiliary connector
Pin

Bosch Motorsport

Name

1

Unused2

Unused3

Unused4

Unused5

Unused6

Unused7

Unused8

Unused9

Ethernet_3_TXP

Incl.

10

Ethernet_3_RXP

Incl.

11

Ethernet_3_RXN

Incl.

12

CAN_4_H

Opt.

13

Unused14

Unused15

Unused16

Unused17

Unused18

Ethernet_screen

Incl.

19

Ethernet_3_TXN

Incl.

20

CAN_4_L

Opt.

21

CAN_3_H

Opt.

22

CAN_3_L

Opt.

DDU_10_Manual

11 / 200

4 | Technical Data

4.1 Upgrades
CCP/XCP_MASTER
Enables CCP/XCP master functionality to request data from foreign devices via CAN/CCP
protocol, XCP over Ethernet (UDP) or XCP via CAN.
(ASAP2 file from ECU manufacturer required)

FULL_LOG_1
1,500 channels/1 kHz sampling rate on Recording 1

FULL_LOG_2
4 GB memory on Recording 2

IO_EXTENS
Additional 12 analog inputs and 2 CAN channels

DATA_USB
Data copy to USB flash drive

ABSDIAG
Upgrade Onboard Diagnostic Package ABS M5– Enables functionality like error memory read and erase, and repair bleed from UIM
menu in display

12 / 200

DDU_10_Manual

Bosch MotorsportMechanical Drawing | 5

5 Mechanical Drawing

Bosch Motorsport

DDU_10_Manual

13 / 200

6 | System Configuration Tool RaceCon

6 System Configuration Tool RaceCon

RaceCon is an all integrated software tool for configuration and calibration of Bosch
Motorsport hardware products, such as ECUs, displays, loggers. The communication isbased on Bosch Motorsport MSA-Box interface.
Calibration of ECU maps and curves
ECU data file up- and download
Parameter file up- and download
Diagnostic functionality for Bosch Motorsport ECUs
Data file / Work base management
Integrated flash functionality
Integrated Bosch sensor database
Configuration of Bosch Motorsport displays
Configuration of Bosch Motorsport data loggers
Configuration of Bosch Motorsport CAN modules
Communication via K-Line/CAN/Ethernet (KWP/CCP/XCP)CAN communication log functionality (baud rate changeable)
Quick data access over Race Mode
Intuitive design, easy to use

EnvironmentPC
IBM PC Pentium/AMD Athlon compatible, min. 1.6 GHz
Min. 2 GB RAM
Min. 1 GB free hard disc space
VGA/WGA monitor (min. 1,024 x 768)
Recommended Operating System: Windows 10

Optional Accessories
MSA-Box II

14 / 200

F02U.V00.327-03

DDU_10_Manual

Bosch Motorsport

First Steps | 7

7 First Steps
Install the software required for the operation of the DDU 10. It is developed for Windows
system software. The following software versions are used in this manual:– DDU 10 setup, configuration and calibration: RaceCon Version 2.6.
– Measurement data analysis: WinDarab V7
Set up the 100 Mbit ethernet connection to the DDU 10.
– The ethernet port has “cable auto crossover” functionality.

7.1 Starting the unit
The DDU 10 powers up by turning on the ignition of the car. At startup the DDU 10 will
display a Bosch logo.
After a moment, the DDU 10 shows a display element screen.

7.2 Connecting the unit to RaceCon
For testing new device configurations, you can connect the device to your computer via
MSA-Box or ethernet cable.

Connection via MSA-Box
1.

Reassure that the MSA-Box driver is installed properly on your computer. If needed,
download the MSA-Box driver from www.bosch-motorsport.com.

2.

Connect an ethernet line of the device to the ethernet line of the MSA-Box.
Please note, that the MSA-Box also requires power supply on the MSA-Box connectorof your wiring loom.

3.

Open RaceCon and connect the MSA-Box to the computer.

4.

In the ‘Info / Status’ Box of RaceCon, you will receive messages that the connection
was successful.

5.

Reassure that the device is switched on.

6.

‘Link LED’ at the computer’s network adapter will illuminate.
If the LED is off, check the wiring harness.
After you created a RaceCon project with the device, the status icon of the device willswitch from grey to one of the following colors: red, orange, green. For further information on how to set up a project, see the chapter “Setting up a new RaceCon Project [} 16]”. For the status color, see chapter “Color indication [} 29]”.

Connection via Ethernet Cable
Instead of connecting the ethernet line to the MSA-Box, connect the ethernet directly toyour computer.

Bosch Motorsport

DDU_10_Manual

15 / 200

7 | First Steps

Troubleshooting while setting up the network interface
The DDU 10 contains a DHCP server, network addresses can be assigned automatically tothe configuration PC. In case of problems during the network connection, please try thefollowing steps:1.

Switch off the PC’s firewall.

2.

Reconfigure the PC or the MSA-Box network interface settings to obtain an IP address
automatically as shown in the pictures below.

Select'Internet Protocol(TCP/IP)'

Select 'Obtainan IP adress
automatically'

Click'Properties'

Click 'OK'
when done

7.3 Setting up a new RaceCon Project
The following screenshot shows an overview of the RaceCon Main Screen with its areas.
All (sub-) windows are resizable and dockable. You can find them under the ‘Windows’
tab.

Main Area
Project
Tree

Toolbox

Data Area

1.

16 / 200

Message Area

Start the RaceCon software.

DDU_10_Manual

Bosch Motorsport

First Steps | 7

2.

In the ‘File’ menu, select ‘New project’ to create a new project.

3.

In the Toolbox, select the DDU10 and drag it into the Main Area. A pop up window to
specify the DDU10 program archive appears.

Bosch Motorsport

DDU_10_Manual

17 / 200

7 | First Steps

4.

Download the firmware for the DDU 10 from www.bosch-motorsport.com. An information shows if the archive is valid or not.
Click ‘Next’.

5.

18 / 200

Select ‘Race track’ or ‘Testbench’ mode according to your application.

DDU_10_Manual

Bosch Motorsport

First Steps | 7

6.

Click ‘Finish’. The DDU 10 is inserted into the project and RaceCon tries to connect tothe device.

RaceCon detects configuration differences between the DDU 10 and the RaceCon project
and asks for permission for data download.
Click ‘Yes’ to download the configurations to the device or ‘No’ to continue without
downloading the data.

Bosch Motorsport

DDU_10_Manual

19 / 200

7 | First Steps

Successful ethernet
connection, Device"talks" to PC.

If the device turns red, you might need to do a firmware update on the device. For more
information see chapter “Firmware update [} 177]”.
The download starts and the DDU 10 carries out a reset.

After the reset, RaceCon reconnects to the DDU 10. Local configuration on both the PC
and DDU 10 match (indicated by green background and dot). The DDU 10 is now connected to RaceCon.

Green backgroundand dot indicate
matching
configuration

For further information on the color indication, see chapter “Color indication [} 29]”.

20 / 200

DDU_10_Manual

Bosch Motorsport

First Steps | 7

7.4 Feature activation– Optional software feature packages are available for the DDU 10– All software feature packages can be purchased prior to delivery or after you have received your device.
– If you have purchased an optional software feature package, it must be activated before it becomes operational.
– The feature activation status is stored permanently in the device and requires activating once only.
– As the activation key is device specific, a key delivered with one DDU 10 does notwork on any other DDU 10.
– When purchasing a software feature package, you have to tell Bosch the ECU ID code.
The ECU ID code is device specific and can be found in the ‘features info’ window,
shown in the screenshots below.
– If you have not purchased an optional software feature package, the next steps canbe skipped.
1.

Ensure a connection to the device.

2.

To activate a feature, double-click on ‘DDU 10’ in the Project Tree.

3.

Click on the ‘Features info’ tab in the Main Area.

1st: Double-clickon DDU

2nd: Click on'Features info'

4.

The ‘DDU 10 features info’ window appears.

ECU ID

Feature status

List of available
features

Locked (disabled)

Bosch Motorsport

DDU_10_Manual

Unlocked (activated)

21 / 200

7 | First Steps

5.

Double-click on the feature you want to activate. A feature unlock window appears.

6.

Enter the activation key you received for this feature on this device and click ‘OK’
when done. The feature’s status changes to ‘unlocked’.

22 / 200

7.

Perform these steps to activate other features you purchased.

8.

Switch the car’s ignition off and on again to cycle the power of DDU 10.

DDU_10_Manual

Bosch Motorsport

First Steps | 7

7.5 First display configuration (Quick Start)
NOTICE:The screenshots shown in this document may show a different device. However, the procedure is identical for all devices.

This chapter explains the configuration of a display element showing the battery voltage.
See chapter Element Configuration [} 45] for a detailed instruction to configure display
elements.
1.

Click on ‘+’ to expand the DDU 10 project tree.

2.

Click on ‘+’ to expand ‘Display’.

3.

Double-click on ‘New Page’, or click on the ‘Display’ tab. RaceCon changes to thepage ‘Display’ to open the DDU 10 display configuration area.

Click '+'
Double-click'New Page'

4.

Drag any display element from the Toolbox and drop it on the display page. The
status signal in the upper left corner switches from green to orange, because the configuration in the tool differs from the configuration of the device.

Drag + Drop

5.

Use the search bar in the ‘Data’ window, to search for ‘ub’ (measurement channel forbattery voltage).

Bosch Motorsport

DDU_10_Manual

23 / 200

7 | First Steps

Search for 'ub'

6.

Drag the ‘ub’ measurement channel from the ‘Data’ window and drop it on the display element.

Drag + Drop

7.

Click on the ‘Download’ button in the upper left corner. The configuration download
starts and the DDU 10 carries out a reset. The status signal in the upper left cornerswitches to green.

24 / 200

DDU_10_Manual

Bosch Motorsport

First Steps | 7

The value of the battery voltage is displayed on the DDU 10.

7.6 First recording (Quick Start)
This chapter explains the configuration of the recording of the battery voltage channel.
See chapter ‘Recording [} 134]’ for a detailed instruction to configure recordings.
1.

Click on the ‘Logger’ tab to go to the page ‘Logger’.

2.

Use the search bar in the ‘Data’ window, to search for ‘ub’ (measurement channel forbattery voltage).

Search for 'ub'

3.

Drag and drop the ‘ub’ measurement channel into the recording area.

Drag + Drop

4.

Click on the ‘Download’ button in the upper left corner. The configuration download
starts and the DDU 10 carries out a reset. Now you can find the ‘ub’ measurement
channel in the ‘Data Area’. As we did not define global start conditions, recording
starts immediately.

Bosch Motorsport

DDU_10_Manual

25 / 200

7 | First Steps

5.

Start the WinDarab software.

6.

Disconnect the DDU 10 network cable.

7.

Click on the ‘Read Data from Logging Device’ icon.
Choose your logger and click ‘OK’ when done. The ‘Data Logger Import’ dialog opens.
Refer to the WinDarab V7 manual for instructions on how to use the ‘Data Logger Import’ dialog and for more detailed descriptions and instructions.

Click'read data from
logging device'8.

Choose the device and the IP address for the device.
Click ‘Apply changes’ when done.

26 / 200

DDU_10_Manual

Bosch Motorsport

First Steps | 7

Choose your Device / IPfrom dropdown list

9.

Connect the DDU 10 network cable.

10. Click on the ‘Current Import’ tab.
11. Click on ‘Import’ in the lower right corner. If the ‘Import all on connect’ box ischecked, the data transmission from the DDU 10 starts automatically. Measurement
files are stored automatically in the folder defined under ‘Settings’.

12. Click on ‘Close’ when the transmission has finished.
13. Click on the Start button and choose ‘Open measurement file’.
14. Select the measurement files from the storage folder.
15. Click on ‘Open’.
16. Click on ‘New Desktop’ to open a new measurement data window.
17. Drag the ‘ub’ measurement channel from the channel list and drop it into the measurement data window. The ‘ub’ measurement channel‘s graph is displayed.

Bosch Motorsport

DDU_10_Manual

27 / 200

7 | First Steps

7.7 Set date and time
The DDU 10 is equipped with a real time clock which is supplied by an internal accumulator. Once this accumulator is charged correctly by 12 V supply of the display, ‘Date &Time’ can be programmed by RaceCon.
Reassure that the time is set correctly, if the device has not been used for more than two
weeks.
1.

Connect the DDU 10 to the PC.

2.

Click on the ‘Set date’ button in the ‘System’ tab menu.

3.

Alternatively, click on ‘Set Date & Time’ in the context menu of the device. A ‘Set Date
& Time’ menu opens

28 / 200

DDU_10_Manual

Bosch Motorsport

First Steps | 7

4.

Set the current local date and time as coordinated universal time.

5.

At ‘Set a specific date & time’ click and type on the value you want to change orchoose from the dropdown menu.

7.8 Color indication
The color indication in RaceCon visualizes different messages, such as differences between
tool and device, status of the device configuration or the accrual of errors.

Visible color indications:– In the status area in the upper left corner.

Bosch Motorsport

DDU_10_Manual

29 / 200

7 | First Steps– As a background, as well as a little dot around the display icon in the ‘System window’.

– As a colored stripe beside the device name in the project tree.

– As a colored background around the device name in the project tree.

– As a colored MIL in the “Error Info” window.

– As a colored dot in the error memory at the bottom.

The colors and their meaning:– Grey: No connection with the device.
– Green: Matching configuration and firmware between device and project.
– Orange: A different configuration between device and project.
– Red: A different firmware between device and project.
– Purple: Device is bricked, too many resets. Reflash the device, reconsider last changes.
– Colored background with orange stripes: Matching configuration with stored (inactive) errors in the device.
– Blinking colored background with orange stripes: Matching configuration with active
errors in the device.
– Black MIL: No errors.
– Orange MIL: Inactive Errors (Error entries existing, but no longer active).
– Blinking MIL (orange/black): Active Errors.
For further information, see chapter Error Memory Properties [} 128].

30 / 200

DDU_10_Manual

Bosch Motorsport

First Steps | 7

7.9 Assign the Mounting Location
At delivery the default role of the devices is set. There is no need to change this, until you
want more than one device of this kind. Up to eight DDU 10 can be used additionally in
one network for I/O expansion and or Multilogging, the mounting location is used for determination between the different DDU 10.
The mounting location is permanently saved in the DDU 10. If necessary, you can reassign
a different mounting location at any time following the same procedure.
A mounting location must not be used several times in one network, this would disturb
the functionality of the respective DDU 10.
1.

In the Project Tree right click on the project name e.g. ‘New Project’ and then select‘Show discovered devices…’.

All connected DDU 10 are listed.

2.

Compare the listed device Type, FNumber and SNumber to the identification plate to
identify the device you want to make changes to:

3.

Bosch Motorsport

Assign the desired mounting location (e.g. ‘Front’) and confirm by clicking ‘Apply’.

DDU_10_Manual

31 / 200

7 | First Steps

The mounting location is now stored in the device. The device will do a reset and the‘RUN’ LED will change to green. The list will show the new mounting location assignment.

It is good practice to physically label the DDU 10 with its mounting location. Now thedevice is ready to be used.
A different coloring of the DDU 10 is used to indicate that the device is already configuredin the currently loaded RaceCon project or not (white/orange).
A conflict of several connected DDU 10 using the same location is indicated by red coloring the involved devices:

32 / 200

DDU_10_Manual

Bosch MotorsportProject Configuration | 8

8 Project Configuration
8.1 Math Channels– Arithmetic and logical operations on up to 4 measurement channel(s)– Numerical result– Result can be used as input source for various display elements (numeric elements,
alarms, bargraphs) and further calculations in the whole RaceCon project

Creating a new Math Channel
1.

Follow the steps shown in the screenshot. The “Create/edit math channel” window appears.

1st: Double-click on"Math Channels" in
the Project tree

2nd: Click on"Add channel"

2.

Define the math channel using the following configuration possibilities:

a)
b)
c)

d)

f)

e)

g)

h)

a) Enter the name of the math channel.
b) Enter a description of the math channel.
c) Enter the formula.
d) Select the logical operator.
e) Choose a measurement channel.
f) Define a value that can be used as a constant in the formula.
g) Choose a function.
h) Describes the function selected above.

Bosch Motorsport

DDU_10_Manual

33 / 200

8 | Project Configuration

Click ‘Finish’ when done. The math channel is displayed in the math channel window.

8.2 Conditional Functions– Arithmetic and logical operations on one or more measurement channel(s)– If-Else structure with reset– Numerical result– Result can be used as input source for various display elements (numeric elements,
alarms, bargraphs) and further calculations in the whole RaceCon project.
All math and conditional channels can be used globally in the whole RaceCon project.

Creating a new Conditional Function
1.

Follow the steps shown in the screenshot. The “create/edit math channel” window appears.

1st: Double-click on"Math Channels"
in Project Tree
2nd: Click on
the dropdown
arrow beside'Add channel'
3rd: Choose'Conditional
function...'2.

Define the math channel using the following configuration possibilities:

a)
b)

d)

c)

e)

a) Enter the name of the conditional function.
b) Enter the If-condition. Click pencil symbol to open an editor to enter expressions.
c) Enter the Then-condition. Click pencil symbol to open an editor to enter expressions.
d) Enter the Otherwise-condition. Click pencil symbol to open an editor to enter expressions.
e) Enter the reset value (must be a number).
Click ‘Finish’ when done.

34 / 200

DDU_10_Manual

Bosch MotorsportProject Configuration | 8

The conditional function works the following way:
The program always calculates the condition entered in the IF window and checks if thecondition is TRUE or FALSE.
If the condition entered in the IF window is TRUE, the program calculates the condition
entered in the THEN window. The returned value is the content of the new variable(entered in “Name”).
If the condition entered in the IF window is FALSE, the program calculates the condition
entered in the OTHERWISE window. The returned value is the content of the new variable(entered in “Name”).
The reset value is always set for the new variable (entered in “Name”):– before the If-condition becomes TRUE for the first time after power-up– when the If-condition changes state from FALSE to TRUE.
An example of a condition to set up the maximum front brake pressure is given on thenext page.
The conditional function is displayed in the DDU 10 math channel window.

Example: Setting up a condition for maximum front brake pressure
Brake pressure ‘front p_br_front’
Brake pressure front p_br_front
40
30
20
10
Condition ‘p_br_front > 20’
Time
Max brake pressure of the variable ‘front p_br_front_mx’
40
30
20
10

Time
Reset
value
is used

Hold
max.
value

ThresholdreachedFollowmax.
value
Hold max.
value

Reset
value
is usedHold max.
value– At power-up, the reset value (10) is used for ‘p_br_front_mx’.

Bosch Motorsport

DDU_10_Manual

35 / 200

8 | Project Configuration– ‘p_br_front’ rises to 30. As ‘p_br_front’ is > 20 (condition is TRUE), the condition ‘max
(p_br_front, p_br_front_mx)’ in the THEN window is triggered. The condition sets thebigger value as new value for ‘p_br_front_mx’. As ‘p_br_front’ (30) is bigger than‘p_br_front_mx’ (10), the new value for ‘p_br_front_mx’ is set to 30.
– Although ‘p_br_front’ falls to 25, the value of ‘p_br_front_mx’ stays 30. This is causedby the THEN-condition, because p_br_front_mx’ (30) is still bigger than p_br_front’(25).
– ‘p_br_front’ rises to 40. As ‘p_br_front’ (40) is bigger than ‘p_br_front_mx’ (30), the newvalue for ‘p_br_front_mx’ is set to 40.
– As ‘p_br_front’ falls below 20, the IF-condition turns to FALSE. Now the OTHERWISEcondition is triggered. Because the condition ‘p_br_front_mx’ sets the value of‘p_br_front_mx’ and the value is already set to 40, nothing changes.
– When ‘p_br_front’ rises to 40, the IF-condition changes to TRUE again and triggers the
THEN-condition. Now the reset value (10) is used for ‘p_br_front_mx’ in the THENcondition.
– The new value of ‘p_br_front_mx’ is 40 because 40 is bigger than 10.

8.3 Conditional Channels– Logical operations on measurement channel(s)– If-Else structure with reset– Logical result– Result can be used as input source for alarm display elements and further calculationsin the whole RaceCon project.

Creating a new Conditional Channel
1.

Follow the steps shown in the screenshot. The “Create/edit condition” window appears.

2.

36 / 200

Define the condition channel, using the following configuration possibilities:

DDU_10_Manual

Bosch MotorsportProject Configuration | 8

a)
b)

c)

d)
e)

f)

a) Enter the name of the conditional channel.
b) Select the comparing mode:– Constant: Compare a measurement channel with a constant value.
– Channel: Compare a measurement channel with a measurement channel.
– Range: Compare a measurement channel with a defined value range.
– Multiple: Compare a measurement channel with up to 5 constant values.
c) Depending on the chosen comparing mode, you can enter the following values:– Constant: Choose the measurement channel or condition, the operator and enter thevalue of the channel.
– Channel: Choose the measurement channel or condition, the operator and the measurement channel or condition to be compared.
– Range: Choose the measurement channel or condition, the operator and define theminium and maximum value.
– Multiple: Choose the measurement channel or condition, the operator and enter thevalue of up to 5 constants.
d) Enter the minimal time to detect the signal of the measurement channel, to avoid highfrequent switchovers.
e) Enter the time by which the signal of the measuring channel is delayed after its end.
f) Choose the output setting of the result.
– Constant TRUE/FALSE: Result is as a constant with the value TRUE or FALSE.
– Blinking: Result is a blinking, if the condition is fulfilled.
– Pulse: Result is a short one-time pulse, if the condition is fulfilled.
– Toggling output: Result is a pulse that lasts until the next condition is fulfilled.
– Click ‘Ok’ when done. The conditional channel is displayed in the DDU 10 condition
channel window.

Bosch Motorsport

DDU_10_Manual

37 / 200

8 | Project Configuration

8.4 Condition Combination– Combination of several (up to 16) conditional channels for more complex calculations– Logical results– All conditions can be used globally in the whole DDU 10 project.

Creating a new Condition Combination
Follow the steps shown in the screenshot.

The ”Create/edit condition combination” window appears. Define the condition combination, using the following configuration possibilities:a) Enter the name of the condition combination.
b) Create the condition combination in the window.
– Choose a channel (condition, conditional function, math, measurement channel withbinary values) to be compared.
– Combine multiple conditions, by adding 'AND' or 'OR' relations.
– To negate a condition, click with the right mouse-button on the condition and select'Negation (!)'.
– Combine several (up to 16) conditions.
Click ‘Next’ to go to the next page. Choose the output setting of the result:

38 / 200

DDU_10_Manual

Bosch MotorsportProject Configuration | 8– Constant TRUE/FALSE: Result is as a constant with the value TRUE or FALSE.
– Blinking: Result is a blinking, if the condition is fulfilled.
– Pulsing: Result is a short one-time pulse, if the condition is fulfilled.
– Toggling output: Result is a pulse that lasts until the next condition is fulfilled.
Click ‘Finish’ when done. The conditional combination is displayed in the DDU 10 condition channel window.

Bosch Motorsport

DDU_10_Manual

39 / 200

8 | Project Configuration

8.5 Display Switch Module
You can use the Display Switch Module to switch display pages and brightness. The output is a display page or brightness output that can be used in display configurations. The
value sustains over a power cycle.
The conditions for incrementing/decrementing the value can be set freely. The maximum
value can be set as constant or read from a measurement.
The page can be configured to wrap around. In this case, no page down condition isneeded.

The resulting outputs are the display switch value and the input conditions.
Measurement label

Function

namepage or brightness value

name_dn

input condition for decrement

name_upinput condition for increment

Example:40 / 200

DDU_10_Manual

Bosch MotorsportProject Configuration | 8

8.6 Timer Module
The Timer Module is designed to implement timing triggers, i.e. for rallye stage timing or
minimum pit time calculations. Any event in the system can be used for starting, stopping
and resetting the timer.
Up counting mode and down counting mode are available, triggers are fired at set time(up counting) or at zero (down counting). The running timer will keep its state over a
power cycle.

The output channels for this module depend on the name used for the module and arecalled …_time and …_trig.
Measurement label

Function

name_time

actual timer value

name_trig

trigger set by timer alarm

In this example, the module is named “Timer_Module”. Resulting channels are:

8.7 GPS Trigger Module
The GPS Trigger Module triggers depending on GPS-position, like the GPS-laptrigger.
There are 50 GPS trigger points for parameter application of latitude/longitude coordinates, as well as 10 macro-based coordinates.
If the car passes one of the trigger points, an output signal is set to 1 shortly. Each trigger
requires a defined latitude, longitude, and detection range.

Bosch Motorsport

DDU_10_Manual

41 / 200

8 | Project Configuration

The parameter-based trigger points need to be set manually in RaceCon, the macrobased trigger points will store latitude and longitude values when the configurable trigger
condition comes true (i.e., steering wheel button). This trigger condition and the detection
range need to be configured in RaceCon.

The GPS trigger points can also be used for segment triggering. If used as segment triggers and i.e., 3 trigger points are selected, the laptrigger module will use the first 3 trigger
points on the list.

42 / 200

DDU_10_Manual

Bosch MotorsportProject Configuration | 8

The channel names depend on the name used for the module, in this example GPS_Trigger. Each trigger has a distance and a trigger channel with the abbreviation m for macroor p for parameter based. The trigger channel will be set to 1, when the lowest distance tothe trigger point is detected. For the macro-based trigger, the stored latitude and longitude values can be seen with the channels.
Measurement label

Function

name_lat

interpolated gps latitude

name_longinterpolated gps longitude

name_ptrig_1..50

trigger output of parameter based trigger (n)name_pdist_1..50

distance to trigger of parameter based trigger (n)name_mtrig_1..10

trigger output of macro based trigger (n)name_mdist_1..10

distance to trigger of parameter based trigger (n)name_macro_lat_1..10

stored latitude for macro based trigger (n)name_macro_long_1..10

stored longitude for macro based trigger (n)Example:8.8 CPU Load Limits
As all microprocessors, the two processors of the DDU 10 have limited capacities. The current load of the processors can be monitored using the channel “cpu_load_001” or“cpu_load_002”. When configuring your device, please make sure the used CPU load is ina save range below 100 %.
Bosch recommends a maximum CPU load of 85 % (averaged). Exceeding this limit might
result in the DDU 10 not being able to fulfill its required measuring/logging/display tasks
or even in crashing and rebooting.
Main factors influencing the CPU load are:– Number and complexity of math channels– Number and complexity of conditions– CAN traffic on both CAN lines– Display configuration, especially displaying pictures– Logger configuration (total logging rate [kB/s], conditional measurement rates)
To help respecting the limit of 85 % CPU load, the DDU 10 creates an error memory entry.
To trigger this error entry, the CPU load must exceed the limit for 5 minutes without interruption.
When being confronted with this error memory entry (see ‘Error info’ in RaceCon) or whenbeing confronted with DDU 10 resets due to complex configuration setups, please consider reducing the demands on the DDU 10 adapting the influencing factors mentioned
above.

Bosch Motorsport

DDU_10_Manual

43 / 200

9 | Display Configuration

9 Display Configuration
9.1 Display page setup
9.1.1 Organizing display pages– All Pages: Display elements placed on this page are displayed on all pages.
– Single Page: Display elements placed on this page are displayed only on this page.
– Under a Page set you can create different display configurations, like style or language based. You can choose which page set should be used on the device (via UIM),
or via RaceCon, by right-clicking on the Page set in the project tree overview.
The priority of display elements placed on ‘All Pages’ is higher than the priority of display
elements placed on single pages.
Alarm Elements have the highest priority and are displayed in front of all other elements.
You can find alarm pages above “All pages” in the project tree.
Example: A bar graph placed on ‘All Pages’ is displayed on all display pages and is always
in front of other display elements on single pages.

9.1.2 Adding a new display page
Click with the right mouse button on ‘Display’ in the project tree and click on ‘Add page’in the menu or on the ‘Add’ button at the top.

A new empty page opens.

44 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

9.1.3 Selecting display pages
Click on the ‘Display’ tab and then on one of the page tabs at the bottom (example: ‘New
Page’).
In the Main Area, a representation of the selected page opens and can be configured.

Configurable
LEDs

Display area
Tabs to switch
between different
items / pages

9.2 Element Configuration
You can insert different display elements and configure these in the ‘Properties’ toolbox.
For an overview of the display elements, see chapter ‘Types of display elements [} 50]’.
1.

Drag a display element from the toolbox and drop it on the display page.
The ‘Properties’ toolbox opens and you can configure the active element.

2.

Use the search bar in the ‘Data’ window, to search for a measurement channel.

3.

Drag the desired measurement channel from the ‘Data’ window and drop it on thedisplay element.

4.

Alternatively, use ‘Value channel’ in the ‘Properties’ toolbox to define a measurement.

5.

To swap the active channel element, click on the needed element.

6.

To perform a multi selection, click and hold the mouse button and swipe over thewanted elements. Alternatively, you can add or remove elements from the selection
with CTRL + mouse click.
(Only overlapping properties will be displayed.)

You can find the following configuration options in the ‘Properties’ toolbox. The following
screenshots are created by way of example for available options. Which options will beavailable, depends on which element is active:

Bosch Motorsport

DDU_10_Manual

45 / 200

9 | Display Configuration

Appearance– Font size: Defines the size of the font.
– Alignment: Defines the alignment of the element content.
– Value alignment: Defines the alignment of the value.
– Orientation: Defines the orientation of the element content.
– Color value: Defines the color of the value.
– Color title: Defines the color of the title.
– Color box: Defines the color of the box.
– Color bar: Defines the color of the bar.
– Color gauge: Defines the color of the gauge.
– Color ticks: Defines the color of the ticks.
– Color border: Defines the color of the border.
– Background: Defines the color of the background.
– Image file: Here you can select the image you want to display.
– Scale image: Enables the fitting of the image according to the box.
– Keep aspect ratio: Keeps the original ratio of the image.
– State channel: Defines the channel to which an alarm icon should react.
– Active icon: Defines an icon, which appears when the channel is active.
– Use inactive icon: Enables the usage of an inactive icon.
– Inactive icon: Defines an icon, which appears when the channel is inactive.

46 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

Visible icon

– Show active: Enables testing of the active icon (only for alarm icon elements).

Format– Title: Defines a specific title.
– Title size: Defines the font size of the title.
– Text: Defines a specific text and/or a value, which will always be displayed in the box.
– Value channel: Defines the value channel, which will be monitored.
– PopUp condition: Defines the condition when the element will be visible on the display.
– Display type: Defines the type of information, which will be displayed. You can differentiate between ‘Value’, ‘Gear’ and a type of time display.
– Decimal places: Defines the decimal places, which will be displayed.
– Fill style: Defines the style of the bar filling. You can choose between blocks and solid.
– Tick visibility: Defines the visibility of the ticks.
– Minimum value: Defines the minimum value at which the counting starts.

Bosch Motorsport

DDU_10_Manual

47 / 200

9 | Display Configuration– Maximum value: Defines the maximum value at which the counting ends.
– Start angle: Defines the angle at which the ticks start.
– Angle range +/-: Defines the angle range of the ticks.
– Tick mark list: Here you can edit the tick mark position.
– Sub divisions: Defines the number of sub divisions between the main ticks.
– Conversion table: Here you can edit the conversion table.
– Fallback: Defines the displayed information when the value channel is invalid for theenumeration box.

Conditional formatting (lower and upper limit respectively)– Limit enable: Enables a lower limit and an upper limit respectively.
– Limit: Defines the threshold limit.
– Reset hysteresis: Defines the value as off when the hysteresis will be reset. You canfind more information about the hysteresis function in general in the chapter Hysteresis [} 113].
– Color value: Defines the color when the value is above/below the set threshold limit.
48 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9– Color title: Defines the new color of the title when the value is above/below the set
threshold limit.
– Color box: Defines the new color of the element when the value is above/below theset threshold limit.
– Color gauge: Defines the new color of the gauge when the value is above/below theset threshold limit.
– Color ticks: Defines the color of the ticks when the value is above/below the set
threshold limit.
– Color bar: Defines the color of the bar when the value is above/below the set
threshold limit.
– Color border: Defines the new color of the border when the value is above/below theset threshold limit.
– Background: Defines the color of the background when the value is above/below theset threshold limit.

Zoom event– Zoom enable: Enables the zoom event.
If checked, the box will increase its size for a short time, after the value changed.
– Zoom percent: Defines the percentage by which the box will zoom out.
– Anchor point: Defines the anchor point, which will be fixed during the zoom event.

Bosch Motorsport

DDU_10_Manual

49 / 200

9 | Display Configuration

Value– Init value: Defines the value, which will be shown in RaceCon during configuration or
on the device if the channel has no link. Allows testing the conditional formatting byentering a representative value.

Size and position– X-Pos: Defines the x-position of the top left corner of the box within the page.
– Y-Pos: Defines the y-position of the top left corner of the box within the page.
– Width: Defines the width of the element.
– Height: Defines the height of the element.

9.3 Types of display elements
RaceCon has two types of element styles, the ‘Classical Elements’ and the ‘Modern Elements’. Both styles contain the same type of elements; the difference is solely in appearance. Additionally, there is the basic element collection, which consists of elements
without any style. Some of these are also transparent and can be used in combination
with other elements by layering them.

50 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

You can find the following display elements in the ‘Display Elements’ catalog:

Classic Box

Classic horizontal bar

Classic vertical bar

Bosch Motorsport

DDU_10_Manual

51 / 200

9 | Display Configuration

Classic Gauge Large

Classic Gauge Small

Modern Box

52 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9Modern horizontal Bar

Modern vertical Bar

Modern Gauge Large

Bosch Motorsport

DDU_10_Manual

53 / 200

9 | Display Configuration

Modern Gauge Small

Basic Box

Value / Text

Can be used as a simple value or text element, which might be placed on top of anotherelement, like the classic gauge large.

Enumeration

54 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

Can be used to translate a value into a text. For example, for a wiper setting 0 - Off, 1 Slow, 2 - fastImage

Can be used to insert images, for example as background images.

Alarm Icon

Icon or Icons, which can be linked to a conditional channel.

9.4 Context menu
The context menu appears when you click with the right mouse button on a display element.

Manage overlapping elements

Delete element

Bosch Motorsport

DDU_10_Manual

55 / 200

9 | Display Configuration

9.5 LEDs
The LEDs are fully configurable to show for example the optimal shifting point. They canalso be configured to flash in case of a customized condition becoming ‘true’.

9.5.1 Configuring shift LEDs
To use shift LEDs, you need a channel with the unit RPM. It is also possible to use gear depending shift light.
You can configure the shift LEDs only in the ‘LEDs Top’.
1.

Double-click on ‘LEDs Top’ in the project tree.
You will find them under ‘Display’.

2.

Alternatively, click on the ‘Display’ tab and then click on the colored LEDs at the top of
the display image.

Tab 'Display'

Tab 'LEDs'

3.

56 / 200

Click on the button ‘Add shift lights’.

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

Button 'Add
shift lights'

4.

The ‘shift light configuration’ window appears. Set up the shifting lights using the following configuration possibilities:

a)
b)

e)

c)

d)

f)

a) Choose the measurement channel for 'Revolution'. Revolution must have 1/min quantization.
b) Enter the limit value when the RPM hysteresis function is active. The RPM hysteresis function avoids
the high-frequent switchover of the measurement channel value.
c) Choose a predefined Pattern style.
d) Define the rpm thresholds to show the LED pattern.
e) Choose the measurement channel for 'Gear'. Gear must have an ASCII quantization (1st gear='1' = 49,
2nd gear='2' = 50, ...). (ASCII quantization is standard for the 'gear' channel of Bosch ECUs.
If you get the gear information of a different control unit as the Bosch ECU (e.g. a gearbox control unit),
use the Gear Lookup Table to translate numeric values to ASCII format.
For more information see chapter "Converting a gear channel to ASCII representation".)f) Click with the right mouse button on the LEDs to reconfigure the LED patterns.

5.

Click ‘OK’ when done. The configuration is displayed in the DDU 10 LED Configuration
window.

9.5.2 Converting a gear channel to ASCII representation
If you get the gear information of a different control unit as the Bosch ECU (e.g. a gearbox
control unit), use the Gear Lookup Table to translate numeric values to ASCII format.
1.

Click on the ‘Measurement Sources’ button in the Toolbox.

2.

Drag the ‘Gear Lookup Table’ symbol and drop it on the ‘Computed Channels’ folder.
The Gear Lookup Table Wizard appears.

Bosch Motorsport

DDU_10_Manual

57 / 200

9 | Display Configuration

Measurement
sourcesDrag + Drop

Gear Lookup Table Wizard
1.

Set up the settings as shown in the screenshot.

Choose the input
channel of thegear information

This column shows
the numeric valueof the input channel

Enter the default
ASCII value thatis set if no output
value is enteredin the table

This column shows
the ASCII value ofthe output channel

2.

Click ‘OK’ when done.
The ‘Create channel on DDU 10’ window appears.

3.

Enter the name and an optional description of the translated ASCII measurement
channel.

e.g. 'gear ASCII'

4.

Click ‘Ok’ when done.
A graphic shows the connection between the input and output channels. You can now
use the measurement channel in the shift LED configuration.

58 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

9.5.3 Creating customized LED pattern
You can create your own LED pattern with an individually created condition, using the top
LEDs and the ones on the sides. The LEDs illuminate or flash if the condition becomes
true.
Click on the button ‘Add pattern’ in the display view. The LED pattern configuration window appears.

a)
b)

d)

c)

a) Choose the needed LEDs by clicking or via multiselect with ctrl + clicking
and define the color of the LEDs by right-clicking on one of the selected LEDsb) Select if the LEDs blink or do not blink.
c) Choose the condition when the LEDs will flash.
- Create a condition using the Condition Creator. For more information see chapter "Creating a new
condition channel".
- Choose an existing condition.
d) Check the box to show a demo of the LEDs. (Important to check blinking)To create a LED that alternately blinks in two different colors, choose 'Display "on" pattern' and define
the LEDs in the first color. Then choose 'Display "off" pattern' and define the LEDs in the second color.

The direction of the pattern changes for each side. For the LEDs on the left side the pattern starts at the bottom LEDs (right side of pattern is for the top LEDs), and for the LEDs
on the right side the pattern starts at the top LEDs (left side of the pattern is for the topLEDs).

Bosch Motorsport

DDU_10_Manual

59 / 200

9 | Display Configuration

Click ‘OK’ when done.
The configuration is displayed in the DDU 10 LED Configuration window.

9.5.4 Assigning display pattern priority
You can assign the priority of the created display pattern and shift lights.
The pattern with a higher priority will always cover patterns with a lower priority, when it
becomes active. If a transparent (grey) LED is used in a pattern, the LEDs of lower patterns
will be visible. Please ensure that for example shift lights do not cover important warnings.
Click the ‘Move up’ or ‘Move down’ button to change the priority. The pattern with thelowest number will have the highest priority.

9.6 Page select / Display brightness / LED
brightness
Any “event” can be used to change the display and LED brightness or the display page.
Those events can be any input channel or an internal calculated channel. In the following
chapters, you will find some examples on how to set up such a configuration.

60 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

9.6.1 General information
To use a channel as a page switch, select “Channel based” as page switch and select thechannel you configure for a switch in the ‘display settings’ dialog (as described in the following chapters).
To use a channel as a brightness switch, check the box “Use a channel to switch brightness” and select the channel you configure for a switch.

Page switch
The pages can be switched from page one to twelve. If not all twelve pages are defined,
the device switches up to the highest defined page number, and ignores higher numbers,
which are not defined.
If the channel value does not only consist of integers, the pages will be switched as follows:
Page 1 is shown with the value < 1.5
Page 2 is shown with 1.5 <= the value < 2.5
Page 3 is shown with 2.5 <= the value < 3.5…
Page 12 is shown with 11.5 <= the value

Brightness switch
The brightness can be switched with 6 positions. In the display settings dialog, you willfind a chart for the 6 switch positions over the display brightness and the LED brightness(the values are in percent).
If the channel value does not only consist of integers, the pages will be switched as follows:
Switch 1 is shown with the value < 1.5
Switch 2 is shown with 1.5 <= the value < 2.5
Switch 3 is shown with 2.5 <= the value < 3.5…
Switch 6 is shown with 5.5 <= the value

Bosch Motorsport

DDU_10_Manual

61 / 200

9 | Display Configuration

9.6.2 Option 1: Hardwired positions switch
1.

Connect a 6- or 12-position switch to one of the analog input pins ANAxx and to thesensor ground. For recommended position switches, please see chapter Upgrades.

2.

Select one of the analog inputs in the project tree.

3.

Go to ‘Measurement Sources’ in the toolbox and select the ‘Characteristic Curve’ under ‘Analog sources’. Drag and drop it on the selected analog input channel in the
project tree.

4.

62 / 200

Select ”Pullup value:” 3.01 kOhm and click on ‘Next’.

DDU_10_Manual

Bosch Motorsport

Display Configuration | 95.

Define the relation between voltage and switch position and click on ‘Next’.
Voltage = 5000 x R/(R + 3010)
5000: Sensor supply (mV)
R: Resistor for each Rotary switch position (Ohm)
3010: Pull-up resistor (Ohm)The following screenshot and the data are an example for a Bosch switch.

Bosch Motorsport

DDU_10_Manual

63 / 200

9 | Display Configuration

6.

Define minimum and maximum Limit.
Select “Output data type” from 8, 16 or 32 Bit.
Do not check “Use adjustment value”.
Choose the Measurement sheet and click on ‘Finish’.

7.

64 / 200

Define Name and Description and click on ‘Ok’.

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

8.

Click on the ‘Display’ tab and select the ‘Settings’ tab at the bottom.

9.

To use the channel as a Page Switch, Select "Channel based" as page switch and select the channel configured above.

10. To use the channel as a brightness switch, check the box "Use a channel to switch
brightness" and select the channel configured above.

11. Click the ‘Download’ button at the top, to download the configuration.
12. If you want to check your configured channel, ensure that the device status is green,
search for the configured channel in the Data window and double-click on it.
You will see a graphical display with the raw and the physical value of the channel.

Bosch Motorsport

DDU_10_Manual

65 / 200

9 | Display Configuration

9.6.3 Option 2: Up/Down switches
1.

Define either one signal for a wrap around switch or two signals for an up/down
switch.

2.

Select the ‘Display Switch’ and drag it into the DDU 10.

3.

Select the Source for signal Up/Down and Edge Falling or Rising.
Select the Maximum count of steps from signal source or from constant.
Select “Display switch does wrap around” or “Display switch does not wrap around”.
“Display switch does wrap around” goes from maximum position to minimum position or the other way around (by switching) in a loop, after the last page it starts again
with the first page.
If you choose “Display switch does not wrap around”, you need two switches to turnthe pages in both directions.

66 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

Bosch Motorsport

4.

Define Name and Description and click on ‘Ok’.

5.

In the project tree, select “Display” and then “Open”.

DDU_10_Manual

67 / 200

9 | Display Configuration

6.

To use the channel as a Page Switch, check the box "Use a channel to switch pages"
and select the channel configured above.

7.

To use the channel as a brightness switch, check the box "Use a channel to switch
brightness" and select the channel configured above.

8.

68 / 200

In the project tree, select “Download configuration”.

DDU_10_Manual

Bosch Motorsport

Display Configuration | 99.

If you want to check your configured channel, reassure that the device status is green,
double-click on the DDU 10 and select the "Statistics" tab.
The configured channel position opens.

Bosch Motorsport

DDU_10_Manual

69 / 200

9 | Display Configuration

9.6.4 Option 3: CAN input signal, math channel or
ANA_IN channel
Define your CAN, math or analog input channel.
1.

Select the 'Display' tab and then the 'Settings' tab at the bottom.

2.

A ‘display settings’ window opens.

3.

To use the channel as a brightness switch, check the box "Use a channel to switch
brightness" and select the channel configured above.

70 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 94.

To use a channel as a Page Switch, check the box" Use a channel to switch page" andselect the channel configured above.

5.

Click on the ‘Download’ button in the upper left corner.

9.7 Alarms
The ‘Alarm’ display element displays a warning message when a defined condition becomes ‘true’. When a condition becomes ‘false’, the ‘Alarm’ display element disappears.

9.7.1 General information on the Alarm Representation– Since an alarm is generally used for an urgent information, the ‘Alarm’ element has
the highest priority and will always be displayed on top of other elements.
– The ‘Alarm’ elements can be defined in four separate areas. In each area, only one
alarm message can be visible at the same time. If more than one alarm message isactive in one area, each one will be visible for 1.5 seconds.
– The size and position within the alarm area is freely configurable.
– The ‘Alarm’ elements match the design styles of the general display elements and areavailable in the design styles “Classic” and “Modern”. For better readability, bothstyles have a non-transparent background.
– An ‘Alarm’ element can display either a text, icon or a value, or any combination of
those separately.

9.7.2 Alarm configuration
To create an alarm, perform the following steps:

Bosch Motorsport

1.

Click on the ‘Display’ tab at the top.

2.

Click on the ‘Alarm’ tab at the bottom. The alarm configuration window opens.

DDU_10_Manual

71 / 200

9 | Display Configuration

Alarm styles
Alarm areas

Choose thealarm condition
channel3.

Choose one of the four alarm areas at the top left.
This defines the position on the screen, where the alarm will be displayed.

4.

Select the design of the ‘Alarm’ element from the drop-down list on the top right.
You can choose between the “Classic” and the “Modern” style. By clicking on thealarm style, an alarm will be added to the alarm list in the middle of the screen.

5.

Select the “Alarm condition” channel, which will trigger the alarm when the channel
becomes true.
The “Alarm condition” channel can be any Boolean channel, like any other conditional
channel.

6.

If desired, select a “Value Channel”.
The value can be displayed or used for a conditional formatting.

7.

Define the text, which will be displayed in the alarm icon.
If you use the phrase <channel value>in the text, it will be substituted with the valueof the chosen channel value.

8.

Check the size, position and appearance of the alarm in the “Alarm Area Preview”.
Change the appearance according to your needs with the properties described below.

72 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

9.7.3 Further Alarm Properties
Representation– Reset Mode: Defines if the alarm is resettable. For more details, see chapter Resettable Alarm [} 78].
– Blink mode: Defines the blinking frequency of the alarm when displayed.
– Min. display time enable: Enables the function min. display time.
– Min. display time: Defines the minimum time an alarm will be displayed.
– Auto reset enable: Enables the function “Auto reset”.
– Auto reset after: Defines the time after an alarm will be hidden, even when the condition is still true, only active for resettable alarms.
– Retrigger lock enable: Enables the function “Retrigger lock”. For more details, seechapter Resettable Alarm [} 78].
– Retrigger lock time: Defines the time in which a new rising edge of the alarm condition will not be accepted anymore, after an alarm was reset.

Bosch Motorsport

DDU_10_Manual

73 / 200

9 | Display Configuration

Appearance– Font size: Defines the size of the font.
– Text alignment: Defines the alignment of the text.
– Color value: Defines the color of the value inside the alarm box.
– Color box: Defines the color of the alarm box.

Format– Text: Defines the Text and/or the value of the alarm.

74 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9– Alarm condition: Defines the alarm condition.
– Value channel: Defines the value channel, which may be displayed and is relevant forthe conditional formatting.
– Decimal places: Defines the decimal places, which should be displayed.

Icon– Default icons: Defines the alarm icon, which should be displayed.
– Default color: Defines the color of the icon.

Bosch Motorsport

DDU_10_Manual

75 / 200

9 | Display Configuration

Conditional formatting (lower and upper limit respectively)– Limit enable: Enables a lower limit and an upper limit respectively.
– Limit: Defines the threshold limit.
– Reset hysteresis: Defines the value as off when the hysteresis should be reset. You canfind more information about the hysteresis function in general in the chapter Hysteresis [} 113].
– Color value: Defines the color when the value is above/below the set threshold limit.
– Color box: Defines the new color of the box when the value is above/below the set
threshold limit.

76 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9Value– Init value: Defines the value, which will be shown in RaceCon during configuration or
on the device if the channel has no link. Allows testing the conditional formatting byentering a representative value.

Size and position– X-Pos: Defines the x-position of the top left corner of the alarm message within thealarm area.
– Y-Pos: Defines the y-position of the top left corner of the alarm message within thealarm area.
– Width: Defines the width of the alarm message.
– Height: Defines the height of the alarm message.

Bosch Motorsport

DDU_10_Manual

77 / 200

9 | Display Configuration

9.7.4 Edit/Delete/Change priority of an Alarm
Perform the following steps:
1.

Click on the ‘Display’ tab and then on the ‘Alarm’ tab to go to the alarm configuration
window.

2.

Select the alarm area of the desired alarm.
The center of the alarm configuration window only shows the alarms of the selectedalarm area.

3.

Click on the alarm, which needs to be edited or deleted.

4.

To delete the alarm, click on the red cross.

5.

Change the properties of the alarm in the properties window on the right.

6.

To change the priority of the alarm, click the up/down arrow to rearrange the priority
list.
If the option “Show alarms” is ticked, the alarm with the highest priority will be visibleon the display page configurator. The visibility of the alarms will not be influenced by
the priority; the alarms will always rotate, if several conditions become true.

9.7.5 Resettable AlarmAn alarm can be configured as a resettable alarm. This means that the alarm can be linked
to a second conditional channel, which will hide the alarm, when the condition becomestrue.
To configure and use a resettable alarm, perform the following steps:
1.

Click on the ‘Display’ tab and then on the ‘Settings’ tab to go to the “DDU10 display
settings”

2.

Select your “Alarm reset channel”, which can be any boolean channel, like any otherconditional channel.

3.

Click on the ‘Alarms’ tab, to change to the alarm configuration window.

4.

Create an alarm or edit an existing alarm as described in the previous chapters, to access the properties “Representation”.

5.

Change the “Reset mode” to resettable. The alarm will be displayed with a little crossat the top right corner.

Important information on resettable channels:– Only visible alarms can be reset. If several alarms are active, only the alarm which isvisible during the reset condition becoming true, will react to the reset.
– A reset alarm will not be shown again, if the alarm condition becomes true again, until
the next power cycle. Exceptions are, a change of the display page or if the retrigger
lock is enabled and the retrigger lock time is over.

78 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

9.8 User Interface Menu UIM
You can use the User Interface Menu (UIM) to conduct minor setting changes on the DDU,
like lap time or fuel reset.

How to configure the UIM
Perform the following steps, to set up an UIM on your device:
1.

Click on the ‘Display’ tab on the top or double-click on “Display” in the project tree.

2.

Click on the ‘UIM’ tab at the bottom. This will open the UIM configurator.

Channels to navigate
through the UIM

Move item/page up/down in the
UIM menu tree
Remove selected menu element
Add menu item
Add menu page3.

Define the channels at the top, to navigate through the UIM. The selected channels
can be any Boolean channels, such as conditional channels. You can also use condition combinations to open the UIM, to avoid an unintentional start of the UIM.

NOTICE

When the close condition is true, you cannot open the UIM. Thisfunction can be used to avoid an unwanted UIM while driving, i.ewith a condition RPM>300
4.

Click “Add menu page” to create a new link to a new page on the selected page.

5.

Click “Add menu item” to create a new item on the selected page.
On a new page, you can create new items or pages as needed.

6.

Define a name for your items and pages and define the settings for your items.
With a new item, you can define either labels, special functions or menu triggered
events.

Labels– With a label you can show any channel of the current project or just a text.

Special Functions– Page set variation: This menu entry enables you to switch between all available pagesets. Activating a different page set automatically reboots the device.
– Outing counter increment: Increments the outing counter by 1.
– Lap counter increment: Increments the lap counter by 1.
Bosch Motorsport

DDU_10_Manual

79 / 200

9 | Display Configuration– Lap distance reset: Resets the traveled lap distance to zero.
– Lap counter reset: Resets the lap counter to the reset value configured in theLaptrigger options.
– Outing counter reset: Resets the outing counter to the reset value configured in theLaptrigger options.
– Best laptime reset: Resets the best laptime.
– Segment times reset: Resets the best laptime segment times.

Menu Triggered Events– With a menu triggered event you can define a new virtual Boolean channel, which will
jump to the condition true for 100 ms, when selected through the UIM. You can use
such a channel for sensor calibration or any further custom calculation.
A UIM configuration to change the current outing counter and to reset the best lap
time could look like this:80 / 200

DDU_10_Manual

Bosch Motorsport

Display Configuration | 9

9.9 ABS Diagnostic
ABS diagnostic can be performed from the User Interface Menu, the built-in pre-configured diagnostic feature include functionalities like reading and erasing error codes andproceeding repair bleed.
If UIM has not yet been setup in your project, see chapter User Interface Menu UIM how
to setup the menu and controls required to operate the menu.
To use ABS Diagnostic, a supporting ABS software version and device unlock is required.
See chapter Technical Data, Upgrades for details.

How to setup ABS Diagnostic
Perform the following steps, to set up ABS diagnostic on your UIM menu and device:
1.

Click on the ‘Add ABS Diagnostic’ icon In UIM configuration to add the ABS diagnostic to your existing menu structure.

2.

Bosch Motorsport

Select an ABS error text file (XML) matching the ABS software used in your project.

DDU_10_Manual

81 / 200

9 | Display Configuration

3.

82 / 200

ABS diagnostic settings

DDU_10_Manual

Bosch Motorsport

CAN Configuration | 10

10 CAN Configuration
The DDU 10 has 2 (plus 2 on request) fully configurable CAN bus(es).
– Baudrate 125 kbaud to 1 Mbaud– 11 Bit or 29 Bit identifiers– Input configuration: Read messages from CAN bus and convert to DDU 10 measurement/display variables. CAN bus supports row counter configuration.
– Output configuration: Write RaceCon measurement variables to CAN messages; output frequency and row counter are configurable, CAN gateway functionality (transferfrom one bus to another).

10.1 CAN Bus Trivia
CAN Message– 11 Bit (standard) or 29 Bit (extended) identifier– Up to 8 bytes of data payload

CAN Bus– Needs termination resistors in wiring harness– All devices connected to the bus must use identical data rate
– Configuration of bus data rate in the ‘CAN messages overview’ menu. To access themenu, double-click on one of the CAN bus items of the project tree

Row Counter Concept– Re-use (multiplex) of message identifiers– One byte of message contains row counter– 7 bytes payload remaining– Position of row counter is configurable

Bosch Motorsport

DDU_10_Manual

83 / 200

10 | CAN Configuration

Payload Area
Row
Counter
Message
Id

Row
Counter

Payload Area

10.2 CAN input
10.2.1 Input configuration
Click with the right mouse button on the desired CAN bus to open the CAN bus dropdown menu.
Create new channel to read from CAN bus
Create new CAN output message
Import Vector CAN database (DBC)
channel configuration
Export Vector CAN database (DBC)
channel configuration
Export RaceCon CAN configuration to file
Import RaceCon CAN configuration from file

Display CAN bus properties (Baudrate)

10.2.2 Create new CAN Input channel

84 / 200

1.

Double-click on any CAN bus item, to open the "CAN messages overview".

2.

Select ‘Add CAN-IN’ and choose the desired CAN bus for the new input channel.

3.

A CAN channel configuration window opens.
DDU_10_Manual

Bosch Motorsport

CAN Configuration | 10

4.

Insert the name and description of the channel.

5.

Click ‘OK’ when done.
The channel is listed in the Data window.

Bosch Motorsport

DDU_10_Manual

85 / 200

10 | CAN Configuration

CAN channel configuration

10.2.3 Extracting data from CAN bus
Representation: Byte
Some CAN devices need to be addressed by a byte represented CAN channel. The address can be assigned in this window and is illustrated by a bargraph.

a)
b)

c)

d)

e)

a) Enter CAN message ID. If extended IDs (29 bit) are used, check the box.
b) If replacement values are used, specify time-out period and raw value.
c) If a multiplexer (row counter) is used, check the box.

86 / 200

DDU_10_Manual

Bosch Motorsport

CAN Configuration | 10d) Enter data position, length and format.
e) The bargraph shows assignment of the bytes.
– Red colored fields show the assignment of the data bytes.
– Orange colored fields show the assignment of the multiplexer bytes.

Representation: Bit
Some CAN devices need to be addressed by a bit represented CAN channel. The address
can be assigned in this window and is illustrated by a matrix table.

a)
b)

c)

d)

e)

a) Enter CAN message ID. If extended IDs (29 bit) are used, check the box.
b) If replacement values are used, specify time-out period and raw value.
c) If a multiplexer (row counter) is used, check the box.
d) Enter data position, length and format.
e) The bargraph shows assignment of the bytes.
– Red colored fields show the assignment of the data bytes.
– Orange colored fields show the assignment of the multiplexer bytes.

Conversion to physical value
e)

a)
b)
c)

f)
g)

d)

a) Enter factor (gain) for conversion to physical value.
b) Enter offset for conversion to physical value.
c) Select type of physical value.
d) Select unit of physical value.
e) Enter minimum physical limit of the channel. (for manual setup)f) Enter maximum physical limit of the channel. (for manual setup)
Bosch Motorsport

DDU_10_Manual

87 / 200

10 | CAN Configurationg) Check the box to automatically adjust the limits of the channel.

CAN analyzer functionality
This functionality is only available, if a MSA-Box (I or II) is used to connect the DDU 10 to
the PC. Choose the CAN bus that is connected to the MSA-Box to display the raw value
and the converted physical value here.

Automatic creation of online measurement sheets
The CAN channel can be automatically inserted into a measurement sheet. Insert a namefor a new sheet or select an existing sheet from the list box.
For an online view of the value measured by the DDU 10, insert the channel in an online
measurement sheet which is described in the chapter Setting up an online measurement[} 117].

10.2.4 Online view of CAN channels in vehicle

1.

Double-click on ‘Sheet 1’ in Project Tree. Measurement Sheet 1 is displayed in Main
Area.

2.

Click on ‘Measurement elements’ in the Toolbox.

3.

Drag the desired Measurement element (e.g. Numeric Indicator) and drop it on the
Measurement Sheet.

88 / 200

DDU_10_Manual

Bosch Motorsport

CAN Configuration | 10

Drag + Drop

4.

Click on folder ‘CAN Input’ of desired CAN bus to display available channels.

5.

Drag desired Measurement channel and drop it on the Measurement element.

Drag + Drop

6.

The measurement element displays the values of the assigned channel.

7.

Connect PC to the vehicle and switch to ‘Race Mode’ by clicking ‘F11’ on the keyboard to display online data.

10.2.5 Import a CAN database (DBC) file

Bosch Motorsport

1.

Right-click on CAN Input of desired bus (CAN1 or CAN2).

2.

Select ‘Import DBC file’ from menu. A file browser opens.

3.

Select DBC file to import and click ‘OK’ when done. A channel import window opens.

DDU_10_Manual

89 / 200

10 | CAN Configuration4.

Select desired channels on the left and use the ‘Add’ button to add them to import
list.

5.

Click ‘OK’ when complete. The channels are inserted in the Data window.

10.3 CAN output
10.3.1 Output configuration

Create new CAN output message
Export RaceCon CAN output configuration
to fileImport RaceCon CAN out configurationfrom file
Display CAN bus properties (Baudrate)

10.3.2 Create a new CAN output message channel– Double-click on any CAN bus item to open the "CAN messages overview".
– Select ‘Add CAN-OUT’ and choose the desired CAN bus for the new output channel.

90 / 200

DDU_10_Manual

Bosch Motorsport

CAN Configuration | 10

– The ‘New CAN-OUT message’ window opens.

– Enter name of message, description, CAN-Id, and Grid (output interval). Optionally,
specify a multiplexer.

Definition of
CAN message

Content of
message– Click on ‘Add channel…’ or ‘Add constant…’, this opens the ‘Add new CAN out channel’ window.
Bosch Motorsport

DDU_10_Manual

91 / 200

10 | CAN Configuration– Select the desired measurement channel and specify the message settings.

Click here

The measurement channel is now assigned to the CAN message.

10.3.2.1 Add CAN out constant
To send a constant value on the CAN, perform the following steps:
1.

Create a new CAN output message or edit an existing message.

2.

Click small arrow beside ‘Add channel…’ and select ‘Add constant…’. The ‘Add new
CAN Out constant’ window appears.

3.

Define the name of the constant, the required value in hex and define the CAN channel settings.

4.

Click ‘OK’ when done.

10.3.2.2 Adding CAN out counterTo send a counter value on the CAN, perform the following steps:
1.

Create a new CAN output message or edit an existing message.

2.

Click small arrow beside ‘Add channel…’ and select ‘Add counter…’. The ‘Add new
CAN out counter’ window appears.

92 / 200

3.

Define the name of the counter, define the CAN channel settings.

4.

Click ‘OK’ when done.

DDU_10_Manual

Bosch Motorsport

CAN Configuration | 10

10.3.2.3 Adding CAN out checksum
To send a checksum on the CAN, perform the following steps:
1.

Create a new CAN output message or edit an existing message.

2.

Click small arrow beside ‘Add channel…’ and select ‘Add checksum…’. The ‘Add new
CAN out checksum’ window appears.

3.

Define the name of the checksum, the algorithm, the byte which should be coveredby the checksum and define the CAN channel settings.

4.

Click ‘OK’ when done.

10.4 Multiplexer
Row counter concept
If certain channel messages are not time-critical and can be imported or exported slowly,
you can use a multiplexer to put several channel messages on one message identifier.
– Re-use (multiplex) of message identifiers by splitting it into several rows.
– Every row is assigned to a unique value of the multiplexer.
– One byte of message contains row counter.
Bosch Motorsport

DDU_10_Manual

93 / 200

10 | CAN Configuration– 7 bytes payload remaining. A multiplexer does not have to consist of one byte only, it
can consist of several bytes as well as single bits.
– Position of row counter is configurable.
To use a multiplexer perform the following steps:
1.

Double-click on any CAN bus item to open the “CAN messages overview”.

2.

Select ‘Add CAN-IN’ and choose the desired CAN bus for the new input channel.

3.

Check the box ‘Use Multiplexer’ and configure the multiplexer for the new CAN-IN
channel.

4.

To configure the multiplexer for a CAN-OUT channel, select ‘Add CAN-OUT’.

5.

Check the box ‘Use Multiplexer’ and click on the button ‘Add row…’ to split the message identifiers into several rows.

6.

Click on one row and select ‘Add channel’ to assign a channel to the row.

7.

The ‘Add new CAN out channel’ dialog opens.

8.

Select a channel and configure it. To assign it to the row selected before, check thebox ‘Multiplexed’.

9.

To move the channel message, change the “Start” value or click and hold the green
field in the “Add new CAN out message” window.

10. Click ‘OK’ when done.

94 / 200

DDU_10_Manual

Bosch Motorsport

CAN Configuration | 10

11. The channel message is assigned to the selected fields.
12. Click ‘OK’ when done.

Bosch Motorsport

DDU_10_Manual

95 / 200

11 | Export and Import in RaceCon

11 Export and Import in RaceCon
You can perform an export or an import on almost any level in the project tree.

11.1 Export in RaceCon
You can choose to export the whole project or you can export specific parts of the project.
Proceed with the following steps to perform an export:
1.

Click with the right mouse button on an item in the project tree.

2.

Select ‘Export…’ from menu. An ‘Export Selection’ window opens.

3.

Click on ‘Export’ to select a destination to store.

4.

Specify the filename.

5.

Click ‘Save’ when done.

11.2 Import in RaceCon
You can choose to import into the whole project or you can import into specific parts ofthe project.
Proceed with the following steps to perform an import:

96 / 200

1.

Click with the right mouse button on any item in the project tree.

2.

Select ‘Import…’ from menu. A file browser opens.

3.

Select the input file and click ‘Open’. An ‘Import Selection’ window opens.

4.

Select channels to import.

5.

Drag and drop the channel to ‘CAN Input’ of desired CAN bus on right hand side.

DDU_10_Manual

Bosch MotorsportExport and Import in RaceCon | 11

6.

Click ‘Finish’. If a measurement channel belongs to more than one source (e.g. DDU
10 and MS 6), the ‘Solve Label Ambiguity’ window opens.

Bosch Motorsport

7.

Assign the ambiguous channels to the desired source.

8.

Click ‘Finish’.

DDU_10_Manual

97 / 200

12 | Analog and Frequency Inputs

12 Analog and Frequency Inputs
Analog inputs– 0 to 5 V– 12 bit A/D converter– Switchable 3.01 kOhm pull-up resistor– 10 kHz acquisition rate, up to 1 kHz recording rate
– Linear phase digital filter

Frequency inputs– 5 V Hall-effect type, 2.5 V trigger level (DF11 input with current interface or 5 V Halleffect input with 2.5 V trigger level)– 20 kHz max. frequency– 10 ms measurement window

12.1 Analog inputs
12.1.1 Measurements channels
For each analog channel, several ‘subchannels’ are available.

Measurement labels with the characters ‘raw’ show the exact values in mV.
Measurement labels with the characters ‘_fi’ show filtered values.
The word ‘name’ in the table is a placeholder for the channel’s name.
Measurement label

Function

raw_namemV value of sensor

raw_name_fi

Filtered mV value of sensor

namePhysical value of sensor

name_fi

Filtered physical value

Filtered channels are routed through digital low pass filters:– DDU 10 uses A/D converter oversampling and digital filtering to recording rate
– Digital filters eliminate ‘out-of-band’ noise– Cut-off frequency automatically adjusted to recording rate
– Linear phase – no signal distortion– Latency compensation – no filter delay in recorded data

98 / 200

DDU_10_Manual

Bosch MotorsportAnalog and Frequency Inputs | 12

12.2 Configuring inputs
12.2.1 Configuring a predefined Bosch sensor with the'Bosch Sensor Wizard'
1.

Click on ‘Measurement Sources’ in the Toolbox.

2.

To expand the list of ‘I/O Channels’, click on ‘+’ in the DDU 10 Project Tree.

3.

Drag the “Bosch Sensor Wizard” from the Toolbox and drop it on the desired analog
input channel in the DDU 10 Project Tree.

Drag + Drop

Bosch Motorsport

DDU_10_Manual

99 / 200

12 | Analog and Frequency Inputs

4.

The “Bosch Sensor Wizard” opens.

1st: Choose thesensor´s category

2nd: To narrow yourchoice, choose a
type

These calibration
values will be used

3rd: Select theexact type

Opens sensor´sdatasheet5.

Click ‘Finish’ when done.
The “Create channel” window opens.

6.

Enter the channel name and description.

7.

Click ‘Ok’ when done.
The channel is inserted into the DDU 10 Project Tree.

Channel is linked
to ANA03

Input pin Pull-up
resistor is activatedCalculation ofphysical value withcharacteristic curve

Available measurements for channel:

100 / 200

Measurement label

Function

raw_namemV value of sensor

raw_name_fi

Filtered mV value of sensor

namePhysical value of sensor

name_fi

Filtered physical value

DDU_10_Manual

Bosch MotorsportAnalog and Frequency Inputs | 12

12.2.2 Configuring a generic linear sensor
Example: Acceleration sensor 5 g– From sensor data sheet - operating characteristics:– Sensitivity 400 mV/g, Offset 2,500 mV– The sensor has a linear output signal with sensitivity and offset
1.

Click on ‘Measurement Sources’ in the Toolbox.

2.

To expand the list of ‘I/O Channels’, click on ‘+’ in the DDU 10 Project Tree.

3.

Drag the “Sensitivity/Offset” analog signal source from the Toolbox and drop it on thedesired analog input channel in the DDU 10 Project Tree. A “Sensitivity/Offset Wizard”
opens.

4.

To activate the internal pullup-resistor, check the box. The internal pullup-resistor isused to get a 5 V signal at the analog channel of the DDU 10. It allows you to use apush-button. The fixed value of the internal pullup-resistor is 3,010 Ohm. If using an
additional external pullup-resistor, set up the overall resistance.

5.

Click ‘Next’ when done.
The second part of the “Sensitivity/Offset Wizard” opens.

Bosch Motorsport

DDU_10_Manual

101 / 200

12 | Analog and Frequency Inputs

Choose unitgroup and unit ofphysical valueEnter values fromsensor datasheet

Physical(channel)value

Electrical (pin) value

6.

Click ‘Next’ when done.
The third part of the “Sensitivity/Offset Wizard” opens.
Enter physicallimits of the sensor
Choose data typeof the measurement
variable
Check box to enable
online calibration of
offset and enter
desired physicaloffset value

Physical limitsof channel

Enter name toautomatically create
a new measurement
sheet

7.

Click ‘Finish’ when done.

8.

Enter a channel name and a description.

9.

Click ‘OK’ when done.
The channel is inserted into the DDU 10 Project Tree.
Name andDescription
editable

Channel is linked
to ANA04
Input pin Pull-up
resistor isactivated

Pin Diagnosis

Sensivity andOffset value
for sensor

Adjustment
is enabled

Available measurements for channel:
102 / 200

DDU_10_Manual

Bosch MotorsportAnalog and Frequency Inputs | 12

Measurement label

Function

raw_namemV value of sensor

raw_name_fi

filtered mV value of sensor

namephysical value of sensor

name_fi

filtered physical value

Note
Working with automatically created measurement sheets is explained in chapter ‘Setting
up an online measurement [} 117]’.

12.2.3 Configuring a generic nonlinear sensor
Example: Thermistor 5 kOhm
– From sensor data sheet - resistance values over temperature:– The sensor has a nonlinear behavior– Use characteristic curve for linearization– Input voltage is the ratio between pull-up resistor and thermistor+5V
3 kOhmPin
Thermistor

1.

Click ‘Measurement Sources’ in the Toolbox.

2.

To expand the list of ‘I/O Channels’, click on ‘+’ in the DDU 10 Project Tree.

3.

Drag the “Characteristic Curve” analogue signal source from the Toolbox and drop iton the desired analogue input channel in the DDU 10 Project Tree.

Bosch Motorsport

DDU_10_Manual

103 / 200

12 | Analog and Frequency Inputs

Drag + Drop

4.

A “Characteristic Curve Wizard” opens.

5.

To activate the internal pull up-resistor, check the box. The DDU 10 pull up-resistor isused to get a 5 V signal at the analogue channel of the DDU 10. It allows you, to use apush-button. The fixed value of the internal pull up-resistor is 3,010 Ohm. If using an
additional external pull up-resistor, set up the overall resistance.

6.

Click ‘Next’ when done.
The second part of the “Sensitivity/Offset Wizard” opens.

104 / 200

DDU_10_Manual

Bosch MotorsportAnalog and Frequency Inputs | 12

Choose 'Ohm' toenter datasheet
values directly.
Select physicalunit.
Physical(channel)
value

7.

Enter resistance/
temperature pairs
from sensor datasheet here (the3.01 kOhm pullupresistor is automatically taken
into account)

Click ‘Next’ when done.
The third part of the “Characteristic Curve Wizard” opens.

Enter physical limitsof the channel
Choose data type ofthe measurement
variableThis sensor does notneed offset
calibration

Physicallimits ofchannelEnter name to automatically create a
new measurement
sheet

8.

Click ‘Finish’ when done.

9.

Enter channel name and description.

10. Click ‘OK’ when done.
The channel is inserted into the DDU 10 Project Tree.

Channel is linked
to ANA05

Characteristic
curve for sensor

Adjustment
is disabled

Input pin Pull-up
resistor is activatedAvailable measurements for channel:

Bosch Motorsport

DDU_10_Manual

105 / 200

12 | Analog and Frequency Inputs

Measurement label

Function

raw_namemV value of sensor

raw_name_fi

filtered mV value of sensor

namephysical value of sensor

name_fi

filtered physical value

Note
Working with automatically created measurement sheets is explained in chapter ‘Setting
up an online measurement [} 117]’.

12.2.4 Configuring a multipoint adjustment
Example: Measurement of wheel force– Physical property ‘wheel force’ not directly measurable– Load transfer through suspension kinematics– Physical value at sensor position defined by vehicle– Curve definition by online adjustment at vehicle
Force at sensor

Force at wheel

1.

Click on ‘Measurement Sources’ in the Toolbox.

2.

Expand the list of ‘I/O Channels’ by clicking on ‘+’ in the DDU 10 Project Tree.

3.

Drag the ‘Multipoint Adjustment’ analog signal source from the Toolbox and drop iton the desired analog input channel in DDU 10 Project Tree.

Drag + Drop4.

106 / 200A ‘Multipoint Adjustment Wizard’ opens.

DDU_10_Manual

Bosch MotorsportAnalog and Frequency Inputs | 12

5.

To activate the internal pullup-resistor, check the box. The internal pullup-resistor isused to get a 5 V signal at the analog channel of the DDU 10. It allows you to use apush-button. The fixed value of the internal pullup-resistor is 3.01 kOhm. If using an
additional external pullup-resistor, set up the overall resistance.

6.

Click ‘Next’ when done.
The second part of the ‘Multipoint Adjustment Wizard’ opens.

Choose unit groupand unit of physicalvalue
Select type of curve

Physical(channel)value

Enter physicaladjustment valuesher (can still beedited later)

Electrical (pin) value

7.

Click ‘Next’ when done.
The third part of the ‘Multipoint Adjustment Wizard’ opens.

Bosch Motorsport

DDU_10_Manual

107 / 200

12 | Analog and Frequency Inputs

Enter physical limitsof the sensor
Choose data typeof the measurement
variable
Enable additional
online calibration

Physical limitsof channel

Enter name to automatically create a
new measurement
sheet

8.

Click ‘Finish’ when done.

9.

Enter channel name and description.

10. Click ‘OK’ when done.
The channel is inserted into the DDU 10 Project Tree.

Channel is linked
to ANA06

Characteristic
curve for sensor

Adjustment
is enabled

Input pull-up resistor
is deactivatedAvailable measurements for channel:
Measurement label

Function

raw_namemV value of sensor

raw_name_fi

filtered mV value of sensor

namephysical value of sensor

name_fi

filtered physical value

Online definition of the curve is covered in chapter ‘Online calibration of measurement
channels [} 122]’.
Note
Working with automatically created measurement sheets is explained in chapter ‘Setting
up an online measurement [} 117]’.

108 / 200

DDU_10_Manual

Bosch MotorsportAnalog and Frequency Inputs | 12

12.2.5 Digital filter details
DDU 10 uses A/D converter oversampling and digital filtering to recording rate.

Digital filters eliminate ‘out-of-band’ noise

Cut-off frequency automatically adjusted to recording rate

Example:– 100 Hz recording rate (10 ms)– <40 Hz pass band (>99 %)– >50 Hz stop band (<1 %)Linear phase – no signal distortion
100Hz Abtastrate
1.5

110000Hz Abtastrate

Wert

2

0.5
1.5

Wert 1

Recorded signal 100Hz(unfiltered)

0

0.5
-0.5
0
-1
-0.5

-1.5
0

-1

5

10

15
Abtastwerte (dezimiert)

20

25

30

-1.5
100Hz Abtastrate
1.5
-2
0

500

1000

1500
Abtastwerte (roh)

2000

2500

3000

Sensor signal with noise

1
Wert
0.5

Recorded signal 100Hz(filtered)

0

-0.5

-1

-1.5
0

5

10

15
Abtastwerte (gefiltert)

20

25

30

Latency compensation – no filter delay in recorded data
– Filtering is (smart) averaging over several samples– Filtered signal is delayed with respect to real time signal

Bosch Motorsport

DDU_10_Manual

109 / 200

12 | Analog and Frequency Inputs– DDU 10 filters have constant, frequency independent delay– Delay (e.g. 22 samples at 10 ms) is corrected during recording– No delay filtered vs. unfiltered in recorded data
– Correction is (of course) not possible for real time data (display, online, PWM out)
– Use filtered data for recording, use unfiltered data for real time

12.2.6 Configuring a frequency input
Example: measurement of wheel speed– Pulse wheel attached to wheel– Each passing tooth of pulse wheel triggers hall sensor– Calculation of wheel speed with wheel circumference

1.

Click on ‘Measurement Sources’ in the Toolbox.

2.

To expand the list of ‘I/O Channels’, click on the ‘+’ in the DDU 10 Project Tree.

3.

Drag the ‘Velocity’ digital signal source from the Toolbox and drop it on the desired‘REV’ input channel in the DDU 10 Project Tree.

Drag + Drop

110 / 200

4.

The ‘Velocity Wizard’ opens.

5.

Select the sensor type. The DDU 10 works with Hall effect and DF11 sensors.

DDU_10_Manual

Bosch MotorsportAnalog and Frequency Inputs | 12

6.

Click ‘Next’.

7.

Define the settings for the sensor.

Number of teeth on thepulse wheel
Circumference of wheel
for speed calculation
Choose data type of themeasurement variable

Enter name to automaticallycreate a new measurement sheet

8.

Click ‘Finish’ when done.

9.

Enter the channel name and description.

10. Click ‘OK’ when done.
The channel is inserted into the DDU 10 Project Tree.

Channel is linked
to REV01

Input pin
has hallinterface

Bosch Motorsport

DDU_10_Manual

Number of
teeth

Wheel
circumference

111 / 200

12 | Analog and Frequency Inputs

Available measurements for channel:
Measurement label

Function

raw_namemV value of sensor

raw_name_fi

filtered mV value of sensor

namephysical value of sensor

name_fi

filtered physical value

Note
Measurement of ‘Revolution’ is similar.

12.3 Configuring computed sources
Computed sources receive data from a measurement channel rather than an input pin.
– Sensitivity/Offset calculation on input channel– Characteristic curve calculation on input channel– Computed vehicle speed– Lap trigger (covered in a special separate section)

Example: Sensitivity/offset calculation on input channel
1.

Click ‘Measurement Sources’ in the Toolbox.

2.

Drag the ‘Sensitivity/Offset’ computed source from the Toolbox and drop it on ‘Computed Channels’ in the DDU 10 Project Tree.

Drag + Drop3.

112 / 200A ‘Computed Sensitivity/Offset Wizard’ opens.

DDU_10_Manual

Bosch MotorsportAnalog and Frequency Inputs | 12

Choose input channel
Choose unit group andunit of output
Enter sensivity and offset
of conversion formula

4.

Click ‘Next’ when done.
The second part of the ‘Computed Sensitivity/Offset Wizard’ opens.

Enter physical limitsof the channel
Choose data type ofthe measurement
variable
Check the box toforce the channel'squantization if thequantization should
be a fixed value inthe whole CAN
system.

Physical limitsof channel

Enter name to automatically create a
new measurement
sheet.

5.

Click ‘Finish’ when done.

6.

Enter channel name and description.

7.

Click ‘OK’ when done.
The channel is inserted into the DDU 10 Project Tree.

Note
Working with automatically created measurement sheets is explained in chapter ‘Setting
up an online measurement [} 117]’.

12.4 Hysteresis
The hysteresis function avoids the high-frequent switchover of the measurement channel
value. The hysteresis can be adjusted for each input measurement channel individuallyand can be used for further processing.
1.

Click ‘Measurement Sources’ in the Toolbox.

2.

Drag the ‘Hysteresis’ computed source from the Toolbox and drop it on ‘Computed
Channels’ in the DDU 10 Project Tree.
A ‘Hysteresis Wizard’ opens.

Bosch Motorsport

DDU_10_Manual

113 / 200

12 | Analog and Frequency Inputs

a)
b)
c)
d)
e)
f)
g)
h)
i)
j)

a) Choose input measurement channel.
b) Choose unit group and unit of output.
c) Enter output value of state A in the unit selected in b).
d) Enter threshold value when state changes from A to B.
e) Enter delay time when state changes from A to B.
f) Enter output value of state B in the unit selected in b).
g) Enter threshold value when state changes from B to A.
h) Enter delay time when state changes from B to A.
i) Enter time when the hysteresis function is activated after vehicle´s startup.
j) Enter the channel´s state (A or B) at startup.
3.

Click ‘Next’ when done.
The second part of the ‘Hysteresis Wizard’ opens.

Choose data type ofthe measurement variable
Check the box to force thechannel's quantization if thequantization should be a fixedvalue in the whole CAN system

Enter name to automaticallycreate a new measurement sheet

4.

Click ‘Finish’ when done.

5.

Enter channel name and description.

6.

Click ‘OK’ when done.
The channel is inserted into the DDU 10 Project Tree.

114 / 200

DDU_10_Manual

Bosch MotorsportAnalog and Frequency Inputs | 12

Channels available
in Computed sources

Calculation of hysteresis
channelAvailablemeasurements
for channel

12.4.1 Special functionality: Vehicle speed
This functionality allows:– high performance vehicle owners to measure wheel spin under acceleration andwheel slip/lock under braking.
– calculating vehicle ‘speed over ground’.

Vehicle speed calculation function– Calculating vehicle speed of 2 wheel drive: (Wheel speeds of non-driven axle as input)– Calculated speed is average of both speeds if speed difference between wheels <limit.
– Calculated speed is maximum of both speeds if speed difference between wheels> limit.
– Calculating vehicle speed of 4 wheel drive: (Wheel speeds of all wheels as input)– Calculated speed is speed of 2nd fastest wheel.

12.4.2 Setting up calculated speed
1.

Click on tab ‘System Overview’.

2.

Click on ‘Measurement Sources’ in the Toolbox.

3.

Drag the ‘Speed’ computed source from the Toolbox and drop it on the project namein the DDU 10 Project Tree. Do not drop it on ‘DDU 10’!

Bosch Motorsport

DDU_10_Manual

115 / 200

12 | Analog and Frequency Inputs

Drag + DropA ‘Calculated Speed Wizard’ opens.

Choose device
Choose input source(internal/external)
Choose driven axle
Choose individual wheel
speed channels

Set limit for speed
difference for calculation

4.

Click ‘Finish’ when done.
The speed calculation is inserted into the DDU 10 Project Tree.

Speed calculationin DDU Project
Tree

Measurement
channels
calculated speed
and calculated
distance
Configuration
window

116 / 200

DDU_10_Manual

Bosch MotorsportOnline Measurement and Calibration | 13

13 Online Measurement and Calibration
DDU 10 configuration– System configuration (channel + display configuration, CAN I/O, etc.) is stored in the
DDU 10– Use RaceCon to create and download configuration from the PC to DDU 10 Communication interface: Ethernet– Communication protocol: XCP

Online Measurement and Calibration– System status and diagnosis– Check and calibrate sensors in the vehicle– Live display of sensor values on the PC– Use RaceCon for diagnosis, online measurement and calibration– Communication interface: Ethernet– Communication protocol: XCP

13.1 Setting up an online measurement
DDU 10 supports online measurement of sensor values and diagnostic variables.
1.

Expand ‘Measurement Container’ and ‘Measurement Folder 1’ in the Project Tree anddouble-click on ‘Sheet1’. Alternatively, click on the ‘Calibration/Measuring’ tab toopen the window directly. ‘Sheet 1’ opens in a new ‘Calibration/Measuring’ window.

RaceCon changes
automaticallyto "Calibration/
Measuring"

2.

Click on the ‘Folder/Sheets’ tab, which appears when you are in the ‘Calibration/
Measurement’ window, to create a new measurement folder.

Bosch Motorsport

DDU_10_Manual

117 / 200

13 | Online Measurement and Calibration

3.

Click on the ‘Add’ button for folders in the upper left corner.

In the menu for sheets, you will find buttons to add, delete and rename new sheets
1.

To change between different sheets, click on the tabs on the bottom of the ‘Calibration/Measuring’ window.

Tabs to switch between sheets

To add an element to a measurement sheet, perform the following steps:
1.

Drag a measurement element from the Toolbox and drop it on the measurement
sheet.

Drag + Drop

118 / 200

DDU_10_Manual

Bosch MotorsportOnline Measurement and Calibration | 13

2.

Select the desired measurement channel from the ‘Data’ area and drop it on themeasurement element.

If the DDU 10 shows the green status, the value is displayed.

Drag + Drop

RaceCon offers different types of measurement elements:

Circular gauge

Temperature

Vertical Bar

Horizontal Bar

gauge

graph stylegraph style

Measurement label

Numeric indicator

Oscilloscope (Chart)

Bosch Motorsport

DDU_10_Manual

119 / 200

13 | Online Measurement and Calibration

13.1.1 Automatic creation of measurement sheets
RaceCon can create measurement sheets automatically.
You can create and use measurement sheets with the DDU 10 as well as with all otherdevices connected to RaceCon.

Drag + Drop1.

During the configuration of a measurement channel, select a measurement sheet
from the list box or enter a name for a new measurement sheet.

Select existing sheet
from list or enter nameof new sheet

120 / 200

DDU_10_Manual

Bosch MotorsportOnline Measurement and Calibration | 132.

To create the sheets, right-click on DDU 10 and select ‘Create measurement views…’
from the DDU 10 context menu.

Click to create
measurement sheets

The automatically created sheet is inserted in the Project Tree under ‘Measurement Container’ and ‘Device Channels’. If the DDU 10 is connected to RaceCon and the status isgreen, live values of the channels are shown.

13.1.2 Using the measurement sheets
1.

When RaceCon is online, press the ‘F11’ key to switch from ‘Design Mode’ into ‘Race
Mode’. The measurement sheet is extended to full screen. The button for offset calibration is active.

Bosch Motorsport

2.

Switch between different sheets using the tabs at the bottom of the window.

3.

Press the ‘Esc’ key to return to ‘Design Mode’.

DDU_10_Manual

121 / 200

13 | Online Measurement and Calibration

13.2 Online calibration of measurement channels– Analog sensors drift with age, temperature, etc.
– Manual calibration is necessary– Solution: online offset calibration– Example: acceleration sensor

13.2.1 Enable online offset calibration for measurement
channelDuring creation of the measurement channel

122 / 200

DDU_10_Manual

Bosch MotorsportOnline Measurement and Calibration | 13

Check box to enable online
offset calibration and enter
desired physical target value

In the channel view

Activate switch
to enable online
calibration

13.2.2 Performing the online offset calibration
DDU 10 has to be connected to RaceCon to calibrate the sensor’s offset.
1.

Apply the desired physical condition to the sensor (e.g. 1 G to an acceleration sensor).

2.

Open the measurement channel’s online page by double-clicking on the measurement channel name in the Data Area.

3.

Enter the physical target value (e.g. 1 G) and press the ‘Calibrate’ button.

Calibration
target value
Initiate
calibration

The sensor’s offset is now calibrated.

Bosch Motorsport

DDU_10_Manual

123 / 200

13 | Online Measurement and Calibration

13.3 Online calibration of multipoint adjustment
channels
Example: measurement of wheel force– Physical property ‘wheel force’ not directly measureable– Load transfer through suspension kinematics– Physical value at sensor position defined by vehicle– Curve definition by online adjustment at vehicle
Force at sensor

Force at wheel

1.

Create a multipoint adjustment measurement channel. To create a multipoint channel,
see chapter ‘Configuring a multipoint adjustment [} 106]’.

2.

Download the configuration on the DDU 10. To connect the DDU 10 to RaceCon, seechapter ‘Setting up a new RaceCon Project [} 16]’.

3.

Click on the desired channel in the DDU 10 Project Tree.

4.

Double-click on a measurement channel in the Data Area to open the online view.

Click to open
measurement
channels in data
view

Analog and physicalvalue

Double-click
to openonline view

Click to open
calibration
window

5.

Click on ‘Calibrate adjustment points’ to open calibration window.

6.

Apply the desired physical condition to the sensor (e.g. by applying a force on thewheel).

7.

Enter the physical value in the value column of the desired calibration point(e.g. 745 N).

124 / 200

DDU_10_Manual

Bosch MotorsportOnline Measurement and Calibration | 13

8.

Press the ‘Calibrate’ button of the desired calibration point.

9.

Repeat for all curve points.

10. Click ‘Close’ when done.
The calibration curve is displayed in the online view.

Adjustment points vs. offset adjustment

Bosch Motorsport

DDU_10_Manual

125 / 200

14 | Error Memory

14 Error Memory
In this chapter “Error Memory”, a lot of screenshots are created by way of example for
DDU 8. Please consider this and replace the product name ‘DDU 8’ in this case with thename of your product.

14.1 Error memory representation in RaceCon
Bosch Motorsport devices feature an error memory. Information on errors can be visualized via RaceCon (online measurement) or can be transmitted via telemetry.

14.1.1 Accessing the memory
The error memory can be accessed as shown in the illustration:

126 / 200

DDU_10_Manual

Bosch MotorsportError Memory | 14

The memory is situated inside the device and is non‐volatile. As a consequence, an error
which has occurred and has not been cleared by the user will remain in the error memory
even after a power cycle. The error state will then reflect if the error is still active or not.
An error is deleted from the list when
– the user actively clears the error memory– the user updates the firmware
The error memory is not cleared by a configuration download and is not cleared by apower cycle.

14.1.2 Clearing the error memory
There are two ways of clearing the error memory, both are shown in the following illustration:

Bosch Motorsport

DDU_10_Manual

127 / 200

14 | Error Memory

14.2 Information on errors available from theerror memory
In general, properties of the error memory and properties of an individual error need tobe distinguished.

14.2.1 Error Memory Properties
The following property is available for the error memory itself:– Error Status (device measurement label “error_state”)
0: no error present in memory
1: at least one inactive error present in memory, no active errors
2: at least one active error present in memory
If displayed in a measurement sheet, this property’s value (0, 1 or 2) is translated into averbal description:

128 / 200

DDU_10_Manual

Bosch MotorsportError Memory | 14

It is also represented by a color scheme within RaceCon (provided RaceCon is online withthe system):0 (no error present in memory):

No orange border

MIL off (black)No entries

1 (at least one inactive error present in memory, no active errors):

Constantly orange border
MIL constantly orange

Info cycling througherrors, present inerror memory

Bosch Motorsport

DDU_10_Manual

129 / 200

14 | Error Memory

2 (at least one active error present in memory):

Blinking orange border
MIL blinking orange

Info cycling througherrors present inerror memory

14.2.2 Error Properties
The following channels are recognized and memorized inside the devices:– Error type (device label “error_type_rotate”):
e.g. “below_threshold” for a violation of the minimum voltage range defined in theconfiguration, “shortcut_Batt” for a shortcut to battery voltage etc.
– Error locations (device label “error_location_rotate”):
e.g. “ANA01” for an error concerning the first ANA channel– Error durations
How long has the error been active? If an error encounters a non-active period before
being cleared from the memory and is then detected again, the error duration keeps
on accumulating. The number of active periods can be seen from the “number of occurrences”.
– Number of occurrences
How many times has the error been detected since the last time the error memory
was cleared.
– Error active state (device label “error_active_rotate”)
All failure modes are continuously diagnosed; any error detected will be written to theerror memory. Once an error is detected, it is qualified as “active”.
– 1 (TRUE) Error was detected in most recent diagnose run (active)

130 / 200

DDU_10_Manual

Bosch MotorsportError Memory | 14

– 0 (FALSE) Error is inactive: error was not detected in most recent diagnostic run,however the error has not been cleared from the memory by the user and remains in the non‐volatile memory
The aforementioned channels (error_active_rotate, error_location_rotate, error_type_rotate) are device specific properties (e.g., C 60) and are not related to the complete RaceCon project (e.g., “error no. 3 from the error memory”). Therefore, only one property label
is available in each device. The errors from the error memory (possibly more than one error possible per device) share these three labels. The labels cycle through the errors currently present in the memory and represent the respective property of each error periodically.
The following screenshot shows error properties, which can be displayed or logged:

Labels hold information
on error 1 (an ANA3 error)

Labels hold information
on error 2 ... n-1

Labels hold information
on error n (a CAN error)

After the last error and its error properties have been displayed, the labels will start again
with the first error in the error memory stack and its error properties will be displayed
again. Therefore, monitoring these labels over a sufficiently long period provides the information on all individual errors in the error memory.
To understand this behavior, it is recommended to observe the three labels in a measurement sheet (while more than one error is active) and watch the values change periodically:

The verbal representation of the numerical codes of these labels can be visualized in theproperties window of the measurement page:

Bosch Motorsport

DDU_10_Manual

131 / 200

14 | Error Memory

14.3 Analog Input Diagnosis
14.3.1 Monitoring limits / Shortcut Detection / Cable
Breakage
The pin diagnosis functionality (check whether measurement is within the desired range)
can be activated in the ANA pin setup wizard; to allow for a diagnosis regarding shortcut
to ground, shortcut to battery voltage and cable breakage, a minimum / maximum has tobe defined.

132 / 200

DDU_10_Manual

Bosch MotorsportError Memory | 14

14.3.2 Open Line Detection
The implementation of open line detection consists of pull up resistors being activatedand deactivated; evaluating the behavior of the measured value detects cable breakage,regardless of the pull up resistor being activated by the user.

Bosch Motorsport

1.

Open the Error Memory of the Device.

2.

Click "start detection of cable".

3.

Check the Error Memory for new fault entries, regarding "Open line errors".

DDU_10_Manual

133 / 200

15 | Recording

15 Recording
15.1 Features– Synchronized recording of DDU 10 analog and digital input channels, DDU 10 internalmeasurement channels, ECU data, Data from external sensor interfaces– Up to two independent recordings– Measurement rate 1 ms to 1 s– Two global start conditions (thresholds)– Up to 16 measurement conditions (fast-slow-switches)

15.2 Configuration of recordings
1.

Expand the list of ‘Loggers’ by clicking on ‘+’ in the DDU 10 Project Tree.

Double-click to display
the configuration(automatically change
to "Logger")2.

Double-click on ‘Recording’ in DDU 10 Project Tree. The recording configuration isdisplayed in the Main Area.

Variables can be grouped

Tabs to access conditions, settings and statistics

3.

To add measurement channels to a recording, click ‘DDU 10’ in the DDU 10 Project
Tree. In the Data Area, the measurement channels are displayed.

4.

134 / 200

Drag and drop desired measurement channels into recording group.

DDU_10_Manual

Bosch Motorsport

Recording | 15

Recording properties

Drag measurement
channels into group

5.

To edit channel’s settings, mark the channel(s) and click ‘Edit Channel’. An ‘Edit Recording Channels’ window opens.

Recording rate
1 ms ... 1 s
List of channels
selected

Condition to switch
between fast/slow rate
Recording rate if
condition is 'true'
Settings for longrange telemetry'None/Fast/Slow'(only if telemetry
unit is available)

6.

Click ‘OK’ when done.

NOTICE

If no condition is defined or condition is ‘false’, measurement channels are recorded at the value chosen in ‘Rate’.
If the condition is ‘true’, measurement channels are recorded at the value chosen in ‘True
rate’.

Using fast block/slow block transmission
DDU 10 telemetry uses available bandwidth of Telemetry Unit FM 40 (19,200 baud -> approx. 1,700 bytes/s). The bandwidth has to be divided into channel information to betransmitted high-frequently and low-frequently using the ‘fast/ slow block’ setting.
Channels are grouped into 8 blocks which are transferred each cycle:– Fast block (Block 1) is transferred every cycle and used for a high-frequent transmission of channel information (e.g. speed, rpm).
– Slow blocks (Block 2…n) are transferred every n-th cycle and used for a low-frequenttransmission of channel information (e.g. tire pressure, oil temperature).

Bosch Motorsport

DDU_10_Manual

135 / 200

15 | Recording

Transmission Scheme

If the maximum bandwidth of a block is reached, a warning will be displayed. To fix thisproblem you can view the allocation of the channels and data rate in the ‘Statistics’ tab of
the Main Area. See chapter ‘Recording statistics [} 138]’ for more information.

15.2.1 Adding a recording
DDU 10 supports up to two independent recordings.
To add a recording, select ‘Add Recording’ from the context menu of the Logger in the
DDU 10 Project Tree.

Maximum two recordings are possible. In the device software the 2nd recording is reserved for scruteneering data. This recording is invisible (protected).

15.2.2 Adding a recording group
Recording channels can be grouped.
To add a new group, select ‘Add group’ in the context menu of the recording. The groups
can be renamed to ‘Gearbox’, ‘Aero’, ‘Engine’, etc.

136 / 200

DDU_10_Manual

Bosch Motorsport

Recording | 15

15.2.3 Global settings
To display the global DDU 10 settings, select the ‘Settings’ Tab.

a)

g)

b)
c)
d)
e)
f)

a) Choose setting for outing counter mode:– For testbench (without lap trigger) select ‘Testbench’.
– For racetrack (with lap trigger) select ‘Racetrack’.
b) Choose your WinDarab version. In V6 the file is encrypted by WinDarab. In V7 you canenter an optional self created password in the ‘Encryption’ field shown in f).
c) Recording Type (Engine or Chassis).
d) Statusblock configuration file for custom Statusblock definition.
e) Choose or create the condition to start recording.
f) If selecting WinDarab V7 in b), enter a password hint and a password (optional).
g) Setting for automatic fragmentation. Do not change!

Bosch Motorsport

DDU_10_Manual

137 / 200

15 | Recording

15.2.4 Recording statistics
The tab ‘Statistics’ shows the channels’ allocation and their current data rate related to thetransmission frequency of the DDU 10 and the whole transmission system.
The overview helps to detect bandwidth bottlenecks of channels. Bandwidth bottlenecks
can be solved by changing the ‘fast/slow block’ setting for each channel.
The data rate of the whole system is often less than the data rate of the DDU 10 and limits
the overall transmission speed.

15.2.5 Recording diagnosis
The channel ‘statectrl_ok’ of the DDU 10 can be used for online monitoring of recording
status.
Bit

Value

Name

0

1

RECORD

1

2

DATAOK

2

4

BLKOK

3

8

-

4

16

-

5

32

-

6

64

STARTED

7

128-

Content of status bits
Name

BitsetRECORD

Measurement data is re- No measurement data will be stored because meas-

DATAOK
BLKOK

Bit cleared

corded.

urement thresholds are not reached.

Received data without

Discarding received data because of wrong

error.

timestamps. Check wiring of SYNC signal.

All measurement blocks Some measurement blocks have not been set up
have been set up cor-correctly.

rectly.

138 / 200

DDU_10_Manual

Bosch Motorsport

Recording | 15

Name

BitsetBit cleared

STARTED A measurement has
been set up.

A measurement is not set up. Either no recording
configuration has been found or logger software
upgrade is not activated.

15.2.6 Displaying online recording diagnosis('statectrl_ok')1.

To add a Recording Diagnosis element to a measurement sheet, change to page “Calibration/Measuring“ and drag a ‘Bit-LED’ element from the Toolbox and drop it on
measurement sheet.

2.

Drag channel ‘statectrl_ok’ from the Data Area and drop it on the ‘Bit-LED’ element.

The ‘Bit-LED’ element shows the state of received channel data in bit-representation. A
green highlighted channel means 0, a red highlighted channel means 1.
– Measurement correctly initialized, but recording threshold(s) not reached: 254– Measurement correctly initialized, DDU 10 is recording data: 255– Values less than 254 indicate an error state– ‘statectrl_ok’ can be linked to an alarm on the display. See chapter ‘'Alarm' display
element’ for details.

Bosch Motorsport

DDU_10_Manual

139 / 200

15 | Recording

15.2.7 Further measurement labels
These additional measurement labels may help you diagnosing the state and operation of
the data logging in more detail. There are a few more, but these are usually enough.
Please refer to statectrl_ok, mentioned in more detail in chapter 'Recording diagnosis'.
Measurement label

Function

card_part1_size

Size of the first logging data partition in MB.

card_part2_size

Size of the second logging data partition in MB. Attention, second logging can also be stored on first partition, depending on chosen settings (Logger -> Settings).

ftp_UserLoggedIn

This measurement allows to monitor for active FTP
connections. RaceCon (WinDCP) and WinDarab may
not connect in parallel.

meas_globcond_m01 / _m03

State of the global logging start condition for first /second logging. TRUE means data is actively recorded.

meas_rate_m01 / _m03

Incoming measurement data rate (first / second logging) for further processing. Does not include compression. Active when meas_globcond_m0x is TRUE but
may also be active while meas_globcond_m0x is FALSE,
if a pretrigger time is configured. In that case data istransferred to the pretrigger buffer, but not necessarily
written to storage medias.

meas_cnt_ecu / _fde

Processed data blocks for first / second logging. This
does not ensure writing the data to a storage media,
e.g., if pretrigger is configured and meas_globcond is
FALSE.

meas_cnt_int / _forked

Processed data blocks per media (internal / USB).

meas_compression_m01 / _m03

Compression factor for first / second logging. For example, factor 2.0 means incoming data can be reduced
to half the size, before data is written to storage medias.

meas_pretrig_buf_size_ecu / _fde Size of data buffered in pretrigger, e.g., while global
logging condition is FALSE. Data will be forwarded tostorage medias when logging condition becomesTRUE.
meas_backend_buf_size_ecu /Size of data buffered (for first / second logging) for_fde

processing by different storage medias (intern / USB).
It is possible, that e.g., internal storage has processed
the data already, while USB is still busy writing the data
blocks. Data is removed from the buffer as soon as all
medias have processed it.

meas_write_rate_intern_001 /Effective data write rate to internal storage media, after_002

compression, for first / second logging.

meas_write_rate_usb_001 / _002

Effective data write rate to USB storage media, after
compression, for first / second logging.

140 / 200

DDU_10_Manual

Bosch Motorsport

Recording | 15

15.3 Event logging
Event Logging implements the possibility to observe a channel if short spikes are expected. With Event Logging, every occurrence of a user defined threshold (more complex
conditions are possible) leads to an event being raised. It is listed in a table along with its
time stamp, its ID and even with a text string freely definable in RaceCon.
Events are stored as text in logging data and displayed in WinDarab like Darab-Events.
Possible use cases are error entry, etc.
Configuration in RaceCon:

Display in WinDarab:

Bosch Motorsport

DDU_10_Manual

141 / 200

15 | Recording

15.4 Data Logger and USB recording
Default settings:

Data from Recording 1 and Recording 2 are stored both into the Internal Memory andadditionally on the USB stick in copy.
To download the data from the Internal Memory of the logger, the Data Logger must be
selected in WinDarab and the data will be downloaded in parallel.

Alternative setting:

Recording 1 is stored on the Internal Memory and additionally on the USB stick in copy.
To download this data, the Data Logger must be selected in WinDarab.
Recording 2 is stored on only the Internal Memory. To download this data, the Long
Term logger must be selected in WinDarab.

15.5 USB recording
This function requires the installation of Software Upgrades. Look into the datasheet ofyour device, to see which upgrades are available for your device.
Software Upgrade DATA_USB enables USB recording. To activate Software Upgrade
DATA_USB, enter the license key as described in the chapter ‘Feature activation’ [} 21].
For USB recording, Software Upgrade FULL_LOG_1 should also be enabled.

Wiring harness
Bit

Value

USB_Device_PowerPower (red)USB_Device_DP

D+ (green)

USB_Device_DN

D- (white)

USB_Device_Gnd

GND (black)

For further information, see the pinlayout of the device.

142 / 200

DDU_10_Manual

Bosch Motorsport

Recording | 15

Colors matching a standard USB cable

Storage device
The recording function can be used with a dedicated Bosch Motorsport USB device. The
USB device must be preformatted with the Bosch File System (BFS) in RaceCon before firstuse.
To format the USB device with the Bosch File System (BFS), do the following steps:
In RaceCon, select ‘Tools’ - ‘Extras’ and choose ‘Format USB stick’.
Press ‘Format’.
An USB device is recognized by Windows as a ‘storage medium’, but it can only be initialized with RaceCon and read with WinDarab.

15.5.1 Recording data on USB device
1.

Plug an USB device to DDU 10.

2.

Prepare a recording configuration in RaceCon.

3.

Power on the system and connect with RaceCon to the vehicle.

4.

Download the configuration to the DDU 10.

5.

Record measurement data. If an USB device is present, the DDU 10 stores the data inparallel on the internal memory and the USB device.

Bosch Motorsport

6.

Power off the system.

7.

Remove USB device from the vehicle.

8.

Start the WinDarab software.

DDU_10_Manual

143 / 200

15 | Recording

9.

Click on the ‘Import/Export’ icon.

10. Select ‘Data logger CXX/DDUX/MSX and click ‘OK’ when done. The ‘Read measurement data’ dialog opens.
Click'read data from
logging device'

11. Click on ‘Settings’ tab and select the option ‘Flash Card/USB Stick’.

12. Activate ‘Apply changes’.
Insert the USB device into the PC. Data transmission from device starts automatically.
Measurement files are stored automatically in the base folder.

144 / 200

DDU_10_Manual

Bosch Motorsport

Recording | 15

13. Click ‘Close’ when transmission has finished.
14. Click on the Start button and choose ‘Open measurement file’.
15. Select the measurement files from the storage folder.
16. Click on ‘Open’.
17. Click in ‘New Desktop‘ to open a new measurement data window.
18. Drag the desired measurement channel from the Channel list and drop it into themeasurement data window. The measurement channel‘s graph is displayed

For more detailed descriptions and instructions, refer to the WinDarab V7 manual.

Bosch Motorsport

DDU_10_Manual

145 / 200

15 | Recording

15.5.2 USB device handling hints
Using the USB device
Always plug the USB device into vehicle before power up to ensure that all measurement
data is stored on the USB device.
If the USB device is plugged in after recording has started, only the current data is saved.
Data recorded on the DDU 10 before the USB device is plugged in will not be saved.

Removing the USB device
Always power off the system before unplugging the USB device!

15.5.3 Troubleshooting
When no data on the USB device is recorded:
Configure the measurement label usb_mediastate on a RaceCon measurement view oron a DDU 10 display page.
The value of usb_mediastate reflects the operating condition of the USB bus:
State

Description

0: Wait: Device not found The USB device is not found (also: waiting for re-plug stick).
No USB device inserted.
USB device is defect.
No electrical connection or wiring harness problem.
USB software upgrade not activated (Purchase of unlock codeneeded).
1: Wait: Device detected

An USB device is found, but not yet installed.

2: Ok: Media installed

The USB device is found and is operational (idle).
This does not imply that recording data is written!

4: Stop: Device unplugged The USB device has been removed.
The DDU 10 performs a restart when an USB device is replugged in.
5: Error: Media error

The communication to the USB device broke down.
The USB device is defect.
The USB device is not supported by DDU 10.

6: Error: Media corrupt

The USB device is not in valid BFS format.
(Hint: Re-format the USB device in RaceCon.)146 / 200

DDU_10_Manual

Bosch Motorsport

Ambient Light Sensor | 16

16 Ambient Light Sensor
The DDU 10 is equipped with an ambient light sensor. The sensor is located at the front of
the DDU 10 below the LEDs on the right side. The sensor is linked to the channel “eamb”
with the unit lux.
The ambient light sensor can be used to calculate an automatic brightness switch. To use
this function, please follow the steps below.
1.

Measure the range of light intensity in your vehicle during all relevant conditions.
The easiest option to evaluate the needed range is to log the “eamb” channel and expose the vehicle to the brightest and darkest conditions it will face during usage.
In this example, the expected value will be 10 lx as the lowest and 300 lx as thehighest measured light intensity in the cockpit.

2.

Drag and drop a “Characteristic Curve” from the “Computed Sources” onto the “Computed Channels”.
This will open the configuration wizard.

3.

Select “eamb” as input channel.

4.

Assign the lowest lux value to the highest possible brightness switch setting (6) andthe highest lux value to the lowest switch position (1).
This will generate a linear change of the switch. If needed you can include additional
points to change the linear behavior.

5.

Click “Next” when all points are defined as needed.

lowesthighest6.

The “Analog Source Properties” window opens in the wizard. The maximum and minimum value of the channel is automatically assigned according to the previous settings. In general, it should be from 1 to 6.

7.

Click “Finish”.

8.

Assign a suiting name to the new channel and click “OK”.
In this example, the channel will be named “Ambient_Light_Switch_Computed”
To avoid a toggling brightness setting, a math channel with a kind of hysteresis has tobe created.

9.

Double click on “Math Channels” and click on “Add channel”.

10. Copy the Formula below into the new math channel and replace the example namewith your name of the computed channel.

Bosch Motorsport

DDU_10_Manual

147 / 200

16 | Ambient Light Sensor

latch(#DDU10#Ambient_Light_Switch_Computed+0.5, abs(#DDU10#Ambient_Light_Switch_Computed-#DDU10#display_brightness) > 0.6)
The formula compares the brightness setting of the device with the computed channel. If the deviation is within a certain range, it allows sending of the new value to thedevice. This formula only works correctly if it is used as the brightness switch channel.
11. Assign a suiting name to the new channel and click “OK”.
12. Go to “Display” - “Settings” and define the created math channel as the brightness
switch channel.
13. Define the percentagewise brightness of the display and the LEDs according to eachswitch position.

148 / 200

DDU_10_Manual

Bosch MotorsportLap Trigger | 17

17 Lap Trigger
17.1 Lap trigger (timing beacon)
Why do we need a lap trigger (timing beacon)?
– Vehicle lap time measurement– Calculation of lap-dependent functions (lap fuel consumption, min/max values)– Calculation of lap distance dependent functions– Control of data logging system

Types of Systems– GPS based (low cost, low precision)– IR based (low cost, high precision, limited reliability)– RF (microwave) based (high precision, high reliability)

IR and RF based Systems consists of– Transmitter (trackside unit)– Receiver (in-vehicle unit)

Lap Trigger
Transmitter
Lap Trigger
Receiver17.1.1 Electrical trigger signal
In DDU 10 all sources of measurement channels can be used as trigger signal.
– Analog input– Digital input– CAN input

Signal (measurement channel) properties
Low active signal (Bosch triggers): Trigger releases if signal is below the threshold.

High active signal (other manufacturer’s triggers): Trigger releases if signal is above thethreshold.

Bosch Motorsport

DDU_10_Manual

149 / 200

17 | Lap Trigger

Two types of trigger signal:– Main trigger (end‐of‐lap at start/finish line)– Sub‐trigger (segment time, optional, not applicable with GPS lap trigger)

Bosch standard:– Main trigger 20 ms, low active (Recommendation for RaceCon “Detecion Time” setting: 15 ms, Setting must be a slightly shorter period than the signal length of thetrigger to avoid a missed trigger due to the update rate)– Sub trigger 40 ms, low active (Recommendation for RaceCon “Detecion Time” setting:
30 ms)

17.1.2 GPS Lap trigger
The GPS lap trigger uses a GPS signal to trigger the lap timer. To function this timer an external GPS sensor (see GPS Sensor [} 164]) has to be connected to the device and a detection point with a detection range has to be defined in RaceCon.
The GPS detection point is defined by the latitude and longitude. The easiest way to get
the latitude and longitude of a finishing line is due to a web mapping program such as
google maps. With google maps, simply left-klick on the spot where you want to set thedetection point. The information about the latitude and longitude will show up, in general
the latitude is given at first. You should insert at least five decimal places for sufficient precision.

Photo: Google Maps

The detection range defines the radius of a circle around the detection point in which thelap trigger can be set. The lap trigger will be set as soon as the distance between the car
and the detection point has reached its smallest peak. By this function an imaginary finishing line is calculated inside of the detection circle.

150 / 200

DDU_10_Manual

Bosch MotorsportLap Trigger | 17

The imaginary finishing line can only be calculated if all channel sources are defined correctly. The latitude and longitude channel sources are mandatory for the functionality.
Missing direction or speed source lowers the precision of the system.

Define the latitude andlongitude of the GPS
detection point.
Define the detection
range around thedetection point.
Define the channel
sources for Longitude,
Latitude, Direction andSpeed.

Note
The configuration of the sensor update rate and the detection range must insure to receive a valid GPS point in the detection range, despite the occurring vehicle speed near
the detection point.

17.1.3 Prevention of false triggers– Race track topology and transmitter location frequently cause false triggers.
– Software functionality prevents acceptance of false triggers.
– Minimum vehicle speed for acceptance of trigger prevents false triggers while vehicle
is stationary in the pits.
– Time based re-trigger protection prevents false triggers due to signal reflections on
Home Straight.
– Lap distance based retrigger protection prevents false triggers due to track topology.

17.1.4 Forced triggers
Lap distance based insertion of ‘forced trigger’.
Under race conditions, trigger signals are sometimes missed. Software functionality introduces ‘forced trigger’.

17.1.5 Setting up a lap trigger

Bosch Motorsport

1.

Click ‘Measurement Sources’ in Toolbox.

2.

Drag ‘Laptrigger’ into ‘System Overview’. Do not drop it on ‘DDU 10’!

DDU_10_Manual

151 / 200

17 | Lap Trigger

Drag + dropA ‘Laptrigger Wizard’ window opens.

Choose the device which
receives the trigger signal
Choose the signal channel
for the trigger signal
Choose the source for thevehicle speed
Enter the distance ofthe racetrack

e)

f)

g)

h)

i)

j)

a)
b)
c)
d)

a) Change signal device, if desired.
b) Change signal channel, if desired.
c) Choose signal threshold. See chapter 'Electrical trigger signal' for details.
d) Define threshold of input channel signal when trigger is released. Only possible, if nodigital source is selected as signal source.

152 / 200

DDU_10_Manual

Bosch MotorsportLap Trigger | 17e) Define presettings for trigger. See chapter 'Lap trigger presettings' for details.
f) Define condition settings; change signal for vehicle speed, define speed settings. See
chapter 'Distance based retrigger protection' and 'Distance based forced trigger' for details.
g) Define settings for main trigger. See chapter 'Lap timing' for details.
h) Define settings for counddown timer. See chapter 'Countdown timer' for details.
i) Define settings for sub trigger. See chapter 'Segment timing' for details.
j) Define settings for a GPS lap trigger. See chapter 'GPS lap trigger' for details. Only applicable if the signal source is set to 'GPS lap trigger'.
Click ‘Finish’ to complete the operation. A pre-configured lap trigger window opens.

Preset values for lap counterand outing counter
Minimum laptime that a new'best laptime' is accepted
Preset value for 'best laptime'

Change signal for vehicle speed,
if desired.
Enter minimum speed fortrigger release.
Define settings for distancebased retrigger protection.

Define settings for distancebased forced trigger.

Define settings for lap timing(main trigger).
Define settings for sub trigger.
Not applicable with a GPS lap trigger.

Bosch Motorsport

DDU_10_Manual

153 / 200

17 | Lap Trigger

Define settings for countdown
timer.

Define settings for segment
timing.

Only applicable for a GPS Laptrigger

Define the latitude andlongitude of the GPS
detection point.
Define the detection
range around thedetection point.
Define the channel
sources for Longitude,
Latitude, Direction andSpeed.

17.1.6 Lap trigger channel diagnosis/counter reset
To display a quick lap trigger channel diagnosis and to reset counters use the diagnosis
page in RaceCon. Any ‘Laptrigger_xxx’ channel can be displayed.
Double-click on any ‘Laptrigger_xxx’ channel in the Data Area. Example: ‘laptrigger_lapdist_dls’
A diagnosis window opens in Main Area.

154 / 200

DDU_10_Manual

Bosch MotorsportLap Trigger | 17

Button to reset lap distance to 0
Button to reset lap counter
Button to reset outing counter
Button to generate trigger signal
Button to reset best lap time
Button to reset best lap time anddistance-based segmentation

Lap trigger diagnosis scheme

17.1.7 Lap trigger presettings
When the reset buttons on the diagnosis page are activated, these values are used.

Preset values for lap counterand outing counter
Minimum laptime that a new'best laptime' is accepted
Preset value for 'best laptime'

17.2 Counting outing/laps/fragments

Functionality– Power ON: system + measurement is initialized but not yet started
Bosch Motorsport

DDU_10_Manual

155 / 200

17 | Lap Trigger– Global start condition fulfilled: recording starts– Reception of valid lap trigger: recording of lap completed, new lap starts– Power OFF or Global start condition not fulfilled: recording of lap completed, system
shutdown
The system is counting:Outing:– The outing counter is incremented with each power cycle when at least one valid lap(not by forced lap trigger) was recorded
Lap:– Leaving the pits to lap trigger– Lap trigger to lap trigger– Enforced lap trigger (see Distance based forced trigger [} 158])
Fragment:– Test bench operation– Power cycle on track or box (e.g. engine stalled)– File fragmentation size [MB], time [sec]Channels for display
To display counters use the following channels:
ChannelFunction

Laptrigger_outcnt_dls

Outing counter

Laptrigger_lapctr_dls

Lap counter

FractrFragment counter

Counting in WinDarab
To automatically name recorded files use filename templates in WinDarab dialog:
Filename template

Function[outing]

Value of outing counter[lap]

Value of lap counter[fragment]

Value of fragment counter[###03] indicates: ‘always use 3 digits with leading zeros’.

17.3 Lap timing
There are different possibilities to adjust the lap trigger to the timing situation.
The detection time defines the minimum time the input signal changes its state. E.g. a low
active signal needs to be below the threshold for min. 15 ms to release the trigger.

Channels for display
To display lap times use the following channels:

156 / 200

ChannelFunction

Laptrigger_lapctr_dls

Number of completed laps

DDU_10_Manual

Bosch MotorsportLap Trigger | 17

ChannelFunction

Laptrigger_laptime_dls

Running laptime

Laptrigger_laptime_best_dls

Laptime of best lap

Laptrigger_laptimeold_dls

Laptime of last lap completed

Laptrigger_laptimeseg_dls

Segment time of last segment

Laptrigger_lapctr_dls

Number of completed laps

17.3.1 Time based retrigger protection
Trigger is locked for 5 s after main trigger was received.
To deactivate time based retrigger protection, set ‘Retrigger lock time’ to 0 ms.
Define settings for lap timing(main trigger).
Define settings for sub trigger.
Not applicable with a GPS lap trigger.

5000msMain Trigger

17.3.2 Distance based retrigger protection
Trigger is locked until configured min distance (i.e. 80 % → 3200 m) of track distance (i.e.
4000 m) has been covered. To deactivate distance based retrigger protection, set min distance to 0 %.
Change signal for vehicle speed,
if desired.
Enter minimum speed fortrigger release.
Define settings for distancebased retrigger protection.

Define settings for distancebased forced trigger.

Bosch Motorsport

DDU_10_Manual

157 / 200

17 | Lap Trigger

Trigger prohibited
Main Trigger

17.3.3 Distance based forced trigger
After a missed main trigger, a forced trigger is inserted, if the configured max. distance(i.e. 120 % → 4800 m) of the track distance (i.e. 4000 m) has been reached. In this case, thechannel ‘Laptrigger_distlap_dls’ starts at the delta between the max. distance and the track
distance (i.e. 800 m).
To deactivate distance based forced triggers, uncheck box.
Change signal for vehicle speed,
if desired.
Enter minimum speed fortrigger release.
Define settings for distancebased retrigger protection.

Define settings for distancebased forced trigger.

17.4 Segment timing
Segment timing is the calculation of elapsed time for parts of laps (segments).
Segments are defined:– based on sub-trigger signals (additional transmitters)– based on distance travelled
Times for segments are compared to:– Last lap completed– Fastest lap

158 / 200

DDU_10_Manual

Bosch MotorsportLap Trigger | 17

Channels for display
To display segment times use the following channels:
ChannelFunction

Laptrigger_lapdiff

Time difference between finished lap and last lap

Laptrigger_lapdiffb

Time difference between finished lap and best lap

Laptrigger_lapseg_dlast

Difference of lap segment time compared to last lap

Laptrigger_lapseg_dbest

Difference of lap segment time compared to best lap

17.4.1 Sub trigger mode
Using main trigger (20 ms pulse) at Start-Finish-Line. 3 sub triggers (40 ms pulse) positioned at 1,000 m, 2,000 m and 3,000 m.
To deactivate sub trigger mode uncheck box.
Define settings for lap timing(main trigger).
Define settings for sub trigger.
Not applicable with a GPS lap trigger.

Sub Trigger

Sub Trigger

Sub Trigger

Main Trigger

The sub trigger mode cannot be used with the GPS lap trigger.

17.4.2 Distance mode
Using main trigger (20 ms pulse) at Start-Finish-Line.
Set ‘Mode’ to ‘Distance’ and enter desired segment distances.
Segment time is automatically calculated at each segment. Time difference to last lap andfastest lap is automatically calculated at each segment.
To deactivate distance mode set ‘Mode’ to ‘None’.

Bosch Motorsport

DDU_10_Manual

159 / 200

17 | Lap Trigger

Define settings for segment
timing.

3000m

+0.1s
-0.1s
2000m

-0.2s
-0.3s

+0.2s
+0.1s
+0.1s

1000m

-0.2s

+0.1s

0.0s

-0.1s

-0.2s

Main Trigger

17.5 Countdown timer
Some race classes require a minimum time spent in the pits. An additional lap trigger Tx is
configured as a segment trigger positioned at pit entry. The trigger signal starts a timer
countdown.
The current value of the timer is stored in the variable Laptrigger_cntdown_dls which canbe displayed.

Define settings for countdown
timer.

160 / 200

DDU_10_Manual

Bosch MotorsportLap Trigger | 17

17.6 Automatic GPS Track Detection
With the GPS lap trigger, an automatic track detection can be activated by checking thehighlighted box in the lap trigger configuration at the GPS tab.
Activating this functionality will overwrite the GPS trigger point coordinates and the track
length with the values of a detected racetrack. The coordinates and the track length will
be grayed out in the tool.
The function will compare the current GPS position with the coordinates of the known
Racetracks list and use the closest GPS trigger point. If there are track variants with different track length, the system will adapt itself to the correct variant, if it is in the known
racetrack list, after ~three detected laps. Please note that the track length needs to bequite accurate, within +/- 100 m, to adapt itself to another variant.

The known Racetrack list can be found in the lap trigger configuration menu within the
Known Racetracks tab. It contains a built-in list and a user-defined list. Each track can be
activated or deactivated with the checkbox to manually set the variant if needed.
User defined tracks can either be added from scratch with the Add Track button or with
the Copy Track button as a modified version of a built in track. Both buttons will open thesame Edit Race Track menu.
In the menu a track name, length and the coordinates of the detection point is required.
The coordinates can be pulled from the GPS tab with the button “Get values …” or sent to
the GPS tab with the button “Set values …”. This allows an easy interaction with themanual GPS lap trigger mode.
The user-defined tracks will be part of the project. If the tracks are required in anotherproject, the lap trigger module can be ex-/imported into another project.

Bosch Motorsport

DDU_10_Manual

161 / 200

17 | Lap Trigger

Following signals are assigned to the function:
Laptrigger_trackdet_id

Signal will show the track name from the
Racetracks list as an enumeration or canshow the ID number as raw value. The enumerated name will also be visible in the logging.

Laptrigger_trackdet_laplen

Track length of the used track variant

Laptrigger_trackdet_lat

Latitude GPS coordinate of the used GPS
trigger point

Laptrigger_trackdet_long

Longitude GPS coordinate of the used GPS
trigger point

17.7 Predicted Laptime
The predicted laptime function allows to compare the current lap- and segment time withthe predicted time of an expected lap. Additionally, the function can estimate the laptimeof the current lap. This functionality is integrated in the laptrigger module in RaceCon.

17.7.1 Setting up the predicted laptime
To use the predicted laptime function you need to set up a laptrigger as described in thechapter Lap Trigger [} 149]. Under the ribbon “Segment timing”, you need to choose yoursegmentation mode which can either be distance or intermediate trigger based.

162 / 200

DDU_10_Manual

Bosch MotorsportLap Trigger | 17

Distance orIntermediate
TriggerEnter yoursegment timeand distanceEnter yourexpected
laptimeFor the distance mode, you need to check on an old lap or estimate how long it takes totravel the segment distance. Please enter those values into input field. The values can also
be copied and pasted to the input field from an excel sheet as a normal text. In the intermediate trigger, you just need to set the expected time the driver takes to reach the segment trigger.
Note
Please note that the segment time and length is always measured from the start line orwhere the main lap trigger is set.

17.7.2 Functionality and channel outputs
Following output channels are generated by the predicted laptime function.
Laptrigger_lapdiff_pred_dls

Laptime difference between the predicted
and the last laptime

Laptrigger_lapsegdiffpred_dls

lagseg difference between the last segment
and the predicted segment

Laptrigger_Lapcurrpred_dls

Estimated laptime of the current lap, basedon the predicted laptime and the predictedsegment deviations

The channel Laptrigger_lapdiff_pred_dls is updated as soon as the main lap trigger is received. Both other channels are updated as soon as the next segment distance is travelled,or the next intermediate trigger is received.

Bosch Motorsport

DDU_10_Manual

163 / 200

18 | GPS Sensor

18 GPS Sensor
18.1 GPS (Global Positioning System)
Space-based global navigation satellite system.
GPS provides positioning, navigation, and timing services to worldwide users.
GPS receiver (sensor) gives digital information about position (longitude, latitude, height),
ground speed, course, and status.

Two types of GPS receivers:
CAN output -> Read in messages via CAN Input of DDU 10 (not covered here)
Serial output -> Read in messages via RS232 Interface of DDU 10
Serial Interface is characterized by:Voltage levels: RS232 is standard (+/-12 V), UART (0 V/ 5 V) needs level shifter
Baud rate: 9,600 is standard for GPS, DDU 10 supports 1,200 to 115,200 baud. GPS Rx interface baud rate must match DDU 10 interface baud rate. DDU 10 Baud rate can be set
with the ‘GPS_BAUDRATE’ characteristic Data format: DDU 10 expects 8 data bits, no parity bit, 1 stop bit (8N1)

18.1.1 Serial interface characterization
Serial Interface is characterized by:Voltage levels: RS232 is standard (+/-12 V), UART (0 V/ 5 V) needs level shifter
Baud rate: 9,600 is standard for GPS, DDU 10 supports 1,200 to 115,200 baud. GPS Rx interface baud rate must match DDU 10 interface baud rate. DDU 10 Baud rate can be set
with the ‘GPS_BAUDRATE’ characteristic Data format: DDU 10 expects 8 data bits, no parity bit, 1 stop bit (8N1)

18.2 Protocol
DDU 10 expects NMEA Protocol (ASCII).
The following messages are decoded:
Message

Function

GGA

GPS fix information

GSA

Overall satellite data

GSV

Detailed satellite data

RMC

Recommended minimum data for GPS

VTG

Vector track and speed over the groundOn most GPS sensors, these messages are activated in the default configuration.

164 / 200

DDU_10_Manual

Bosch Motorsport

GPS Sensor | 18

18.3 Sensor recommendation
The system has been tested with the Navilock NL-8004P MD6 Serial PPS Multi GNSS Receiver. This sensor is based on a U-Blox 8 chipset and is fully configurable with theNavilock “U-Center” software. To use this sensor with Bosch Motorsport components thetransfer rate, the satellite system and the update rate need to be reconfigured. More information about the configuration can be found in the Appendix.

18.3.1 Configuration of the recommended Navilock
NL-8004P MD6 Serial PPS Multi GNSS Receiver
For the sensor configuration, the sensor needs to be connected to the Navilock software“U‑Center” which is available from Navilock free of charge. Navilock offers a USB connection cable for the sensor.
In “U-Center” click “View” – “Configuration View” to start the configuration. The following 3 points have to be changed:

Transfer Rate
– Click on “PRT (Ports)”.
– Change the baud rate to a fixed value, this value needs to meet the setting of RaceCon. For a good signal quality we recommend 115,200 baud.
– Click on “Send” to store the new setting in “U-Center”.

– Click on “CFG (Configuration)”.
– Click on “Send” to save the new setting on the sensor.

Bosch Motorsport

DDU_10_Manual

165 / 200

18 | GPS Sensor

Satellite System– Click on “GNSS (GNSS Config)”.
– Set the ticks as shown in the following picture.
– Click on “Send” to store the new setting in “U-Center”.
– As during configuration step 1, click on “CFG (Configuration)”.
– Click on“Send” to save the new setting on the sensor.

166 / 200

DDU_10_Manual

Bosch Motorsport

GPS Sensor | 18

Update Rate
– Click on “RATE (Rates)”.
– Change the “Measurement Period” to 55 ms.
– Change the “Navigation Rate” to 1 cyc.
– Values which lead to a lower frequency will lower the precision of the sensor, we recommend the mentioned values.
– Click on “Send” to store the new setting in “U-Center”.
– As during configuration step 1, click on “CFG (Configuration)”.
– Click on“Send” to save the new setting on the sensor.

Note
Sensor needs reception for visible signal.
It takes time to start the sensor.

18.4 Measurement labels
The decoded NMEA messages are copied to these DDU 10 measurement labels.
Measurement label

Function

gps_PDOP

Position Dilution Of Precision

gps_HDOP

Horizontal Dilution Of Precision

gps_VDOP

Vertical Dilution Of Precision

gps_lat

Latitude +/‐ [degree]

gps_longLongitude +/‐ [degree]

gps_elv

Antenna altitude above/below mean sea level (geoid) inmetersBosch Motorsport

gps_speed

Speed over the ground in kilometers/hour

gps_direction

Track angle in degrees
DDU_10_Manual

167 / 200

18 | GPS Sensor

Measurement label

Function

gps_declination

Magnetic variation degrees (Easterly var. subtracts from truecourse)gps_yearYears since 1900

gps_monMonths since January - [0,11]

gps_day

Day of the month - [1,31]

gps_hour

Hours since midnight - [0,23]

gps_min

Minutes after the hour - [0,59]

gps_sec

Seconds after the minute - [0,59]

gps_hsec

Hundredth part of second - [0,99]

gps_smask

Bit mask over received NMEA sentences (Bit 0 = GGA, Bit 1 =GSA, Bit 2 =GSV, Bit 3 = RMC, Bit 4 =VTG) within last second.

gps_sig

GPS quality indicator (0 = Invalid; 1 = Fix; 2 = Differential, 3 =Sensitive)

gps_fix

Operating mode, used for navigation (1 = Fix not available; 2= 2D; 3 = 3D)

These measurement labels are arrays, where the indexed element points to the same
satellite.
(E.g. gps_info_satsigstrength[3] tells the receiving signal strength of satellite 3. Satellite 3
has the SAT-ID given in gps_info_satid[3])Measurement label

Function

gps_info_satid[ ]Satellite PRN number

gps_info_satinuse[ ]Used in position fix

gps_info_satelevation[ ]Elevation in degrees, 90 maximum

gps_info_satazimuth[ ]Azimuth, degrees from true north, 000 to 359

gps_info_satsigstrength[ ] Signal, 00-99 dB

18.5 GPS troubleshooting
Electrical
Is the transmitter signal of the GPS sensor connected to the receiver pin of serial interfaceof the DDU 10?
Is the GPS sensor powered up?
Does the GPS sensor deliver RS232 signal levels?
Is the sensor connected to the „sensor ground“ of the device?

Interface
Do the baud rates of the GPS sensor and the DDU 10 match?
Is the GPS sensor set up for 8N1 transmission parameters?
Is the GPS sensor set up for NMEA messages?
Are the GGA, VTG, RMC messages activated?

168 / 200

DDU_10_Manual

Bosch Motorsport

GPS Sensor | 18

GPS sensor start-up
Does the GPS sensor ‘view’ the sky?
Did the GPS sensor complete its initial start-up procedure? This may take up to 20 min.
A correct reception is indicated when ‘gps_fix’ is showing ‘3D Fix’.

GPS sensor values are frozen
Does the sensor has lost its reception? The old values will be kept if the reception is lost.
The gps_smask channel shows which NMEA sentence is received.

Bosch Motorsport

DDU_10_Manual

169 / 200

19 | Telemetry System LTE 65

19 Telemetry System LTE 65– Support for long-range online telemetry– Individual programmable team code
– Fast block – slow block mechanism– Programmable data rate
– Ethernet or RS232 interface– Full online track coverage on almost all tracks

19.1 Software setup
Drop Telemetry from Toolbox into system overview.

Adding channels to telemetry
1.

Expand the list of ‘Loggers’ by clicking on ‘+’ in the DDU 10 Project Tree.

2.

Double-click on ‘Recording’ in DDU 10 Project Tree.
The recording configuration is displayed in the Main Area.

3.

Click ‘Edit channel(s)’.
The ‘Edit Recording Channels’ window appears.

4.

Choose between ‘Fast/Slow block’ transmission.

Using fast block/slow block transmission
DDU 10 telemetry has a bandwidth 200 kBit/s, the used bandwith can be adjusted to copewith the transmitting system. The bandwidth has to be divided into channel information
to be transmitted high-frequently and low-frequently using the ‘fast/ slow block’ setting.
Channels are grouped into 8 blocks which are transferred each cycle:– Fast block (Block 1) is transferred every cycle and used for a high-frequent transmission of channel information (e.g. speed, rpm).
– Slow blocks (Block 2…n) are transferred every n-th cycle and used for a low-frequenttransmission of channel information (e.g. tire pressure, oil temperature).

170 / 200

DDU_10_Manual

Bosch MotorsportTelemetry System LTE 65 | 19

Transmission Scheme

None – channel(s) are not transferred
Slow – channel(s) are transferred in the slow telemetry block
Fast – channel(s) are transferred in the fast telemetry block

If the maximum bandwidth of a block is reached, a warning will be displayed. To fix thisproblem you can view the allocation of the channels and data rate in the ‘Statistics’ tab of
the Main Area.

19.2 Telemetry channels with special functionality
The Telemetry system allows the transmission of special information such as running distance of current lap, lap number of current lap and lap time, fuel consumption of last lap
completed. You have to assign the channel type to the telemetry channel so that it is recognized accurately by RaceCon.
Channel's names are e.g.: Laptrigger_lapdist_dls, fuelcons, lapctr, Laptrigger_lapdist_dls.
Different channel names are possible between different devices (e.g. ECU MS6, laptrigger
module used in RaceCon).
For displaying the position of the car in the cloud, additionally GPS-position and lapdist
can be send to the cloud, this is activated with the checkbox “cloud statistics”.

Bosch Motorsport

DDU_10_Manual

171 / 200

19 | Telemetry System LTE 65

1.

Assign the desired channels to the channel types. The table below shows the functionof the available channel types.

2.

Click ‘Ok’ when done.

Measurement channel

Function

Distance

Running distance of current lap

Lap number

Lap number of current lap

Lap fuel

Fuel consumption of last lap completed

Lap time

Exact lap time of lap completed

The telemetry channels and their assigned channel types are displayed in the overview list.

19.3 Setting up car in WDServer
WDServer is a program used to capture data streaming from a transmitter and convert to
WinDarab; WDServer also creates a log of the data received over telemetry.

172 / 200

DDU_10_Manual

Bosch MotorsportTelemetry System LTE 65 | 19

1.

To set up a new car, select ‘Add Car’.

2.

In the Car settings tab, enter a name for the new vehicle.
This name will be used as a part of the file name for WDServer’s log of received telemetry data and will show up in WinDarab, when searching for the telemetry stream in
the Network folder.

3.

You are now at the final step of configuring the telemetry stream. In order for thedata to be decrypted by WDServer, two *.ini files must be referenced by WDServer.
After the configuration is sent to the logger, these two different *.ini files will be created in the base folder. You can find the base WDServer folder, if you right-click the
Telemetry and select ‘Properties’. You can change this folder location for easier access
if desired.

4.

Define the link to the folder of the *.ini files for each car or define it in the general
WDServer settings, under the ‘Telemetry’ tab.

Bosch Motorsport

DDU_10_Manual

173 / 200

19 | Telemetry System LTE 65

5.

Under the ‘UDP’ tab, select the drop-down menu and type in “UDP”.

6.

For the UDP Port, type in the port number assigned to the device in RaceCon.
Each vehicle being read by a single receiver device must have a unique port number.
This information will be provided by Bosch upon delivery of the devices.

7.

174 / 200

Click ‘OK’, to close the window.

DDU_10_Manual

Bosch MotorsportTelemetry System LTE 65 | 19

8.

Select the button ‘WDServer Settings’.

9.

Under the ‘Common’ tab, choose directories where WDServer can store its temporary
files and log files. These are created during telemetry reception and can be used tohelp diagnose issues.

Under the ‘Telemetry’ tab, the first section requests a folder path for the DCP- Configuration files. This is the folder path where RaceCon stored the *.ini files required by WDServer.
1.

Click on the “Change” button next to this section and navigate to this folder.
A template can also be specified for the file nomenclature for logged telemetry as
well as a save location.

Bosch Motorsport

DDU_10_Manual

175 / 200

19 | Telemetry System LTE 65– To ensure proper communication between WDServer and the receiver, do not delete
any old *.ini files from this folder path. As mentioned in section 5, RaceCon will generate a new *.ini file each time a project is synchronized; each new *.ini file instance has
an incremented file name. Retaining all of these *.ini file iterations will ensure that
WDServer always has a reference to whichever configuration is programmed into yourvehicle’s logger system.
– If the RaceCon project for the vehicle resides on a different computer, than that which
is used for telemetry, then all *.ini files for a given project should be transferred to thetelemetry computer after every data synchronization in RaceCon. WDServer may havetrouble recognizing *.ini files stored on removable media, so best practice is to copy
these files to the telemetry computer’s hard drive.

19.4 Loading the telemetry data
The following is an example of a file name and data format for Car #91. File is typicallylocated in WinDarab/Config/WDServer:In the File Explorer, click ‘Open’ and navigate to the data set. Under ‘Network’, search forthe car or cars that are required for viewing.
176 / 200

DDU_10_Manual

Bosch MotorsportFirmware | 20

20 Firmware
20.1 Firmware and configuration
DDU 10 holds 2 types of data:
Firmware: The software (PST program file) of the DDU 10.
Configuration: The default parameters for controlling the output of the DDU 10.

20.2 Firmware update
Firmware updates are performed via XCP. Following standards are supported:– ASAM MCD-1 (XCP); Version 1.5.0; Date: 2017-11-30– ASAM MCD-2 MC (ASAP2 / A2L); Version 1.7.1; Date: 2018-01-30
Additional files for firmware update (like ProF-Scripts for INCA) will be provided by
BOSCH.

Bosch Motorsport

DDU_10_Manual

177 / 200

21 | Cloning the Unit

21 Cloning the Unit
Chapter left intentionally blank

178 / 200

DDU_10_Manual

Bosch Motorsport

Fuel Consumption Calculation | 22

22 Fuel Consumption Calculation
22.1 Setting up fuel consumption calculation andtank management
1.

Select ‘Measurement Sources’ in Toolbox.

2.

Drag ‘Fuel’ element and drop it on the vehicle in System Overview. Do not drop it on
the DDU 10!

Drag + DropA ‘fuel consumption wizard‘ opens.

a)
b)
c)
d)
e)

f)

g)

a) Change device for fuel calculation, if desired.
b) Enter tank capacity of vehicle.
c) Choose calculation mode:
Bosch Motorsport

DDU_10_Manual

179 / 200

22 | Fuel Consumption Calculation– using fuel consumed (summed-up fuel consumption)– using fuel flow rate (momentary fuel consumption)d) Choose input channel and enter adaption factor. Use adaption factor to adapt value of
input channel to:– 1ml per inc for summed-up fuel consumption– 1ml/s per inc for momentary consumptione) Enter factor to correct calculated consumption in device vs. ‘real’ consumption ofvehicle, if required.
f) Choose method to calculate remaining laps with fuel in tank, if desired:– using fuel consumption of last lap completed– using target lap consumption (entered in the field ‘Target lap consumption’)g) Choose values to initiate a reset of fuel consumption, if desired:– Manually using RaceCon– On ‘power down’ (assuming that the tank is filled each time the ignition is turned off)
– By signal source as input channel (e.g. a switch connected to input pin)
Press ‘Finish’ when done.

22.2 Fuel consumption diagnosis/counter reset
To display a fuel consumption diagnosis and to reset counters, use the diagnosis page in
RaceCon.
Double-click on any ‘fuel_xxx’ channel in channel list.
A diagnosis window opens in Main Area.
Button to reset total
fuel consumption(Reset with RaceCon
only)
Button to reset fuelconsumption manually(Can also be triggered )Settings
overview

180 / 200

DDU_10_Manual

Bosch Motorsport

Fuel Consumption Calculation | 22

ExampleBosch Motorsport

Measurement label

Function

Fuel_fuelcons_dls

Running fuel consumption, starting at ‘0’

Fuel_fuelrem_dls

Remaining fuel in tank, starting at tank capacity

Fuel_fuellap_dls

Fuel consumption for current lap, starting at ‘0’

Fuel_fuellapold_dls

Fuel consumption of last lap completed

Fuel_laprem_dls

Remaining laps with fuel in tank

DDU_10_Manual

181 / 200

23 | RaceCon Shortcuts

23 RaceCon Shortcuts
The table shows important shortcuts simplify controlling the DDU 10 in RaceCon.
Shortcut

Function

General navigation
F1

Open RaceCon help

F2

Rename selected object

F3

Select Data Area

F4

Select Project Tree

F5

-

F6

Start the data comparison

F7

Start dataset manager

F8

Toggle WP/RP

F9Start measurement

CTRL + F9

Start recording

F10 or Alt

Go to menu bar

F11

Toggle display to fullscreen ‘Race Mode’

F12

Enlarge main screen

CTRL + Tab

Switch between opened windows

Project Tree
Plus (+) at numeric pad

Expand selected nodeor right cursor
Minus (-) at numeric pad

Close selected nodeor left cursor
Star (*) at numeric padOpen all nodes

DEL

Delete seleted object

Display page, measurement page
CursorMove selected display element one grid unit in chosen direction

182 / 200

SHIFT + cursor

Enlarge/reduce selected display element one grid unit

Tab

Switch between display elements

DDU_10_Manual

Bosch MotorsportLegal | 24

24 Legal
24.1 Legal Restrictions of Sale
The sale of this product in Mexico is prohibited.
Due to embargo restrictions, sale of this product in Russia, Belarus, Iran, Syria, and North
Korea is prohibited.

24.2 Open Source Software (OSS) Declaration for
the Display
These third party software components are used within the Graphic Rendering Engine.

24.2.1 antlr-2.7.7.jar License
ANTLR-2.7.7

SOFTWARE RIGHTSANTLR 1989-2006 Developed by Terence Parr
Partially supported by University of San Francisco & jGuru.com

We reserve no legal rights to the ANTLR--it is fully in the public domain. An individual orcompany may do whatever they wish with source code distributed with ANTLR or thecode generated by ANTLR, including the incorporation of ANTLR, or its output, into commercial software.

We encourage users to develop software with ANTLR. However, we do ask that credit isgiven to us for developing ANTLR. By "credit", we mean that if you use ANTLR or incorporate any source code into one of your programs (commercial product, research project,
or otherwise) that you acknowledge this fact somewhere in the documentation, research
report, etc... If you like ANTLR and have developed a nice tool with the output, pleasemention that you developed it using ANTLR. In addition, we ask that the headers remain
intact in our source code. As long as these guidelines are kept, we expect to continue enhancing this system and expect to make other tools available as they are completed.

The primary ANTLR guy:

Terence Parr
parrt@cs.usfca.edu
parrt@antlr.org

Bosch Motorsport

DDU_10_Manual

183 / 200

24 | Legal

24.2.2 antlr311runtime.jar License
ANTLR-3.1.1

ANTLR 3 License[The BSD License]
Copyright (c) 2010 Terence Parr
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.
Neither the name of the author nor the names of its contributors may be used to endorse
or promote products derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANYWAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

24.2.3 BSD 3-Clause License (getsubopt)
The NetBSD getsubopt argument parsing function is used by Graphic Engine plugins toparse plugin options.
Applies To:
libgre.dll, libgre.a
The Graphic Runtime engines used on most operating systems, including all Windows
platforms (win32).
Copyright (c) 1990, 1993
The Regents of the University of California. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
184 / 200

DDU_10_Manual

Bosch MotorsportLegal | 24

1.

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2.

Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.

3.

Neither the name of the University nor the names of its contributors may be used toendorse or promote products derived from this software without specific prior written
permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

24.2.4 BSD 4-Clause License (getopt)
The NetBSD getopt argument parsing function is used to parse command line arguments.
The Graphic Runtime engines used on all Windows platforms (win32, wince, wincompact7,
wec2013) includes the getopt source from the NetBSD operating system distribution.
Copyright (c) 1987, 1993, 1994
The Regents of the University of California. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2.

Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.

3.

All advertising materials mentioning features or use of this software must display thefollowing acknowledgement:This product includes software developed by the University of California, Berkeley andits contributors.

4.

Neither the name of the University nor the names of its contributors may be used toendorse or promote products derived from this software without specific prior written
permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY
EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE AREDISCLAIMED. IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
Bosch Motorsport

DDU_10_Manual

185 / 200

24 | Legal

CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE
USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

24.2.5 crc32 License
Copyright (c) 2003 Markus Friedl. All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2.

Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR “AS IS” AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISEDOF THE POSSIBILITY OF SUCH DAMAGE.

24.2.6 EZXML License
The ezxml library (ezxml.sourceforge.net) provides XML model parsing support for theGraphic Engine.
Applies To:
libgre.dll, libgre.a
The ezxml xml parsing library is used by all Graphic Engine runtime configurations
Copyright 2004-2006 Aaron Voisine aaron@voisine.org

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom
the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies orsubstantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL

186 / 200

DDU_10_Manual

Bosch MotorsportLegal | 24

THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

24.2.7 FreeType License
The FreeType Project's www.freetype.org) library is used by the Graphic Engine for nonbitmap font rendering.
Applies To:
All Graphic Runtime Engines using sbfreetype libraries
Applies To:
librender-plugin-*.dll, librender-plugin-*.a
Unless explicitly configured, all Graphic Engine render plugins link against the FreeTypelibraries.
Portions of this software are copyright © <2011> The FreeType Project (www.freetype.org). All rights reserved.

Legal Terms
0. Definitions
Throughout this license, the terms `package', `FreeType Project', and `FreeType archive'
refer to the set of files originally distributed by the authors (David Turner, Robert Wilhelm,
and Werner Lemberg) as the `FreeType Project', be they named as alpha, beta or final release.
`You' refers to the licensee, or person using the project, where `using' is a generic term including compiling the project's source code as well as linking it to form a `program' or`executable'. This program is referred to as `a program using the FreeType engine'.
This license applies to all files distributed in the original FreeType Project, including all
source code, binaries and documentation, unless otherwise stated in the file in its original,
unmodified form as distributed in the original archive. If you are unsure whether or not aparticular file is covered by this license, you must contact us to verify this.
The FreeType Project is copyright (C) 1996-2000 by David Turner, Robert Wilhelm, andWerner Lemberg. All rights reserved except as specified below.
1.

No Warranty
THE FREETYPE PROJECT IS PROVIDED `AS IS' WITHOUT WARRANTY OF ANY KIND,
EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, WARRANTIES OF
MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT WILLANY OF THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY DAMAGESCAUSED BY THE USE OR THE INABILITY TO USE, OF THE FREETYPE PROJECT.

2.

Redistribution
This license grants a worldwide, royalty-free, perpetual and irrevocable right and license to use, execute, perform, compile, display, copy, create derivative works of, distribute and sublicense the FreeType Project (in both source and object code forms)
and derivative works thereof for any purpose; and to authorize others to exercise
some or all of the rights granted herein, subject to the following conditions:

Bosch Motorsport

DDU_10_Manual

187 / 200

24 | Legal– Redistribution of source code must retain this license file (`FTL.TXT') unaltered;any additions, deletions or changes to the original files must be clearly indicatedin accompanying documentation. The copyright notices of the unaltered, original
files must be preserved in all copies of source files.
– Redistribution in binary form must provide a disclaimer that states that the software is based in part of the work of the FreeType Team, in the distribution documentation. We also encourage you to put an URL to the FreeType web page inyour documentation, though this isn't mandatory.
These conditions apply to any software derived from or based on the FreeType Project, not just the unmodified files. If you use our work, you must acknowledge us.
However, no fee need be paid to us.
3.

Advertising
Neither the FreeType authors and contributors nor you shall use the name of theother for commercial, advertising, or promotional purposes without specific priorwritten permission.
We suggest, but do not require, that you use one or more of the following phrases torefer to this software in your documentation or advertising materials: `FreeType Project', `FreeType Engine', `FreeType library', or `FreeType Distribution'.
As you have not signed this license, you are not required to accept it. However, as the
FreeType Project is copyrighted material, only this license, or another one contractedwith the authors, grants you the right to use, distribute, and modify it. Therefore, byusing, distributing, or modifying the FreeType Project, you indicate that you understand and accept all the terms of this license.

24.2.8 GNU LESSER GENERAL PUBLIC LICENSE (pthreadwin32)
Applies To:
All Graphic Runtime Engines using Windows operating systems
Applies To:
pthreadVC2.dll, pthreadVC2.lib
This provides POSIX pthread API functionality in a Windows environment (win32, wince,
wincompact7, wec2013).
Project Page: https://www.sourceware.org/pthreads-win32/
pthreads-win32 - a POSIX threads library for Microsoft Windows

This file is Copyrighted
This file is covered under the following Copyright:
Copyright (C) 2001,2006 Ross P. Johnson
All rights reserved.
Everyone is permitted to copy and distribute verbatim copies of this license document,
but changing it is not allowed.

188 / 200

DDU_10_Manual

Bosch MotorsportLegal | 24

Pthreads-win32 is covered by the GNU Lesser General Public
LicensePthreads-win32 is open software; you can redistribute it and/or modify it under the termsof the GNU Lesser General Public License as published by the Free Software Foundation
version 2.1 of the License.
Pthreads-win32 is several binary link libraries, several modules, associated interface definition files and scripts used to control its compilation and installation.
Pthreads-win32 is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
See the GNU Lesser General Public License for more details.
A copy of the GNU Lesser General Public License is distributed with pthreads-win32 under
the filename:
COPYING.LIB
You should have received a copy of the version 2.1 GNU Lesser General Public Licensewith pthreads-win32; if not, write to:Free Software Foundation, Inc.
59 Temple Place
Suite 330
Boston, MA 02111-1307
USA
The contact addresses for pthreads-win32 is as follows:
Web: http://sources.redhat.com/pthreads-win32
Email: Ross Johnson
Please use: Firstname.Lastname@homemail.com.au

Pthreads-win32 copyrights and exception files
With the exception of the files listed below, Pthreads-win32 is covered under the following GNU Lesser General Public License Copyrights:
Pthreads-win32 - POSIX Threads Library for Win32
Copyright(C) 1998 John E. Bossom
Copyright(C) 1999,2006 Pthreads-win32 contributors
The current list of contributors is contained in the file CONTRIBUTORS included with thesource code distribution. The current list of CONTRIBUTORS can also be seen at the following WWW location:
http://sources.redhat.com/pthreads-win32/contributors.html
Contact Email: Ross Johnson
Please use: Firstname.Lastname@homemail.com.au
These files are not covered under one of the Copyrights listed above:
COPYINGCOPYING.LIB
tests/rwlock7.cBosch Motorsport

DDU_10_Manual

189 / 200

24 | Legal

This file, COPYING, is distributed under the Copyright found at the top of this file. It is important to note that you may distribute verbatim copies of this file but you may notmodify this file.
The file COPYING.LIB, which contains a copy of the version 2.1 GNU Lesser General Public
License, is itself copyrighted by the Free Software Foundation, Inc. Please note that theFree Software Foundation, Inc. does NOT have a copyright over Pthreads-win32, only the
COPYING.LIB that is supplied with pthreads-win32.
The file tests/rwlock7.c is derived from code written by Dave Butenhof for his book 'Programming With POSIX(R) Threads'. The original code was obtained by free download fromhis website http://home.earthlink.net/~anneart/family/Threads/source.html and did notcontain a copyright or author notice. It is assumed to be freely distributable.
In all cases one may use and distribute these exception files freely. And because one may
freely distribute the LGPL covered files, the entire pthreads-win32 source may be freely
used and distributed.

General Copyleft and License info
For general information on Copylefts, see:
http://www.gnu.org/copyleft/
For information on GNU Lesser General Public Licenses, see:
http://www.gnu.org/copyleft/lesser.html
http://www.gnu.org/copyleft/lesser.txt

Why pthreads-win32 did not use the GNU General Public License
The goal of the pthreads-win32 project has been to provide a quality and complete implementation of the POSIX threads API for Microsoft Windows within the limits imposed byvirtue of it being a stand-alone library and not linked directly to other POSIX compliant
libraries. For example, some functions and features, such as those based on POSIX signals,
are missing.
Pthreads-win32 is a library, available in several different versions depending on supported
compilers, and may be used as a dynamically linked module or a statically linked set ofbinary modules. It is not an application on it's own.
It was fully intended that pthreads-win32 be usable with commercial software not coveredby either the GPL or the LGPL licenses. Pthreads-win32 has many contributors to it's code
base, many of whom have done so because they have used the library in commercial or
proprietry software projects.
Releasing pthreads-win32 under the LGPL ensures that the library can be used widely,while at the same time ensures that bug fixes and improvements to the pthreads-win32
code itself is returned to benefit all current and future users of the library.
Although pthreads-win32 makes it possible for applications that use POSIX threads to beported to Win32 platforms, the broader goal of the project is to encourage the use ofopen standards, and in particular, to make it just a little easier for developers writing
Win32 applications to consider widening the potential market for their products.

24.2.9 log4j.jar License
The Apache Software License, Version 1.1

190 / 200

DDU_10_Manual

Bosch MotorsportLegal | 24

Copyright (C) 1999 The Apache Software Foundation. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2.

Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.

3.

The end-user documentation included with the redistribution, if any, must include thefollowing acknowledgment: "This product includes software developed by the Apache
Software Foundation (http://www.apache.org/)." Alternately, this acknowledgment
may appear in the software itself, if and wherever such third-party acknowledgments
normally appear.

4.

The names "log4j" and "Apache Software Foundation" must not be used to endorse
or promote products derived from this software without prior written permission. For
written permission, please contact apache@apache.org.

5.

Products derived from this software may not be called "Apache", nor may "Apache"appear in their name, without prior written permission of the Apache Software Foundation.

THIS SOFTWARE IS PROVIDED ``AS IS'' AND ANY EXPRESSED OR IMPLIED WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY
AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE
APACHE SOFTWARE FOUNDATION OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT,INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSSOF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON
ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
This software consists of voluntary contributions made by many individuals on behalf of
the Apache Software Foundation. For more information on the Apache Software Foundation, please see <http://www.apache.org/>.
/

24.2.10 Lua License
The Lua engine (http://www.lua.org) provides a script interface for manipulating content
in a Graphic application.
Applies To:
libgre-plugin-lua.dll, libgre-plugin-lua.a
The Lua Graphic Engine plugin
License for Lua 5.0 and later versions
Copyright © 1994-2008 Lua.org, PUC-Rio. Permission is hereby granted, free of charge, toany person obtaining a copy of this software and associated documentation files (the"Software"), to deal in the Software without restriction, including without limitation therights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the

Bosch Motorsport

DDU_10_Manual

191 / 200

24 | Legal

Software, and to permit persons to whom the Software is furnished to do so, subject tothe following conditions: The above copyright notice and this permission notice shall be
included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALLTHE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

24.2.11 opencsv License
opencsv http://opencsv.sourceforge.net sconway@users.sourceforge.net arjones@t-online.de

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1.

Definitions.
"License" shall mean the terms and conditions for use, reproduction, and distribution
as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by the copyrightowner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposesof this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications, including but
not limited to software source code, documentation source, and configuration files.
"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated
documentation, and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or Object form, madeavailable under the License, as indicated by a copyright notice that is included in or

192 / 200

DDU_10_Manual

Bosch MotorsportLegal | 24

attached to the work (an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object form, that isbased on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work ofauthorship. For the purposes of this License, Derivative Works shall not include works
that remain separable from, or merely link (or bind by name) to the interfaces of, theWork and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including the original version of
the Work and any modifications or additions to that Work or Derivative Works
thereof, that is intentionally submitted to Licensor for inclusion in the Work by the
copyright owner or by an individual or Legal Entity authorized to submit on behalf ofthe copyright owner. For the purposes of this definition,"submitted" means any form of electronic, verbal, or written communication sent to
the Licensor or its representatives, including but not limited to communication onelectronic mailing lists, source code control systems, and issue tracking systems thatare managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution.""Contributor" shall mean Licensor and any individual or Legal Entity on behalf ofwhom a Contribution has been received by Licensor and subsequently incorporated
within the Work.
2.

Grant of Copyright License. Subject to the terms and conditions of this License, eachContributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge,
royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3.

Grant of Patent License. Subject to the terms and conditions of this License, eachContributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge,
royalty-free, irrevocable (except as stated in this section) patent license to make, have
made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institutepatent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to
You under this License for that Work shall terminate as of the date such litigation is
filed.

4.

Redistribution. You may reproduce and distribute copies of the Work or Derivative
Works thereof in any medium, with or without modifications, and in Source or Object
form, provided that You meet the following conditions:(a) You must give any other recipients of the Work or Derivative Works a copy of thisLicense; and(b) You must cause any modified files to carry prominent notices stating that Youchanged the files; andBosch Motorsport

DDU_10_Manual

193 / 200

24 | Legal(c) You must retain, in the Source form of any Derivative Works that You distribute, allcopyright, patent, trademark, and attribution notices from the Source form of theWork excluding those notices that do not pertain to any part of the Derivative Works;
and(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain toany part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not
modify the License. You may add Your own attribution notices within Derivative
Works that You distribute, alongside or as an addendum to the NOTICE text from theWork, provided that such additional attribution notices cannot be construed as modifying the License.
You may add Your own copyright statement to Your modifications and may provide
additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided
Your use, reproduction, and distribution of the Work otherwise complies with theconditions stated in this License.
5.

Submission of Contributions. Unless You explicitly state otherwise, any Contribution
intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the termsof any separate license agreement you may have executed with Licensor regarding
such Contributions.

6.

Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing thecontent of the NOTICE file.

7.

Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS
IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You aresolely responsible for determining the appropriateness of using or redistributing theWork and assume any risks associated with Your exercise of permissions under this License.

8.

Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of theuse or inability to use the Work (including but not limited to damages for loss of
goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

194 / 200

DDU_10_Manual

Bosch MotorsportLegal | 24

9.

Accepting Warranty or Additional Liability. While redistributing the Work or Derivative
Works thereof, You may choose to offer, and charge a fee for, acceptance of support,
warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf
and on Your sole responsibility, not on behalf of any other Contributor, and only if
You agree to indemnify, defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason of your accepting
any such warranty or additional liability.

END OF TERMS AND CONDITIONS

24.2.12 Sensor Driver for BMI160 Sensor
Copyright (c) 2021 Bosch Sensortec GmbH. All rights reserved.

BSD-3-Clause

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1.

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2.

Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.

3.

Neither the name of the copyright holder nor the names of its contributors may be
used to endorse or promote products derived from this software without specificprior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANYWAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

24.2.13 SharpZipLib License
SharpZipLib 0.86.0 © Mike Krueger and John Reilly https://github.com/icsharpcode/
SharpZipLib

MIT License=======================================

Bosch Motorsport

DDU_10_Manual

195 / 200

24 | Legal

Copyright © 2000-2016 SharpZipLib Contributors

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom
the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies orsubstantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALLTHE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

24.2.14 Simple OpenGL Library License (SOIL)
The SOIL library (http://www.lonesock.net/soil.html) is used to load images in a Graphic
application.
Applies To:
libgre.dll, libgre.a
The SOIL image library is used by all Graphic Engine runtime configurations
Jonathan Dummer
2007-07-26-10.36
Simple OpenGL Image Library
Public Domainusing Sean Barret's stb_image as a baseThanks to:* Sean Barret - for the awesome stb_image* Dan Venkitachalam - for finding some non-compliant DDS files, and patching some explicit casts* everybody at gamedev.net

24.2.15 stringtemplate License[The "BSD licence"]
Copyright (c) 2003-2008 Terence Parr
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

196 / 200

DDU_10_Manual

Bosch MotorsportLegal | 24

1.

Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

2.

Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution.

3.

The name of the author may not be used to endorse or promote products derived
from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE AUTHOR ``AS IS'' AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO
EVENT SHALL THE AUTHOR BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL,EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR
BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY,
WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISEDOF THE POSSIBILITY OF SUCH DAMAGE.

24.2.16 xml_io_tools License
xml_io_tools

Copyright (c) 2007, Jaroslaw Tuszynski
All rights reserved.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

– Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
– Redistributions in binary form must reproduce the above copyright notice, this list of
conditions and the following disclaimer in the documentation and/or other materials
provided with the distribution

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS "AS
IS" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT,STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANYWAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
SUCH DAMAGE.

Bosch Motorsport

DDU_10_Manual

197 / 200

24 | Legal

24.2.17 Avalonia
The MIT License (MIT)Copyright (c) .NET Foundation and Contributors All Rights Reserved
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without
restriction, including without limitation the rights to use, copy, modify, merge, publish,
distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom
the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies orsubstantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALLTHE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR
OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE,
ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR
OTHER DEALINGS IN THE SOFTWARE.

24.3 REACH Statement
According to the REACH regulations, any supplier of an article containing a substance ofvery high concern (SVHC) in a concentration above 0.1 % (w/w) has the duty to provide
the recipient of the article with sufficient information to allow safe use of the article. Our
product contains:

198 / 200

SVHC Substance

CAS Number

Lead monoxide (lead oxide)1317-36-8

Lead7439-92-1

DDU_10_Manual

Bosch Motorsport

Disposal | 25

25 Disposal
Hardware, accessories and packaging should be sorted for recycling in an environmentfriendly manner.
Do not dispose of this electronic device in your household waste.

Bosch Motorsport

DDU_10_Manual

199 / 200

Bosch Engineering GmbH
Motorsport
Robert-Bosch-Allee 174232 Abstattwww.bosch-motorsport.com