BOSCH Engine Control Unit MS 6 EVO User Manual

Engine Control Unit MS 6 EVO
User Manual

Getting Started

Disclaimer
Due to continuous enhancements we reserve the rights to change illustrations, photos or technical data within this manual. Please retain this manual for your records.
Before starting
Before starting your engine for the first time, install the complete software. Bosch
Motorsport software is developed for Windows operation systems. Read the manual carefully and follow the application hints step by step. Don’t hesitate to contact us.
Contact data can be found on the backside of this document.

CAUTION
Risk of injury if using the MS 6 EVO inappropriately.
Use the MS 6 EVO only as intended in this manual. Any maintenance or repair must be performed by authorized and qualified personnel approved by Bosch Motorsport.
CAUTION
Risk of injury if using the MS 6 EVO with uncertified combinations and accessories
Operation of the MS 6 EVO 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 is only permitted when they have been determined to be compliant from a performance and safety standpoint by a representative from Bosch Motorsport.
NOTICE
For professionals only
The Bosch Motorsport MS 6 EVO was developed for use by professionals and requires in depth knowledge of automobile technology and experience in motorsport. Using  the system does not come without its risks.
It is the duty of the customer to use the system for motor racing purposes only and not on public roads. We accept no responsibility for the reliability of the system on public roads. In the event that the system is used on public roads, we shall not be held responsible or liable for damages.

Technical Data

The MS 6 EVO engine control unit features a powerful digital processing dual- core with floating point arithmetic and a high-end field programmable gate array FPGA for  ultimate performance and flexibility.
The software development process is based on MATLAB® & Simulink®. It significantly speeds algorithm development by using automatic code and documentation  generation.
Custom functions can be generated quickly and easily. The flexible hardware design allows the MS 6 EVO to support complex or unusual engine or chassis configurations.  Integrated logger control areas present a cost efficient and weight optimized all-in-one solution.

2.1 System Layout

Layout restrictions

CAN Network| Extended number of members and wiring leads extend the risk of error frames
---|---
RS232| Limited to one additional component
USB| Limited to additional Bosch Motorsport USB stick
LIN| Permitted for the use of Bosch Motorsport preconfigured configur- ations
SENT| Use with preconfigured configurations that are available from Bosch Motorsport on request

2.2 Mechanical Data

Aluminum housing
2 automotive connectors, 196 pins in total
Vibration suppression via multipoint fixed circuit boards

2.3 Electrical Data

2.3.1 Inputs
The analogue inputs are divided in different hardware classes and qualities.
3.01 kOhm pull-ups are fixed or switchable designed to assist passive sensor elements like NTC temperature sensors or to change to active signal inputs.
Some of the inputs assist only active sensors and offer no pull-up.
To improve measurement tasks, angle related measurements are an option for some inputs, mainly used for engine related leading signals.
The connection between function and related input is free selectable, beside electronic throttle functionalities.
All linearization mappings are open to the customer, some signals offer online modes to calibrate gain and offset.
Digital inputs for speed measuring offer divers hardware options to connect inductive- or digital speed sensors.
Please respect: for camshaft- or wheel speed signals Hall-effect or DF11 sensors have to be used and for wide range Lambda measurement and control the Lambda sensor Bosch LSU 4.9 has to be used.
Standard number of Inputs; for additional channels see Structure of Devices and Licenses [9]

38 analog inputs (CUP: 26; 6.1, 6.3: 21)
6 x reserved for electronic throttle controls (Cup: 4)
10 x no integrated pull-up (Cup: 5; 6.1, 6.3: 3)
4 x option for angle synchronous measurement, no integrated pull-up (Cup, 6.1, 6.3: 3)
5 x fixed 3.01 kOhm pull-up (Cup, 6.1, 6.3: 4)
13 x switchable 3.01 kOhm pull-up (Cup: 10; 6.1, 6.3: 5)

8 analog/digital inputs (shared) (CUP, 6.1, 6.3: 0)
8 x option for angle synchronous measurement / digital (e.g. SENT)
10 digital inputs (CUP, 6.1, 6.3: 18)
1 x switchable Hall or inductive sensor for flywheel measurement
2 x Hall sensor for sync wheel detection
4 x switchable Hall or DF11 sensors for camshaft position or wheel speed
2 x switchable Hall or inductive sensors for turbo speed measurement
10 digital inputs (CUP, 6.1, 6.3: 18)
1 x digital switch for engine ON/OFF
8 x digital inputs, e.g. SENT (Only CUP, 6.1, 6.3)
6 internal measurements
1 x ambient pressure
1 x acceleration 6-axis
2 x ECU temperature
2 x ECU voltage
9 function related inputs (CUP: 3; 6.1, 6.3: 8)
2 x thermocouple exhaust gas temperature sensors (K-type) (CUP, 6.1, 6.3: 1)
2 x Lambda interfaces for LSU 4.9 sensor types (CUP: 1)
1 x lap trigger/beacon input (CUP: 0)
4 x knock sensors (CUP: 1)

2.3.2 Sensor supplies and screens
4 x sensor supplies 5 V / 50 mA
3 x sensor supplies 5 V / 150 mA
7 x sensor grounds
2 x sensor screens

2.3.3 Outputs
38 function related outputs (CUP: 15; 6.1, 6.2: 28)
High Pressure Injection (not 6.1, 6.2)

• 8 x high pressure injection power stages for magnetic valves, e.g. HDEV 5 (CUP: 4)
• 2 x outputs for high pressure pump with MSV controls (CUP: 1) Low Pressure Injection
• 12 x low pressure injection power stages for high impedance valves (max. 2.2 amps and min. 6 Ohm internal resistance of the injectors) (CUP: 4) Ignition
• 12 x ignition controls, support of coils with integrated amplifier only (CUP: 4)
  2 x 8.5 amp H-bridge for electronic throttle control (CUP: 1)
  2 x 4 amp pwm lowside switch for Lambda heater (CUP: 1)

19 freely configurable outputs (CUP: 13)
1 x 8.5 amp H-bridge (CUP: 2)
2 x 4 amp pwm lowside switch (CUP: 1)
4 x 3 amp pwm lowside switch (CUP: 2)
8 x 2.2 amp pwm lowside switch (CUP: 5)

19 freely configurable outputs (CUP: 13)
4 x 1 amp pwm lowside switch (CUP: 3)
3 output signals
1 x engine rpm
1 x flywheel
1 x trigger wheel

