ekb 3008 data exchange format - description · 2015. 10. 13. · vda ekb 3008 data exchange format...

VDA EKB 3008 Data Exchange Format

305

As a rule, several development partners are involved in the development of a brake system. The measurement analysis and test rig technology applied is based on in-house measuring systems, some of which are also based on own developments. Every measuring system saves the measured data in its own file structures, which are not compatible with each other. As a rule, data exchange between the measuring systems is not possible. In the context of ever more complex and faster development processes, the uncomplicated exchange of data is becoming more important. The data exchange format described in the following provides the basis for the exchange of brake-relevant measurement data between measuring systems or for importing a detailed analysis into evaluation and mathematical programs. In addition, the easy use with widely used standard programs (editors, spreadsheet programs, multimedia software) has been taken into account Objectives:

File format for the exchange of brake-relevant measurement data

The data and information scope can be configured according to the exchange purpose

Application possible for conventional brake tests and brake noise tests

Application for test rig measurement data and mobile (vehicle) measuring technology

Standard information values and boundary conditions for the test run (e.g. test duration or the number of brake applications) are also transferred

Version April 2013 EKB – European Brake Noise Experts Group

Publisher: Verband der Automobilindustrie Copyright

Behrenstrasse 35 Reprints and any other form 10117 Berlin of duplication is only permissible Phone +49(0)30/897842-0 when the source is cited.

Telefax +49(0)30/897842-606 Internet: www.vda.de

mailto:[email protected]

VDA Recommendation 305 Version April 2013

Copyright: VDA

Disclaimer VDA recommendations are freely available for general use. The user is responsible for ensuring correct application for the specific case. They represent the latest technology available at the time of issue. Application of VDA recommendations does not relieve the user from responsibility for his own actions. In this regard, all users act at their own risk. VDA and those involved with VDA recommendations do not accept any liability. Anyone applying VDA recommendations who identifies inaccuracies or possible incorrect interpretations is invited to inform VDA immediately and any errors can thus be rectified.


Copyright: VDA

1 Overview of File Formats .............................................................................................. 4

1.1 EEC file ................................................................................................................. 5

1.2 EEH and EET files ................................................................................................. 5

1.3 EED files ............................................................................................................... 5

1.4 EES files ................................................................................................................ 5

1.5 EEW files ............................................................................................................... 6

1.6 Combination of tests to one file ............................................................................. 6

2 File Names Used .......................................................................................................... 7

2.1 File names of the EEC file ................................................................................... 12

2.2 File names of the EED file ................................................................................... 12

2.3 File names of the EES file (only for noise tests) .................................................. 13

2.4 File names of the EEW file .................................................................................. 14

2.5 File names of the packed test archives ............................................................... 15

3 Format conventions .................................................................................................... 16

3.1 General specifications ......................................................................................... 16

3.2 Header lines ........................................................................................................ 18

3.3 Types used .......................................................................................................... 19

3.4 Units used ........................................................................................................... 20

4 Detailed description of the EEC file format ................................................................. 21

4.1 EEC file ID ........................................................................................................... 21

4.2 Unit system definition .......................................................................................... 21

4.3 EEC file header ................................................................................................... 22

4.3.1 Description of the test ..................................................................................... 23 4.3.2 Description of the brake .................................................................................. 24

4.3.3 Description of the noise measurement............................................................ 25

4.4 Table with overview of results ............................................................................. 28

4.5 Comment block ................................................................................................... 33

4.6 Separate header: EEH file ................................................................................... 33

4.7 Separate results: EET file .................................................................................... 34

5 Detailed description of the EED file format ................................................................. 37

5.1 EED header ......................................................................................................... 37

5.2 EED data sector .................................................................................................. 37

6 Detailed description of the EES file format ................................................................. 42

6.1 EES header ......................................................................................................... 42

6.2 EES data sector .................................................................................................. 42

7 Detailed description of the EEW file format ................................................................ 44

7.1 EEW header ........................................................................................................ 45

7.2 General specification for EEW files ..................................................................... 46

Appendix I: EEC Header Identifier ..................................................................................... 47

Appendix II: EEC Result Summary Table Identifier ........................................................... 57

Appendix III: EED Data Table Identifier ............................................................................. 58

Appendix IV: PB Header List Cross Reference ................................................................. 60


Copyright: VDA

1 Overview of File Formats

To take the different requirements and data transmission volumes into account, different file formats are defined within EKB 3008*). It is thus possible e.g. to transfer the results of a brake test with only a single (text) file that can be viewed using standard software (e.g. Notepad, Excel). If more extensive information is required, additional files can be added, which enable more detailed analyses. The contents of the files can be influenced within wide limits so that the data volume can also be controlled. Due to its flexibility, the file format is suitable for conventional brake tests as well as for brake noise tests. Due to the standardized format, the results can be easily compared or set in relationship. The EEC file is the data transmission core and is therefore always required. It can already provide sufficient information for many purposes of the test documentation. The additional EED and EES files (EES for noise tests only) contain the information required for the daily development process. The data scope can usually be sent via e-mail. If a test consists of several files (i.e. not only of the EEC file), the complete test can also be transferred in the form of a packed archive file (zip format).

Edited by the European Brake Noise Experts Group – Subgroup Data Processing

*) The Data Format has been introduced under the name “EKB 3008 Data Exchange Format” by the European Brake Noise Experts Group (EKB)


Copyright: VDA

1.1 EEC file

The EEC file is the “anchor” for all other files; it is therefore the only indispensable component and needs to be evaluated before other files are processed. The EEC file includes information on the existing file format version, the language version and the unit system used. In addition, it includes header data (“header information”) of the test or of the tested objects; the individual header information is identified clearly with defined header identifiers (see Appendix I). The scope and type of the header information can be chosen as desired to a large extent and depends on the corresponding data exchange purpose. In addition, summarized test results can be stored in a results table in an EEC file. How these contents are to be identified clearly is also only defined here, not the data volume to be stored. The results tables defined for EEC files include one value line per brake application. The EEC file can be used to exchange test results using only a single file if the header information included there and the results table are sufficient for the intended exchange purpose. More detailed information can be provided by adding more files to the EEC file.

1.2 EEH and EET files

The EEH and EET files do not represent separate definitions in addition to the EEC file. They only permit the header information (EEH file) and results tables (EET file) normally included in the EEC files to be stored in separate files, if that is practical or necessary for technical reasons.

1.3 EED files

EED files are created for each individual brake application (multiplied with the number of brakes used in the test). For example, if a test applies to a single brake and consists of 1000 brake applications, this results in the creation of 1000 EED files. Essentially, an EED file consists of a value table, of which each column represents a measurement signal (e.g. pressure, temperature, torque, rotational speed etc.) and every row represents a sampling period. The signal in a column is specified by a column identifier defined for this purpose (see Appendix III); the physical unit to be used is also defined in the unit system. Since the EED files are files in text format, only “low speed signals” should be included here whose sampling rate does not significantly exceed a value of about 1 kHz. By contrast, “high speed signals” are sampled with up to about 50 kHz (or higher) and are signals that occur during noise measurements in particular. These signals are stored in special, binary “Wave Form” files (EEW files).

1.4 EES files

EES files are only defined for noise tests (and not for other brake tests). They contain value pairs in table form for the indication of the spectrums of the air- and structure-borne sound signals for each brake application (average and peak hold spectrums). Normally one file is created for each brake application and brake or measuring point.


Copyright: VDA

1.5 EEW files

These files contain the chronological sequence of the “high speed signals”, i.e. measurement data recorded with a significantly higher sampling rate than 1 kHz (typically 50 kHz). For example, the raw data of the air- and structure-borne sound signals is stored here; these files are therefore only intended for noise tests up to now. This file format is basically also suitable for other signals sampled at high frequency (e.g. information on fluctuations in thickness during DTV tests etc.). One file is created for each brake application and brake or measuring point.

1.6 Combination of tests to one file

Since complete test runs may consists of a large number of files (EEC, EED, EES and EEW files, see above), the option has been provided of “packing” complete tests into an archive file. The ZIP format and either no compression method or the DEFLATE compression method (“Public Domain”) should be used for this. Software created specially for EKB 3008 should be able to correctly open test archives packed in this way (i.e. unpack them) and also save them if necessary (i.e. pack them). You can find more detailed information on the ZIP format e.g. at ftp://ftp.uu.net/pub/archiving/zip/doc http://tools.ietf.org/html/rfc1950 http://en.wikipedia.org/wiki/ZIP_(file_format)

ftp://ftp.uu.net/pub/archiving/zip/doc

http://tools.ietf.org/html/rfc1950

http://en.wikipedia.org/wiki/ZIP_(file_format)


Copyright: VDA

2 File Names Used The storage location of a file is described in the operating system by the path, the file name and the file extension. The path should be identical for all files that belong to a test, i.e. all files are stored in one directory (exception: EEW files, see below, chapter 2.4). The name of the directory can be chosen as desired. However, it is advisable to use the <testname> described below for the directory. The file names themselves are self-explanatory to a large extent: every file name begins with the (freely selectable) test name, which documents the assignment of the corresponding file to a specific test. Since a test may apply to several brakes, an identifier for the corresponding brake (<brakeID>) is attached to the test name if the corresponding file applies to only one brake. If a separate file exists for every brake application, an identifier for the corresponding brake application (<stopID>) is also added. Furthermore, a file may also only apply to a specific input channel or measurement point; in such a case, an appropriate identifier (<chanID>) needs to be added. Every file name is always completed at the end by an identifier for the file type (<fileID>) (possible file types: EEC, EEH, EET, EES, EED, EEW). Whereas <brakeID>, <stopID> and <chanID> are only used in the file name if the corresponding files may deviate in terms of these properties, every file name always begins with <testname> (assignment to a specific test) and always ends with <fileID> (identification of the file type). By contrast, the file extension should always be selected according to the standard file type, since that facilitates work with the operating system and standard software (e.g. Excel, Mediaplayer) significantly. For the text-based file types EEC, EEH, EET, EED and EES, this is the extension “.csv” (“Comma Separated Values” Format) and for the EEW file type the extension “.wav” (MS-Wave format). The file names are therefore given the following basic structure: <testname><brakeID><stopID><chanID><fileID>.<fileExt>

<testname>: identifier for the test As mentioned above, the <testname> identifier can be chosen as desired for each test and is then to be used at the start of every file name belonging to the test. Basically, there are no size restrictions. However, for a good overview, only a limited number of characters should be used, which are sufficient to clearly assign a test. Examples of test names would be e.g. “W211-P0815-T4711” or “MYTEST001” etc. To avoid any confusion, always make sure, if possible, that the test names themselves do not include the identifiers defined in the following for the brake (<brakeID>), the brake application (<stopID>), the initiation channel (<chanID>) or the file type (<fileID>). The selected <testname> should still match the EEC header “test” entry (see chapter 4.3.1), if possible.


Copyright: VDA