2.4 Description of Device Status LEDs
The MS 6 EVO provides state LEDs showing various operation states by means of color /blinking frequency. In detail, there exits three LEDs: ”LOG” (Data logger),  ”RUN” (Motronic Run) and ”POW” (Motronic Power). Indications are as follows:

2.5 Communication

3 x CAN| The MS 6 EVO has 3 CAN buses configurable as input and output. Different baud rates are selectable. Please note that the MS 6 EVO contain integrated switchable 120 Ohm CAN termination resistors.
---|---
1 x LIN| The Bus is not configurable by the customer, but Bosch Motorsport offers data selectable protocols to integrate LIN based devices into the system.
8 x SENT| The MS 6 EVO has 8 SENT interfaces for using SAEJ2716.
2 x Ethernet| Integrated are 100 Mbit full duplex Ethernet communication ports, internally connected with an Ethernet switch. The ports have “cable auto crossover” functionality
1 x USB| For data transfer to an USB-stick
1 x RS232| One serial port with programmable baud rate for online telemetry
1 x Timesync Co- ordination| For additional devices added via Ethernet

2.6 Structure of Devices and Licenses
To accommodate the wide range of different engine requirements and racetrack operating conditions, the MS 6 EVO Motronic system is classified into the main groups high-
and low pressure injection support, subdivided into fully equipped- and functional reduced versions.
Beside the change from low- to high-pressure systems, all limited functions may be activated later. The license concept is related to the individual device and the requested
upgrading.

For all MS 6 EVO Versions

| Driveshaft Gradient Control
Acceleration Control
Wheelie Control
---|---
Innovation License Device| Activation of a set of additional functions for a single device:
– Crank rotation direction detection (using sensor DG23i)
– Using a 2nd crank backup sensor
– Crank-Pre-set, quick start based on previous crank stop position
– Far-Bank, 2nd injector per cylinder possible
– Cam-only-synchronisation, engine run without crank sensor signal (specific cam trigger wheel
needed)
Innovation Package Project| Innovation Package Project has the same content as Innovation License Device, but license is valid for the whole project instead of a single device.

NOTICE
Verify the necessity of gearbox control licenses by checking the Features info window in RaceCon (see section Feature/License Activation [33].

Recommendation
Use rubber vibration absorbers for soft mounting in the vehicle. To assist the heat flow, especially if HP injection is active, the device has to be mounted uncovered and air  circulation has to be guaranteed around the entire surface area.
Inside touring cars placement passenger side is favored, open connectors should not be uncovered to vertical axe. It has to be assured in mounting position that water cannot  infiltrate through wiring harness into the ECU and that the pressure compensating element and the sealing in the revolving groove do not get submerged in water. Wiring harness needs to be fixed mechanically in the area of the ECU in a way that excitation of ECU have the same sequence.

2.8 Supply System
Please ensure that you have a good ground installation with a solid, low resistance connection to the battery minus terminal. The connection should be free from dirt,
grease, paint, anodizing, etc.
– MS 6 EVO power consumption at appr. 13 V (vary according to use cases)
– ~ 25 – 30 amps (4 cyl. FDI at 8,500 1/min/200 bar single injection, 1 MSV, 1 electronic throttle, standard chassis equipment)
– ~ 35 – 40 amps (8 cyl. FDI at 8,500 1/min/200 bar single injection, 2 MSV, 2 electronic throttle, standard chassis equipment)
– Power consumption of LP-injectors, actuators and coils are to calculate separately.
– The MS 6 EVO power supply is separated into the maintenance of controller and power stages.
– Ensure controller supply UBAT is activated before the power stages.
– The MS 6 EVO is able to control a main relay or even the power box itself via a low side output.
– As long as the controller is activated, data logging, telemetry and communication is also ongoing.
– The engine On/Off switch activates the ignition and injection outputs to enable engine start separately from power supply.

2.9 Pin Layout
The pin layout is available at Bosch Motorsport website on MS 6 EVO product page.
Most of MS 6 EVO functions to pin relations may be modified to project demands.
Please see details in the function description SWITCHMATRIX.
Bosch Motorsport tests check the defined connections of the pin layout.
Using a MS 6.1 EVO or MS 6.3 EVO version, ensure not using analogue inputs of the measurement package without enabled license.
For MS 6.1 EVO and MS 6.3 EVO, these hardware-options are only available if MS 6 EVO measurement package is in use.

Analogue Inputs

2.10 Harness
Harness connectors
Bosch automotive connectors are not available as complete set of components, so Bosch
Motorsport itself offers such a package. For more technical details please check Boschconnector homepage, 196 pins
http://www.bosch-onnectors.com/bogscoca/category/142

MS 6 harness connector type A (105 con- tacts), coding variant 1| F02U.B00.712-01
---|---
MS 6 harness connector type K ( 91 con- tacts), coding variant 1| F02U.B00.711-01
Protection Classification| IP X6K, X8, X9K
Temperature range| -40 to 120°C
Shakeproofed| Max. 3.4 g
Wiring diameter| 0.35 to 2.5 mm²
Pinsize| 1.2 mm; 2.8 mm

Dummy Plug

Dummy plug 1928.405.459 for unused connections| Matrix 1.2 / CB / 0.75 to 1.0 mm²
---|---
Dummy plug 1928.405.460 for unused connections| Matrix 1.2 / CB / 1.0 – 1.5 mm²
Dummy plug 1928.301.207| BTL 2.8

Tools and Contacts

Wiring
Bosch Motorsport recommends using the specified cable material and harness layout for automotive connectors and wiring applications.
For Ethernet and USB connection CAT5 specified material is recommended and the pairs and shield connections have to be strictly respected as shown in the wiring  diagram.
For USB, the maximum wiring length is limited to 3 m and it is not allowed to be included into a common harness and also there is no interruption allowed.
Due to installation condition, the length may have to be reduced.
Keep network wiring in distance to main sources of electrical noise like coils, coil- and HPinjector wirings and also in distance to any telemetry transmitter.
CAN-networks need a 120 Ohm termination at 2 ends of the wiring.
The MS 6 EVO is able to switch on an internal 120 Ohm termination, set CWCANx_TERM true to enable the termination.
For wiring layout, respect the common rules of failure reduction like separated sensor power supply between important system sensors (e.g. camshaft detection) and measure options (e.g. damper position).
Be ensure HP-injectors, electronic throttles and other high frequently switched actuators are connected within the wiring limits of 2.5 m and all wires are manufactured as  twisted pairs.
If using a preinstalled production harness, first verify the way of sensor- and actuator controls.
Often production parts have to be connected to 12 V power supply and actuators are controlled in different ways. The production harness may need to be modified.
Office harness
Reduced layout to realize communication between PC, MS 6 EVO device and Display DDU, recommended for flash configuration, display configuration and installation  tasks. Bosch Motorsport part number: F02U.V01.809

2.11 Ignition Trigger Wheel
To detect the engine position and to calculate the exact crankcase position, the system assumes toothed trigger wheels for proper operation. Recommended is to use 60 (-2) teeth for the flywheel and one teeth for the camshaft detection. Modifications of the mechanical designs are possible, such as using quick-start production designs for the camshaft or different number of teeth for the flywheel (limited to 30 to 60 teeth).
NOTICE
Less number of teeth reduces the accuracy of the system angle measurement.
Not usable are flywheels with 4-1 or 6-1 teeth. Please follow the description below as recommendation for the mechanical dimensions.
Recommended values:
– D = min. 160 mm
– h1 = 3.5 mm
– h2 = h1/2 (important for the use of inductive sensor)
– LSKW = 0.8 mm +/- 0.3 mm
– t = min. 5 mm
– LNSW = 1.0 mm +/- 0.5 mm

NOTICE
All angles are shown and indicated in crankshaft degrees.
The width of the cam trigger tooth is not important, however it is recommended to use at least 48 crankshaft degrees (24 cam degrees).
The Hall effect signal may be the inversion of its cam trigger: the tooth effects a “low” signal at the sensor and vice versa for other trigger wheel configurations the indicated  values may vary.

Starting up

NOTICE
All following chapters (Starting up to Harness / Wiring) refer to the MS 6 base family. Some screenshots were taken from the MS 6 family.

3.1 Installation of Software Tools
PC tools and ECU programs for the MS 6 EVO system are available at Bosch Motorsport homepage for free download.

RaceCon V2.7.0.9 or higher| System configuration, data application and online measurement
---|---
WinDarab V7| Data analysis tool, Light version as shareware or Expert version if license available
MS 6 EVO customer_delivery| ECU programs and function description

All tools are delivered as self-installing executable files.
Select your personal installation folder.

3.1.1 Communication PC to device
Ethernet as used network may have some restrictions by firewall and IT protections. Be assure no firewall is active at the PC.
For assistance, Bosch Motorsport homepage explains the necessary PC installations.
The MS 6 EVO system requests a defined IP-adress at the PC, for example 10.10.0.14. Middle of 2016, programs and basic systems were extended to handle automatic TCP/IP selection also. Former produced devices and program versions may be modified to  customer request and -order.
MS 6 EVO devices are connectable via commercial CAT7 cables to the PC; also Bosch Motorsport offers diagnostic cable and programming harnesses as track- and office  connections.
Successful connection between PC and MS 6 EVO is shown as green marked connection in the top left corner of RaceCon.

3.2 Configuration of the system
Bosch MS 6 EVO devices are delivered in a not engine executable mode. The customer has to include the correct programs, data applications and licenses.
The MS 6 EVO offers two mainly different configuration areas, related to the two core areas of the controller. MS 6 EVO ECU 1 st core area for the functional part of the  MS 6 EVO program. The available content is documentated in the functional descriptions Bosch Motorsport adds to the customer deliveries. Application works will be done  via opening the data labels in the edition windows of INCA or  RaceCon.MS 6 EVO Logger 2 nd core area for the tool displayed parts like logger-, lap trigger, telemetry and CAN-net- work configurations. Application work will be done in the predefined function windows of RaceCon.
MS 6 EVO Programming
For system programming or flashing of the device we developed the system configuration tool RaceCon. After the start of the tool, RaceCon opens the screen “Welcome to  RaceCon”. With “Last Projects” former projects can be opened directly.

3.2.1 First Steps to create and configure a Project
File / New / RaceCon Project opens a new project in RaceCon.

To create a new vehicle configuration, the devices can be pushed via drag & drop from the toolbox to the vehicle. Then they are part of the project and can be configured.
Select an ECU model MS 6 EVO from the Toolbox / Devices / ECUs.
Drag the ECU icon with pressed left mouse click on the vehicle view, then a dialog opens.

Now the ECU program archive PST files must be selected. These archives are delivered by Bosch or are available at Bosch Motorsport homepage. Specify the MS 6 EVO  program archive: MS6B_XXX_xxx.pst. Access to all configurable data is now available.
Installation may now be saved as customer project for further data application.

3.2.2 Programs Installation
Going Online for program and license configuration
In the project tree both parts of the MS 6 EVO core are shown as >red<, means MS 6 EVO device and RaceCon project differ in the used program version.

Synchronize MS 6 EVO and RaceCon program version / update the firmware of the device: Project-tree / right mouse button to one of the red MS 6 EVO core / synchronize / update firmware >select customer software of the MS 6 EVO (file with extension: -.pst)
NOTICE
Do not interrupt flash process.In the project tree, the MS 6 EVO logger core is shown as >yellow<, means the firmware of MS 6 EVO device and project are identical, but the data differs.The offline preconfigured data have to be sent to the MS 6 EVO. Option one, select: Project tree /right mouse button to the yellow MS 6 EVO core / synchronize / or  follow the RaceConmenu:

Both MS 6 EVO cores are shown as green, means firmware and data of device and project are now identical.

3.2.3 Feature/License Activation
For code area generation, additional functionalities and/or data logging licenses may be requested for activation. Generally all MS 6 EVO licenses are related to one specific  device and the delivered code is only to activate for this ECU. Both cores, MS 6 EVO ECU and MS 6 EVO logger, content own license structures. Double-click to the core  symbol at the project and choice features info. Select the license feature and activate the functionality using the related license code.

The licenses for gearbox and engine controls are to activate at the MS 6 EVO ECU core.
The licenses for USB or logger packages are handled in the MS 6 EVO logger core. MS 6 EVO ECU is now ready for customer data and use.

Prepare Data Base

Using RaceCon, the data base is already generated and the modification may start immediately. For information, please see RaceCon manual.
4.1 Initial Data Application
The following chapter deals only with the main parameters which should be checked before a first engine startup. Several functions are recommended to be switched off, many software labels will not be explained in detail. To work on these functions and labels after the first startup, please refer the full- scope function description. The offline  data application guide shall help to get the engine started the first time without problems.

CAUTION
Wrong engine setup data may lead to serious engine damages.

4.1.1 Basic Engine Data
The MS 6 EVO system can be used for engines up to 12 cylinders. Please ensure that the correct software variant is loaded in your ECU. Define the engine parameters like  number of cylinders, firing order, injection system, and cam- and crankshaft designs in relation to TDC.

4.1.2 Crank- and Camshaft Wheel
The system initially supports wheels with 60-2 teeth. Other configurations in the limits between 30- and 60 teeth may be possible to configure also. Please refer also to the  chapter Ignition Trigger Wheel.

Main Data Labels to configure for crank- and camshaft wheel

CRANK_TOOTH_CNT| Number of teeth of the flywheel (including the missing teeth) (limited to 30-60 teeth)
---|---
CWINTF_A047_A048| Selection of used crankshaft sensor type (Hall or inductive
type)
CRANK_GAP_TOOTH_CNT| Number of missing teeth on the flywheel
CAM_MODE| Camshaft position detection mode
CAM_TOOTH_CNTx| Number of teeth on the camshaft
CAM_POS_EDGESx| Position [°CRK] of positive camshaft edges
CAM_NEG_EDGESx| Position [°CRK] of negative camshaft edges (online measurement, see channels cam_neg(pos)_edges_xxx)
ANG_CAM_CATCHx| Max. deviation of cam edges angles allowed
SYNC_CAM| Camshaft signal used for engine synchronization

4.1.3 Initial Steps
The following data must be set initially to start injection calibration for the first time.
Main Data Labels to configure for firing order and engine design

Example typ. 8 cyl. engine:
Cylinder 1 2 3 4 5 6 7 8 9 10 11 12
CYLBANK 1 1 1 1 2 2 2 2 0 0 0 0
Engines with one Lambda sensor (e.g. 4-in-a-row) run as 1bank-systems
Set CYLBANK to 1.
CYLNUMBER| Number of cylinders
CYLANGLE| Angle of cylinder TDCs relative to reference mark (RM →TDC)
CWINJMODE| Selection of injection mode
QSTAT| Static valve quantity for n-heptane in g/min (injectors are typically measured with n-heptane)
TDTEUB| Battery voltage correction low-pressure injection. Characteristics can be requested at the injector valve
manufacturer.
TECORPRAIL| Battery voltage correction high-pressure injection. Characteristics can be requested at the injector valve manufacturer.

4.1.4 Basic Path of Injection Calculation
The ECU MS 6 EVO is a so called physically based system. This means in particular that corrections are made according to their origin influence (e.g. air temperature, fuel  pressure etc.). For it, the initial engine load signal (throttle angle ath) or the engine charge signal rl (relative load) is defined as 100 %, if the cylinder is filled with air of 20°C  and 1013 mbar (“standard condition”). Corrections related to the air path (air temperature, ambient pressure) are therefore performed to this value rl. Based on this central value most of the relevant ECU signals are calculated, first and foremost injection and ignition.
Due to this constellation changes in the air path are centrally considered for all following functions, independently whether they are caused by ambient influences, mechanical changes of the intake system or even a change from alpha/n-system to p/n-system.
Using this rl value, a relative fuel mass rfm is constructed. For an operating point of rl =100 %, a fuel amount of 100 % is needed, if the desired Lambda =

1. All corrections  to the desired fuel quantity like start enrichment, warm up factor, transient compensation, but also the desired Lambda value and the correction factor of the Lambda control  are considered as an adjustment of this relative fuel mass. I.e. all corrections are still made independently of the size and other specifications of the injectors.
   Next step is the conversion of the relative fuel mass to a desired injection time te. Here the engine´s displacement, the fuel flow through the injector and influences of the fuel pressure are considered.
   Finally the actual duration of the control pulse ti is calculated, considering pick-up delays of the injectors, fuel cutoff (e.g. overrun cutoff, speed limiter, gear cut) and cylinder  individual correction factors. Please refer also to the system overview in the Function Description ECOV.

4.1.5 Main Data Labels to configure for Engine Start up

Main Data Labels to configure for engine start up

startup
CWPRAILCOR| If a correction by fuel pressure is intended, set = 1. In this case please set PRAILREF according to the referenced  fuel pressure. Also refer to MP_P22MOD. Usually the predefined values are suitable. If unsure, set CWPRAILCOR to 0 for first startup.
FINJ_WARMUP| Correction via engine coolant temperature. Usually the predefined values are suitable. Ensure, that for coolant temperatures driven on your dyno during calibration, no warm up factor applies (i.e. FINJ_WARMUP is 0.0 for this temperature).
MP_LAM_MP1| Desired Lambda value, valid for map position 1. According to your expectations, e.g. 0.9. For alternative positions  of your map switch the maps MP_LAM_MP2 (3) or (_PACE) apply, therefore ensure correct switch position

4.1.9 Main Data Labels for Ignition

Main Data Labels for ignition
Notice: Positive values stand for ignition angles before TDC, negative values after TDC. Begin with moderate values to protect your engine from damages.

MP_TDWELL| Coil dwell time. Consult the coil manufacturer for details. Most coils need dwell times about
1.5 to 2.5 ms at 12 to 14 V. For further background information please refer to the Function Description
IGNITION.
---|---
DIGN_CYL1-…12| Cylinder individual corrections. Set to 0.0. Numbering refers to mechanical cylinders.
MP_IGN_START/DIGN_ST_TINT| Base spark advance during engine start. Set to 5 to 10 deg, according to the requirements of the engine.
MP_IGN(2/3)| Base ignition timing in deg crankshaft before TDC. Use modest values at the first time. Atmospheric  engines may run safe at 20 to 25 deg in part load, turbo engines at high boosts may demand even less  spark advance. These values are strongly dependant on compression ratio, fuel quality, temperature and  engine specifics. If you know you’re using “poor” fuel, run at high temperatures or your engine is very  sensitive on spark advance, go to the safe side.
MP_DIGN_TEMP/MP_DIGN_TEMPW| Ignition angle temperature dependent
DIGN_APPL| Delta value for spark advance, use for application work. Start at 0.0 for first startup.
IGN_IDLE_STAT| Ignition timing during idle. 10 deg are suitable for most applications
NIDLE_NOM / DIGN_IDLECTRL| Desired engine idle speed for idle stabilization. Set value to desired speed or deactivate stabilization by  setting DIGN_IDLECTRL to 0.0.

4.1.10 Main Data Labels for Engine Speed Limitation
The rev limiter works in two steps:

• Soft limitation by ignition retardation or cylinder individual cutoff of injection and/or ignition
• Hard limitation by injection cut off and/or ignition cutoff of all cylinders
  To achieve a good dynamic behavior by advanced intervention, the engine speed is predicted by means of the speed gradient.

Main Data Labels for engine speed limitation

CWNMAX_CUTOFF| Codeword for type of intervention during soft limiter:
0 = only ignition retard
1 = injection cutoff
2 = ignition cutoff,
3 = injection and ignition cutoff
---|---
CWNMAXH_CUTOFF| Codeword for type of intervention during hard limiter:
1 = injection cutoff
2 = ignition cutoff,
3 = injection and ignition cutoff
NMAX_GEAR| Engine speed limit, gear dependent
NMAX_P| Determines the slope of the soft limiter between soft limit and hard limit.
Predefined. Vary according to your engine´s dynamic behavior.
TC_GEARNMAXPR| Prediction time for rev limiter, depends on the inertial torque of the engine. If oscillations occur, reduce  value or turn off by setting = 0.0.

4.2 Peripherals
Sensors and peripherals can be checked when the system is powered up electrically.
Do not start the engine before all steps in this chapter are carried out.

NOTICE
Make sure the battery is connected properly, all sensors are connected and ground wiring is fixed before powering up the system. Check all sensors for errors (E_…) and  reliable measure values before starting the engine.
Sensor configuration
The MS 6 EVO has the option to link a lot of functionalities to a possible hardware input.
The chapters “ECUPINS, SWITCHMATRIX and Input Signal Processing” of the functional description explains the details. All functions of Base MS 6 EVO programs are linked like described in the MS 6 EVO documents (e.g. function description ADC_ECU_MAP) or the wiring diagrams.
Analogue sensor inputs
The physical way of conversion from sensor signal voltage to physical values follow the same structures. The hardware input may be connected to different kinds of pull-up  options. Inputs with fixed 1.47 kOhm or 3.01 kOhm pull-up resistors are prepared to handle passive sensor elements, for instance temperature sensors with integrated  resistors (NTCor PT100 sensors). Inputs without any pull-up resistors are prepared to handle active sensor elements, which deliver 0 to 5 V signals, for instance pressure-,  potentiometer- or acceleration sensors. Inputs with switchable 1.47 kOhm pull-ups are designed to handle mainly active sensors with disabled pull-up, but are prepared for future measuring of digital signals. Inputs with switchable 3.01 kOhm pull-ups offer the most options and are recommended to link after the standard sensors are connected.  The pull-up resistor itself is not modifiable and for better measure results may be, the version of sensor/mapping line has to be changed. To activate the Pin-Selection, first  the label “PIN_IN_function” has to be enabled. Error detection of an analogue input signal detects short cuts to ground, U”function”_MIN recommended to be set to 0.2 V  and short cuts to power supply U”function”_MAX recommended to be set to 4.8 V. Failure are activated after the adjustable debounce time of diagnosis TD”function”. If  a sensor error is set, the output is switched to the default value “function”_DEF. 

Pressure measurements
The system offers many different pressure channels; please see function description input signal processing for details. For gradient and offset information contact sensor  manufacturer.

Example: Ambient Pressure|
---|---
PAMB_OFF, PAMB_GRD| Sensor offset and gradient
UPAMB_MIN, UPAMB_MAX| Minimum and maximum accepted sensor voltage. When violated, an error is set (E_pamb = 1).
PAMB_DEF| Default value if an error occurred.
FCPAMB| Filter constant. For ambient pressure use 1 second, for other pressures choose appropriate values, ~ 100 to 200 milliseconds

All other variables are named by the same rule; replace “pamb” by e.g. “poil” to apply data for the oil pressure sensor.
Temperature measurements
The system offers many different temperature channels; please see function description input signal processing for details.

Example: Intake Air Temperature

UTINT_MIN, UTINT_MAX| Minimum and maximum accepted sensor voltage. When violated, an error is  set (E_tint = 1).
TINT_CONV| Sensor characteristic. Consult the sensor manufacturer.
PULLUP_TINT| Value of the used pull-up resistor. If only the ECU´s pull-up is used (standard  case). Keep the predefined value of 3.01 kOhm.

Thermocouples
The exhaust gas temperatures are measured via thermocouple elements, using a special evaluation circuit. Predefined values should be suitable for NiCrNi or k-type elements.  For further details and project specific variants, please refer to the function description.
Digital sensor inputs
MS 6 EVO digital sensor inputs used for frequency measurements are possible to configure to different of sensor types.

CWINTF_A047_A048| Selection between Hall effect or inductive sensor for flywheel measurement, related to MS 6 EVO  contact A047 (use ground A048 if inductive type is selected).
---|---
CWINTF_K045/K046| Selection between Hall effect or inductive sensors for frequency measurements, like turbo- or  driveshaft speeds, related to MS 6 EVO contacts K045 or K046 (use ground K062 if inductive types are selected).
CWINTF_A049/A050/A051/A052| Selection between Hall effect or DF11 sensors for frequency measurement, like wheel speeds or cam  position detection, related to MS 6 EVO contacts A49, A50,  A51 or A52.

4.3 Throttle Control
The system supports mechanic and electronic throttle controls. Using an MS 6.1 EVO device, respect the necessary license for electronic throttle is activated. Electronic Throttle Control is a safety-critical function. The Bosch Motorsport Electronic Throttle Control System (ETC) is designed and developed exclusively for use in racing cars during motorsport events and corresponds to prototype state. Therefore the driving of an ETC equipped vehicle is limited exclusively to professional race drivers while motorsport events and to system‐experienced drivers on closed tracks for testing purposes. In both cases the driver must be instructed regarding the functionality, possible malfunctions of the system and their consequences and must be familiar with possible emergency actions (e.g. pressing the emergency stop switch or the main switch). The system must have emergency switch, whose activation at least cuts the throttle valve actuator from the power supply. Depending on specific use and/or construction, the safety functions, fault detections and fault responses of the ETC system may differ in several points from ETC systems used in series production. Hence before each vehicle- commissioning the system must be checked for accuracy and faultlessness. Using an MS 6.1 EVO device, respect the necessary license for electronic throttle is activated. Electronic Throttle Control is a safety-critical function. The Bosch Motorsport Electronic Throttle Control System (ETC) is designed and developed exclusively for use in racing cars during motorsport events and corresponds to prototype state. Therefore the driving of an ETC equipped vehicle is limited exclusively to professional race drivers while motorsport events and to system‐experienced drivers on closed tracks for testing purposes. In both cases the driver must be instructed regarding the functionality, possible malfunctions of the system and their consequences and must be familiar with possible emergency actions (e.g. pressing the emergency stop switch or the main switch). The system must have emergency switch, whose activation at least cuts the throttle valve actuator from the power supply. Depending on specific use and/or construction, the safety functions, fault detections and fault responses of the ETC system may differ in several points from ETC systems used in series production. Hence before each vehicle- commissioning the system must be checked for accuracy and faultlessness. The functionality of the ETC diagnosis and the fault responses are described in the technical documents, handed over to the customer together with the system. Each driver must be briefed regarding the system description. Further information you will find in document “SICHERHEITSHINWEISE-Systemanforderungen zum Betrieb eines Bosch Engineering GmbH EGas-Systems” or can be enquired at Bosch Motorsport. The customer is responsible for the activation of all ETC‐relevant diagnosis and for their correct parameterization. By disregarding this information the functionality of the ECU and the safety cannot be ensured. Notice: For detailed information see function description ETC The usual route of ETC determines the drivers input measuring the pedal position and transferring this leading signal via functionality options into the control of an electrical throttle actuator. Pedal- and actuator positions are generally measured in a secondary redundant way to verify the reliability of the function. To activate the system, first verify the signal tolerances and error messages by moving acceleration pedal and throttle actuator manually. An inactive system usually is the result of inverted wired sensor signals or actuator controls. Calibrate the pedal- and  throttle positions.
Verification of acceleration pedal signals:
The mathematic value of voltage pedal signal 1 – 2*voltage pedal signal 2 has to be below 0.5 V or below value of “UAPSCM_MAX”.

Signal principle of an acceleration pedal sensor:

approx. 200 mV/4,800 mV.
Check if the uaps(x) outputs are changing when the pedal is moved.
CWAPSADJ| Codeword to adjust acceleration pedal signal:
0 = calibration inactive
1 = calibrate release pedal
2 = calibrate full-pressed pedal
E_APS| Detected error messages of acceleration pedal functionality. If errors are detected, the ETC functionality will become inactive.

Verification of throttle position signals:
The mathematic value of voltage throttle signal 1 + voltage throttle signal 2 – 5 V has to be below value of “UDTHRCM_MAX” (recommended 0.2 V)
The signal sequences of a throttle position sensor:

Throttle position main data labels:
CWTHR
Codeword for type of throttle controls:
0 = mechanical throttle
1 = mechanical throttle with backup potentiometer
2 = electric throttle single bank
3 = electric throttle dual bank

Throttle position signals:

UDTHR_MIN, UDTHR_MAX| Minimum and maximum accepted sensor voltage. When violated, an error is set (E_thr =  1). Set to approx. 200 mV/4800 mV Check if the uthrottle(xx) outputs are changing when  throttles are moved
---|---
uthrottle| 2 sensor output values and their redundant
uthrottle_b| signals (_b). The system expect a rising up
uthrottle2| voltage for the main signals and a falling signal
uthrottle2_b| for the redundant one.
UDTHRCM_MAX| max. allowed difference between sensor output and redundant signal abs  (uthrottle(x)+uthrottle(x)_b)-5V < UDTHRCM_MAX

Manual Procedure:

• Close throttle and set CWTHRADJ to 2.
• Open throttle fully and set CWTHRADJ to 3.
• Adjust the throttle to idle point.
• Do not forget to set CWTHRADJ back to 0. Check calibration by moving throttle.

4.4 Vehicle Test
Before starting with your vehicle test, some initial data should be set:

Speed & distance measurements| The signals for speed calculation may be available from different sources, like MS 6 EVO own measurement, GPS data or ia
CAN received information from ABS calculation. For MS 6 EVO own calculation, mechanical influenced data like number of  available sensors, front wheel drive, number of detected increments, wheel circumferences and dynamic corrections like   corner speed application a lot of functional options assist the calculation of the effective vehicle speed. Distance measure  channels may bederived from speed information. For  detailed information see function description >CARSPEED<
---|---
CWWHEELCAN| Selection for car speed from CAN signal
CWWHEEL| Connected number of wheel speed sensors or -signals
CWFWD| Selection of front driven vehicle
CWSPEEDDYN| Release of dynamic speed calculation
INC_FRONT| Number of pulses per revolution of the front speed signal
INC_REAR| Number of pulses per revolution of the rear speed signal
CIRCWHEEL_F| Wheel circumference of the front wheels
CIRCWHEEL_R| Consider dynamic increase of the tire
Vwheel_xx| Wheel circumference of the rear wheels.
Consider dynamic increase of the tire.
Speed| Measure channel of the individual wheel speeds
Accv| Result of calculated vehicle speed
Ltdist| Result of speed based derivation of longitudinal acceleration
Lap information and -functions| Lifetime distance as accumulated result of speed derivation

and drop the subfolder to the project and follow  the wizard
Set time & date| MS 6 EVO device is equipped with a real time clock which is supplied for max. 14 days, if the ECU is  disconnected from power supply. Please connect the ECU to the PC and click on “SET DATE &  TIME” in the context menu of the MS 6 EVO.
time_xx| The measure channels of the real time clock.

ECU plus Data Logger

The MS 6 EVO combines ECU and data logger in one common housing for a cost efficient and weight optimized all-in-one solution.
5.1 Software Tools

RaceCon| Create and configure a project
Configuration & management of recordings
Create a new recording
Add channels to a recording
Create user-defined conditions for the recording
Download recording configuration
---|---
WinDARAB| Upload recorded data
Display and analyze the data

First Steps

Install the software required for the operation of the MS 6 EVO. It is developed for Windows system software. The following software versions are used in this manual:

• MS 6 EVO setup, configuration and calibration: RaceCon Version 2.9.0.7 or later.

• Measurement data analysis: WinDarab V7
  Set up the 100 Mbit ethernet connection to the MS 6 EVO.

• The ethernet port has “cable auto crossover” functionality.

6.1 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 connector of 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 will switch 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 [ 52]”. For the status color, see chapter “Color indication [ 63]”.

Connection via Ethernet Cable
Instead of connecting the ethernet line to the MSA-Box, connect the ethernet directly to your computer.
Troubleshooting while setting up the network interface
The MS 6 EVO contains a DHCP server, network addresses can be assigned automatically to the configuration PC. In case of problems during the network connection,  please try the following 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.
   

6.2 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.

1. Start the RaceCon software.
   

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

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

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

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

6. Click ‘Finish’. The MS 6 EVO is inserted into the project and RaceCon tries to connect to the device.
   

RaceCon detects configuration differences between the MS 6 EVO 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.
If the device turns red, you might need to do a firmware update on the device. For more information see chapter “Firmware update [137]”.
The download starts and the MS 6 EVO carries out a reset.
After the reset, RaceCon reconnects to the MS 6 EVO. Local configuration on both the PC and MS 6 EVO match (indicated by green background and dot). The MS 6 EVO is now connected to RaceCon.
For further information on the color indication, see chapter “Color indication [ 63]”.
6.3 Feature activation
– Optional software feature packages are available for the MS 6 EVO
– 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 MS 6 EVO does not work on any other MS 6 EVO.
– 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 can be skipped.

1. Ensure a connection to the device.

2. To activate a feature, double-click on ‘MS 6 EVO’ in the Project Tree.

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

4. The ‘MS 6 EVO features info’ window appears.
   

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’.

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 MS 6 EVO.

6.4 First recording (Quick Start)
This chapter explains the configuration of the recording of the battery voltage channel.
See chapter ‘Recording [102]’ 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 for battery voltage).
   

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