<brakeID>: identifier for the brake If a file only applies to one brake, an identifier for the brake needs to be added to the file name. The corresponding brake is indicated by the <brakeID>. Possible values for <brakeID> (e.g. for tests with car brakes) are: _fl Brake front left _fr Brake front right _rl Brake rear left _rr Brake rear right The identifiers “_fl”, “_fr”, “_rl” and “_rr” determine the position of the tested brake (“front left”, “front right”, “rear left”, “rear right”); this information must correspond to the EEC header entries “brake_axle” (front, rear) and “brake_side” (left, right) (see also chapter 4.3.2 and Appendix I-2.3.1). With single-track vehicles, the terms above are used in the same way, depending on which side of the wheel the relevant brake is. If the side cannot be determined, “_fl” (front wheel) and “_rl” (rear wheel) should always be used (i.e. a single brake per axle without reference to a side is always “left”). If a vehicle has more than two axles and/or more than two brakes per axle, the <brakeID> is created from the information on the axle and brake position as follows: The axles are numbered consecutively with “a<n>” and the first axle “a1” is the very front axle of the vehicle. The brakes arranged on the axle are numbered consecutively with “l<n>” for the left side and “r<n>” for the right side from the outside to the inside so that “l1” indicates the brake on the outside left and “r1” the brake on the outside right. With this identification system, the EEC header entries “brake_axle” (axle#1, axle#2, …) and “brake_side” (left#1, left#2, … , right#2, right#1 then also correspond; see also chapter 4.3.2 and Appendix I-2.3.1). Example of the <brakeID> of a vehicle with two axles and four brakes per axle: Front axle: _a1l1, _a1l2, _a1r2, _a1r1 Rear axle: _a2l1, _a2l2, _a2r2, _a2r1 If none of the previously mentioned assignments are possible or practical, the brakes can also simply be numbered with the identifiers _br#1, _br#2, _br#3, .., _br#<n> (<n> = placeholder for the number of the brake). “_br#0” means “no brake”. Note 1: As already mentioned, normally no <brakeID> is specified if a file does not apply to a specific brake. However, it may sometimes still be practical to use a <brakeID>: in such cases (no assignment to a specific brake) “_br#0” can also be used as the <brakeID>.


Copyright: VDA

Note 2: For dynamometer tests with only one brake, the correct <brakeID> still needs to be used to indicate the assignment of the brake to a position on the actual vehicle. In addition, any existing measured values for the wheel speed with a positive sign are always interpreted as “forward” and with a negative sign as “backward” in the data sector of the EKB 3008 files. Positive torque values always represent brake torques, negative values represent driving torques. Data input systems need to take this into account and adapt the signs of the measurement data accordingly. Special features of noise tests: For noise tests, the <brakeID> is also equivalent to the location of a sensor (e.g. microphone). For example, the identifiers “_fl”, “_fr”, “_rl” and “_rr” do not only indicate that the corresponding signal belongs to these brakes in such a case, but also that the sensor was at this location. However, since (at least in the case of the inside microphones for noise tests) there may be a different location and no direct brake assignment, the following values are also used for microphone and structure-borne sound signals (EES and EEW files) instead of the previously mentioned <brakeID>: Outside microphones (fastened to the outside of the fender / in the wheelhouse, test rig as specified) _f Arrangement front _fl Arrangement front left _fr Arrangement front right _r Arrangement rear _rl Arrangement rear left _rr Arrangement rear right Inside microphones _i Arrangement inside center _if Arrangement inside front _ir Arrangement inside rear Solid-borne sound sensors (on the brake, e.g. attached to the cover panel) _fl Arrangement front left _fr Arrangement front right _rl Arrangement rear left _rr Arrangement rear right Note: the exact arrangement of the microphone and sensors normally results from the test standard applied to the test (see also EEC header entry “test_program”) and is therefore not part of this specification.


Copyright: VDA

<stopID>: identifier for the brake application If a file applies to a specific brake application, an identifier needs to be added to the file name. The corresponding brake application is indicated by the <stopID>. The <stopID> has the following structure: _nr<nnnnn> or _nr<ss>0<nnnnn> whereas <nnnnn> is the five-digit number of a brake application within the test (“00001”, “00026” etc.) and <ss> is the (optional) two-digit “step number”. (The “step number” is optional; if it is used, the number following “_nr” has eight digits; if it is not used, the number following “_nr” has five digits. Examples: _nr00001 Brake application no.1 (five digits = without step number) _nr00026 Brake application no.26 (five digits = without step number) _nr07000009 Step number 7, brake application no.9 <chanID>: identification of the input channel or measuring point If a file only includes the signal of a single input channel, a (unique) identifier with a <chanID> is additionally required (so far, only for noise tests for the EES and EEW files). The <chanID> has the following structure: _mic<nnnn> for microphones (e.g. “_mic0001”, “_mic0002” etc.) _acc<nnnn> for structure-borne sound sensors (accelerometer, e.g.

“_acc0001”, “_acc0002” etc.) _dtv<nnnn> for travel sensors (DTV measurements, e.g. “_dtv0001”,

“_dtv0002” etc.) _chn<nnnn> for any channels on which the previously mentioned identifiers

cannot be applied. <fileID>: identification of the file type Every file name ends with the <fileID> for the file type. The following values are possible for the <fileID>: _eec EEC file (main file, contains header data and overview of results) _eeh EEH file (optional header file, contains header data or additional header data) _eet EET file (optional results file, contains overview of results) _eed EED file (data file, contains measurement data for each brake application) _ees EES file (only for noise tests, contains spectrums for each brake application)


Copyright: VDA

_eew EEW file (contains raw data of fast input channels for each input channel and for each brake application, normally only for noise tests) <fileExt>: standard file extension The file extension always corresponds to the standard file type. <fileExt> should therefore be selected as follows: .csv for the text-based file types EEC, EEH, EET, EED and EES .wav for the binary “Wave Form” files of the file type EEW


Copyright: VDA

2.1 File names of the EEC file

The EEC file is always required for data exchange. It applies to the entire test for one brake. The file name consists of the test name, the <brakeID> for the corresponding brake and the “_eec” (<fileID>) for the EEC file. “.csv” is used as the file extension: <testname><brakeID>_eec.csv Examples of EEC file names: W211-P0815-T4711_fl_eec.csv Test “W211-P0815-T4711”, brake front left MYTEST001_br#2_eec.csv Test “MYTEST001”, brake no.2 The EEC file may contain header data and an overview of the results. These may also be stored in separate files as an option. One EEH file is then used for the header and one EET file for the overview of results. The file names correspond to those of the EEC file. Only the file identifier “_eec” needs to be replaced with “_eeh” or “_eet”: EEH file name: <testname><brakeID>_eeh.csv EET file name: <testname><brakeID>_eet.csv

2.2 File names of the EED file

The EED file contains the measured signals (e.g. pressure, temperature, torque, rotational speed, friction coefficient etc., sampled at a lower rate up to approx. max. 1 kHz) for one brake and one brake application (possibly including the brake pause following the brake application). The file name consists of the test name, the <brakeID> for the corresponding brake, the <stopID> for the corresponding brake application and the “_eed” (<fileID>) for the EED file. “.csv” is used as the file extension: <testname><brakeID><stopID>_eed.csv Examples of EED file names: W211-P0815-T4711_fl_nr00026_eed.csv Test “W211-P0815-T4711”, brake

front left, Brake application no. 26 MYTEST001_br#2_nr07000009_eed.csv Test “MYTEST001”, brake no. 2, step

number 7, Brake application no. 9


Copyright: VDA

2.3 File names of the EES file (only for noise tests)

EES files are only defined for noise tests (and not for other brake tests). An EES file contains the average and peak hold spectrums for one input channel (which may be assigned to a brake) and one brake application in each case. The file name consists of the test name, the <brakeID> for the corresponding brake or measurement point, the <stopID> for the corresponding brake application, the <chanID> for the input channel and the “_ees” (<fileID>) for the EES file. “.csv” is used as the file extension. If only one EES file exists for each brake and brake application, the <chanID> can be omitted. In such a case, the EES file must include the spectrums of the (airborne sound) microphone used for noise detection. The structure of the file name for an EES file is therefore as follows: <testname><brakeID><stopID><chanID>_ees.csv or alternatively <testname><brakeID><stopID>_ees.csv The corresponding <chanID> is also determined for the EES files – as described further below for the EEW files – using the EEC header entries “noise_eew_name1, …, noise_eew_name<n>”. The channel that includes the signal of the noise trigger is defined using the entry “noise_detection_eew”. The corresponding header entries apply to both file types, the EES files and the EEW files. Examples of EES file names: W211-P0815-T4711_fl_nr00026_acc0001_ees.csv

Test “W211-P0815-T4711”, Brake measurement point front left, Brake application no. 26, Structure-borne sound sensor no. 1

MYTEST001_if_nr07000009_mic0005_ees.csv

Test “MYTEST001”, Measurement point inside front, Step number 7, Brake application no. 9, Microphone no. 5

NOISETEST07_fr_nr00195_ees.csv

Test “NOISETEST07”, Brake measurement point front right, Brake application no. 195, Airborne sound microphone


Copyright: VDA

2.4 File names of the EEW file

So far, EEW files are only defined for noise and DTV tests. The EEW file includes the raw data, sampled at a high rate, of the microphone or sensor channels for one measurement point (brake or other location), one brake application and one input channel (one microphone, one sensor) in each case. The file name consists of the test name, the <brakeID> for the measurement point or the brake, the <stopID> for the corresponding brake application, the <chanID> for the corresponding input channel and “_eew” (<fileID>) for the EEW file. “.wav” is used as the file extension. If there is only one EEW file for each brake and brake application, <chanID> can be omitted. In such a case, the EEW file must always include the raw signal of the (airborne sound) microphone used for noise detection. The structure of the file name for an EEW file is therefore as follows: <testname><brakeID><stopID><chanID>_eew.wav or alternatively <testname><brakeID><stopID>_eew.wav If more signals are recorded than only the airborne sound microphone used to measure noise, the number needs to be specified using the EEC header entry “noise_eew_no”. The corresponding <chanID> is then determined for the EEW files using the EEC header entries “noise_eew_name1”, “noise_eew_name2” etc. to “noise_eew_name<no>”. The channel that includes the signal of the noise trigger is defined using the entry “noise_detection_eew”. The signal of any sensor used for the validation of the noise signals is defined using “noise_validation_eew” (for other header entries, see chapter 4.3.3). Generally, all of the corresponding header entries also apply to the file types EES and EEW. Examples of EEW file names: W211-P0815-T4711_fl_nr00026_mic0002_eew.wav

Test “W211-P0815-T4711”, Measurement point front left, Brake application no. 26, Microphone no. 2

MYTEST001_br#2_nr07000009_chn0014_eew.csv

Test “MYTEST001”, Brake no. 2, Step number 7, Brake application no. 9, Input channel no. 14

NOISETEST07_fr_nr00195_eew.wav

Test “NOISETEST07”, Brake measurement point front right, Brake application no. 195, Airborne sound microphone


Copyright: VDA

2.5 File names of the packed test archives

All files created in the context of a test are to be saved to one directory. Depending on the selected scope of information, a large number of files may be created. To transfer a complete test (e.g. via CD-ROM or e-mail attachment), all files of a test or brake may be “packed” into a single file. For this, the ZIP format and the DEFLATE compression method are to be used. Since most files are in text format, a high compression rate is thus achieved. In additional, transmission errors are detected reliably, due to the ZIP checksums. However, “.eec” (or “.eew”) should be used as <fileExt>, not “.zip”; the file is thus identified directly as brake test in the packed EKB 3008 format: <testname>.eec or alternatively (if the test is split up for individual brakes) <testname><brakeID>.eec Since the EEW files may be very extensive and therefore might need to be saved separately, they can also be stored in separate archive files with the names <testname>.eew or alternatively (only one brake) <testname><brakeID>.eew The compression can be omitted for EEW files.


Copyright: VDA

3 Format conventions With the exception of the EEW file, all file types are text files whose structure corresponds to Microsoft’s CSV (“Comma Separated Values”) format. Data fields (text information or numerical values) are stored here in text format.

3.1 General specifications

The files have a line-by-line structure. Every line ends with the character sequence <CR><LF> (Carriage Return, Line Feed).

A line may have several fields (“columns”). Within a line with several fields, the individual fields are separated by field or column separators (<colSep>). Additional field separators at the end of a line (before the end of line sequence <CR><LF>) are permitted, but normally not necessary.

Every data element (identifier, numerical value or text) is assigned to a field. Leading or trailing blanks (which enable e.g. better text formatting) are permitted. However, they will be removed by the reading program or not evaluated.

Data in floating point notation is given a decimal separator (in the English language version the decimal point). Other separators (e.g. thousands separator, in the English language version a comma) are not permitted for displaying numbers.

Texts that contain field and/or decimal separators shall be set in quotation marks (example: “this text contains ; a semicolon”). If the text itself has a quotation mark, it needs to be duplicated (example: “here, “”brake”” is in quotes” or “one inch is 1””). It is advisable to always set all texts in quotation marks.

The first line of a file must include the file identifier, which defines the file type, the file version and the language version (e.g. “eec_200_us” means: EEC file, version 2.00, US English language version). No other entries are permitted in the first line. Files with an unknown file identifier are discarded. Field and decimal separators deviate according to the language version of the operating system. To ensure the unproblematic handling of the files, the language version used must be specified in the first line. So far, the language versions “US English” and “German” are defined: “_us” identifier: US English version: decimal separator dot (.), field separator comma (,) “_de” identifier: German version: decimal separator comma (,), field separator semicolon (;)


Copyright: VDA

The second line of the EEC (anchor) file must contain the “unit system” entry made with the header identifier “unit_system”: unit_system , ekb_eu

In the first stage, formatting is planned with the units normally used in Europe (“ekb_eu”). Other unit systems may be subsequently added. The second line of all other files must reference the corresponding EEC file; this is done with the header identifier “eec_file_name”: eec_file_name , MyTest4711_fl_eec

All identifiers are not “case sensitive”, i.e. upper case or lower case may be used or a combination of both (e.g. “test_program”, “Test_Program” and “TEST_PROGRAM” are identical identifiers).

A line with leading “{” character is interpreted as a comment line and therefore ignored completely. A field that starts with the “{” character is interpreted as a comment line and ignored. Note: Such comments may only be used in the corresponding header areas. In the area of the file ID (i.e. the first and second lines of the file) and in the data sectors (i.e. between the identifiers “brake_data_begin” and “brake_data_end”), these comments are not permitted.

An identifier beginning with the “@” character is interpreted as a user-specific identifier and is ignored (however, it can be evaluated by user-specific software).


Copyright: VDA

3.2 Header lines

A header line shall start with a valid identifier; that means that the first field of a header line shall contain an identifier. Leading and trailing blanks are permitted. In general, header lines have the following structure: <headerID><colSep><value><CR><LF>

<headerID> is the placeholder for the desired header identifier, <colSep> is the field separator and <value> is the placeholder for the desired value. There are also header identifiers, to which several values need to be assigned. For example, if two values are necessary, a header line has the following structure: <headerID><colSep><value><colSep><value><CR><LF>

Example: The header identifier “caliper_piston_no” requires two values. The first value specifies the number of outer pistons and the second value the number of inner pistons. For example, the header entry caliper_piston_no , 2, 2 specifies that there are two outer and two inner pistons. Typical examples of header lines: <headerID> <colSep> <value> eec_200_de unit_system , ekb_eu test_program , SAE2521 start_date , 09/21/2008 15:49:15 total_no_of_cycles , 1430 { - this is a comment - } brake_axle , front brake_side , left brake_wheel_radius , 274 brake_init_pressure , 0.5


Copyright: VDA

3.3 Types used

Only the following data types are used to display the values in all language versions in the header and data sector of the EEC, EED and EES files: <text> Any text; if there is no entry: empty string or string filled with blanks <num> Number. With or without sign, with or without decimal separator; if there

is no entry: “novalue” or “n/a” <enum> List type, e.g. “left, right” or “front, rear” etc…; if there is no entry:

“novalue” or “n/a” <bool> Boolean expression, values are “yes” or “no”, “On” or “Off”, “1” or “0”,

“true” or “false” (always equivalent); if there is no entry: “novalue” or “n/a”

<time> Specification of a time difference in the form “(h)hh:mm:ss” <date> Specification of the date and time in the form: “dd.mm.yyyy hh:mm:ss”

(German language version) or “mm/dd/yyyy hh:mm:ss” (US English language version).

Note: Normally, value fields without values can simply be omitted, instead of using “novalue” or “n/a” (empty string). However, bear in mind that some programs (e.g. MS Excel) use the numerical value 0 without a message for such empty strings, whereas “novalue” or “n/a” will possibly result in a desired error message if there really are no measured values.


Copyright: VDA

3.4 Units used

For calculations or conversions with the data provided it is essential to transfer the data in defined units. The unit system used is specified in the header under “unit_system”. So far, only the “ekb_eu” unit system is defined; further definitions (e.g. a system with Anglo-Saxon units etc.) may still follow. (Non-SI units are displayed in bold) Unit system “ekb_eu” Value Unit Length (distance driven by the vehicle) [m] Length (total driving distance of a test) [km] Length (diameter, piston/lever travel, thickness) [mm] Length (compression values) [µm] Area (piston area) [mm²] Velocity (vehicle) [km/h] Velocity (cooling air) [m/s] Flow rate (cooling air) [m³/h] Volume (brake fluid) [mm³] Acceleration (vehicle, structure-borne sound)(1) [m/s²] Force [N] Torque [Nm] Brake pressure [bar] Pressure increase [bar/s] Sound pressure(2) [Pa] Temperature [°C] Weight [kg] Moment of inertia [kgm²] Time [s] Frequency [Hz] Angle (general, angle of rotation) [deg] Rotational Speed [rpm] Rel. humidity, axle load distribution, frequency etc. [%] Damping (lining damping) [‰] Friction coefficient, efficiency [--] (no dimension) (1) The solid-borne sound is measured in [m/s²]. Solid-borne sound levels are always displayed as rms values in [m/s²]. (2) The sound pressure is measured in [Pa]. Sound pressure levels are displayed in dB or dB(A) (i.e. 20 log (prms/p0), with prms = rms value of the sound pressure signal in [Pa] and p0 = 2x10

-5 Pa).


Copyright: VDA

4 Detailed description of the EEC file format The EEC file format is the main element for data transfer and is therefore required for every provision of data. It includes the identification (“EEC file ID”) of the file format, the file version and the language version in the first line of the file. The second line contains the specification of the unit system used (“Unit System”; this information always applies to all other files of a test). The header area (EEC header) begins in the third line, which may basically consist of any number of lines. The overview table (“EEC summary table”) with the summarized test results (one line per brake application) follows at the end of the file – indicated by the start line “brake_data_begin” and the final line “brake_data_end” – Structure of an EEC file:

4.1 EEC file ID

The first line contains the file ID (EEC file ID), which results from the string “eec_” and the version number multiplied with 100. The identifier for the language version is attached (see also Notes on the language version in chapter 3.1). Examples: eec_200_us - meaning: EEC file format, version 2.0, language version: US English eec_200_de - meaning: EEC file format, version 2.0, language version: German

4.2 Unit system definition

The second line contains the “unit_system” identifier with the value assigned to it. It defines the unit system used. So far, only the European unit system is defined with the “ekb_eu” value (see also chapter 3.2): unit_system, ekb_eu

EEC File ID

Unit System

EEC Header

EEC Summary

Table


Copyright: VDA

4.3 EEC file header

The area of the EEC file header always begins in the third line of the EEC file and ends with the start of the “EEC Summary Table” (table with overview of results, see chapter 4.4), which is indicated by the identifier “brake_data_begin”, or at the end of the file (if the “EEC Summary Table” is missing). The header data describes the boundary conditions for the test run or the boundary conditions for the vehicle equipment. Header data is to be indicated with the header identifiers listed in Appendix I and entered in the physical unit also specified there. A header entry always consists of at least two column entries: the identifier and the assigned value. Since the files are always read line by line, if identical header entries are repeated, the last entry is valid (i.e. it overwrites the previous entry). Example: brake_axle ,front brake_side ,left brake_wheel_radius ,274 brake_init_pressure ,0.5 : : : brake_wheel_radius ,311 THIS ENTRY IS VALID! You can find more information on overwriting header entries in chapter 4.6 (Description of the separate EEH header file). The header entries listed in the following should always exist. Numerous other header entries are defined in Appendix I. In addition to the mandatory entries mentioned, the number and sequence of the header entries is not defined (the parties involved in the exchange of data can define a minimum scope themselves for the intended purpose). However, in terms of the sequence of the header data, it is practical (but not mandatory) to comply with a specific sequence (e.g. the sequence selected in the attachment).


Copyright: VDA

4.3.1 Description of the test

company, <text> Specification of the company performing the test, as text. project, <text> Identification of the project (number, text or combination) to which this test belongs, as text. test, <text> Identification of the test (number, text or combination) as text. This entry should correspond to the <testname> in the file name, if possible (see also chapter 2). test_program, <text> Identification of the test program, circuit, test procedure etc. as text (e.g. “SAE J2521” or similar) test_options, <text> Optional elements of the test procedure, e.g. deviations from the standard, or similar test_rig_car, <text> Identification of the test rig or vehicle used to conduct this test, as text or number (e.g. test rig name, number plate ID etc.). test_modification, <text> Modifications made to the test object before this test (as text). test_motivation, <text> Reason / motivation for the conduction of this test (as text). test_start_date, <date> Start of the test (date + time). The start of the test is not necessarily the start of the first brake application. It is the time when the test was started on the measuring system (possibly manually, by a signal from the test rig (“Test Active”), by a signal from the test driver, etc.). test_end_date, <date> End of the test run (date + time). The end of the test run is after the end of the last brake application of the test, including the cooling down phase (if data was written, the end of the last EED file). test_time, <time> Duration of the test (equivalent to the difference “test_end_date – test_start_date”) in the format (h)hh:mm:ss. test_total_cycles, <num> Planned number of brake applications for this test.


Copyright: VDA

test_actual_cycles, <num> The number of brake applications included in this test. test_aborted, <num> Message in the event of a program abortion (0=no program abortion). Messages still need to be defined (reason for the abortion). test_error, <num> Status error (0=no error). Error numbers still need to be defined.

4.3.2 Description of the brake

The header entries listed here only consist of the mandatory entries. More detailed specifications are possible with the additional header identifiers (see Appendix I – 2.3) e.g. for “Caliper”, “Disc”, “Pad”, “Shim” etc. brake,<text> Identification of the brake or brake system examined (e.g. type designation) brake_manufacturer, <text> Manufacturer of the brake or brake system brake_part_number, <text> Part number of the brake / brake system brake_version_number, <text> Version number of the brake / brake system (e.g. in the event of modifications to / deviations from the series); Specification of a unique version number or text information on changes brake_id_number, <text> Serial number of the brake / brake system brake_axle, <enum> Axle on which the brake is located (“front”, “rear”, “axle#1”, “axle#2” etc., see also App. I-2.3.1) brake_side, <enum> Side of the axle in driving direction on which the brake is located (“left”, “right” etc. see also App. I-2.3.1) brake_type, <enum> Brake design (“disc” or “drum”) brake_wheel_load, <num> Wheel load in [kg]


Copyright: VDA

brake_piston_area, <num> Total piston area in [mm²]. This value is to be taken for friction coefficient calculations. (See also: “caliper_piston_no” and “caliper_piston_diameter” in Appendix I – 2.3.2) brake_effective_ radius, <num> Effective friction radius in [mm] brake_wheel_radius, <num> Dynamic wheel radius in [mm]. This value is used to calculate the vehicle velocity according to a measured rotational speed of the wheel brake_init_pressure, <num> Application pressure in [bar] brake_efficiency, <num> Efficiency of the brake in [--]. (for Disk = 1)

4.3.3 Description of the noise measurement

The header entries listed here are only necessary for noise tests. noise_frequency_weighting, <enum> Weighting of the airborne sound data (should always be A-weighted). Possible values: “none”, “A”. If no specification is made (no header entry or “novalue”), A-weighting is assumed. Structure-borne sound data or data of the acceleration sensors is not weighted. noise_time_weighting, <enum> Time weighting of the airborne sound data (normally there should not be any time weighting). Possible specifications: “none”, “fast”, “slow”, “pulse”. Structure-borne sound data or data of the acceleration sensors is not weighted. If there is no specification, “none” is assumed. noise_lower_level_limit, <num> Detection threshold for the microphone level in [dB] or [dB(A)] (equivalent to “noise_frequency_weighting”). See also “noise_detection”. noise_lower_duration_limit, <num> Detection threshold (minimum duration) for a noise event in [s]; see also “noise_detection”. noise_lower_frequency_limit, <num> Lower analysis frequency in [Hz] (no “detection” below this value) noise_upper_frequency_limit, <num> Upper analysis frequency in [Hz] (no “detection” above this value)


Copyright: VDA

noise_trigger_test, <bool> A noise trigger test was performed. If that is the case (“yes”), the first “brake application” includes this trigger test. The data of the first “brake application” saved may therefore not be used for the assessment of the brake. noise_detection, <text> Description of the method used for the noise detection (e.g. EKB 3006). This is the method used to assess the measured noise, which is assigned to the brake, e.g. to make the decision “noisy brake application” (and not the “Validation”, see below). noise_validation_used, <bool> “Validation” is the method used by the measuring system to decide whether a measured noise is to be assigned to the brake. If such a method is used, only “validated” noise events are applied to the “detection” (see above). If that is the case (“yes”), the table of results only contains validated noise events in the EEC file; there may also have been other noise events during the individual brake applications that were not assigned to the brake. However, if the measured noise is transferred to the “Detection” without being checked, there is no validation (entry: “no”). noise_validation, <text> Description of the method for the validation of detected noise, if one was used. A validation may e.g. take place via a more detailed analysis of the airborne sound signal itself or via the correlation with a structure-borne sound signal of the brake (other method possible). The following header entries are only necessary if several sensors (microphones, acceleration sensors etc.) were used, rather than only a single microphone. If only one microphone is used, it is assumed that the airborne sound spectrums belonging to a brake application (if stored) are in the EES file with the name (see also chapter 2.3) <testname><brakeID><stopID>_ees.csv and any stored raw data of the airborne sound signal is in the EEW file with the name (see also chapter 2.4) <testname><brakeID><stopID>_eew.wav If several sensors are used (e.g. microphone and structure-borne sound sensor or several microphones and sensors for vehicle measurement) the following header entries need to be made. Whenever these header entries exist, the previously mentioned default settings no longer apply. In this case, the names of the EES files must correspond to the specification <testname><brakeID><stopID><chanID>_ees.csv and the names of the EEW files must correspond to the specification


Copyright: VDA

<testname><brakeID><stopID><chanID>_eew.wav Even if the header identifiers listed in the following have the name “eew”, they apply to both EES and EEW files simultaneously. noise_eew_no, <num> Number <n> of the channel names (“<chanID>”) listed in the following under “noise_eew_name1” to “noise_eew_name<n>” to which the EES and/or EEW files are assigned. Channel names are the corresponding <chanID> of the input channels (see chapter 2); for example “_mic0002” for microphone no. 2 or “_chn0012” for input channel no. 12. Header entries “noise_eew_name1” to “noise_eew_name<n>” are made according to the specified amount. noise_eew_name<n>, <text> <chanID> for the <n>th input channel. Exists only if “noise_eew_number” > 0 etc. noise_eew_type<n>, <num> Type/unit of the signal of the <n>th input channel. (1=airborne sound in [Pa], 2=acceleration in [m/s²], 3=distance in [m]; see also chapter 7.2 EEW file). noise_detection_eew, <num> Number <n> of the input channel (see “noise_eew_name<n>”) that includes the signal of the noise trigger (see also “noise_lower_level_limit”). noise_validation_eew, <num> Number <n> of the input channel (see “noise_eew_name<n>”) that includes a validation signal for “noise_detection_eew” (see also “noise_validation”).


Copyright: VDA

4.4 Table with overview of results

An overview of results (“EEC Summary Table”) can be inserted in the EEC file, which contains one line per brake application (number of lines = number of brake applications in the test). The data sector with the overview of results directly follows the previously described header data and starts with the line: brake_data_begin A line with column identifiers follows directly as the next line. The number of identifiers defines the number of columns. The identifiers themselves clearly define the values in the columns and their physical units. Such a line could e.g. be as follows: Stop, test, dir, v1_start, p1_mean, frc1_mean, temp1_start, f_1, l_1, d_1, ... Two lines follow this identifier-line, which are not evaluated and which may therefore include comments. However, they shall include just as many fields (columns) as corresponds to the number of previously defined column identifiers; they should be used for the improved legibility of the table and contain column headings and the physical units in plain text. Similar to the previous example, the lines could be e.g. as follows: Stop-No., Test, Dir, Velocity, Press., Frict., TRotor, Freq1, Level1, Duration1, ... ---, ---, ---, km/h, bar, ---, °C, Hz, dB(A), s, ... These three lines with the table heading (column identifier, column heading, unit text) are followed by the corresponding data lines: one line per brake application. (Example): 1, s, f, 612, 29.4, 0.36, 100, 2125, 70.7, 0.208 2, s, f, 615, 29.4, 0.37, 100, 1650, 70.0, 0.494 3, s, f, 613, 29.4, 0.38, 101, 2125, 70.9, 0.387 Note: Since the first line after “brake_data_begin” defines the sequence and number of columns, all subsequent lines shall have the same number of columns. That is also the case if the first line in a field contains an unknown identifier or a blank field. Empty columns or special columns can thus also be created with signals not defined here. For example, if an empty column is to be inserted instead of the column for “frc1_mean” / “Friction”, the table example above would look like as follows: Stop, test, dir, v1_start, p1_mean, , temp1_start, f_1 l_1, d_1 Stop-No., Test, Dir, Velocity, Pressure, empty!, TRotor, Freq1, Level1, Duration1 ---, ---, ---, km/h, bar, , °C, Hz, dB(A), s 1, s, f, 612, 29.4, , 100, 2125, 70.7, 0.208 2, s, f, 615, 29.4, , 100, 1650, 70.0, 0.494


Copyright: VDA

To indicate user-defined identifiers (and to ensure that they can never collide with identifiers defined in EKB 3008), they should be indicated by a leading “@” character. The following example shows this:

Stop, test, dir, v1_start, p1_mean, @MyID, temp1_start, f_1 l_1, d_1 Stop-No., Test, Dir, Velocity, Pressure, MySignal, TRotor, Freq1, Level1, Duration1 ---, ---, ---, km/h, bar, kg³/Hz², °C, Hz, dB(A), s 1, s, f, 612, 29.4, 47.11, 100, 2125, 70.7, 0.208 2, s, f, 615, 29.4, 15.08, 100, 1650, 70.0, 0.494 The list of data lines is completed with the line brake_data_end All of the following entries are then ignored by the reading program. The values in the individual columns have the following meaning, depending on the column identifier selected: stop <num> The number of the brake application in the test, as integer. test <enum> The type of brake application: entry “s” = stop braking, “d” = dragging, “p” = park braking. dir <enum> Driving direction, entry “f” for “forward” and “b” for “backward”. tctrl <num> (Specified) temperature for the brake application in [°C]. tctrl_no <num> Specifies the number (1-7) of the temperature sensor used to control the current brake application (dynamometer test rig). This number shall match the numbers of the temperature sensors (see Appendix I - 1.5) and the numbers of the temperature signals “temp1” to “temp7” (see EED file, chapter 5). pctrl <num> (Specified) pressure for the brake application in [bar]. nctrl <num> (Specified) engine speed for the brake application in [rpm]. vctrl <num> (Specified) speed for the brake application in [km/h]. torqctrl <num> (Specified) torque for the brake application in [Nm].


Copyright: VDA

decctrl <num> (Specified) deceleration for the brake application in [m/s²]. sequ <num> Sequence number as integer. step <num> Step number as integer. dist <num> Braking distance in [m]. snorm <num> Normalized stopping distance in [m]. (FMVSS 135, see ISO/DIS 26867). startmean <time> Start of the brake application (time since test start in (h)hh:mm:ss). endmean <time> End of the brake application (time since test start in (h)hh:mm:ss). stoptime <num> Duration of the brake application in [s]. cycletime <num> Cycle time. Time from the start of the last brake application to the start of the current brake application in [s] (for the first brake application = 0). Noise events are entered in columns with the identifiers “f_<n>”, “m_<n>”, “l_<n>” and “d_<n>”. <n> is the sequence number of the noise event; the events are sorted by level (f_1, m_1, l_1, d_1 = loudest event, l_1 is the highest level). In the event of a noise event, the selected detection method is decisive (see also “noise_detection” in section 4.3.3). If there is no noise event, no entries are made in the data sector of the table (empty columns). For a better overview and the reduction of the required table width, the line with the column identifiers should only have as many entries <n> (f_1, m_1, l_1, d_1, f_2, m_2, l_2, d_2 … f_<n>, m_<n>, l_<n>, d_<n>) as the maximum number that occurred in the test. A number <n> greater than 20 should not be used. f_<n> <num> The frequency of the noise event <n> in [Hz]. m_<n> <num> The average level of the event <n> (at the frequency f_<n>) for the entire brake application in [dB] or [dB(A)]. l_<n> <num> The peak level of the event <n> at the frequency f_<n> in [dB] or [dB(A)].


Copyright: VDA

d_<n><num> The duration of the event <n> at the frequency f_<n> in [s] (in accordance with EKB 3006). Note: Average level values (“m_<n>”) and peak levels (“l_<n>”) apply to individual spectrum lines or band center frequencies and are to be specified as “rms” and not as “peak-to-peak”. Whether the levels are specified in unweighted [dB] or weighted [dB(A)] form depends on the EEC header entry “noise_frequency_weighting” (most tests require A-weighting!). If the parameters f, l, m, d of other input channels are to be added that do not necessarily include the airborne sound assigned to the brake, the <chanID> of the corresponding input channel is to be added to the previously described identifiers f_<n>, l_<n> etc.: f_<n><chanID> The frequency of the entry <n> in [Hz] of input channel <chanID>. m_<n><chanID> The average level of the entry <n> (at the frequency f_<n><chanID>) of input channel <chanID> for the entire brake application. l_<n><chanID> The peak level of the entry <n> (at the frequency f_<n><chanID>) of input channel <chanID>. d_<n><chanID> The duration of the entry <n> (at the frequency f_<n><chanID>) in [s] of input channel <chanID>. The level units for l_<n><chanID> and m_<n><chanID> are derived from the header entry “noise_eew_type<n>”. The following applies: 1=airborne sound, i.e. level in [dB]; 2=acceleration, i.e. level in [m/s²]; 3=distance, i.e. level in [m]. Examples: l_1_acc0003, f_1_acc0003: Maximum level l_1 (corresponding frequency f_1) that occurs during the brake application for the input channel with the <chanID> “_acc0003” (accelerometer no. 3). l_1_chn0012, m_1_chn0012: Maximum level l_1 that occurs during the brake application for the input channel with the <chanID> “_chn0012” (input channel no. 12) and average level for the entire brake application.


Copyright: VDA

In addition to the previously described column identifiers, numerous other identifiers are derived from the identifiers defined for the EED files. The chronological sequence of various different signals are defined for the EED files. Individual parameters for each brake application can be extracted from these signals and used here. For this, the following identifiers are attached to the identifiers defined for EED files: _start Value of the signal at the start of the brake application _end Value of the signal at the end of the brake application _meant Average signal value during the brake application (averaged by time) _meand Average signal value during the brake application (averaged by

distance) _peak Maximum signal value during the brake application, or _max Maximum signal value during the brake application _min Minimum signal value during the brake application _<n> Current signal value at the maximum level of the noise entry <n> Examples: p1_start Brake pressure p1 at the start of the brake application temp1_max Maximum temperature value temp1 during the brake application frc1_meant Average by time value of the friction coefficient frc1 for the brake

application temp1_1 Current temperature value temp1 at the maximum level of noise

entry 1 More defined identifiers for the “EEC Summary Table” are listed in Appendix II.


Copyright: VDA

4.5 Comment block

One comment block can be added to the file. The line comment_begin is inserted before the comment block and the line comment_end is inserted after the comment block. The number and sequence of the comment entries inserted between “comment_begin” and “comment_end” can be chosen freely as desired. The entries are ignored by an evaluation software product. The comment block can be inserted after the first two lines of the EEC file (before the header area), within the header area, and before the start of the “EEC Summary Table” (identified with “brake_data_begin”). No comment blocks are permitted within and after the “EEC Summary Table”.

4.6 Separate header: EEH file

Header entries may also be stored in a separate EEH file; the information included there is processed in the same way as if it were included in the EEC file. Parts of the header data may also be included directly in the EEC file and additional header data may be included in the EEH file. If such an EEH file is used, an entry of the form eeh_file_name, <text> is made at the point in the header area of the EEC file where the information of the EEH file is to be inserted. The file name of the corresponding EEH file needs to be specified here. This file shall also be in the same directory. If the file name is not specified (in that case, the identifier “eeh_file_name” only indicates the insertion position), a file name using the previously described convention is applied: EEH file name: <testname><brakeID>_eeh.csv The EEH file itself has the file ID eeh_200_us (or eeh_200_de) in the first line and the assignment to the corresponding EEC file in the second line: eec_file_name, <text> The header entries to be inserted are then included in the following lines.


Copyright: VDA

Note: The use of an EEH file is practical e.g. if the measuring system, which creates the EEC file, does not have sufficient information about the creation of a detailed header. Then, the missing data could be added at the end of the header created by the measuring system by means of a reference to the EEH file (caution: any duplicate header entries are overwritten; the last entry is valid).

4.7 Separate results: EET file

If the overview of results (table) is not to be saved directly to the EEC file, it can also be stored in a separate EET file. In this case, instead of the results table, a line of the form eet_file_name, <text> is to be added to the end of the EEC file. The file name of the corresponding EET file needs to be specified here. If the file name is not specified (in that case, the identifier “eet_file_name” only refers to the external table), a file name using the previously described convention is applied: EET file name: <testname><brakeID>_eet.csv The EET file itself has the file ID eet_200_us (or eet_200_de) in the first line and the assignment to the corresponding EEC file in the second line: eec_file_name, <text> The lines of the table to be inserted are then included in the following lines: brake_data_begin : ---- Table lines ---- : brake_data_end


Copyright: VDA

Example of an EEC file

General EEC file header: eec_200_us unit_system , ekb_eu company , ABC Brake Testing Inc. project , Brake Development 0815 test , Dyno Noise Test 4711 test_program , SAE2521 test_options , with ABC modifications test_rig_car , Dyno CAESAR test_modification , pad with shim XYZ test_motivation , old version too noisy test_start_date , 9/21/2008 15:49:15 test_end_date , 9/22/2008 07:10:43 test_time , 15:21:27 test_total _cycles , 1430 test_actual_ cycles , 1430 test_aborted , 0 test_error , 0 brake , XYZ Super XL brake_manufacturer , XYZ Brakes Ltd. brake_part_number , XYZ-007 brake_version_number , serial state brake_id_number , QWERT009-4711 brake_axle , front brake_side , left brake_type , disc brake_wheel_load , 400.0 brake_piston_area , 3644.0 brake_effective_radius , 158.00 brake_wheel_radius , 343.00 brake_init_pressure , 0.50 brake_efficiency , 1.00 {(more header entries in accordance with Appendix I can be optionally added)}

Additional header entries (only necessary for noise tests!): noise_frequency_weighting , A noise_time_weighting , none noise_lower_level_limit , 70.0 noise_lower_duration_limit , 0.045 noise_lower_frequency_limit , 900.0 noise_upper_frequency_limit , 16000.0 noise_detection , EKB 3006 noise_validation_used , yes noise_validation , EVS VAL01 noise_eew_no , 2 noise_eew_name1 , mic0001 noise_eew_name2 , acc0001 noise_eew_type1 , 1 noise_eew_type2 , 2 noise_detection_eew , 1 noise_validation_eew , 2 noise_trigger_test , no {(more header entries in accordance with Appendix I can be optionally added)}


Copyright: VDA

Optional comment block: comment_begin : -- any number of free comment lines – : comment_end

Overview of results: brake_data_begin stop ,test ,dir ,n1_start ,p1_mean, frc1_mean , temp1_start , f_1 , m_1 , l_1 , d_1 Stop, Test, Dir, Speed, Pressure, Friction, TRotor, Freq1, Mean1, Level1, Duration1 ---, ---, ---, rpm, bar, ---, °C, Hz, dB(A), dB(A), s 0001, s, f, 612, 29.4, 0.36, 100, 2125, 63.1, 70.7, 0.208 0002, s, f, 615, 29.4, 0.37, 100, 1650, 63.2, 70.0, 0.494 : -- in this example, 1427 more value lines follow (one line per brake application) –

: 1430, s, f, 613, 29.4, 0.38, 101, 2125, 63.4, 70.9, 0.387 brake_data_end


Copyright: VDA

5 Detailed description of the EED file format The EED file format includes the data of the signals recorded at a lower rate (max. sampling rate of approx. 1 kHz). One file is created for each brake application and brake. The maximum data volume consists of the period from starting to brake until the next brake application; data may therefore be saved with and without brake pressure applied.

5.1 EED header

eed_200_us Mandatory entry in the first line (EED file ID). Here: EED file, version 2.0, US English language version. eec_file_name, <text> The EEC file (without specification of the path) that defines the basic test. braking_start_time, <date> Date and time of the start of the brake application (activation of the trigger). elapsed_time_since_start, <num> Time since the start of the test in seconds (test start = “start_date” in EEC file). current_no_of_cycle, <num> Number of the brake application to which the data applies.

5.2 EED data sector

The data sector starts with the line: brake_data_begin A line with column identifiers follows directly as the next line. The number of identifiers defines the number of columns. The identifiers themselves clearly define the values in the columns and their physical units. Such a line could e.g. be as follows: time,p1,temp1,temp2,temp3,n1,torq1 Two lines follow this identifier-line, which are not evaluated and which may therefore include comments. However, they shall include just as many fields (columns) as corresponds to the number of previously defined column identifiers; they should be used for the improved legibility of the table and contain column headings and the physical units in plain text. Similar to the previous example, the lines could be e.g. as follows:


Copyright: VDA

Time,Press,TRotor,Temp2,Temp3,Speed,Torque s,bar,°C,°C,°C,rpm,Nm Note: Since the first line after “brake_data_begin” defines the sequence and number of columns, all subsequent lines shall have the same number of columns. That is also the case if a field contains an unknown identifier or a blank field. Empty columns or special columns can thus also be created with signals not defined here (see also chapter 4.4 “EEC Summary Table”) These three lines with the table heading (column identifier, column heading, unit text) are followed by the corresponding data lines: one line per time increment (equivalent to 1/sampling rate). Example of a data line: 0.000,19.0,99.2,0.0,0.0,615.7,465.2 The list of data lines is completed with the line brake_data_end All of the following entries are then ignored by the reading program. The first column identifier shall always be “time” for the identification of the time increment. Furthermore, there should at least be values for p1, temp1 and v1. More signals result from the requirements of the corresponding test. All column identifiers (apart from “time”) are completed by a consecutive number (e.g. temp1, temp2 etc.) to facilitate the addition of further identifiers in future file versions. time The time since the start of braking (“braking_start_time”) in seconds (with a sufficient number of decimal places). Note: The specification of “time” per time increment is necessary since no fixed time increment (sampling rate) is specified (e.g. different time increments while braking and during the following pause). The existing sampling rate therefore results from the difference of the “time” values of two consecutive lines. p1 Brake pressure 1 in [bar]. p2 Brake pressure 2 in [bar]. temp1 (alternative: trot1) Brake temperature 1 in [°C]. This is the rotor temperature (disk or drum). temp2 (alternative: tlin1) Brake temperature 2 in [°C]. This is the inner lining temperature (inboard lining).


Copyright: VDA

temp3 (alternative: tlin2) Brake temperature 3 in [°C]. This is the outer lining temperature (outboard lining). temp4 (alternative: tbpl1) Brake temperature 4 in [°C]. This is the inner backplate temperature (inboard backing plate). temp5 (alternative: tbpl2) Brake temperature 5 in [°C]. This is the outer backplate temperature (outboard backing plate). temp6 (alternative: tfld1) Brake temperature 6 in [°C]. This is temperature 1 of the brake fluid. temp7 (alternative: tfld2) Brake temperature 7 in [°C]. This is temperature 2 of the brake fluid. n1 The current rotational speed in [rpm] (if nec. calculated from the current car velocity using “brake_wheel_radius” from the EEC file). The sign is also set (specification: forward = positive sign, backward = negative sign). pos1 The current angle position (shaft position) of the wheel / of the disk or drum in [°] (0..360°). v1 The current car velocity in [km/h] (if nec. calculated from the current rotational speed using “brake_wheel_radius” from the EEC file). The sign is also set (specification: forward = positive sign, backward = negative sign). s1 The current braking distance in [m] (calculated if nec.). torq1 The current torque in [Nm]. The sign is also set (specification: braking torque = positive sign, driving torque = negative sign). frc1 The current friction value (friction coefficient) in [--] (without dimension). This value corresponds to the “instantaneous friction value” in accordance with ISO 26867. dec1 The current deceleration in [m/s²] (deceleration = positive sign). fp1 The current pedal force in [N].


Copyright: VDA

sp1 The current pedal travel in [mm]. dispf1 The currently displaced brake fluid volume (fluid displacement) in [mm³]. pbload1 The current parking brake load in [N]. pbtrav1 The current parking brake cable travel in [mm]. tamb1 The current ambient temperature in [°C]. rh1 The current relative humidity in [%]. airflow1 The current cooling air flow rate in [m³/h]. airspeed1 The current cooling air speed in [m/s]. airtemp1 The current cooling air temperature in [°C]. extr1 Current status of an external trigger. Set = 1, not set = 0. sls1 Current status of the stop light switch as trigger. Set = 1, not set = 0. Note: Since both the brake application itself as well as the following “brake pause” up to the start of the following brake application can be saved, the actual brake application is indicated by the values for “extr1”, “sls1” or possibly by the brake pressure values p1 or p2. If a trigger is used and if the pause that follows the brake application is also saved, signal “sls1” should be used, for example, to clearly define the actual brake application. If this information is not available, one can assume that no “brake pause” has been recorded. spl1 (or rms1) Overall sound pressure level in [dB] or [dB(A)]. (alternatively also “rms1”, in particular for signals that do not represent any airborne sound pressure). l1 Current maximum (peak) airborne sound level in [dB] or [dB(A)]. The maximum value of “l1” in relation to the entire brake application then becomes “l_1” in the EEC file (maximum peak level of a brake application; see also “EEC Summary Table”).


Copyright: VDA

f1 The current frequency of the level l1 described above in [Hz]. m1 The current average level at frequency f1 in [dB] or [dB(A)]. f_<n>, l_<n>, m_<n>, d_<n> If these signal identifiers, which were really only defined for the “EEC Summary Table”, are used in the EED data sector, the result is the following: frequency “f_<n>” is constant throughout the duration of the brake application (e.g. “f_1” = frequency of the maximum peak level of a brake application). The identifiers “l_<n>”, “m_<n>” und “d_<n>” provide the chronological sequence of these signals for the duration of braking at a frequency of “f_<n>”. Since the frequency “f_<n>” is only known at the end of the brake application, this data may only be generated by systems that do not create the EED files online, but e.g. perform an offline analysis of data already entered. The parameters spl1, rms1, l1, f1, m1 can also be listed for other input channels by adding the <chanID> (see chapter 2) (the unit results from the definition of the signal, e.g. m/s² instead of dB etc.) rms1<chanID>, l1<chanID>, f1<chanID>, m1<chanID> More defined identifiers for the EED data sector are listed in Appendix III.


Copyright: VDA

6 Detailed description of the EES file format The EES file format normally includes the calculated spectrums of the measured airborne sound signals. If spectrums of other signals are to be saved, the file name must additional have the <chanID> of the corresponding input channel (see also chapter 2), which is specified in the EEC header under “noise_eew_name<n>”; then, the level unit results from the EEC header entry: “noise_eew_type<n>” (for airborne sound dB or dB(A)). One file is created for each brake application and brake (and possibly input channel). It includes the peakhold and average values.

6.1 EES header

ees_200_us Mandatory entry in the first line. (Here: EES file, version 2.0, language version: US English; alternatively “ees_200_de” for German language version). eec_file_name, <text> The eec file (without specification of the path) that defines the basic test. current_no_of_cycle, <num> Number of the brake application to which the data applies.

6.2 EES data sector

The data sector starts with the line: brake_data_begin A line with column identifiers follows directly as the next line. The number of identifiers defines the number of columns. The identifiers themselves clearly define the values in the columns and their physical units. This line is normally as follows: frequency,average_level,peakhold_level Two lines follow this identifier line, which are not evaluated and which may therefore include comments. However, they shall include just as many fields (columns) as corresponds to the number of previously defined column identifiers; they should be used for the improved legibility of the table and contain column headings and the physical units in plain text. These lines are normally as follows: Frequ.,Avg. Level,Peak Level Hz,dB(A),dB(A) They are followed by the data lines (one line per frequency value). The individual values have the following contents:


Copyright: VDA

frequency <num> The frequency in [Hz] that applies to the line. average_level <num> The average rms level at this frequency for the entire brake application. peakhold_level <num> The peak-hold level (rms) of the entire brake application at this frequency. The list of data lines is ended with the line brake_data_end All of the following entries are then ignored by the reading program.


Copyright: VDA

7 Detailed description of the EEW file format The EEW file format includes the measured time data of the airborne sound, structure-borne sound and other signals (signals recorded at a high sampling rate). If only the airborne sound signals are saved, one file is created for each brake application and brake. If other input channels (e.g. structure-borne sound signals or other microphone channels) are to be saved, the corresponding <chanID> needs to be added to the file name (see also chapter 2). The EEW format is based on the WAVE format. The WAVE format itself is a sub-group of the Microsoft RIFF (Resource Interchange File Format) specification. A RIFF file consists of a file header with the following data packets, referred to as chunks. A simple WAVE file consists of the RIFF header with the “WAVE” format specification, a format sub-chunk (´fmt´) and the actual data sub-chunk (´data´). This simplest form can normally also be processed by all software packages that are basically able to read WAVE files. Special sub-chunks that the corresponding program is not able to evaluate are skipped (and therefore do not interfere). Basic information on the WAVE file format is available e.g. at: •http://ccrma.stanford.edu/courses/422/projects/WaveFormat •http://en.wikipedia.org/wiki/Wave_format However, the format sub-chunk included does not have any scaling information relating to physical data entered (e.g. SI unit information). The included information is therefore not sufficient for measuring purposes. However, the chunk principle can also be used to add proprietary information that then also only needs to be evaluated by suitable software; WAVE files modified in this way can thus be used in standard software (e.g. playback via Mediaplayer etc.). Caution is required when processing (e.g. editing) such WAVE files with standard software, since the processing results might no longer include the added (proprietary) sub-chunks. The following always applies to the EEW brake noise format: •Standard RIFF-WAVE header •One standard format sub-chunk •One proprietary EEC sub-chunk (no problem for standard software) •Only one standard data sub-chunk


Copyright: VDA

7.1 EEW header

Noise or solid-borne sound raw data is saved in binary form. The data can therefore be adapted to the WAVE format relatively simply. The EEW format therefore creates a “single” WAVE file per initiation channel and brake application and only adds a proprietary “eecw” sub-chunk to the header. This chunk contains all of the information required for the correct evaluation of the data. The header of an EEW file therefore has (at least) the following structure (example of the header of a 16-bit file): Name Contents Model Bytes Meaning Chunkname ‘RIFF’ 4 x char 4 Riff file identification

ChunkLength ??? long 4 Total file length in bytes – 8

ChunkType ‘WAVE’ 4 x char 4 “Wave” type

ChunkName ‘fmt ’ 4 x char 4 “Format” chunk name

ChunkLength 16 long 4 Chunk length in bytes

Format type 1 word 2 PCM coding

Channels 1 word 2 Number of channels (always=1)

SampleFreq ??? long 4 Sampling rate in Hz

BytesPerSec ??? long 4 SampleFreq*FrameLength

FrameLength 2 word 2 Channels*BitsPerSample/8

BitsPerSample 16 word 2 Resolution in bits (here 16)

ChunkName ‘eecw’ 4 x char 4 “eecw” chunk name

ChunkLength 28 long 4 Chunk length in bytes

Version 200 word 2 Version (here 2.00)

SystemName ‘STAC...’ 16 x char 16 System designation

ScaleFactor ??? float 4 Scaling factor

ScaleOffset ??? float 4 Scaling offset

UnitType ??? word 2 Type of phys. unit

ChunkName ‘data’ 4 x char 4 “DATA” chunk name ChunkLength ??? long 4 Chunk length in bytes

(following data: 16 or 24 bit samples)


Copyright: VDA

7.2 General specification for EEW files

Resolution either 16 bits (BitsPerSample=16) or 24 bits (BitsPerSample=24), PCM coding (Format Type=1), only one channel per file (Channels=1). Parameter in the “eecw” chunk: Version: The version number of the data format x 100. Version 1.0 (16-bit resolution only) and the current Version 2.0 (16-bit or also 24-bit resolution) are currently defined, which is why Version=100 or Version=200 needs to be set. SystemName: Free text designator of the measuring system (max. of 16 characters). ScaleFactor,ScaleOffset: Scaling factor and offset for the data. The measured value results in: Value = Data x ScaleFactor + ScaleOffset UnitType: The physical unit: 0 – unknown 1 – Air-borne sound pressure in [Pa] (microphone signal) 2 – Acceleration in [m/s²] (solid-borne sound signal) 3 – Distance in [m] (DTV distance signal) The “UnitType” is identical to the specification “noise_eew_type<n>” in the EEC header. Edited by the European Brake Noise Experts Group – Subgroup Data Processing

November, 2009


Copyright: VDA

Appendix I: EEC Header Identifier

1. Test Parameters

Identifier Type Unit Description

1.1 Responsible for the Test

company text Company which has performed this Test

name_user text User's Name (e.g. Test Engineer, Driver...)

name_responsible text Responsible's Name

1.2 Project of the Test

project text Name or ID of the Project

project_remark<n> text free comment line <n> for the project

1.3 General Test Description

test text Name or ID of Test (belonging to the Project)

test_multi_id text Name or ID of a Multi Test (multiple linked tests)

test_program text Test Program, Test Matrix ("SAEJ2521" etc.)

test_options text Program Options ("without fading, cold block...")

test_rig_car text Dyno ID or Vehicle ID used for the test

test_modification text Modifications prior to this test

test_motivation text Motivation for this test

test_remark<n> text Comment line for the test (before test)

test_finalremark<n> text Comment line for the test (after test)

1.4 Test Run Information

test_start_date date Test Start Date & Time in "dd.mm.yyyy hh:mm:ss"

test_end_date date Test End Date & Time in "dd.mm.yyyy hh:mm:ss"

test_time time Test Duration (Difference of test_end_date - test_start_date) in "(h)hh:mm:ss"

test_eval_date date Evalution Date & Time in "dd.mm.yyyy hh:mm:ss"

test_total_cycles num -- Total stops defined in Test Program

test_actual_cycles num -- Total No. of Stops executed in this Test (available data)

test_distance num km equivalent distance driven during the test

test_tamb_mean num °C Average Ambient Temperature during the Test

test_tamb_start num °C Ambient Temperature at Test Start

test_tamb_sensor_position text Ambient Temperature Sensor Position

test_rh_mean num % Average Rel. Humidity during the Test

test_rh_start num % Rel. Humidity at Test Start

test_rh_sensor_position text Rel. Humidity Sensor Position

test_dac_trigger_start text Data Acqu. Start Trigger (pressure cond., other)

test_dac_trigger_stop text Data Acqu. Stop Trigger (pressure cond., other)

test_aborted num -- Not aborted = 0, otherwise Abortion Code ID (tbd)

test_error num -- No Error = 0, otherwise Error Code ID (tbd)


Copyright: VDA


1.5 Temperature Measurement Setup

temp1_sensor text Temp1 Sensor Type (Pyrometer, Thermo Couple…)

temp1_sensor_position text Temp1 Sensor Position (disc outer rim, friction material center -1mm, backplate…)













Remark: These are sensor types and positions of temp1 ... temp7 signals (see EED Data Files).


Copyright: VDA


1.6 Dyno Test Setup (not used with Vehicle Tests)

dyno text Name or ID of the Dyno

dyno_manufacturer text Dyno Manufacturer

dyno_id_number text Dyno ID Number (e.g. Serial Number…)

dyno_axle_completeness text (corner module, incl. subframe, complete axle…)

dyno_fixture text (welded or assembled steel frame, vertical assembly plate…)

dyno_drive_via text (shaft from outer / inner, roller and wheel…)

dyno_wheel_replacement text (steel / alu wheel adaptor, rim, wheel incl. tire…)

dyno_wheel_load_simulation text (hub preload via bearing,…)

dyno_inertia_vehicle num kgm² Calculated Inertia of the Vehicle simulated

dyno_inertia_dyno num kgm² Realized Inertia on the Dyno

dyno_inertia_regulation text e.g. fully mechanical, mechanical/electrical, fully electrical…

dyno_inertia_level_no num

Number of inertia levels during the same test (e.g. FMVSS 105 or FMVSS 135 dynamometer tests). The levels are reported below (dyno_inertia_level1, dyno_inertia_level2, …, dyno_inertia_level<n>)

dyno_inertia_level<n> num kgm² Inertia value of level <n> (as reported under "dyno_inertia_level_no" above)

dyno_pressure_control text Brake Pressure Control (pneumatic, hydraulic)

dyno_pressure_ramp num bar/s Max. Pressure Ramp

dyno_air_conditioning bool Air Conditioning in Use during the Test ("yes", "no")

dyno_air_flow_mean num m³/h Average Cooling Air Flow during the Test

dyno_air_flow_start num m³/h Cooling Air Flow at Test Start

dyno_air_type text Fresh air, conditioned…

dyno_air_blower text Types: "push", "pull", "push-pull", …

dyno_air_flow_position text vertical, horizontal

dyno_air_flow_direction text caliper side, opposite to caliper, …

dyno_air_flow_fraction text e.g "complete air flow", 50%,…

dyno_remark<n> text Free Comment Line for the Dyno

dyno_setup_picture_no num Number of Picture Files listed below

dyno_setup_picture<n> text File Name of Test Setup Picture File (Photo)


Copyright: VDA


1.7 Noise Measurement Setup (Noise Tests only)

1.7.1 Detection

noise_lower_level_limit num dB Noise Level Limit for Detection (e.g. 70 dB(A))

noise_upper_level_limit num dB reserved - unused

noise_lower_duration_limit num s Noise Duration Limit for Detection (e.g. 0,045 ms)

noise_upper_duration_limit num s reserved - unused

noise_lower_frequency_limit num Hz Lower Frequency Limit for Detection (e.g. 900 Hz)

noise_upper_frequency_limit num Hz Upper Frequency Limit for Detection (e.g. 16 kHz)

noise_frequency_weighting enum A,B,C Frequency Weighting used (default: A-Weighting). Values: "none", "A", "B", "C", "D". No Weighting: "none" or "novalue". If omitted, "A" is assumed.

noise_time_weighting enum none, fast,…

Time Weighting used (default: "none"). Values: "none", "fast", "slow", "impuls". If omitted, "none" is assumed.

noise_trigger_test bool Default: "No". If "Yes": The first stop recorded belongs to a Noise Trigger Test and may not be used for evaluation.

noise_detection text Description of the Detection Procedure (e.g. "EKB 3006"…)

noise_validation_used bool If "Yes": Validation has been used, only validated Noise Events are reported

noise_validation text If any: Description/Name of the Validation Procedure

noise_limit_level<n> num dB Noise Limit Level<n> (velocity dependent)

noise_limit_velocity<n> num km/h Velocity for "noise_limit_level<n>"

1.7.2 Sensors

microphone text Type of Microphone

microphone_position text Position of Microphone (according to AK-Standard, other…)

nvh_sensor<n> text Type of additional NVH Sensor <n> (if any: microphone, accelerometer,…)

nvh_sensor_position<n> text Position of additional NVH Sensor <n>

1.7.3 Recording

noise_recorded bool yes/no Indicates if time data have been recorded (EEW files)

noise_eew_no num --

Number of Channels (recorded to EEW Files) available for this Brake. Channel Identifiers (see <chanID> in chapter 2) are reported below (noise_eew_name1, noise_eew_name2, …, noise_eew_name<n>)

noise_eew_name<n> text Channel Identifier ("<chanID>") of the Recording Number <n> (as reported under "noise_eew_no" above).

noise_eew_type<n> num According to EEW file unit definitions: 0-unknown, 1-Sound Pressure (Pa/dB), 2-Acceleration Signal from Body Sound/Vibration (m/s²), 3-DTV distance (m)

noise_trigger_eew num -- Number <n> of the Noise Trigger Recording (see "noise_eew_name<n>" above)

noise_validation_eew num -- Number <n> of the Validation Signal Recording (see "noise_eew_name<n>" above)


Copyright: VDA


1.7.4 Analyzer Setup

analyzer Name / Type of the Noise Signal Analyzer

analyzer_manufacturer text Manufacturer of the Signal Analyzer

analyzer_frequency_resolution num Hz FFT resolution (Sample Rate/ FFT Block Size)

analyzer_window enum Window Function used for Analysis (default: "Hanning"). Possible Values: "Rectangle", "Hanning", "Flat Top"

analyzer_overlap num % Time Window Overlap during Analysis. Default: 0%

analyzer_averaging num Number of Averages used by Analyzer

analyzer_fft_lines num FFT number of lines (e.g. 400, 800…)

analyzer_sample_rate num Hz Sample Rate for Noise Signals

analyzer_adc_bits num Analyzer ADC Resolution (bits) (Noise Signals)

analyzer_multifreq_detection text Multi-Frequ. Detect. Possible (yes, no, number)

1.7.5 Comments

noise_measurement_multifreq text Multi. Frequ. Stored in file (yes, no, number)

noise_measurement_remark<n> text Free Comment Line for the Noise Measurement

1.7.6 Noise Test Result Summary

noise_no_of_cycles num -- Total Amount of Noisy Stops

noise_total_occurence num % noise_no_of_cycles / test_actual_cycles

noise_level_1_mean num dB Average Max. Noise Level of Noisy Stops

noise_level_1_max num dB Highest Max. Noise Level

noise_frequency_1_max num Hz Frequency of Highest Max. Noise Level

noise_level_2_max num dB 2nd high Max. Noise Level

noise_frequency_2_max num Hz Frequency of 2nd high Max. Noise Level

noise_fband_freq<n> num Hz Frequency Band <n> - highest Occurence

noise_fband_occ70db<n> num % Rel. Occurance >70dB in Frequency Band <n>

noise_fband_occ80db<n> num % Rel. Occurance >80dB in Frequency Band <n>

noise_fband_eventnum<n> num -- Number of Events in Frequency Band <n>

noise_fband_levelmax<n> num dB max. Level in Frequency Band <n>

noise_fband_levelmean<n> num dB mean Level in Frequency Band <n>

noise_fband_fwnum<n> num -- "forward" Events in Frequency Band <n>

noise_fband_bwnum<n> num -- "backward" Events in Frequency Band <n>

noise_fband_nmin<n> num 1/min min. rot. Speed of Frequency Band <n> Events

noise_fband_nmax<n> num 1/min max. rot. Speed of Frequency Band <n> Events

noise_fband_vmin<n> num km/h min. Velocity of Frequency Band <n> Events

noise_fband_vmax<n> num km/h max. Velocity of Frequency Band <n> Events

noise_fband_tmin<n> num °C min. Temperature of Frequency Band <n> Events

noise_fband_tmax<n> num °C max. Temperature of Frequency Band <n> Events

noise_fband_pmin<n> num bar min. Pressure of Frequency Band <n> Events

noise_fband_pmax<n> num bar max. Pressure of Frequency Band <n> Events


Copyright: VDA

2. Test Object Parameters


2.1 Vehicle / Car

vehicle text Name/Type of the Car (OEM project name... )

vehicle_manufacturer text Vehicle Manufacturer

vehicle_version_number text Vehicle Evolution Step

vehicle_id_number text Vehicle ID Number (e.g. Serial Number…)

vehicle_mass num kg Test Weight (see also: "dyno_inertia_vehicle")

vehicle_load_condition text gross vehicle weight, half fuel + driver, etc.

vehicle_mass_laden num kg max. declared mass by vehicle manufacturer (GVWR)

vehicle_mass_unladen num kg mass of unladen vehicle (LLVW)

vehicle_mass_front num kg max. mass on front axle when stationary (GAWRf)

vehicle_mass_rear num kg max. mass on rear axle when stationary (GAWRr)

vehicle_brake_distribution num % Brake Force Distribution (% front)

vehicle_brake_configuration text disc/disc, disc/DiH, disc/drum, drum/drum

vehicle_brake_electronic text none, ABS, ESC, EBP, …

2.2 Suspension

2.2.1 Suspension General

suspension text Type / Name of Suspension, Suspension Parts

suspension_spring text Type / Name of Spring

suspension_damper text Type / Name of Damper

suspension_version_number text Suspension Evolution Step

suspension_last_modified date Date of last suspension modification

suspension_remark<n> text Free Comment Line for the Suspension

2.2.2 Knuckle

knuckle text Type / Name of the Knuckle

knuckle_manufacturer text Knuckle Manufacturer

knuckle_part_number text Knuckle Part Number

knuckle_version_number text Knuckle Evolution Step

knuckle_id_number text Knuckle ID Number (e.g. Serial Number…)

knuckle_sec_measure<n> text Knuckle Secondary Measure <n>

knuckle_eigenfrequency_no num -- Amount of Knuckle Eigen Frequencies reported (default: max. 2)

knuckle_eigenfrequency_values num Hz Knuckle Eigen Frequency Values in [Hz] (amount of values = "knuckle_eigenfrequency_no")

knuckle_mode_descriptions text Knuckle Mode Descriptions (amount of values = "knuckle_eigenfrequency_no")

knuckle_remark<n> text Free Comment Line for the Knuckle

2.2.3 Other Axle Parts

axlepart_no num Amount of Axle Parts listed below

axlepart<n> text Axle Part <n> Description (damper, spring etc.)

axlepart_part_number<n> text Axle Part <n> Part Number

axlepart_version_number<n> text Axle Part <n> Evolution Step


Copyright: VDA


2.3 Brake

2.3.1 Brake General

brake text Type / Name of the Brake (Brake System)

brake_manufacturer text Brake Manufacturer

brake_part_number text Brake Part Number

brake_version_number text Brake Evolution Step

brake_id_number text Brake ID Number (e.g. Serial Number…)

brake_axle enum front, rear

Axle where the Brake belongs to: "front", "rear". If not applicable: count axles (#1=front): "axle#1", "axle#2", …

brake_side enum left, right

Side of the Brake: "left", "right". If multiple brakes on one side: count from outside to inside ("left#1", "left#2", …, "right#2", "right#1")

brake_type enum disc, drum

Type of the Brake: "disc" or "drum"

brake_wheel_load num kg Load of the Wheel where the Brake belongs to

brake_piston_area num mm² Total Area to calculate Actuation Force

brake_effective_radius num mm Effective Radius of the Brake

brake_wheel_radius num mm Dynamic Wheel Radius

brake_init_pressure num bar Initial Pressure Threshold

brake_efficiency num -- Brake Efficiency (default for disc = 1.0)

brake_remark<n> text free comment line for Brake / Brake System

2.3.2 Caliper

caliper text Type / Name of the Caliper

caliper_manufacturer text Caliper Manufacturer

caliper_part_number text Caliper Part Number

caliper_version_number text Caliper Evolution Step

caliper_id_number text Caliper ID Number (e.g. Serial Number…)

caliper_batch_number text Caliper Batch Number

caliper_piston_no num -- Amount of Pistons: two values. First value = outer pistons, second value = inner pistons (Example: 2; 2 = 2 outer & 2 inner pistons)

caliper_piston_diameters num mm

Piston Diameters in [mm]. Amount of Values = Amount reported under "caliper_piston_no". At first values for outer pistons, then values for inner pistons. Total area of all pistons is reported under "brake_piston_area" above.

caliper_sec_measure<n> text Caliper Secondary Measure <n>

caliper_condition text Actual Caliper Condition

caliper_eigenfrequency_no num -- Amount of Caliper Eigen Frequencies reported (default: max. 2)

caliper_eigenfrequency_values num Hz Caliper Eigen Frequency Values in [Hz] (amount of values = "caliper_eigenfrequency_no")

caliper_mode_descriptions text Caliper Mode Descriptions (amount of values = "caliper_eigenfrequency_no")

caliper_mass num kg Mass of Caliper

caliper_remark<n> text Free Comment Line for the Caliper


Copyright: VDA


2.3.3 Disc

disc text Type / Name of the Disc

disc_manufacturer text Disc Manufacturer

disc_part_number text Disc Part Number

disc_version_number text Disc Evolution Step

disc_id_number text Disc ID Number (e.g. Serial Number…)

disc_batch_number text Disc Batch Number

disc_diameter_nominal num mm Disc Nominal Diameter

disc_thickness_nominal num mm Disc Nominal Thickness

disc_thickness num mm Disc Actual Thickness

disc_ventilation text Description of Disc Ventilation

disc_material text Disc Material

disc_first_test text Disc used first in Test (Name / ID)

disc_corrosion_protection text Information about Disc Corrosion Protection (if any)

disc_rim_adapter bool Rim Adapter present ("yes", "no")

disc_rim_adapter_material text Description of Rim Adapter Material

disc_sec_measure<n> text Disc Secondary Measure <n>

disc_condition text Disc Condition (new, little wear, wear>10%...)

disc_eigenfrequency_no num -- Amount of Disc Eigen Frequencies reported (default: max. 2)

disc_eigenfrequency_values num Hz Disc Eigen Frequency Values in [Hz] (amount of values = "disc_eigenfrequency_no")

disc_mode_descriptions text Disc Mode Descriptions (amount of values = "disc_eigenfrequency_no")

disc_assessment_after_test text Condition of the disc after test

disc_remark<n> text Free Comment Line for the Disc

If “brake_type” is set to “drum”, use the “disc_...” identifiers (if applicable) and exchange “disc_” against “drum_”. Some examples:

2.3.3 Drum

drum text Type / Name of the Drum

drum_manufacturer text Drum Manufacturer

drum_part_number text Drum Part Number

drum_version_number text Drum Evolution Step

drum_id_number text Drum ID Number (e.g. Serial Number…)

drum_batch_number text Drum Batch Number

The following identifier is applicable for drum brakes only:

drum_type text Simplex, duplex, duo, uni servo, s-cam, simplex wedge, duo duplex wedge… (see ISO 611)

Identifiers listed under item 2.3.2 (“caliper”) still apply for drum brakes (except for thickness measurements). Identifiers listed under item 2.3.4 (“pad”) still apply for drum brakes.

Important:

The instantaneous friction value µ* for disc brakes or the C* value for drum brakes are both calculated by using “brake_piston_area”, “brake_effective_radius”, “brake_init_pressure”, and “brake_efficiency” of item 2.3.1.


Copyright: VDA


2.3.4 Pad

pad text Type / Name of the Pad

pad_manufacturer text Pad Manufacturer

pad_part_number text Pad Part Number

pad_version_number text Pad Evolution Step

pad_id_number text Pad ID Number (e.g. Serial Number…)

pad_batch_number text Pad Batch Number

pad_batch_size num -- Pad Batch Size

pad_wva_number text Pad WVA Number

pad_fmsi_number text Pad FMSI Number

pad_friction_material text Description of Friction Material

pad_lining_dsheet text Lining Data Sheet Number / Reference

pad_underlayer text Type of Under Layer

pad_chamfers text Chamfer Description (or "yes", "no"…)

pad_slots text Slots Description (or "yes", "no"…)

pad_backp_thickness num mm Backing Plate Thickness

pad_lining_thickness num mm Lining Thickness (before Test)

pad_lining_finalthickness num mm Lining Thickness after Test

pad_condition text Pad Condition (new, little wear, wear>10%...)

pad_first_test text Pad used first in Test (Name / ID)

pad_disc_pairing text Pad/Disc Pairing (from previous test, new pairing,...)

pad_shim_used bool yes,no Indicate if a Shim is used ("yes", "No")

pad_grease_used bool yes,no Indicate if grease is used

pad_sec_measure<n> text Pad Secondary Measure <n>

pad_compressvalue_type enum k3, k6 Type of Compress Value ("k3", "k6")

pad_compressvalue_inner num µm Inner Pad Compress Value

pad_compressvalue_outer num µm Outer Oad Compress Value

pad_eigenfrequency_inner_no num -- Amount of Inner Pad Eigen Frequencies reported (default: 1)

pad_eigenfrequency_inner_values num Hz Inner Pad Eigen Frequency Values in [Hz] (amount of values = "pad_eigenfrequency_inner_no")

pad_eigenfrequency_outer_no num -- Amount of Outer Pad Eigen Frequencies reported (default: 1)

pad_eigenfrequency_outer_values num Hz Outer Pad Eigen Frequency Values in [Hz] (amount of values = "pad_eigenfrequency_outer_no")

pad_damping_inner_no num -- Amount of Inner Pad Damping Values reported (default: 1)

pad_damping_inner_values num ‰ Inner Pad Damping Values in [‰] (amount of values = "pad_damping_inner_no")

pad_damping_outer_no num -- Amount of Outer Pad Damping Values reported (default: 1)

pad_damping_outer_values num ‰ Outer Pad Damping Values in [‰] (amount of values = "pad_damping_outer_no")

pad_mode_inner_descriptions text Inner Pad Mode Descriptions (amount of values = "pad_eigenfrequency_inner_no")

pad_mode_outer_descriptions text Outer Pad Mode Descriptions (amount of values = "pad_eigenfrequency_outer_no")


Copyright: VDA


pad_assessment_after_test text Condition of the Pad after the Test

pad_spring_part_number text Pad Fixing Spring Part Number

pad_spring_version_number text Pad Fixing Spring Evolution Step

pad_spring_material text Pad Fixing Spring Material

pad_spring_first_test text Pad Spring used first in Test (Name / ID)

pad_remark<n> text Free Comment Line for the Pad


2.3.5 Shim

shim text Type / Name of the Shim

shim_manufacturer text Shim Manufacturer

shim_part_number text Shim Part Number

shim_version_number text Shim Evolution Step

shim_batch_number text Shim Batch Number

shim_description text Shim Description

shim_attachment text Shim Attachment

shim_riveted bool Shim riveted? ("yes" or "no")

shim_painted bool Shim painted? ("Yes" or "no")

shim_assessment_after_test text Condition of the Shim after the Test

shim_remark<n> text Free Comment Line for the Shim


Copyright: VDA

Appendix II: EEC Result Summary Table Identifier


EEC Result Summary Table

stop num -- Actual Number of Brake Application

test enum Type of Brake Application. "s" = stop braking, "d" = dragging, “p” = parking brake

dir enum Direction. "f" = forwards, "b" = backwards

sequ num -- Sequence Number

step num -- Step Number

dist num m Braking Distance

snorm num M Normalized stopping distance (see ISO/DIS 26867)

mfdd num m/s² Mean fully developed deceleration (ECE Reg 13-H)

dil_no num Actual dyno inertia level number (Appendix I-1.6)

tctrl num °C Temperature Control Value

tctrl_no num Identifies the thermocouple, which is used to control the cycle (number of sensor listed under item 1.5)

pctrl num bar Pressure Control Value

nctrl num 1/min Shaft Speed Control Value

vctrl num km/h Velocity Control Value

torqctrl num Nm Torque Control Value

decctrl num m/s² Deceleration Control Value

startmean time Stop begin (since test start in (h)hh:mm:ss)

endmean time Stop end (since test start in (h)hh:mm:ss)

stoptime num s Stop duration

cycletime num s Elapsed time from start of previous stop to start of current stop

l_<n> (or l<n>_<n>) num dB Level of <n> highest Peak

f_<n> (or f<n>_<n>) num Hz Frequency of <n> highest Peak

m_<n> (or m<n>_<n>) num dB Average Level of <n> highest Peak

d_<n> (or d<n>_<n>) num s Duration of <n> highest Peak

l_<n><chanID> num Level of <n> highest Peak of channel <chanID>

f_<n><chanID> num Hz Frequency of <n> highest Peak of channel <chanID>

m_<n><chanID> num Average Level of <n> highest Peak of <chanID>

d_<n><chanID> num s Duration of <n> highest Peak of channel <chanID>

In addition, the following identifiers may be used (extracted from EED Data signals, <EED-ID> = EED Data Table Identifier, see Appendix III):

<EED-ID>_start value at stop begin <EED-ID>_end value at stop end <EED-ID>_mean or <EED-ID>_meant value averaged by stop time <EED-ID>_meand value averaged by stop distance <EED-ID>_peak or <EED-ID>_max highest value during stop <EED-ID>_min lowest value during stop <EED-ID>_<n> value at occurence of noise event <n> <EED-ID>_<n><chanID> value at occurence of event <n> at <chanID>

Examples:

p1_mean brake pressure averaged by time temp1_start rotor temperature at stop begin n1_1 shaft speed at noise event 1 l_1_chn0012 highest peak level of channel no. 12


Copyright: VDA

Appendix III: EED Data Table Identifier


EED Data Table

time num s Actual Time since Stop Begin

p1 num bar Brake Pressure 1

p2 num bar Brake Pressure 2

temp1 (or trot) num °C Rotor Temperatur (alt.: "trot")

temp2 (or tlin1) num °C Inboard Lining Temperature (alt.: "tlin1")

temp3 (or tlin2) num °C Outboard Lining Temperature (alt.: "tlin2")

temp4 (or tbpl1) num °C Inboard Backing Plate Temp. (alt.: "tbpl1")

temp5 (or tbpl2) num °C Outboard Backing Plate Temp. (alt.: "tbpl2")

temp6 (or tfld1) num °C Fluid Temperatur 1 (alt.: "tfld1")

temp7 (or tfld2) num °C Fluid Temperatur 2 (alt.: "tfld2")

n1 num 1/min Brake Shaft Speed

pos1 num deg Shaft position angle in [deg] (0..360°)

v1 num km/h Car Velocity

s1 num m Actual Braking Distance

torq1 num Nm Brake Torque

frc1 num -- Friction Coefficient

dec1 num m/s² Deceleration

fp1 num N Pedal Force

sp1 num mm Pedal Travel

dispf1 num mm³ Fluid displacement

pbload1 num N Parking brake load

pbtrav1 num mm Parking brake cable travel

tamb1 num °C Ambient Temperature

rh1 num % Relative Humidity

airflow1 num m³/h Cooling Air Flow

airspeed1 num m/s Cooling Air Speed

airtemp1 num °C Cooling Air Temperature

extr1 bool External Trigger ("0" or "1")

sls1 bool Stop Light Switch ("0" or "1")

gpslat1 num deg GPS Latitude (North = +, South = -)

gpslong1 num deg GPS Longitude (East = +, West = -)

gpsspeed1 num Km/h GPS speed over ground

gpsgeohgt1 num m GPS geodetical height (+/- mean sea level)

gpsanthgt1 num m GPS antenna height (+/- mean sea level)

gpssats1 num -- GPS number of satellites in view

gpsutc1 date GPS UTC time (date + hh:mm:ss)

gpscourse1 num deg GPS course (North = 0°)

gpshdop1 num m GPS horizontal dilution of precision

gpsvdop1 num m GPS vertical dilution of precision

gpsstatus1 text GPS status information (**)

(continued on next page)


Copyright: VDA

EED Data Table Identifier – continued -


EED Data Table

spl1 (or rms1) num dB Overall sound pressure level (rms level)

l<n> num dB Level of <n> highest peak (at frequency f<n>)

f<n> num Hz Frequency of <n> highest peak

m<n> num dB Mean level of <n> highest peak (at frequency f<n>)

spl1<chanID> (or rms1…) num dB,… Overall rms level of channel <chanID>(*)

l<n><chanID> num dB,

m/s²… Level of <n> highest peak (at frequency f<n>) of channel <chanID>(*)

f<n><chanID> num Hz Frequency of <n> highest peak of channel <chanID>

m<n><chanID> num dB,

m/s²… Mean level of <n> highest peak (at frequency f<n>) of channel <chanID>(*)

(*) <chanID> is the identifier of the input channel, like “_mic0001”, “_acc0003”, or “_chn0012”. (See chapter 2 for details). Level units are obtained by EEC header identifier “noise_eew_type<n>”.

(**) GPS Status Information: A text string consisting of four numbers: “SQFM”

S – Status: 0-unknown, 1-invalid, 2-valid Q – Qualtiy: 0-unknown, 1-no fix, 2-GPS, 3-DGPS F – Fix Type: 0-unknown, 1-no fix, 2-2D, 3-3D M – Mode: 0-unknown, 1-manual, 2-automatic Example: valid, DGPS, 2D, automatic: gpsstatus1 = “2322”


Copyright: VDA

Appendix IV: PB Header List Cross Reference

An extension of EKB 3008 based data files is a header list which consists of all relevant informations for dynamometer noise tests. This list consists of data values identified by ID values. The ID values are grouped into categories, ranging from 1 to 9. In the following, the Header list (developed by Porsche and Bosch) is called “PBH”. The file name of such a list should be

<testname><brakeID>_PBH.csv

If the list is generated in CSV format, it can easily be loaded into Excel sheets.

One line of the list file consists of the following fields

<category>; <custom language description>; <PB Description>; <value>; <PBID>

where

<category>

is the name of the category, like “1 – Project”, “2 – General Set-Up”, … , “9 – Pad”.

<custom language description>

is the “PB Description” (as listed below) in a custom language (e.g. German)

<PB Description>

is the description of the item as listed below

<value>

is the actual value of the item, derived or converted from EKB 3008 data (see identifiers listed below). If the value is not available (“novalue”), the text “(ID <PBID>)” is set instead.

<PBID>

The ID value of the item as listed below.

There are as many lines in a list file as PBIDs are defined (see below).

Example

„1 – Project“; „Fahrzeug“; „Car; “Beispielfahrzeug”; 101 „1 – Project“; „Achse“; „Axle“; „Vorderachse“; 102

(lines for ID 103 up to ID 207)

“2 – General Set-Up”; „Massenträgheitsmoment (Fzg.) / kgm²”; “Inertia (vehicle) / kgm²”; “(ID 208)”; 208


“4 – Test specific”; “Laufstrecke / km”; “distance / km”; 1180; 431


“9 – Pad”; “Zustand Belag”; “Pad Condition”; “(ID 924)”; 924

(lines up to ID 942)


Copyright: VDA

Category: 1 - Project

PBID EEC Header Identifier / Conversion PB Description

101 vehicle Car

102 brake_axle Axle

103 project Project ID

104 project_remark1 Remark (Project)

105 project_remark2 Remark 2 (Project)

Category: 2- General Set-Up


201 brake_side Side to test

202 dyno_axle_completeness Axle completeness

203 dyno_fixture Fixture

204 dyno_drive_via Drive via

205 dyno_wheel_replacement Wheel replacement

206 dyno_wheel_load_simulation Wheel load simulation

207 brake_wheel_load Vertical wheel load / kg

208 dyno_inertia_vehicle Inertia (vehicle) / kgm²

209 dyno_inertia_dyno Inertia (dyno) / kgm²

210 brake_wheel_radius / 1000 R dyn. /m

211 brake_effective_radius / 1000 R eff. /m

212 brake_piston_area / 1.0E+6 Area "inner piston(s)" /m²

213 brake_efficiency * 100% Efficiency /%

214 dyno_remark1 Remark (Gen. Set-Up)

215 dyno_remark2 Remark2 (Gen. Set-Up)

216 dyno_remark3 Remark3 (Gen. Set-Up)

217 test_rig_car or dyno Dyno ID

218 dyno_manufacturer Dyno Supplier

219 vehicle_mass vehicle total mass

220 vehicle_load_condition vehicle load condition

221 vehicle_brake_distribution brake force distribution, front

222 100% - vehicle_brake_distribution brake force distribution, rear

223 dyno_inertia_regulation Inertia regulation

224 dyno_pressure_control Pressure control

225 dyno_pressure_ramp max. pressure ramp


Copyright: VDA

Category: 3 - Measurement Set-Up


301 microphone_position Microphone position

302 nvh_sensor1 NVH sensor2 (type)

303 nvh_sensor_position1 NVH sensor 2 (position)

304 temp1_sensor temperature sensor 1 (type)

305 temp1_sensor_position temperature sensor 1 (position)

306 temp2_sensor temperature sensor 2 (type)

307 temp2_sensor_position temperature sensor 2 (position)

308 noise_lower_frequency_limit Lower frequency limit / Hz

309 noise_upper_frequency_limit Upper frequency limit / Hz

310 noise_lower_level_limit SPL threshold /dB(A)

311 analyzer Data acquisition system system

312 noise_measurement_remark1 Remark (Meas. Set-Up)

313 noise_measurement_remark2 Remark2 (Meas. Set-Up)

314 noise_measurement_remark3 Remark3 (Meas. Set-Up)

315 nvh_sensor2 NVH sensor 3 (type)

316 nvh_sensor_position2 NVH sensor 3 (position)

317 noise_limit_level1 SPL threshold 2 (veloc. dep.) /dB(A)

318 noise_limit_velocity1 velocity for SPL threshold 2 / kph

319 noise_limit_level2 SPL threshold 3 (veloc. dep.) /dB(A)

320 noise_limit_velocity2 velocity for SPL threshold 3 / kph

321 noise_recorded time data recorded

322 analyzer_sample_rate sample rate / Hz

323 analyzer_adc_bits resolution / bit

324 noise_frequency_weighting (if A=yes) A-weighting

325 analyzer_fft_lines FFT lines (number)

326 analyzer_overlap overlapping / %

327 analyzer_averaging Averaging (number)

328 analyzer_window FFT window type

329 analyzer_multifreq_detection multiple frequency detection possible

330 noise_measurement_multifreq multiple frequencies shown in report

331 test_dac_trigger_start data acquisition start trigger

332 test_dac_trigger_stop data acquisition stop trigger

333 noise_lower_duration_limit Noise Duration Limit / s

334 noise_detection Noise Detection

335 noise_validation_used Noise Validation used

336 noise_validation Noise Validation


Copyright: VDA

Category: 4 - Test specific


401 test_program Test matrix description

402 test_options Test matrix options

403 test Test-No.

404 test_start_date date (start)

405 test_eval_date date (evaluation)

406 test_time (convert to hours) Test duration / h

407 test_actual_cycles No. of brake applications performed

408 test_tamb_mean Air temperature (nominal) / °C

409 test_rh_mean rel. air humidity (nominal) / %

410 dyno_air_flow_mean Cooling air flow (nominal) /m³/h

411 test_modification Modifications prior to this test

412 test_motivation Motivation for this test

413 noise_total_occurence total noise occurence (relative) / %

414 noise_level_1_mean Average SPL / dB(A)

415 noise_level_1_max Max. SPL / dB(A)

416 noise_frequency_1_max Freq. @ Max. SPL / Hz

417 noise_level_2_max 2nd high SPL / dB(A)

418 noise_frequency_2_max Freq. @ 2nd high SPL / Hz

419 test_remark1 Remark1 (before test)



422 name_user Performed by

423 name_responsible Responsible

424 test_tamb_start Air temperature (measured) / °C

425 test_tamb_sensor_position Air temperature - sensor location

426 test_rh_start rel. air humidity (measured) / %

427 test_rh_sensor_position rel. air humidity - sensor location

428 dyno_air_flow_start Cooling air flow (measured) /m³/h

429 dyno_air_flow_fraction Cooling air flow - fraction at brake

430 dyno_setup_picture1,…,dyno_setup_picture<n> Photos of test set-up

431 test_distance distance / km

432 test_total_cycles no. of brake applications (nominal)

433 test_finalremark1 Remark4 (after test)



(continued on next page)


Copyright: VDA


436 noise_no_of_cycles total noise occurence (number)

437 noise_fband_freq1 Frequency band 1 - highest occurence

438 noise_fband_occ70db1 f1: rel. occurence > 70 dB(A) / %


440 noise_fband_eventnum1 f1: Number of events

441 noise_fband_levelmax1 f1: max. SPL / dB(A)

442 noise_fband_levelmean1 f1: mean SPL / dB(A)

443 noise_fband_fwnum1 / noise_fband_bwnum1 f1: Travel Direction (fw/bw)

444 noise_fband_nmin1 - noise_fband_nmax1 f1: velocity range / 1/min

445 noise_fband_vmin1 - noise_fband_vmax1 f1: velocity range / km/h

446 noise_fband_tmin1 - noise_fband_tmax1 f1: temperature range / °C

447 noise_fband_pmin1 - noise_fband_pmax1 f1: pressure range / bar

.. up to:

459 noise_fband_freq3 Frequency band 3 - highest occurence



462 noise_fband_eventnum3 f3: Number of events

463 noise_fband_levelmax3 f3: max. SPL / dB(A)

464 noise_fband_levelmean3 f3: mean SPL / dB(A)

465 noise_fband_fwnum3 / noise_fband_bwnum3 f3: Travel Direction (fw/bw)

466 noise_fband_nmin3 - noise_fband_nmax3 f3: velocity range / 1/min

467 noise_fband_vmin3 - noise_fband_vmax3 f3: velocity range / km/h

468 noise_fband_tmin3 - noise_fband_tmax3 f3: temperature range / °C

469 noise_fband_pmin3 - noise_fband_pmax3 f3: pressure range / bar


Copyright: VDA

Category: 5 - Suspension


501 suspension_version_number Suspension (evolution step)

502 suspension_last_modified last modified (date)

503 suspension_spring / suspension_damper Spring / damper (description)

504 suspension_remark1 Remark (suspension)

505 suspension_remark2 Remark2 (suspension)

506 suspension_remark3 Remark3 (suspension)

507 axlepart1 axle part 1 - description

508 axlepart_part_number1 axle part 1 - part no.

509 axlepart_version_number1 axle part 1 - evolution step

.. up to:

564 axlepart20 axle part 20 - description

565 axlepart_part_number20 axle part 20 - part no.

566 axlepart_version_number20 axle part 20 - evolution step

Category: 6 - Knuckle


601 knuckle_manufacturer Knuckle manufacturer

602 knuckle Knuckle type

603 knuckle_part_number Knuckle part-No.

604 knuckle_version_number Knuckle evolution step

605 knuckle_id_number Knuckle ID-No.

606 knuckle_sec_measure1 Knuckle secondary measures

607 knuckle_remark1 Remark (knuckle)

608 knuckle_remark2 Remark2 (knuckle)

609 knuckle_remark3 Remark3 (knuckle)

610 knuckle_eigenfrequency_values (1st value) Knuckle eigenfrequency (1) / Hz

611 knuckle_mode_descriptions (1st entry) Knuckle mode (1) description

612 knuckle_eigenfrequency_values (2nd value) Knuckle eigenfrequency (2) / Hz

613 knuckle_mode_descriptions (2nd entry) Knuckle mode (2) description


Copyright: VDA

Category: 7 - Caliper


701 caliper_manufacturer Caliper manufacturer

702 caliper Caliper type

703 caliper_piston_diameters (1st inner value) Piston diameter, inner1 / mm

704 caliper_piston_diameters (2nd inner value) Piston diameter, inner2 / mm

705 caliper_piston_diameters (3rd inner value) Piston diameter, inner3 / mm

706 caliper_piston_diameters (4th inner value) Piston diameter, inner4 / mm

707 caliper_piston_diameters (5th inner value) Piston diameter, inner5 / mm

708 caliper_piston_diameters (1st outer value) Piston diameter, outer1 / mm

709 caliper_piston_diameters (2nd outer value) Piston diameter, outer2 / mm

710 caliper_piston_diameters (3rd outer value) Piston diameter, outer3 / mm

711 caliper_piston_diameters (4th outer value) Piston diameter, outer4 / mm

712 caliper_piston_diameters (5th outer value) Piston diameter, outer5 / mm

713 caliper_part_number Caliper part-No.

714 caliper_version_number Caliper evolution step

715 caliper_id_number Caliper ID-No.

716 caliper_batch_number Caliper batch-No.

717 caliper_sec_measure1 Caliper secondary measures

718 caliper_condition Caliper condition

719 caliper_eigenfrequency_values (1st value) Caliper eigenfrequency (1) / Hz

720 caliper_mode_descriptions (1st entry) Caliper mode (1) description

721 caliper_eigenfrequency_values (2nd value) Caliper eigenfrequency (2) / Hz

722 caliper_mode_descriptions (2nd entry) Caliper mode (2) description

723 caliper_remark1 Remark (caliper)

724 caliper_remark2 Remark2 (caliper)

725 caliper_remark3 Remark3 (caliper)

726 caliper_mass*1000 mass (caliper) / g


Copyright: VDA

Category: 8 - Disc


801 disc_manufacturer Disc manufacturer

802 disc Disc type

803 disc_diameter_nominal / disc_thickness_nominal Disc nominal diamtr./thickness / mm

804 disc_part_number Disc part-No.

805 disc_version_number Disc evolution step

806 disc_id_number Disc ID-No.

807 disc_batch_number Disc batch-No.

808 disc_thickness Disc thickness measured / mm

809 disc_condition Disc condition

810 disc_sec_measure1 Disc secondary measures

811 disc_eigenfrequency_values (1st value) New disc eigenfrequency (1) / Hz

812 disc_mode_descriptions (1st entry) Disc mode (1) description

813 disc_eigenfrequency_values (2nd value) New disc eigenfrequency (2) / Hz

814 disc_mode_descriptions (2nd entry) Disc mode (2) description

815 disc_eigenfrequency_values (all values <10kHz) All New Disc Eig.freqs. <10kHz / Hz

816 disc_remark1 Remark (disc)

817 disc_remark2 Remark2 (disc)

818 disc_remark3 Remark3 (disc)

819 disc_ventilation description disc ventilation

820 disc_material disc material

821 disc_first_test disc used first in test no.


Copyright: VDA

Category: 9 - Pad


901 pad_manufacturer Pad manufacturer

902 pad_friction_material Friction Material

903 pad_part_number Pad part-No.

904 pad_version_number Pad evolution step

905 pad_id_number Pad ID-No.

906 pad_batch_number Pad batch-No.

907 pad_lining_dsheet Lining Data Sheet No.

908 pad_batch_size Total batch size

909 pad_underlayer Underlayer

910 pad_compressvalue_inner Cold compressibilty inner / µm

911 pad_compressvalue_outer Cold compressibilty outer / µm

912 pad_shim_used measured with shim?

913 pad_chamfers Chamfers

914 pad_slots Slots

915 shim Shim name

916 shim_description Shim description

917 shim_attachment Shim attachment

918 shim_riveted Shim riveted?

919 shim_painted Shim painted over?

920 pad_sec_measure1 other pad secondary measures 1

921 pad_sec_measure2 other pad secondary measures 2

922 pad_backp_thickness Backpl. thickness measured / mm

923 pad_lining_thickness Fric.mat. thickness before test / mm

924 pad_condition Pad condition

925 pad_disc_pairing Pairing pad - disc

926 pad_eigenfrequency_inner_values (1st value) Pad eigenfrequency (inner) / Hz

927 pad_eigenfrequency_outer_values (1st value) Pad eigenfrequency (outer) / Hz

928 pad_damping_inner_values (1st value) Pad damping (inner) / Promille

929 pad_damping_outer_values (1st value) Pad damping (outer) / Promille

930 pad_mode_inner_descriptions (1st entry) Pad mode description

930 pad_mode_outer_descriptions (1st entry) Pad mode description

931 pad_wva_number WVA-Nr.

932 pad_remark1 Remark (pad)



935 pad_grease_used with grease

936 pad_lining_finalthickness Fric.mat. thickness after test / mm

937 shim_version_number Shim evolution step

938 pad_first_test Pad used first in test no.

939 pad_spring_part_number Pad fixing spring - part. no.

940 pad_spring_version_number Pad fixing spring - evolution step

941 pad_spring_material Pad fixing spring - material

942 pad_spring_first_test Pad fixing spring used first in test no.

ekb 3008 data exchange format - description · 2015. 10. 13. · vda ekb 3008 data exchange format...

Documents