4. Click on the ‘Download’ button in the upper left corner. The configuration download starts and the MS 6 EVO 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.
   

5. Start the WinDarab software.
   

6. Disconnect the MS 6 EVO 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.
   

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

9. Connect the MS 6 EVO 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 is checked, the data transmission from the MS 6 EVO 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.
    

6.5 Set date and time
The MS 6 EVO 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 MS 6 EVO 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
   

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 or choose from the dropdown menu.
   

6.6 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.

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.

Project Configuration

7.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.
   

2. Define the math channel using the following configuration possibilities:
   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.
   Click ‘Finish’ when done. The math channel is displayed in the math channel window.

7.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.
   

2. Define the math channel using the following configuration possibilities:
   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.
The conditional function works the following way:
The program always calculates the condition entered in the IF window and checks if the condition 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 the next page.
  The conditional function is displayed in the MS 6 EVO math channel window.

Example: Setting up a condition for maximum front brake pressure

• At power-up, the reset value (10) is used for ‘p_br_front_mx’.
• ‘p_br_front’ rises to 30. As ‘p_brfront’ is > 20 (condition is TRUE), the condition ‘max (pbrfront, pbr_front_mx)’ in the THEN window is triggered. The  condition sets the bigger 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 ‘pbr_front_mx’ is set to  30.
• Although ‘p_brfront’ falls to 25, the value of ‘p_br_front_mx’ stays 30. This is caused by the THEN-condition, because pbrfront_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 new value for ‘p_br_frontmx’ 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.

7.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 calculations in the whole RaceCon project.

Creating a new Conditional Channel

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

2. Define the condition channel, using the following configuration possibilities:
   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 the value 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 the minium and maximum value.
   – Multiple: Choose the measurement channel or condition, the operator and enter the value 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 MS 6 EVO condition channel window.

7.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 MS 6 EVO 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 with binary 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:

• 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 MS 6 EVO condition channel window.

7.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 is needed.

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

7.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 are called …_time and …_trig.

7.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.

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.
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 for macro or p for parameter based. The trigger channel will be set to 1, when the lowest distance to the trigger point is detected. For the macro-based trigger, the stored latitude and longitude values can be seen with the channels.

7.8 CPU Load Limits
As all microprocessors, the two processors of the MS 6 EVO 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 in a save range below 100 %.
Bosch recommends a maximum CPU load of 85 % (averaged). Exceeding this limit might result in the MS 6 EVO 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
• Logger configuration (total logging rate [kB/s], conditional measurement rates)

To help respecting the limit of 85 % CPU load, the MS 6 EVO 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 when being confronted with MS 6 EVO resets due to complex configuration setups,  please consider reducing the demands on the MS 6 EVO adapting the influencing factors mentioned above.

CAN Configuration

The MS 6 EVO has 3 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 MS 6 EVO 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 (transfer from one bus to another).

8.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 the menu, 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

8.2 CAN input

8.2.1 Input configuration

Click with the right mouse button on the desired CAN bus to open the CAN bus dropdown menu.

8.2.2 Create new CAN Input channel

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.
4. Insert the name and description of the channel.
5. Click ‘OK’ when done.
   The channel is listed in the Data window.

CAN channel configuration 8.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) 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.

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) 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 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)
g) 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 MS 6 EVO 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 name for a new sheet or select an existing sheet from the list box.
For an online view of the value measured by the MS 6 EVO, insert the channel in an online measurement sheet which is described in the chapter Setting up an online measurement [} 91].

8.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.
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.
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.

8.2.5 Import a CAN database (DBC) file

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.
4. 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.

8.3 CAN output
8.3.1 Output configuration

8.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.
• The ‘New CAN-OUT message’ window opens.
• Enter name of message, description, CAN-Id, and Grid (output interval). Optionally, specify a multiplexer.
• Click on ‘Add channel…’ or ‘Add constant…’, this opens the ‘Add new CAN out channel’ window.
• Select the desired measurement channel and specify the message settings.
  The measurement channel is now assigned to the CAN message.

8.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.
   

8.3.2.2 Adding CAN out counter
**** To 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.
3. Define the name of the counter, define the CAN channel settings.
4. Click ‘OK’ when done.

8.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 covered by the checksum and define the CAN channel settings.
4. Click ‘OK’ when done.

8.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.
• 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 the box ‘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.
    

11. The channel message is assigned to the selected fields.

12. Click ‘OK’ when done.
    

Export and Import in RaceCon

You can perform an export or an import on almost any level in the project tree.
9.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.

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

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.
   

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

7. Assign the ambiguous channels to the desired source.

8. Click ‘Finish’.

Online Measurement and Calibration

MS 6 EVO configuration

• System configuration (channel + display configuration, CAN I/O, etc.) is stored in the MS 6 EVO
• Use RaceCon to create and download configuration from the PC to MS 6 EVO 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

10.1 Setting up an online measurement
MS 6 EVO supports online measurement of sensor values and diagnostic variables.

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

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

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.

   ---

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.
   

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

If the MS 6 EVO shows the green status, the value is displayed. RaceCon offers different types of measurement elements:
10.1.1 Automatic creation of measurement sheets
RaceCon can create measurement sheets automatically.
You can create and use measurement sheets with the MS 6 EVO as well as with all other devices connected to RaceCon. **![BOSCH Engine Control Unit MS 6 EVO

• Figure 81](https://manuals.plus/wp-content/uploads/2022/11/BOSCH-Engine- Control-Unit-MS-6-EVO-Figure-81-1.jpg)**

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

     ---

  2. To create the sheets, right-click on MS 6 EVO and select ‘Create measurement views…’ from the MS 6 EVO context menu.

     ---

The automatically created sheet is inserted in the Project Tree under ‘Measurement Container’ and ‘Device Channels’. If the MS 6 EVO is connected to RaceCon and the status is green, live values of the channels are shown.
10.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 calib-ration is active.
2. Switch between different sheets using the tabs at the bottom of the window.
3. Press the ‘Esc’ key to return to ‘Design Mode’.

10.2 Using the Measurement Sheets

• When RaceCon is online, press “F11” key to switch from Design Mode into Race Mode.
• The measurement sheet is extended to full screen.
• Switch between different sheets using the tabs at the bottom of the page or the keyboard shortcuts associated with the sheets.
• Press ESC key to return to Design Mode.

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 the name of your product.
11.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. 11.1.1 Accessing the memory
The error memory can be accessed as shown in the illustration:

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 a power cycle.
11.1.2 Clearing the error memory
There are two ways of clearing the error memory, both are shown in the following illustration:

**| **
---|---

11.2 Writing an Error
For the functional part of the MS 6 EVO system (MS 6 EVO -ECU) the error bits are related to the function and have to be distinguished if the function is activated. If an error is detected, the information may be shown as part of the error monitor in RaceCon, as display information and as measure channel. To support driver visibility, an activated error may activate also an output to enable the MIL-light (B_mildiag will be enabled).

The single error bits may be collected in the error monitor.
11.3 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 the 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 value (0, 1 or 2) is translated into a verbal description.
**It is also represented by a color scheme within RaceCon (provided RaceCon is online with the system):
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)

Recording

12.1 Features

• Synchronized recording of MS 6 EVO analog and digital input channels, MS 6 EVO internal measurement 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)

12.2 Configuration of recordings

1. Expand the list of ‘Loggers’ by clicking on ‘+’ in the MS 6 EVO Project Tree.
   

2. Double-click on ‘Recording’ in MS 6 EVO Project Tree. The recording configuration is displayed in the Main Area.
   

3. To add measurement channels to a recording, click ‘MS 6 EVO’ in the MS 6 EVO Project Tree. In the Data Area, the measurement channels are displayed.

4. Drag and drop desired measurement channels into recording group.
   

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

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
MS 6 EVO 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 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-frequent transmission of channel information (e.g. tire pressure, oil temperature).

If the maximum bandwidth of a block is reached, a warning will be displayed. To fix this problem you can view the allocation of the channels and data rate in the ‘Statistics’ tab of the Main Area. See chapter ‘Recording statistics [106]’ for more information.
12.2.1 Adding a recording
MS 6 EVO supports up to two independent recordings.
To add a recording, select ‘Add Recording’ from the context menu of the Logger in the MS 6 EVO Project Tree. Maximum two recordings are possible. In the device software the 2nd recording is reserved for scruteneering data. This recording is invisible (protected).
12.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. 12.2.3 Global settings
To display the global MS 6 EVO settings, select the ‘Settings’ Tab.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 can
enter 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!
12.2.4 Recording statistics
The tab ‘Statistics’ shows the channels’ allocation and their current data rate related to the transmission frequency of the MS 6 EVO 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 MS 6 EVO and limits the overall transmission speed.![BOSCH Engine Control MS 6 EVO

• Figure 9](https://manuals.plus/wp-content/uploads/2022/11/BOSCH-Engine- Control-MS-6-EVO-Figure-9.jpg) 12.2.5 Recording diagnosis
  The channel ‘statectrl_ok’ of the MS 6 EVO can be used for online monitoring of recording status.

Content of status bits

because measurement thresholds are not reached.
DATAOK| Received data without error.| Discarding received data because of wrong timestamps. Check wiring of SYNC signal.
BLKOK| All measurement blocks have been set up correctly.| Some measurement blocks have not been set up correctly.
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.

12.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, MS 6 EVO 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.

12.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.

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 is transferred 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 to storage medias when logging condition becomes TRUE.
meas_backend_buf_size_ecu /_fde| Size of data buffered (for first / second logging) for 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 /_002| Effective data write rate to internal storage media, after 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.

12.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: 12.4 USB Recording
This function requires the installation of Software Upgrades. Look into the datasheet of your device, to see which upgrades are available for your device. Software Upgrade USB_DATA enables USB recording. To activate Software Upgrade USB_DATA, enter the license key as described in the chapter ‘Feature activation’ [57]. For USB recording, Software Upgrade FULL_LOG_1 should also be enabled.
Wiring harness

For further information, see the pinlayout of the device.
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 first use.
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.
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 first use.
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.
12.4.1 Recording data on USB device

1. Plug an USB device to MS 6 EVO.

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 MS 6 EVO.

5. Record measurement data. If an USB device is present, the MS 6 EVO stores the data in parallel on the internal memory and the USB device.

6. Power off the system.

7. Remove USB device from the vehicle.

8. Start the WinDarab software.

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.
    

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.| ![BOSCH Engine Control MS 6 EVO

• Figure 18](https://manuals.plus/wp-content/uploads/2022/11/BOSCH-Engine- Control-MS-6-EVO-Figure-18.jpg)
  ---|---
  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 the measurement data window. The measurement channel‘s graph is displayed

For more detailed descriptions and instructions, refer to the WinDarab V7 manual.
12.4.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 MS 6 EVO 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!
12.4.3 Troubleshooting
When no data on the USB device is recorded:
Configure the measurement label usb_mediastate on a RaceCon measurement view or on a MS 6 EVO display page.
The value of usb_mediastate reflects the operating condition of the USB bus:

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 code needed).
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 MS 6 EVO 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 MS 6 EVO.
6: Error: Media corrupt| The USB device is not in valid BFS format.
(Hint: Re-format the USB device in RaceCon.)

Lap Trigger

13.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)

Bosch Engineering GmbH
Motorsport
Robert-Bosch-Allee 1
74232 Abstatt
www.bosch-motorsport.com

References

• Home - JGuru
• STRATO - Domain reserved
• opencsv –
• Compare, Download & Develop Open Source & Business Software - SourceForge
• Welcome to The Apache Software Foundation!
• Licenses

Read User Manual Online (PDF format)

Read User Manual Online (PDF format)  >>

Download This Manual (PDF format)

Download this manual  >>