ADTF Devicetoolbox

Discover the Experience
Device Toolbox 2.7

EB Assist ADTF v2.12 or higher required
Device Toolbox – EB Assist ADTF
Elektrobit Automotive GmbH

Am Wolfsmantel 46
91058 DE-Erlangen, Germany
+49-9131-7701-0
+49-9131-7701-6333
info.automotive@elektrobit.com
Technical support
EB Assist ADTF Support
Phone: +49-9131-7701-7777
http://automotive.elektrobit.com/support

c 2019 Elektrobit Group Plc., Erlangen
Contents
1. Toolbox 9
1.1. Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
1.2. Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.3. Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.4. Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1.5. Remarks regarding system configurations . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.6. Implementation specific restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
1.7. Driver version check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
1.8. Special text formats and symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
2. Config Codec—Signal Configurator 14

2.1. General usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
2.2. File menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3. Mode menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.4. Header menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18
2.5. Databases Tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.6. Configuration tree . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
2.7. Configuration value table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
2.8. Link database and Config Codec elements . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.9. Property Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.9.1. InputPin/OuputPin . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22
2.9.2. Struct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23
2.9.3. Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.9.4. Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.10.Description of built in Macros . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
3. CAN 30
3.1. Vector CAN XL Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.1.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.1.2. Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.1.3. Filter GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30
3.1.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.1.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.2. Vector CAN XL Sender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2.2. Platform Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2.3. Filter GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3
Contents
3.2.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.2.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3. Peak CAN Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.3.2. Platform support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.3.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.4. Peak CAN Sender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.4.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.4.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.4.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.4.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.5. CAN Legacy Filter In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.5.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.5.2. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.5.3. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.6. CAN Legacy Filter Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.6.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.6.2. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.6.3. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.7. Can Config Codec Ext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.7.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 40
3.7.2. Decode CAN Messages with CCCExt . . . . . . . . . . . . . . . . . . . . . . . . 40
3.7.3. Encode CAN Messages with CCCExt . . . . . . . . . . . . . . . . . . . . . . . . 41
3.7.5. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.7.6. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.7.7. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.7.8. Media Description Format . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46
3.7.9. Extensibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47
3.7.10. Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.8. Can Config Codec Ext—Signal Configurator . . . . . . . . . . . . . . . . . . . . . . . . 48
3.8.1. CAN Specific Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 48
3.9. Can Config Codec (XML-CanCodec) . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.9.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50
3.9.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.9.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.9.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.9.6. Limitation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.10.CAN Trace View Extended Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.10.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.10.2. CAN Trace Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53
3.10.3. CAN Trace List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.10.4. Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4
Contents
4. LIN 56
4.1. Vector LIN Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.1.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.1.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56
4.1.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.1.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.2. LIN Config Codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.2.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.2.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58
4.2.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.2.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
4.3. LIN Config Codec—Signal Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.3.1. LDF4Channel Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61
4.4. LIN Trace View Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.4.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.4.2. LIN Trace Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62
4.4.3. LIN Trace List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63
4.4.4. Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
5. FlexRay 66
5.1. Support of several FlexRay Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67
5.2. VectorFlexrayDevice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.2.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.2.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69
5.2.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.2.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.3. FlexCardDevice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.4. FlexRay ECU Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.4.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.4.2. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.4.3. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.4.4. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.5. FlexRay Trace View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.5.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.6. FlexRay Signal Provider . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.6.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.7. FlexRay Config Codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.7.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74
5.7.2. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75
5.7.3. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.7.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.8. FlexRay Config Codec—Signal Configurator . . . . . . . . . . . . . . . . . . . . . . . . 77
5.8.1. FlexRay Specific Differences . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.8.2. Special issues on decoding or encoding a FlexRay signal . . . . . . . . . . . . . 78
5.9. FlexRay DAT Exporter Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79
5
Contents
6. MOST 81
6.1. Vector MOST Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.1.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.1.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81
6.1.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.1.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.2. OptoLyzer G1 MOST Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.2.1. description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.2.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.2.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.2.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.3. OptoLyzer G2 MOST Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.3.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 85
6.3.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6.3.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6.3.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 87
6.4. MOST Support Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88
7. Ethernet 89
7.1. Ethernet Device UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
7.1.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 89
7.1.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
7.1.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
7.1.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.2. Ethernet Device TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.2.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.2.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
7.2.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
7.2.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8. Camera 94
8.1. General Video Capture Device Options . . . . . . . . . . . . . . . . . . . . . . . . . . . 94
8.2. Blue Fox Capture Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.2.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.2.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 95
8.2.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.2.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.3. Direct Show Video Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.3.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.3.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.3.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.3.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
6
Contents
8.4. uEye Capture Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

8.4.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.4.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.4.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.4.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.5. Linux Video Capture Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.5.1. Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.5.3. Filter-GUID . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.5.4. Pins . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.5.5. Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
9. Additional Service 103

9.1. External File Support Service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
9.1.1. External Stream Sync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 103
9.1.2. Usage of ADTF DAT Exporter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 104
9.1.3. Overview of sinks and sources . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
9.1.4. MOST . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 106
9.1.5. CAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 107
9.1.6. LIN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
9.1.7. FlexRay . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 108
9.2. ADTF MDF4 DeviceTB support for the Dat Exporter Service . . . . . . . . . . . . . . . . 109
9.2.1. Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 109
10. FAQ 112
11. Abbreviations 114
A. Change Log 115

A.1. Version 2.7.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
A.2. Version 2.7.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 115
A.3. Version 2.6.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 117
A.4. Version 2.6.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
A.5. Version 2.6.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 118
A.6. Version 2.5.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
A.7. Version 2.5.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121
A.8. Version 2.4.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122
A.9. Version 2.3.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 123
A.10.Version 2.3.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 124
A.11.Version 2.3.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 125
A.12.Version 2.2.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
A.13.Version 2.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126
A.14.Version 2.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
A.15.Version 2.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
A.16.Version 2.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128
A.17.Version 2.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 129
A.18.Version 2.0.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131
A.19.Version 1.2.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132
A.20.Version 1.1.4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133
7
Contents
A.21.Version 1.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

A.22.Version 1.1.2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
A.23.Version 1.1.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134
A.24.Version 1.1.0 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135
A.25.Version 1.0.1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 136
A.26.Known Problems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 137
List of Figures 138
List of Tables 139
8
1 Toolbox
This is the documentation of the ADTF Device Toolbox. The toolbox provides filters to connect several
external communication system devices to A D T F.
The supported systems are:
I CAN bus system (see chapter 3 CAN)
I LIN bus system (see chapter 4 LIN)
I FlexRay bus system (see chapter 5 FlexRay)
I MOST bus system (see chapter 6 MOST)
I Ethernet (see chapter 7 Ethernet)
I Cameras (see chapter 8 Camera)
For Device-Toolbox-Programming have a look at the ADTF Device Toolbox SDK Documentation. You will
find it in the doc directory within your Device Toolbox installation directory.
1.1 Requirements
The system requirements are described in chapter 1.1 of the ADTFUserManual.
The toolbox has no additional system requirements.
Basic knowledge about A D T F and the FlexRay protocol is required.
Documentation about the FlexRay protocol can be obtained from the FlexRay consortium (www.flexray.
com). Documentation about the FIBEX format can be obtained from the “Assaociation for Standardization
of Automation and Mesauring Systems” (www.asam.net).
Device Toolbox – EB Assist ADTF 9

Chapter 1. Toolbox
1.2 Installation
Any previously installed ADTF FlexRay Toolbox has to be uninstalled prior to installing this
ADTF Device Toolbox!
It is recommended to install the toolbox to <ADTF_DIR>/addons. If a manual installation with another

installation path will be selected, the given manifest files (<InstallDir>/bin/) have to be specified
at the related manifest file(s).
The following line has to be inserted below the tag <manifests>:

<manifest optional="false" url="<installdir>/bin/devicetoolbox.manifest" />
If you are using ADTF on a Windows 7 operating system, you should not install it into the
“ProgramFiles” or any other “System” directory. Because of the user account control (UAC)
you have to have administrative privileges to run CMake and/or the batch-file to build the
examples. If you don’t have these privileges, the build will fail every time.
1.3 Licensing
The ADTF Device Toolbox does only run with a valid toolbox flag in your A D T F license. If the needed
feature flag is not set, the Plugins will not be loaded.
There is no warning that the needed flag could not be found in the given license file while
starting A D T F except in the ADTF DebugMonitor.
1.4 Templates
A Device Toolbox Project bases on a template. These templates are standard Configurations that ease
the creation of new Projects with the devices of the ADTF Device Toolbox. Each Configuration can also
be used as a template. An overview of available templates is provided in Table 1.1 Description of the
templates.
Toolbox is delivered with an example test file example_test_file_can.dat. Example file contains
video and CAN data (tCANData) streams. Both data types are described in DDL file
example_test_file_can.dat.description. Please see the ADTF SDK Documentation for
details on the tCANData structure. Both files are located in ADTF bin/templates directory.

Chapter 1. Toolbox
Template Description
BlueFox There are also Three Configurations (Live, Playback, Recording) with the
corresponding Filters for the recording, playback and live viewing of video
data from a camera via Matrixvision BlueFox API.
CanConfigCodecExt Template for the usage of the CanConfigCodecExt Filter, the TableDisplay and
the Random Number Generator (the code of last two Filters can be found in
the ADTF installation in the example folder. The Filters have to be build first).
DirectShow Three Configurations (Live, Playback, Recording) with the corresponding

Filters for the recording, playback and live viewing of video data from a
camera via Microsoft DirectShow API.
VectorCANDevice Three Configurations (Live, Playback, Recording) with the corresponding Fil-
ters Vector_CAn_XL_Receiver and Vector_CAN_XL_Sender for the recording
and playing the CAN Data from a Vector CAN card (CANcardX or CANcardXL).
Table 1.1.: Description of the templates
1.5 Remarks regarding system configurations
Receiving FlexRay data consumes noteworthy processing power. To minimize the probability of data loss
it is recommended to use a system with a dual-core CPU at least. Although the priority of the thread
handling communication with the FlexRay hardware is set to the highest value, data loss can occur during
heavy system load.
If FlexRay data is to be sent the requirements on response time are even higher. The thread responsible
for sending the data to the FlexRay hardware has to react to each cycle start event. When this event is
received from the device, the data of the next cycle has to be sent to the FlexRay hardware. Any delay
during this process may lead to transmission of erroneous data on the FlexRay bus. It is recommended
to use a PCI-card device for sending FlexRay data, since devices connected via USB induce higher delay
and system load.
1.6 Implementation specific restrictions
FIBEX standard versions 1.2.0, 2.0.1, 3.0.x and 3.1.x are supported with the following restrictions:
I Multiplexed signals or sub-frames are not supported
I Signals using text-table coding rules ar not supported. They are handled like integer values.
I A signal may only be aggregated in one frame; otherwise the decoding/coding is ambiguous.

Chapter 1. Toolbox
I PDU-TRIGGERING elements are ignored (FRAME and FRAME-TRIGGERING elements are

evaluated in order to create the layout). If you want to send FlexRay Media Samples with a
PDU-TRIGGER, you can use the stop_msg Trigger, described in subsection 2.9.4.
I A cell in the dynamic segment has to be reserved for only one ECU.
I FIBEX XML files have to use the ASCII character-set. If UTF-8 is used non-ASCII characters will
not be recognized correctly.
I The redundant sending of PDUs/Frames on both FlexRay Channels simultaneously is currently not
supported. You can work around this limitation by manually sending them on both channels. To
do so with the help of the FlexRay Config Codec add two Pins with the same layout but use the
Signals from the PDUs of the different Channels. Then connect your Filter to both input Pins. Note
that timing limitiations may lead to data inconsistencies between the two Channels.
CAN restrictions:
I Please keep in mind that there will be a null-terminated string in use and the last character is
reserved for the null character ’\0’. Consequently the message- and signal-names can only have
MAX_SIG_LEN - 1 characters.
1.7 Driver version check
Every device in the ADTF Device Toolbox has been tested with a specific set of drivers. All device Filters
will check on initialization if a tested driver is used. If this requirement is not fulfilled, the Filter will interrupt
the initialization and display an error message. All Filters have a Property to disable this interruption.
For detailed information about the tested driver versions, each device provides a subsection
Platform Support.
For the using of Vector Devices it is necessary that they are part of the XL Driver Library
(current used version is 9.8.1.0). Only Vector Devices which are part of this API could
be supported by the ADTF Device Toolbox. For further information please refer to http:
//www.vector.com/.
1.8 Special text formats and symbols
This software guide uses special text formats and symbols to indicate important elements and facts, as
shown here:
Windows, Dialogs and other elements of the user interface

Chapter 1. Toolbox
File names, directory names, etc.
Cross reference section 1.8 Special text formats and symbols
URLs: www.url.com
inline code
Source code
Properties
Proper names
Warnings indicate potential error sources.

→ The arrow indicates the steps you have to take to prevent an error.
This note symbol indicates useful information.
Tips provide additional information.

2 Config Codec—Signal Configurator
The ADTF Signal Config application is used to select elements of database files. This can be *.dbc
(CAN), *.xml (FlexRay) or *.ldf (LIN) files.
Selected elements can be processed to configuration files for ADTF Filters like the Can Config Codec
(abbreviated CCC), the Can Config Codec Ext (abbreviated CCCExt, see section 3.7 Can Config Codec
Ext), LIN Config Codec (abbreviated LCC, see section 4.2 LIN Config Codec) and the FlexRay Config
Codec (abbreviated FCC, see section 5.7 FlexRay Config Codec). Existing configurations for CCC,
CCCExt, LCC and FCC can be imported from XML files.
Additionally existing structs and buffers from header files (see section 2.4 Header menu) can be imported
and changes can be returned. A validation of the configurations is also possible.
2.1 General usage
The filters Can Config Codec Ext, LIN Config Codec, FlexRay Config Codec and Can Config Codec have
an adjusted context menu. So if you click on the Filter you will see the context menu (for example the
CCCExt was taken) shown in Figure 2.1 Context menu of the CCC Ext.

Chapter 2. Config Codec—Signal Configurator
Figure 2.1.: Context menu of the CCC Ext
If the menu Edit Properties with ADTF Signal Config Filter Editor for CCCExt is selected then the
dialog in Figure 2.2 Signal Configurator of CCC Ext is opened. Initially all database files found in the
Global Configuration Settings and Configuration Settings are loaded in Databases. The Configuration
File of the selected Can Config Codec Ext Filter is opened in Configuration.

Figure 2.2.: Signal Configurator of CCC Ext
In this dialog you can add one or more databases using the menu point File → Add Database . . . . Then
using the File → New Config . . . menu point you can create a new Buffer Configuration file. You will get
the nodes Input Pins and Output Pins in the second tree. With a right click on one of those nodes you
can add a new Pin on which you can now drag one or more signals of a database.
Now you can close the dialog by clicking on the button Ok. All database files loaded in Databases will
be stored in the Configuration Settings if they are not already stored in the Global Configuration Settings.
The currently opened Configuration File in Configuration will be used by the selected Config Codec
Filter.
2.2 File menu
With the help of the file menu (see Figure 2.3 File menu of the Signal Configurator) Configuration files
and database files are handled.

Figure 2.3.: File menu of the Signal Configurator
The following menu points are available:
I New Config: A new and empty Configuration file will be generated. The configuration tree will be
empty.
I Open Config: An existing Configuration file can be opened. The content of the file will be inserted
in the configuration tree.
I Save Config: The current content of the configuration tree will be saved in the currently loaded
Configuration file.
I Save Config as: The current content of the configuration tree will be saved in a new Configuration
file.
I Add Database: An existing database file (e.g. .dbc) has to be selected. The content of the
database file will be added to the databases tree as a new node.
2.3 Mode menu
With the mode menu (see Figure 2.4 Mode menu of the Signal Configurator) additional operations can be
executed.
Figure 2.4.: Mode menu of the Signal Configurator
The following menu points are available:
I Link Mode: The link mode can be (de-)activated. With activated link mode it is possible to relink
existing structure elements in the configuration tree to another database signal. If the link mode is

activated the text “Link Mode is active!” is shown in the statusbar.
I Check . . . : The current configuration will be checked. If an error is detected then this is either
shown in a message box or a log file will be generated.
2.4 Header menu
Using the Header → Save Header . . . menu point you can create a C++ header file, which maps the
pins and structs shown in Configuration.
typedef struct
{
tInt32 ESP_v_Signal; // signal=RawDataChannel_Tr$idx$.CycleCounter_Tr$idx$;
tUInt8 PSD_Endkruemmung; // signal=PSD_01.PSD_Endkruemmung;
} tStruct0;
typedef struct
{
tStruct0 sStruct0[90];
} tTest_output;
The comment
// signal=PSD_01.PSD_Endkruemmung;
is optional. Besides of signal you can also specify the signed signal:
// signal=PSD_01.PSD_Endkruemmung; sign_signal=PSD_Endkruemmung_Vorz;
The following line indicates an array, see Figure 2.5 Signal Configurator—Array of Structs).
tStruct0 sStruct0[90];

Figure 2.5.: Signal Configurator—Array of Structs
To import structs from a header file see section 2.6 Configuration tree.
A struct is saved under the same name and has a “t” as prefix. If a struct is imported and it
has a “t” at the beginning, then the “t” is considered as a prefix and will be omitted.
The typedef struct statement must have the same appearance as shown in the example
above to be imported correctly.
2.5 Databases Tree
In the Databases Tree all added database files are shown as own nodes. The messages and signals
included in the added database files are shown in nodes within the according database node. If you have
set any databases (DBC-Files, LDF-Files or XML-Files) in one of the properties DBCFiles4ChannelX,
flexray_fibex_filename or LDF4ChannelX (Global Configuration Settings -> Bus -> (CAN, FlexRay, LIN,
MOST), the Signal Configurator will load these files to the Databases Tree.
The Signal Config Filter Editor takes all settings from the globals.xml and puts them to
the system.xml. If the pathes of the files are absolute, they will be kept absolute. If using
MACROS they will be kept also. If the pathes are defined relative (to the globals.xml), they
will be extended with the $GLOBALSDIR$ -Macro.
With the help of the edit field on top of the tree the messages and signals can be filtered. The field works

comparable to an InStr() search. So all messages and signals which have the input character sequence
in their names are displayed. All others are hidden.
The following menu points are available for a database node:
I Delete: Delete the selected database
I Expand All: Expand all child items
I Collapse All: Collapse all child items
The following menu point is always available:
I Add Database . . . : An existing database file has to be selected. The content of the file will be
added to the databases tree as new node.
2.6 Configuration tree
The configuration tree has the following nodes:
I Input Pins and Output Pins: With a right click on this node there is the possibility to add a new Pin
to the selected node by selecting the menu point Add Input Pin or Add Output Pin.
. one or more Pins (i.e. in 1)
• one trigger: A trigger can be added with the context menu point Add Trigger which
appears by right clicking on the Pin node.
• one or more signals: Signals can be added to a created Pin by dragging signals from the
database to the wished Pin.
• one or more items: Any child item, which does not necessarily has to be a signal, can be
added to a Pin (or a structure).
• one or more structures: There is the possibility to create more than one structure for a
selected Pin. To do so a right click on the Pin node has to be performed and the menu
point Add Struct has to be selected. A structure can contain one or more structures.
Signals or items are always stored within a struct. A pin can have one or more structs. If
you create a new pin, you can add items or signals to the pin. In this case the pin has one
single struct. Although it is not visible, it contains the items and signals you’ve justed added.
The struct becomes visible, if you define a second struct. After that, even if you remove the
second struct, the first struct will remain visible anyway.

An Input Pin is saved as an Output Pin in the Buffer Configuration file and vice versa.
Using the context menu Import Structs . . . , structs can be imported from a C++ header file.
Figure 2.6.: Signal Configurator—Import Structs
For additonal information see section 2.4 Header menu.
2.7 Configuration value table
The configuration value table on the right of the dialog (see Figure 2.2 Signal Configurator of CCC Ext)
shows additional information for:
I Database
I Pin
I Structure
I Trigger
I Signal

2.8 Link database and Config Codec elements
If the link mode is activated, multiple selection is deactivated in Databases. A database signal can be
dragged to Configuration and replaces a signal.
2.9 Property Description
This section describes the available properties in the Signal Configuration Editor.
2.9.1 InputPin/OuputPin
Property Value Optional Description
channel [0..31] No, either The channel on which the referenced

channel or messages and signals are available.
channelmask
must be
defined.
channelmask hexadecimal No, either Through the channel mask a range

channel or of possible channels can be specified.
channelmask Each bit in this 32bit integer corre-
must be sponds to a channel.
defined.
delay milliseconds yes A fixed delay that will be substracted

from the buffer timestamp.
pack 1,2,4,8,16 yes Memory packing in the buffer. The de-

fault is 8.
timestamp $FIRST$ yes Specifies when and how the time stamp
$LAST$ is set for the decoded data:
$MEAN$ $FIRST$: time stamp of the first valid
message message in the cycle for this buffer
name $LAST$: time stamp of the last mes-
sage in the cycle before the data of this
buffer is sent.
$MEAN$: average value of the
$FIRST$ and $LAST$ time stamp
MessageName: time stamp of the cor-
responding message is used if this is
received (otherwise 0)

clear_after_transmit true false yes Clear the buffer to 0 after transmitting.
major_type hexadecimal yes MediaType/MajorType for the Pin. If

this attribute is lacking, the value ME-
DIA_TYPE_STRUCTURED_DATA is
used.
sub_type hexadecimal yes MediaType/SubType for the Pin. If

this attribute is lacking, the value ME-
DIA_SUBTYPE_STRUCT_
STRUCTURED is used.
cycletime Milliseconds InputPin Only Cyclic transmission of the buffer. De-

fault -1.
Table 2.1.: Property Description of the InputPin/OuputPin
2.9.2 Struct
The struct node defines a specific C-structure, whose elements can be filled with decoded signals, macros
or just nothing. A buffer node can contain multiple structs with different attributes (array, pack, etc.). When
creating the structures, special care must be taken that the "pack" specification matches the #pragma
pack (see Microsoft Visual Studio help) of the C-structure so that the alignment of the individual structure
elements fits! By default in Visual Studio, a #pragma pack(8) is set.
pack 1,2,4,8,16 yes Memory packing of member elements.

The default is 8.
array_index_name String yes A name that can be used to a

placeholder for the array index in
the elemnts’ signal name (Message-
Name.Signal$array_index_name$).
array_start_index Int yes Start index of the array.
array_stop_index Int yes End index of the array.

array_format format speci- yes printf format specifier for the array in-
fier dex.
Table 2.2.: Property Description of the Struct
The alignment of the base types depends on the compiler used. The Microsoft compiler
uses an alignment value equal to the size of the type e.g. 8 for a "double" value. GCC uses
a 4 byte alignment for all 64 bit types. For "#pragma pack"-values larger than 1, this can
lead to a different memory layout of the structure!
2.9.3 Element
type ADTF data no Data type of the structure element.

type Valid types: tBool, tInt8, tUInt8, tInt16,
tUInt16, tInt32, tUInt32, tInt64, tUInt64,
tInt, tUInt, tFloat64, tFloat32
signal Message. yes when "MessageName.SignalName" in the ex-

Signal macro is used act notation as in the corresponding
database file.
corrective_factor float yes Factor to apply to the signal before

the buffer is transmitted. Note that
the calculation for the corrective factor
changed between the CanConfigCodec
and the CanConfigCodecExt.
CanConfigCodec (value = value * dbc-
factor * corrective_factor + offset)
CanConfigCodecExt (value = (value *
dbcfactor + offset) * corrective_factor)
corrective_offset float yes Offset to applay to the signal before the

buffer is transmitted.
unit_conversion true false yes Apply the unit conversion described in

the database file.

sign_signal SignalName yes Reference a seperate sign signal.
limits ignore yes Select a limit handling policy. With this

clip you can clip a signal to the min/max
warn values specified in the database file or
warn via log message when the limits
are exceeded.
macro $MACRO yes See section 2.10 Description of built in

NAME$ Macros for detailed information.
Table 2.3.: Property Description of the Element
It is not possible to send signals of he same message but in different multiplexes in one
buffer.
2.9.4 Triggers
The optional trigger specifies when a decoding cycle begins and when it ends. If no such node exists,
all appropriate messages are decoded and, if all messages required for the buffer were received, the
MediaSample is sent. During this step multiplexed signals are treated just as signals from different
messages, i.e. all needed multiplexes of a message must have been received to trigger a transmit. By
setting the stop_valid_signal to the multiplexor it is possible to trigger the buffer transmission on specific
multiplexes. The stop trigger can be composed of a stop message (with an optional valid condition) and a
timeout.
timeout Milliseconds yes Triggers the buffer after the specified

time (depends on the Stream Time) if
the required signals have not been re-
ceived entirely. If all signals were re-
ceived before the timeout the buffer is
transmitted and the timeout reset.

start_msg MessageName yes The name of the message that trig-

gers a new decoding cycle. All other
received messages which are config-
ured in the buffer will be ignored until
this message was received. It is possi-
ble to use only the message as trigger
(without valid checking see below). The
start message has to be received at
the same channel as configured in the
buffer.
start_valid_signal SignalName yes Used in combination with start_msg to

select a signal in the message that is
used as a source for a value compari-
son.
start_valid_value Numeric yes The value which the start_valid_signal

Value will be compared against.
start_valid_ [==,!=,>=, yes The operation used in the comparison.

operation <=,>,<]
stop_msg MessageName yes The name of the message that stops

the current decoding cycle. After re-
ceiving the message, a new Mediasam-
ple will be transmitted. If there is
configured a start_msg, all other re-
ceived messages which are configured
in the buffer will be ignored until the
start_msg was received. It is possi-
ble to use only the message as trig-
ger (without valid checking see be-
low). The stop message has to be re-
ceived at the same channel as config-
ured in the buffer. The value should
have the following structure: ECU-
Name.PDUChannelValue.PDUName
stop_valid_signal SignalName yes Used in combination with stop_msg to

select a signal in the message that is
used as a source for a value compari-
son.
stop_valid_value Numeric yes The value which the stop_valid_signal

Value will be compared against.

stop_valid_ [==,!=,>=, yes The operation used in the comparison.

operation <=,>,<]
Table 2.4.: Property Description of the Triggers
2.10 Description of built in Macros
Macros allow the user to extend input or output data with algorithmically generated content such as
checksums or counters. The CanConfigCodecExt ships with a number of built in macros which shall be
described in this section. It is possible to extend the macro functionality with user generated macros, for
further information see "Conversion of Old CanConfigCodecExt Macros" in the ADTF Device Toolbox
SDK Documentation.
Element Macros Element macros generate content for a buffer element or can signal. To use an element
macro you need to select a macro from the dropdown list in the macro property, additional attributes may
be required to provide data to a macro implementation. Macros have a direction, which means that they
can be used for input or ouput data.
Macro Additional Direction Data Description

Attributes Type
$CONSTANT$ value Input None The $CONSTANT$ macro fills the el-
Ouput ement with a constant numeric value
provided by the attribute "value".
$COUNTER$ value Output tInt64 The $COUNTER$ macro increments

the element value each time a new
buffer is generated. The "value" at-
tribute can be used to provide a modulo
operand (element = counter % value).
$TIMESTAMP$ message| Input tInt64 Fills the element with a timestamp. The
signal source of the timestamp can be a mes-
sage or a signal.
$TIMESTAMP_SEC$ message| Input tFloat64 Fills the element with a timestamp in

signal seconds. The source of the timestamp
can be a message or a signal.

Macro Additional Direction Data Description

Attributes Type
$HARDWARETIME$ message| Input tUInt64 Fills the element with a devices’ hard-
signal ware timestamp. The source of the
timestamp can be a message or a sig-
nal.
$CURRENT_TIME$ message| Input tInt64 Fills the element with IO time of the
signal mediasample. The source of the times-
tamp can be a message or a signal.
$CURRENT_TIME_ message| Input tFloat64 Fills the element with IO time of the
SEC$ signal mediasample in seconds. The source
of the timestamp can be a message or
a signal.
$MSG_TIMESTAMP$ message| Input tInt64 Fills the element with the received Me-
signal diasample timestamp.
$MSG_TIMESTAMP_ message| Input tFloat64 Fills the element with the received Me-
SEC$ signal diasample timestamp in seconds.
$IF_RECEIVED$ message| Input none Fills the element with the content of
signal + "value" if a message or signal was re-
value ceived and the value of "else" otherwise.
else The attribute "else" is optional and a
value of 0 is used if it is not present.
$RAWVALUE$ signal Input tUInt64 Fills the element with the raw can signal
value.
$CHECKSUM$ signal Input none Calculates an XOR checksum on all

Output elements in the buffer and writes the
result as a raw value.
Table 2.5.: Property Description of the Description of built in Macros
Available Macros for each Config Codec Signal Editor

Besides the Can Config Codec Ext Signal Configurator there is a Signal Configurator for LIN Config
Codec and FlexRay Config Codec (described in section 4.3 and 5.8). For each Signal Configurator,
the list of available Macros is different. The next table lists all macros, which are available for each
Configurator.

Macro CAN CC Ext LIN CC FLEXRAY CC
$CONSTANT$ x x x
$COUNTER$ x x x
$TIMESTAMP$ x x x
$TIMESTAMP_SEC$ x x x
$HARDWARETIME$ x x x
$CURRENT_TIME$ x x x
$CURRENT_TIME_ x x x
SEC$
$MSG_TIMESTAMP$ x x x
$MSG_TIMESTAMP_ x x x
SEC$
$IF_RECEIVED$ x x x
$RAWVALUE$ x x x
$CHECKSUM$ x - -
$MYCHECKSUM$ x - -
$MYRAWVALUES$ - - x
The Macros MYCHECKSUM and MYRAWVALUES are defined in the demos

can_macro_checksum and flexray_macro_rawvalue.

3 CAN
3.1 Vector CAN XL Receiver
3.1.1 Description
The Vector CAN XL Receiver serves to receive CAN data via the Vector XL Hardware into A D T F.
Vector XL Hardware is hardware that is supported by the Vector XL Driver Library (e.g. CANcardXLe,
CANboardXL, CANcaseXL, VN7600, . . . ).
For more information about the hardware, drivers, and driver compatibility issues see the vendor’s
homepage http://www.vector.com/.
3.1.2 Platform Support
Windows Linux
X (32 and 64 bit) –
The device has been tested with the driver pack- –

age in the version 9.8.1.0.
Table 3.1.: Platform support of the Vector CAN XL Receiver
3.1.3 Filter GUID
adtf.io.vector_can_xl_receiver

Chapter 3. CAN
3.1.4 Pins
Name Type I/O Description
output MEDIA_TYPE_CAN out Output Pin for the received CAN data
MEDIA_SUBTYPE_CAN_DATA
Table 3.2.: Pins of the Vector CAN XL Receiver
3.1.5 Properties
Property Default Type Description
application_name “ADTF” String The application name as defined by the Vector Hard-
ware tool.
Warning: in ADTF the channels begin with 0, there-
fore, the Vector CAN channel CAN1 matches channel
0 in A D T F!
tx_receipts false Bool If set to “true”, tx receipts will be generated for all
transmitted CAN messages.
add_hardwaretime_info false Bool If “true”, the Device Original Time of a message will
be transmitted with the media sample info area.
VerifyDriverVersion true Bool If “true”, the filter will check if a tested driver version
is used and interrupt initialization if this requirement
is not fulfilled.
WakeUp false Bool If “true”, the device will generate a high voltage
wakeup impulse on the CAN channels.
Table 3.3.: Properties of the Vector CAN XL Receiver
This filter sends every second a bus status message for each of the device’s can controller,
even there is no data on the bus!

Chapter 3. CAN
3.2 Vector CAN XL Sender
3.2.1 Description
The Vector CAN XL Sender serves to transmit CAN messages via the Vector XL Hardware. Vector XL
Hardware is hardware that is supported by the Vector XL Driver Library (e.g. CANcardXLe, CANboardXL,
CANcaseXL, VN7600, . . . ).
3.2.2 Platform Support
Windows Linux
X (32 and 64 bit) –

Table 3.4.: Platform support of the Vector CAN XL Sender
3.2.3 Filter GUID
adtf.io.vector_can_xl_sender
3.2.4 Pins
input MEDIA_TYPE_CAN in Input Pin for the CAN data to send

MEDIA_SUBTYPE_CANDATA
Table 3.5.: Pins of the Vector CAN XL Sender

Chapter 3. CAN
3.2.5 Properties
application_name “ADTF” String The application name as defined by the Vector Hardware
tool.
Warning: in ADTF the channels begin with 0, therefore,
the Vector CAN channel CAN1 matches channel 0 in
A D T F!
VerifyDriverVersion true Bool If “true”, the filter will check if a tested driver version is
used and interrupt initialization if this is requirement is not
fulfilled.
WakeUp false Bool If “true”, the device will generate a high voltage wakeup
impulse on the CAN channels.
Table 3.6.: Properties of the Vector CAN XL Sender
Starting with Device Toolbox 2.3.0 the Vector CAN XL Device is marked as deprecated and
will not be supported any more ! Starting with the Device Toolbox 2.4.0 the Vector CAN XL
Device is removed completely from the Toolbox. Please use the Vector CAN XL Receiver
and Vector CAN XL Sender instead!
3.3 Peak CAN Receiver
3.3.1 Description
The Peak CAN Receiver serves to receive CAN raw data via the Peak Hardware into A D T F.
homepage http://www.peak-system.com/.

Chapter 3. CAN
3.3.2 Platform support
Windows Linux
X (32 and 64 bit) X (64 bit)
Peak CAN Device Basic Peak CAN Device
The device has been tested with the driver in the The device has been tested with the driver in the
version 3.13.0.15462. version 7.14.0.0.
Table 3.7.: Platform support of the Peak CAN Receiver
3.3.3 Filter-GUID
adtf.io.peak_can_receiver
3.3.4 Pins
output MEDIA_TYPE_CAN out Output Pin for the received CAN raw data
MEDIA_SUBTYPE_CAN_DATA of the hardware.
Table 3.8.: Pins of the Peak CAN Receiver
3.3.5 Properties
Property Default Type Usage
baudrate 500000 int Baudrate of the CAN bus [bit/s]

If a Peak CAN Sender with the same devicename is active,
this Property has to be set to the same value in both Filter
configurations!

Chapter 3. CAN
channel_id 0 int This device supports only a single CAN channel. All
mesages will be given to this channel ID (in the tCANData
structure). Please see the ADTF SDK Documentation for
details on the tCANData structure.
If a Peak CAN Sender with the same devicename is active,
this Property has to be set to the same value in both Filter
configurations!
devicename “default” String For Windows:

I “default” ⇒ PCAN-USB interface, channel 1
I “65” ⇒ PCAN-PCI interface, channel 1
I “81” ⇒ PCAN-USB interface, channel 1
I “97” ⇒ PCAN-PC Card interface, channel 1
I “98” ⇒ PCAN-PC Card interface, channel 2

For Linux: Name of the Peak CAN device, e.g.
/dev/pcan32
add_hard- false bool If true, the Device Original Time of a message will be trans-
ware- mitted with the MediaSample in info area.
time_info

Chapter 3. CAN
VerifyDriver- true bool If “true” the Filter will check if a tested driver is used and
Version interrupt initialization if this requirement is not fulfilled.
Table 3.9.: Properties of the Peak CAN Receiver
On Windows, the Peak CAN Device has to be connected to the computer before starting
A D T F. Otherwise A D T F cannot detect it correctly!
This filter sends a bus status message each second, even there is no data on the bus!
3.4 Peak CAN Sender
3.4.1 Description
The Peak CAN Sender serves to transmit CAN messages via the Peak hardware.
homepage http://www.peak-system.com/.
Windows Linux
X (32 and 64 bit) X (64 bit)
Peak CAN Device Basic Peak CAN Device
version 3.13.0.15462. version 7.14.0.0.
Table 3.10.: Platform support of the Peak CAN Sender

Chapter 3. CAN
3.4.3 Filter-GUID
adtf.io.peak_can_sender
3.4.4 Pins
output MEDIA_TYPE_CAN out Output Pin for the received CAN raw data
MEDIA_SUBTYPE_CAN_DATA of the hardware.
Table 3.11.: Pins of the Peak CAN Sender
3.4.5 Properties
baudrate 500000 int Baudrate of the CAN bus [bit/s]

If a Peak CAN Receiver with the same devicename is
active, this Property has to be set to the same value in
both Filter configurations!
channel_id 0 int This device supports only a single CAN channel. Only
CAN messages with this channel ID will be forwarded to
the CAN bus.
If a Peak CAN Receiver with the same devicename is
active, this Property has to be set to the same value in
both Filter configurations!
devicename “default” String For Windows: see Table 3.9 Properties of the Peak CAN
Receiver
For Linux: Name of the Peak CAN Device, e.g.
/dev/pcan32
VerifyDriverVersion true bool If “true”, the Filter will check if a tested driver is used and
interrupt initialization if this requirement is not fulfilled.
Table 3.12.: Properties of the Peak CAN Sender

Chapter 3. CAN
On Windows, the Peak CAN Device has to be connected to the computer before starting
A D T F. Otherwise, A D T F cannot detect it correctly!
Starting with Device Toolbox 2.3.0 the Peak CAN Device and Peak CAN Device Basic are
marked as deprecated and will not be supported any more ! Starting with the Device Tool-
box 2.4.0 the the Peak CAN Device and Peak CAN Device Basic are removed completely
from the Toolbox. Please use the Peak CAN Sender and Peak CAN Receiver instead!
3.5 CAN Legacy Filter In
3.5.1 Description
The Filter transforms legacy CAN data to the new CAN data format.
3.5.2 Filter-GUID
adtf.io.can_legacy_in
3.5.3 Pins
input MEDIA_TYPE_CAN in Input Pin for the CAN mes-

MEDIA_SUBTYPE_CAN_RAW_MESSAGE sages in the legacy format
input_ext MEDIA_TYPE_CAN in Input Pin for extended CAN

MEDIA_SUBTYPE_CAN_RAW_MESSAGE_EXT messages in the legacy for-
mat
output MEDIA_TYPE_CAN out Output Pin for the new CAN

MEDIA_SUBTYPE_CAN_DATA data format
Table 3.13.: Pins of the CAN Legacy Filter In

Chapter 3. CAN
3.6 CAN Legacy Filter Out
In Device Toolbox 2.3.x and lower there is a bug at conversion of the extended CAN
message identifiers in the CAN Legacy Filter Out. This causes corrupt message identifiers
in the legacy extended can data. Unfortunately there is no suitable way to recover extended
can identifier, which are processed with this filter and recorded. Because of the bug bit 27 is
removed from the identifier instead of bit 31 (see ADTF Device Toolbox SDK Documentation
tCANData::MSG_EXTENDED_FLAG for more information). Hence the bit was removed the
resulting identifier in legacy extended can data is ambiguous.
3.6.1 Description
The Filter transforms new CAN data (tCANData) to the legacy CAN data format (tCanMessage/tCanMes-
sageExt).
3.6.2 Filter-GUID
adtf.io.can_legacy_out
3.6.3 Pins
input MEDIA_TYPE_CAN in Input Pin for the new CAN

MEDIA_SUBTYPE_CAN_DATA format
output MEDIA_TYPE_CAN out Output Pin for CAN mes-

MEDIA_SUBTYPE_CAN_RAW_MESSAGE sages in the legacy format
output_- MEDIA_TYPE_CAN in Output Pin for extended

ext MEDIA_SUBTYPE_CAN_RAW_MESSAGE_EXT CAN messages in the legacy
format
Table 3.14.: Pins of the CAN Legacy Filter Out

Chapter 3. CAN
3.7 Can Config Codec Ext
3.7.1 Description
The Can Config Codec Ext Filter decodes and encodes raw CAN data (as its predecessor Can Config
Codec). The Can Config Codec Ext knows no previously specified C structures, but only storage ranges
that are filled via the decoding instructions specified in an individual configuration file. This process is
extendible via the interface ICanDynamicMacro.
During decoding (CAN input), the raw CAN messages (e.g. from the Peak CAN Device, Vector CAN
Device and Harddisk Player ) are read in via the Pin “input” into the Filter and then decoded with the help
of DBC files and a configuration file, that maps CAN signals to locations in a buffer.
Here for each configured input buffer of Can Config Codec Ext, an individual Output Pin is generated,
which is used to forward the data to other Filters. These can transform the data into the corresponding C
structures using casts. The Output Pin has the same name as the corresponding input buffer.
The requested signals are converted into the appropriate SI unit if the DBC file specifies a valid (and
known) physical unit (e.g. [km/h] → [m/s]). The supported unit strings are listed in the ADTF SDK
Documentation of the class cUnitConversion.
During encoding (CAN output) raw data structures are read in via an Input Pin with the name of the
corresponding buffer. These structures are converted into CAN messages according to the output
configuration, which maps buffer locations to CAN signals. Then the generated CAN messages are
forwarded to the Pin “output”. For these output buffers a configurable timer allows to send the generated
messages repeatedly.
Data structure elements can also be filled with macros with constant values or time stamps instead of
decoded signals.
3.7.2 Decode CAN Messages with CCCExt
The decoding of CAN messages will be shown on the basis of the following example.
Let Message1 and Message2 be two CAN Messages of the form:
Message 1: S1 # S2 S3 #
Message 2: S1 S2 S3 S4 #
The messages are filled with Signals. The symbol ’#’ means, that there is no signal at this part of the
message. In the following, a Signal i of message j will be written as Messagej_Si.

Chapter 3. CAN
Figure 3.1.: Decoding CAN Messages with CCCExt
With the help of the CCCExt a decode buffer can be defined, that includes signals of any CAN message.
If the CCCExt receives these messages, it will fill the buffer and write it to a media sample and transmit it.
A look at figure 3.1 shows how it works. The buffer that should be transmitted, contains all signals of
message 1 and message 2. At time t = 0 the CCCExt has received message 1. At time t = 1 message
2 has arrived and the CCCExt will fill the media samle and transmit it.
Sometimes a media sample is transmitted/triggered at specific times (see: 2.9.4). If, for
example message 2 has not arrived before the sample is triggered, all signals of message
2 will be set to their default values. The default values are taken from the DBC file. You can
also set your own default value in this case, with the help of the Signal Configurator 3.8.
3.7.3 Encode CAN Messages with CCCExt
The encoding of CAN messages will also be shown on the basis of the previous example. At first, have a
look at figure 3.2.

Chapter 3. CAN
Figure 3.2.: Encoding media samples with CCCExt
With the help of the CCCExt a encode buffer can be defined, that includes signals of any CAN message.
If the CCCExt receives a media sample belonging to this buffer, it will create all CAN messages that
contain signals of the buffer and transmit it. A look at figure 3.2 shows how it works. The buffer contains
two signals of message 1 and two signals of message 2. Since Message1_S1, Message2_S3 and
Message2_S4 can not be filled with values, they will be set to their default values defined in the DBC
file.
Every bit of a CAN message, that does not belong to a signal will be set to zero.
Windows Linux
X X
Table 3.15.: Platform support of the Can Config Codec Ext
3.7.5 Filter-GUID
adtf.io.can_config_codec

Chapter 3. CAN
3.7.6 Pins
input MEDIA_TYPE_CAN in Input Pin for CAN raw data

MEDIA_SUBTYPE_CAN_RAW_MESSAGE (e.g. from the CAN Device
Filter )
input_ext MEDIA_TYPE_CAN in Input Pin for CAN raw data in

MEDIA_SUBTYPE_CAN_RAW_MESSAGE_EXT the extended CAN message
format (e.g. from the CAN
Device Filter )
can_- MEDIA_TYPE_CAN out Output Pin for encoded CAN

output MEDIA_SUBTYPE_CAN_RAW_MESSAGE raw data (e.g. for the CAN
Device Filter )

output_- MEDIA_SUBTYPE_CAN_RAW_MESSAGE_EXT raw data in the extended
ext CAN message format (e.g.
for the CAN Device Filter )
Table 3.16.: Pins of the Can Config Codec Ext

Chapter 3. CAN

Chapter 3. CAN
3.7.7 Properties
Automatic SI Unit false bool If “true”, every signal with a known unit is automatically
Conversion [Auto- converted to its SI unit.
CalcUnitToSI] This behaviour is overridden signal-specifically by the con-
figuration file. This Property defines the default behaviour.
Buffer Configura- “” string Path to XML Codec Configuration File [mandatory]

tion File [filename]
Create Media true bool This allows you to disable the generation of media de-
Descriptions scriptions for the buffer pins. If these become rather large
[create_media- ( > 10000 Signals) this can be a very time consuming step.
_descriptions] A media description is only created for input buffers (Out-
put Pins)! Output buffers (Input Pins) of the Can Config
Codec Ext have no media description.
Default CAN 0 int Default channel for CAN I/O. this behaviour is overidden
Channel [de- by configuration file.
fault_channel]
Dump Buffer false bool Print sizes of encoded/decoded data structures (for de-
Layout bugging issues)
[show_struct_info]
Dump Sig- false bool Dump all signal values to ConsoleView (for debugging
nal Updates issues)
[dump_signal_up-
dates]
Handling of Signal ignore string How should the Codec handle a signal’s min/max value
Limits of Database from database during encoding messages ?
[LimitHandlingPol- The following options are supported:
icy] ’ignore’ (default) Do not do anything, treat limits as com-
ments.
’clip’ Silently clip the signal to the violated boundary.
’warn’ Send the signal as is, but issue a log warning.
This behavior is signal-specifically overridden by the con-
figuration file. This Property defines the default behavior.
Ignore Error Mes- false bool Ignore incoming CAN error messages.
sages [ignore_er-
ror_messages]
Skip irrele- true bool Checks each incoming CAN message for relevance be-
vant messages fore processing. Increases performance if only a few
[skip_irrelevant_me- messages are needed. Disable this check, if most of the
ssages] messages are configured. The transmitted data field will
be filled with zeros
Table 3.17.: Properties of the Can Config Codec Ext

Chapter 3. CAN
3.7.8 Media Description Format
If the property Create Media Descriptions is set to “true”, the Can Config Codec Ext Filter will create a
Media Description for the configured Output Pins of following format:
Two structs, one for the Output Pin and one for its struct:
I Output Pin (“struct1”)
. name: t<name_of_filter>_<name_of_output_pin>
. contains element with
• name: struct_<index>
• type: “struct2”
I Output Pin struct (“struct2”)
. name: t<name_of_filter>_<name_of_output_pin>_struct_<index>
. contains element with the name and the type of the configured signal (mapped to database)
in Can Config Codec Ext Filter
And the following stream:
I name: <name_of_output_pin>
I contains a struct with
. name: “struct1”
. type: “struct1”
Example:
Excerpt of configured Buffer Configuration File:

<buffer name="outPin">
<struct name="outStruct">
<element
name="ESP_v_Signal"
signal="ESP.ESP_v_Signal"
type="tFloat64"
/>
</struct>
</buffer>
Excerpt of the resulting Media Description:

Chapter 3. CAN
<structs>
<struct
alignment="1"
name="tCAN_Config_Codec_Ext_outPin"
version="1">
<element
alignment="8"
arraysize="1"
byteorder="LE"
bytepos="0"
name="struct_0"
type="tCAN_Config_Codec_Ext_outPin_struct_0"
/>
</struct>
<struct
alignment="8"
name="tCAN_Config_Codec_Ext_outPin_struct_0"
version="1">
<element
alignment="8"
arraysize="1"
byteorder="LE"
bytepos="0"
name="ESP_v_Signal"
type="tFloat64"
/>
</struct>
</structs>
<streams>
<stream
description="streamid_1"
name="outPin"
type="adtf.core.media_type">
<struct
bytepos="0"
name="tCAN_Config_Codec_Ext_outPin"
type="tCAN_Config_Codec_Ext_outPin"
/>
</stream>
</streams>
3.7.9 Extensibility
The Can Config Codec Ext Filter is extendable with the help of the interface ICanDynamicMacro.
There is an example which presents a macro that calculates the known XOR checksum for a CAN
message. This example can be found in /src/example/src/can_macro_checksum. The
macros are always addressed with the “macro” attribute of a buffer element.

Chapter 3. CAN
3.7.10 Limitation
CAN messages with identifier set to 0 are not supported and will never be decoded because CAN
message identifier 0 is internally used by the Can Config Codec Filter to mark invalid CAN identifiers.
3.8 Can Config Codec Ext—Signal Configurator
The CAN Config Codec Ext has an adjusted context menu. If the menu Edit Properties with ADTF
Signal Config Filter Editor for CCCExt is selected, then the ADTF Signal Config Filter Editor is opened.
The editor works almost the same way as the editors for the FlexRay Config Codec and LIN Config
Codec. For detailed information see chapter 2 Config Codec—Signal Configurator. The CAN specific
differences are demonstrated here:
3.8.1 CAN Specific Differences
Element Properties
The property default_value is only available for the Can Config Codec Ext:
default_value float yes Default value of the signal. The value

is taken from the DBC-File, but can
be edited and saved to the configura-
tion file. This property is only available
for output pins. It represents the Gen-
SigStartValue of your DBC-File. Please
note, that ADTF is guessing the sig-
nal type when you drag and drop a
signal from the Database-View to the
Configuration-View. It is possible, that
the signal type is guessed wrong and
therefore the default_value is changed
(e.g. from 1.1234 to 1). Please edit the
value in this case.

Chapter 3. CAN
DBCFiles4Channel Properties
You can adjust the channel id of a database by selecting a database node (see Figure 3.3 Signal
Configurator—Set database channel).
Figure 3.3.: Signal Configurator—Set database channel
The DBCFiles4ChannelX properties are available in Global Configuration Settings -> Bus -> CAN and
also in the Configuration Properties (Property Browser ). How the Signal Config Editor handles global
and local DBCFiles4ChannelX properties is demonstrated with the following example:
I The following Global Configuration Settings are set:
. DBCFiles4Channel0 = DBC0.dbc
The properties are not set in the Configuration’s settings.
. DBCFiles4Channel0 = ""
I After opening the Signal Config Filter Editor for CCCExt, the Databases Tree will show the three
entries DBC0.dbc, DBC1.dbc and DBC2.dbc. DBC0.dbc is set to channel 0. DBC1.dbc is set to
channel 1. DBC2.dbc is set to channel 2. These databases are loaded into ADTF by opening
the editor. After closing the Signal Config Filter Editor for CCCExt these DBC files are set to the
Configuration’s settings.

Chapter 3. CAN
I If you change the channel of a DBC File with the Signal Config Filter Editor, these changes will be
taken to the Configuration’s settings. For example, the channel of DBC1 is changed from channel 1
to channel 0. This influences the Configuration’s settings as follows:
. DBCFiles4Channel0 = "DBC0.dbc, DBC1.dbc"
. DBCFiles4Channel2 = "DBC2.dbc"
I After opening the Signal Config Filter Editor for CCCExt again, you will now see three databases.
. DBC0.dbc on channel 0
Using Macros to define CAN channels
You can edit input and output pins of your Can Config Codec Ext Configuration-Files to set the channel-
property to a specific environment variable or ADTF-Macro.
Example: <input channel="$(CANIDMacro)">
Please refer to chapter Overview of the available macros in ADTF in the ADTF SDK Documentation
to get an overview of the available macros in ADTF or how to define your own macro.
3.9 Can Config Codec (XML-CanCodec)
3.9.1 Description
This Filter is ouf of date and is not supported anymore. Users are encouraged to use the
Can Config Codec Ext Filter instead.
The Can Config Codec Filter decodes and encodes raw CAN data. The Can Config Codec (abbreviated
CCC) knows no previously specified C structures, but only storage ranges that are filled via the decoding
instructions specified in an individual configuration file.
During decoding (CAN input), the raw CAN messages (e.g. from the Peak CAN Device, Vector CAN
Device and Harddisk Player ) are read in via the Pins “input” or “input_ext” into the Filter and then
decoded with the help of DBC files and the configuration in the configuration file.

Chapter 3. CAN
Here for each configured input buffer of Can Config Codec, an individual Output Pin is generated, which
is used to forward the data to other Filters. These can transform the data into the corresponding C
structures using casts. The Output Pin has the same name as the corresponding input buffer.
When reading in CAN signals, their values are automatically converted into the appropriate SI unit if a
valid physical unit is specified for the input signal the DBC file (e.g. [km/h] → [m/s]).
During encoding (CAN output) raw data structures are read in via an Input Pin with the name of the
corresponding buffer. These structures are converted into CAN messages according to the output
configuration, which maps buffer locations to CAN signals. Then the generated CAN messages are
forwarded to the Pins “can_output” and “can_output_ext”. For these output buffers a configurable timer
allows to send the generated messages repeatedly.
The data structures except CAN signals can also be described through macros with constant values or
time stamps.
Windows Linux
X X
Table 3.19.: Platform support of the Can Config Codec
3.9.3 Filter-GUID
adtf.io.can_config_codec

Chapter 3. CAN
3.9.4 Pins
input MEDIA_TYPE_CAN in Input Pin for CAN raw data

MEDIA_SUBTYPE_CAN_RAW_MESSAGE (e.g. from the CAN Device Fil-
ter )
input_ext MEDIA_TYPE_CAN in Input Pin for CAN raw data in

MEDIA_SUBTYPE_CAN_RAW_MESSAGE_EXT the extended CAN message
format (e.g. from the CAN De-
vice Filter )

output MEDIA_SUBTYPE_CAN_RAW_MESSAGE raw data (e.g. for the CAN De-
vice Filter )

output_- MEDIA_SUBTYPE_CAN_RAW_MESSAGE_EXT raw data in the extended CAN
ext message format (e.g. for the
CAN Device Filter )
Table 3.20.: Pins of the Can Config Codec
3.9.5 Properties
filename “” String Path to XML configuration file
ShowStructInfo false bool Activates the debug outputs for the initialization
AutoCalcUnitToSI false bool If “true” the conversion of the signal values with known units
into the corresponding SI unit is enabled.
Table 3.21.: Properties of the Can Config Codec
3.9.6 Limitation
CAN messages with identifier set to 0 are not supported and will never be decoded because CAN
message identifier 0 is internally used by the Can Config Codec Filter to mark invalid CAN identifiers.

Chapter 3. CAN
3.10 CAN Trace View Extended Service
3.10.1 Description
The CAN Trace View Extended Service replaces the standard ADTF Trace View Service (The ADTF
Trace View Service was removed in ADTF 2.9). Apart from general performance improvements this
service is capable of handling the new CAN MediaType as described on the CAN Support Service page
in the ADTF Device Toolbox SDK Documentation. Additionally a second display called the CAN Trace
List View window is available.
3.10.2 CAN Trace Tree View
The window displays a current snapshot of all CAN messages, which were transmitted by any Pin in the
current Configuration. For each channel the following additional information is displayed (see Figure 3.4
CAN Trace Tree View):
I Configured baudrate and bus state
I The count of CAN Error frames (after the first error frame was received)
I The approximately calculated busload of each channel (only if the baudrate is known)
I The Info column contains information about the CycleTime and the current time. The information
about the CycleTime is taken from the database, the current time is the calculated difference
between the timestamps of the last two signals. Normally the current time should not differ more
than 10% from the CycleTime, however a divergence greater than 10% is possible.

Chapter 3. CAN
Figure 3.4.: CAN Trace Tree View
3.10.3 CAN Trace List View
The window displays a chronological list of transmitted CAN messages of one Pin in the current Configu-
ration (see Figure 3.5 CAN Trace List View).
The displayed CAN messages can be filtered using three filters: CAN Channel Id, CAN Message Id
and Filter.Pin.
CAN Channel Id and Filter.Pin allows a selection of one or more entries using checkboxes. For example
it is possible to select all messages from channel 00 and channel 01. The CAN Message Id accepts
regular expressions to filter the message number or the name.
The filter settings will be saved if ADTF is closed and restored if restarted again.
The green button in the upper right allows to stop the update of the list, the Configuration will not be
affected by using this option. To enable the update of the view, the button has to be pressed again.
The global Property CANTrace: CAN list view history size defines the count of CAN messages which
can be displayed in the window.

Chapter 3. CAN
Figure 3.5.: CAN Trace List View
3.10.4 Settings
Via the Settings Editor (see Figure 3.6 Settings for the CAN Trace View) it is possible to specify the font
size and other settings.
The CAN Trace View Extended uses the Global Configuration Settings to decode the messages of the
CAN channels and for the mapping of DBC files to the channel number in A D T F. DBC files which are
configured in the Global Configuration Settings are valid system wide for every loaded Configuration File.
These settings are saved in the Global Configuration Settings File. Configuration Files may set their own
Properties for each Configuration. These specific settings override the Global Configuration Settings.
This can be done with the Configuration Editor (Context menu of the Configuration: Configuration →
Properties).
Figure 3.6.: Settings for the CAN Trace View

4 LIN
4.1 Vector LIN Device
4.1.1 Description
This Vector LIN Device Filter serves to read the raw LIN data via the Vector hardware into A D T F.
The LDF database filename has to be provided as Property in Global Configuration Settings or in
Configuration Settings (see subsection 4.1.5 Properties).
Windows Linux
X (32 and 64 bit) –

Table 4.1.: Platform support of the Vector LIN Device
4.1.3 Filter-GUID
adtf.io.vector_lin_device

Chapter 4. LIN
4.1.4 Pins
input MEDIA_TYPE_LIN in The Input Pin is used for LIN data to the
MEDIA_SUBTYPE_LIN bus.
output MEDIA_TYPE_LIN out The Output Pin is used for receiving LIN
MEDIA_SUBTYPE_LIN data from the bus.
Table 4.2.: Pins of the Vector LIN Device
4.1.5 Properties
application_name “ADTF” String The application name as defined by the Vector Hardware
tool.
Warning: in A D T F the channels begin with 0, there-
fore, the Vector LIN channel LIN1 matches channel 0 in
A D T F!
channel 0 int Channel number of this device
ecu_name “Master” String Name of the ECU which parameters are to be used for
LIN Configuration
queuesize 16000 int Transmit or receive message queue size
queuelevel 1 int Maximum size of the message MediaSampleArray

which is sent for a receipt by the Vector driver via the Pin
(maximum 10).
add_hardware- false bool If “true”, the Device Original Time will be transmitted with
time_info the MediaSample in info area
Table 4.3.: Properties of the Vector LIN Device

Chapter 4. LIN
4.2 LIN Config Codec
4.2.1 Description
The LIN Config Codec Filter decodes and encodes raw LIN data. For this it uses no previously specified
C structures, but only storage ranges that are filled via the decoding instructions specified in the individual
configuration file.
During decoding (LIN input), the raw LIN messages (e.g. from the Vector LIN Device or the Harddisk
Player ) are read in via the Input Pin and are then decoded with the help of LDF database files and the
configuration in the associated XML file.
For each configured input buffer of the LIN Config Codec an individual Output Pin is generated, which
is used to forward the data to other Filters. These can transform the data into the corresponding C
structures using casts. The Output Pin has the same name as the input buffer.
For encoding (LIN output), data structures are converted into LIN messages according to the output
configuration and are then transferred to the connected LIN device via the Output Pin.
The LDF database filename has to be provided in the Global Configuration Settings or in the Configuration
Settings (see subsection 4.2.5 Properties).
Windows Linux
X X
4.2.3 Filter-GUID
adtf.io.lin_config_codec

Chapter 4. LIN
4.2.4 Pins
input MEDIA_TYPE_LIN in Input Pin for LIN raw data (e.g. from the
MEDIA_SUBTYPE_LIN LIN Device Filter )
output MEDIA_TYPE_LIN out Output Pin for encoded LIN raw data (e.g.
MEDIA_SUBTYPE_LIN for the LIN Device Filter )
Table 4.4.: Pins of the LIN Config Codec

Chapter 4. LIN
4.2.5 Properties

channel_id 0 int LIN channel id [mandatory]
Create Media true bool This allows you to disable the generation of media descrip-
Descriptions tions for the buffer pins. If these become rather large ( >
[create_media- 10000 Signals) this can be a very time consuming step. A
_descriptions] media description is only created for input buffers (Output
Pins)! Output buffers (Input Pins) of the Lin Config Codec
have no media description.
[show_struct_info]
nal Updates issues)
[dump_signal_up-
dates]
ments.
Table 4.5.: Properties of the LIN Config Codec

Chapter 4. LIN
4.3 LIN Config Codec—Signal Configurator
The LIN Config Codec has an adjusted context menu. If the menu Edit Properties with ADTF Signal
Config Filter Editor for LIN Config Codec is selected, then the ADTF Signal Config Filter Editor is
opened. The editor works almost the same way as the editor for the CAN Config Codec Extended and
LIN Config Codec. For detailed information see chapter 2 Config Codec—Signal Configurator. The LIN
specific differences are demonstrated here:
4.3.1 LDF4Channel Properties
The LDF4ChannelX properties are available in Global Configuration Settings -> Bus -> LIN and also in
the Configuration Properties (Property Browser ). How the Signal Config Editor handles global and local
LDF4ChannelX properties is demonstrated with the following example:
I The following Global Configuration Settings are set:
. LDF4Channel0 = LDF0.dbc
The properties are not set in the Configuration’s settings.
. LDF4Channel0 = ""
. LDF4Channel1 = ""
. LDF4Channel2 = ""
I After opening the Signal Config Filter Editor for LIN Config Codec, the Databases Tree will show
the three entries LDF0.dbc, LDF1.dbc and LDF2.dbc. LDF0.dbc is set to channel 0. LDF1.dbc is
set to channel 1. LDF2.dbc is set to channel 2. These databases are loaded into ADTF by opening
the editor. After closing the Signal Config Filter Editor for LIN Config Codec these LDF files are
set to the Configuration’s settings.
I If you change the channel of a LDF File with the Signal Config Filter Editor, these changes will be
taken to the Configuration’s settings. For example, the channel of LDF1 is changed from channel 1
to channel 0. This influences the Configuration’s settings as follows:
. LDF4Channel0 = "LDF0.dbc, LDF1.dbc"
. LDF4Channel1 = ""
. LDF4Channel2 = "LDF2.dbc"

Chapter 4. LIN
I After opening the Signal Config Filter Editor for LIN Config Codec again, you will now see three
databases.
. LDF0.dbc on channel 0
You can adjust the channel id of a database by selecting a database node (compare with figure Figure 3.3
Signal Configurator—Set database channel of CCCExt).
4.4 LIN Trace View Service
4.4.1 Description
The LIN Trace View Service provides two trace displays for LIN message analysis during runtime.
4.4.2 LIN Trace Tree View
This window displays a current snapshot of all LIN messages, which were transmitted by any Pin in the
current Configuration.

Chapter 4. LIN
Figure 4.1.: LIN Trace Tree View
4.4.3 LIN Trace List View
This window displays a chronological list of transmitted LIN messages of one Pin in the current Con-
figuration (see Figure 4.2 LIN Trace List View). To select the Pin for which LIN messages should be
dsplayed, the combobox Filter.Pin can be used. By using the combobox LIN Channel Id the displayed
LIN messages can be filtered by a specific channel ID.
The green button in the upper right allows to stop the update of the list, the Configuration will not be
affected by using this option. To enable the update of the view, the button has to be pressed again.
The global Property LINTrace: LIN list view history size defines the count of LIN messages which can
be displayed in the window.

Chapter 4. LIN
Figure 4.2.: LIN Trace List View
4.4.4 Settings
Via the Settings Editor (see Figure 4.3 Settings for the LIN Trace View) it is possible to specify the font
size and other settings.
The LIN Trace View uses the Global Configuration Settings to decode the messages of the LIN channels
and for the mapping of LDF files to the channel number in ADTF. LDF files which are configured in the
Global Configuration Settings are valid system wide for every loaded Configuration File. These settings
are saved in the Global Configuration Settings File. Configuration Files may set their own Properties for
each Configuration. These specific settings override the Global Configuration Settings.
This can be done with the Configuration Editor (Context menu of the Configuration: Configuration →
Properties).

Chapter 4. LIN
Figure 4.3.: Settings for the LIN Trace View

5 FlexRay
For processing FlexRay data the information about the configuration of the FlexRay bus is required. This
information is stored in a FIBEX file. ADTF FlexRay modules need this file for handling the FlexRay data
and for configuration of the FlexRay devices. The filename has to be provided in the Global Configuration
Settings or in the Configuration Settings (see Table 5.1 General Configuration Settings for FlexRay).
Bus::FlexRay:: “” String Filename(s) of the FIBEX file(s) [mandatory]. Add

flexray_fibex_- a comma-seperated list of all FIBEX files needed
filename(s) in your configuration.
Bus::FlexRay:: DO_NOT_UPDATE enum Defines the behavior of the flexray coder when the
flexray_- update bit is not set on a PDU or signal group.
updatebit_- The ADTF Device Toolbox SDK Documentation
behavior provides additional information about the update
bit behavior and how it can be used in implemen-
tations.
DO_NOT_UPDATE: The coder will not process
the PDU or signal. Data buffers will not be updated
with received values and hence their content is
undefined.
SAMPLE_AND_HOLD: The coder will stick to the
last valid receive value. That means data buffers
are not updated with the reveived values but re-
main in the state of the last valid received PDU/sig-
nal value. Valid denotes in this case the last re-
ceive operation with update bit set.
USE_RECEIVED_VALUE: The coder updates
data buffers with the received values no matter
if the update bit has been set or not.
Table 5.1.: General Configuration Settings for FlexRay

Chapter 5. FlexRay
5.1 Support of several FlexRay Networks
Using more than one FIBEX-File (Project ID)
If you use more than one FIBEX-File, some Clusters, Channels, ECUs, PDUs and Signals can have
the same short name and same ID’s. To make sure that ADTF will not overwrite information of one
FIBEX-File with information from another File, every FIBEX-File must have an unique Project-ID! ADTF
will use this ID to store all internal information and give you the possibility to access signals from a specific
File! Figure 5.1 shows where the Project-ID can be found in a FIBEX-File.
Figure 5.1.: Make sure that each ProjectID is unique, if you want to use more then one FIBEX-File!
A FlexRay-Cluster or -Network within ADTF contains FlexRay Channel A, FlexRay Channel B or

FlexRay Channel A and B. A FlexRay-Channel can be Channel A or Channel B. You can use several
FlexRay-Networks with ADTF. Each Network can have Channels A, B or A and B.
The ADTF Device Toolbox supports more than only one FlexRay-Network (Channel A and B). All clusters
defined in the FIBEX-File(s) (see property flexray_fibex_filename) will be parsed and can be used in all
FlexRay modules within ADTF. FIBEX files can contain more than one FlexRay Cluster. All valid clusters
from all files in the property flexray_fibex_filename will be available after parsing.
In the Vector Hardware Config Tool a Cluster/Network is called Channel. Furthermore,

vector starts counting at Channel 1. ADTF starts at Network 0. This means that channel n
in the Vector Hardware Config Tool resembles Network n − 1 in ADTF. Please have a look
at Figure 5.2.
Expand Signal Name for Signal View structure
The Signal string now contains additional information for Cluster-Name and Project-ID. The structure is:
FlexRay-PIN/ClusterName(Project-ID)/Channel-Name/ECU/PDU/Signal
FlexRay-PIN Clustername Project-ID
Hardware_Player.output D4_FlexRay_Kanal_A Cluster
Table 5.2.: Examples for Signal Name View structure

Chapter 5. FlexRay
Figure 5.2.: Hardware Configuration of several FlexRay Networks
Please use the Vector Hardware Config Tool to map all the connected FlexRay-Devices to Channels.
Afterwards connect the Vector FlexRay Device to these channels (Networks) with the following steps:
I Set the Property DeviceID of the Vector FlexRay Device to a comma-seperated list of Device ID’s.
I Each ID connects the Device-Filter to a FlexRay Network provided by the Vector Hardware Config
Tool.
I Example: 0,2,5 - The Device Filter will work with the Devices mapped to Channel 1,3 and 6. Each
Channel is a Cluster/Network within ADTF and contains Channels A,B or A and B
I Please enter the Cluster name for each ’DeviceIDXClusterName’-Property in the Property Browser.

Chapter 5. FlexRay
Hints for some FlexRay modules:
I The FlexRay Signal Provider registers all Signals to the Signal Registry. Use the Signal View
from ADTF Display Toolbox to make signals of different FlexRay Networks and Channels A and B
visible.
I The FlexRay Trace View shows a tree of all PDU’s from all used Networks.
I The FlexRay Vector Device can handle several FlexFray Networks with different cluster configura-
tions.
I The FlexRay Config Codec can handle several FlexFray Networks and both channels A and B.
The ADTF Device Toolbox provides several FlexRay modules for ADTF. These modules are documented
in the following sections.
5.2 VectorFlexrayDevice
5.2.1 Description
This Filter enables the communication with the FlexRay hardware from Vector Informatik (VN3300,
VN3600, and VN7600).
Windows Linux
X (32 and 64 bit) –

Table 5.3.: Platform support of the VectorFlexrayDevice
5.2.3 Filter-GUID
adtf.io.vector_flexray_device

Chapter 5. FlexRay
5.2.4 Pins
Input MEDIA_TYPE_FLEXRAY in The Input Pin is used for sending FlexRay

MEDIA_SUBTYPE_FLEXRAY data to the bus.
Output MEDIA_TYPE_FLEXRAY out The Output Pin is used for receiving data
MEDIA_SUBTYPE_FLEXRAY from the bus.
Table 5.4.: Pins of the VectorFlexrayDevice
5.2.5 Properties
DeviceId 0 String Comma seperated List of ID’s of FlexRay devices to

be used. If more than one devices are connected,
this Property can be used to choose the wanted
devices. When the Filter starts it will output a list
of all connected devices on the console.
By using the “Vector-Hardware-Config” Tool, which
can be found in the windows system configuration,
a direct association between device and the ADTF
application can be configured. A FlexRay Network
with ID X in ADTF resembles a channel with ID
X + 1 in the Vector Hardware Config Tool.
If the Property is set to 0 the first device in the
“Vector-Hardware-Config” Tool will be used.
DeviceIDX- “” String Name of the Cluster, that should be mapped to the

ClusterName Network with ID X. A FlexRay Network with ID X
in ADTF resembles a channel with ID X + 1 in
the Vector Hardware Config Tool. All Clusters, that
have been parsed from the FIBEX File(s) are listed
as dropdown menu and can be selected.
ECUSendFilter “” String List of ECU names (comma separated) for which

data has to be sent by the device:
I “”: No data is sent.
I “*”: Data of all ECUs is sent.
Attention: By setting this Property carelessly the
communication of the bus may be disturbed in an
unpredictable way. [optional]

Chapter 5. FlexRay
ECU “” String Name of the ECU used to retrieve communication

parameters from the FIBEX database.
If this Property is not set the first FlexRay ECU
which is found in the FIBEX database will be used.
[optional]
ColdStart False Bool Set this Property to “true” to allow the device to
initialize the cluster communication. [optional]
ColdStartSlotId 0 Integer FlexRay slot ID for cold start. If this Property is set
to “0”, the value specified in the FIBEX database
for the ECU will be used. [optional]
Wakeup False Bool If this Property is set to “true” the FlexRay device is
configured to transmit a wakeup pattern. [optional]
ColdStart2 False Bool If this Property is set to “true” the second commu-
nication controller on the FlexRay device is config-
ured to perform a cold start. For this functionality
an “Advanced API” license from Vector Informatik
is required. [optional]
ColdStart2Slot 0 Integer FlexRay slot ID for cold start. If ColdStart2 is set to

“true” this Property becomes mandatory. [optional]
HILSendMode False Bool If this Property is set to “true” all Flexray frames
will be sent as they were recorded. Otherwise if
set to “false” the PDU Update-Bits of each frame
are checked. If Update-Bits are set, a new frame
containing the appropriate PDUs is created and
sent on the Flexray bus. [optional]
SendCycleOffset 5 Integer Set this Property to change the cycle sending be-
havior. Change this value with caution and only! if
the signal view shows unpredictable signal values.
[hidden]
Note: The Harddisk Player is not synchronized
with the FlexRay bus. The time lag between
the time of playback and the transmission on the
FlexRay bus is not predictable.
Table 5.5.: Properties of the VectorFlexrayDevice

Chapter 5. FlexRay
5.3 FlexCardDevice
The ’Eberspaecher FlexRay Device’ Filter (deprecated) is not supported with this version of
the Device Toolbox. The device will be supported as soon as a new Linux and Windows
driver is released for the device.
5.4 FlexRay ECU Filter
5.4.1 Description
The purpose of this Filter is to filter the FlexRay data on ECU level.
For each FlexRay data frame it is checked whether the name of the sending ECU is included in the
Property ECUs. In the positive case the data will be sent on the Output Pin.
5.4.2 Filter-GUID
adtf.io.flexray_ecu_filter
5.4.3 Pins
input MEDIA_TYPE_FLEXRAY in The Input Pin is used for sending FlexRay

MEDIA_SUBTYPE_FLEXRAY data to the bus.
output MEDIA_TYPE_FLEXRAY out The Output Pin is used for receiving

MEDIA_SUBTYPE_FLEXRAY FlexRay data from the bus.
Table 5.6.: Pins of the FlexRay ECU Filter

Chapter 5. FlexRay
5.4.4 Properties
ECUs “” String List of ECU names (comma separated). [optional]
Table 5.7.: Properties of the FlexRay ECU Filter
5.5 FlexRay Trace View
5.5.1 Description
This Service is started if it is integrated in the Manifest File. A new child window FlexRay Trace View is
created. In this window all Output Pins which transport FlexRay data are displayed. Starting from the Pin,
the tree displays items in the following hierarchy:
1. Pins
2. channels
3. ECUs
4. PDUs
5. signal values
In the Global Settings the following Properties can be set to modify the FlexRay Trace View:
FontName Courier String Font name for the displayed text in the tree view. It is recom-
mended to use a monospaced font here.
FontSize 8 Integer Font size
Also show false bool If “true”, additional text will be shown in column “Time/Value” for
text for all parameter values the FlexRay database provides them for.
values

Chapter 5. FlexRay
5.6 FlexRay Signal Provider
5.6.1 Description
The FlexRay Signal Provider Service visualizes signal values in cooperation with the Signal View Filter
from the ADTF Display Toolbox.
Further documentation can be found in the documentation of the ADTF Display Toolbox.
5.7 FlexRay Config Codec
5.7.1 Description
This FlexRay Config Codec Filter can be used to decode and encode FlexRay data. The format of
the data is controlled by a XML file which has to be specified in the Properties section. To create
this XML configuration file the ADTF Signal Config Filter Editor may be used, see below. The FlexRay
Config Codec depends on the FlexRay Support Service, so this Service needs to run and be properly
configured.
If you are using more than one FIBEX-File, you might have the Problem that a Signal (that you want
to use) is part of several files. There is an easy way to tell ADTF, which Signal-Information it should
use to encode/decode this signals values. If you edit new Configurations with the ADTF Signal Config
Filter Editor (XML-Files), ADTF will automatically store the Project-ID into each Signal-Name-String (see
Section 5.1).
With this information it is possible to determine from which FIBEX-File this signal came from. If you
are using old Configuration-Files together with other FIBEX-Files loaded, it can happen, that ADTF will
use the wrong Signal-Information for encoding/decoding. To prevent this effect, please expand your old
configuration files with the ProjectID of your desired FIBEX-File. This is shown in Figure 5.3.
Figure 5.3.: The ProjectID-Information is stored automatically, if you use Device Toolbox-Version >= 2.6.0.
Configuration-Files, that have been generated with older Device Toolbox-Versions must be
edited by the user, if you want to make sure that the Signal-Information is taken from a
specific FIBEX-File!

Chapter 5. FlexRay
Since FIBEX databases can become rather large, starting the Filter for the first time may
take a while depending on the configuration of your system.
At startup the FlexRay Config Codec Filter will check if the FIBEX database specified in the XML
configuration and in the global settings of ( ADTF) are the same and will generate a warning message if
they don’t match.
5.7.2 Filter-GUID
adtf.io.flexray_config_codec

Chapter 5. FlexRay
5.7.3 Properties

Create Media true bool This allows you to disable the generation of media de-
Descriptions scriptions for the buffer pins. If these become rather large
[create_media- ( > 10000 Signals) this can be a very time consuming
_descriptions] step. A media description is only created for input buffers
(Output Pins)! Output buffers (Input Pins) of the FlexRay
Config Codec have no media description.
[show_struct_info]
nal Updates issues)
[dump_signal_up-
dates]
ments.
Table 5.8.: Properties of the FlexRay Config Codec

Chapter 5. FlexRay
5.7.4 Pins
input MEDIA_TYPE_FLEXRAY in The Input Pin is used to receive FlexRay

MEDIA_SUBTYPE_FLEXRAY data which should be decoded.
output MEDIA_TYPE_FLEXRAY out The Output Pin is used to send the en-
MEDIA_SUBTYPE_FLEXRAY coded FlexRay data.
Table 5.9.: Pins of the FlexRay Config Codec
5.8 FlexRay Config Codec—Signal Configurator
The FlexRay Config Codec has an adjusted context menu. If the menu Edit Properties with ADTF
Signal Config Filter Editor for FlexRay Config Codec is selected, then the ADTF Signal Config
Filter Editor is opened. The editor works almost the same way as the editors for the CAN Config
Codec Extended and LIN Config Codec. For detailed information see chapter 2 Config Codec—Signal
Configurator. The FlexRay specific differences are demonstrated here:
5.8.1 FlexRay Specific Differences
InputPin/OutputPin
The properties channel and channelmask do not exist for FlexRay. The Vector FlexRay Device can
be configured to send and receive data from a specific cluster on a specific channel. Please refer to
section 5.1 Support of several FlexRay Networks.
Triggers
stop_msg MessageName yes The value should have the

following structure: ECU-
Name.PDUChannelValue.PDUName
Table 5.10.: FlexRay Specific Differences of Trigger-Properties

Chapter 5. FlexRay
Element
The properties default_value, unit_conversion, sign_signal and limits do not exist for FlexRay.
FlexRay-specific element properties are:
signal Signal Short- yes when The short-name of the signal.

name macro is used
channel Channel No The short-name of the channel, where

Shortname this signal is used. This can be useful,
if a signal with the same name appears
on different channels.
ecu ECU Short- No The short-name of the ECU, this signal

name belongs to.
pdu PDU Short- No The short-name of the PDU, this signal

name belongs to.
project-id Project ID Yes The ProjectID of the FIBEX-File, where

this signal comes from. This can be
useful, if a signal with the same name
appears in different files. Please refere
to section 5.7 FlexRay Config Codec.
Table 5.11.: FlexRay Specific Differences of Element-Properties
5.8.2 Special issues on decoding or encoding a FlexRay signal
Signals in a FIBEX file are defined by several properties like position in the PDU or the width of the signal
in bits. Because the FIBEX standard allows the use of several computation methods like scaling (offset,
factor, min, max) and/or additional TEXTTABLEs it’s necessary to do the following when configuring a
XML.

Chapter 5. FlexRay
Example:
The FIBEX file defines a signal with a bitlength of 7. So the RAW value range will be 0 to 127. Assuming
that there is also a computation info for scaling defined with OFFSET = 0.0, FACTOR = 2.0, MINIMUM =
0 (raw) and MAXIMUM = 125 (raw). In addition there is a TEXTTABLE defined e.g. for status handling
with the entries INIT = 126 (raw) and ERROR = 127 (raw).
Decoding case: To receive a reliable signal (scaled signal values AND status handling) 2 output
buffer/pins should be defined in the ADTF Signal Config Filter Editor. The first one is to receive the
scaled values. Because of FCC raw value forwarding these could also be the raw values scaled with
FACTOR = 1.0 and OFFSET = 0.0. So the output of the first buffer could be from 0.0 to 250.0 (in the
example FACTOR = 2.0 for scaled values) AND also 126.0 or 127.0 (FACTOR = 1.0 for raw values). This
causes a misinterpretation in the application, because the raw value 63 AND the raw value 126 will be
126.0 on the output buffer. To check the validity of a signal, the second buffer is needed to receive the
raw values for status handling. Therefor the $RAWVALUE$ macro has to be set for that signal in the
second buffer. Both buffers will be transmitted at the same time (depending on their configuration). In the
case mentioned before the application can check the validity by comparing the scaled value with the raw
value (scaled_1 = 126.0 and raw_1 = 63 / scaled_2 = 126.0 and raw_2 = 126).
Encoding case: To transmit the whole signal (scaled signal value AND status handling) 2 input buffer/pins
have to be defined in the ADTF Signal Config Filter Editor. The first one is to transmit the scaled values.
The second one is to transmit the the status handling values. Therefor the $RAWVALUE$ macro has to
be set for that signal in the second buffer. The first buffer will only be scaled to raw and transmitted if the
incomming value is in (scaled) range between 0.0 and 250.0 (in the example factor is 2.0). Otherwise
an error log message will be shown in the ADTF Console View. To avoid overwriting the outgoing PDU
data (on FCC "output" pin, the second buffer should not act at the same time. In case of status handling
only the second buffer should transmit something to the FlexRay Config Codec Filter as raw value (0 ...
127).
It’s not advisable to use a float value for encoding a raw value. The FCC will only copy the
incomming value bytewise. Using an usingned integer instead is recommended.
In this Toolbox version the $RAWVALUE$ macro for encoding is only available for FlexRay.
5.9 FlexRay DAT Exporter Support
With the FlexRay DAT Exporter Support FlexRay data recorded into DAT Files can be exported into the
Vector Informatik ASC format (see ADTF User’s Manual to get further information about the ADTF DAT
Exporter and how it works). The ASC files are used for logging purposes by CANoe itself and reflect all
relevant messages which were sent over the FlexRay bus.

Chapter 5. FlexRay
After export, it’s possible to create an offline configuration inside CANoe or CANalyzer and use the
exported file as input to this configuration. The FlexRay DAT Exporter Support is installed automatically
if you install the Device Toolbox.

6 MOST
6.1 Vector MOST Device
6.1.1 Description
This Vector MOST Device Filter serves to communicate with MOST hardware from Vector Informatik.
The following devices are supported:
I VN2610 (USB)
Windows Linux
X (32 and 64 bit) –

Table 6.1.: Platform support of the Vector MOST Device
6.1.3 Filter-GUID
adtf.io.most.vector

Chapter 6. MOST
6.1.4 Pins
input MEDIA_TYPE_MOST in Input Pin for the MOST data to be sent

MEDIA_SUBTYPE_MOST
output MEDIA_TYPE_MOST out Output Pin for the received MOST data
MEDIA_SUBTYPE_MOST
Table 6.2.: Pins of the Vector MOST Device

Chapter 6. MOST
6.1.5 Properties
UseVector- true bool For the assignment of MOST channel numbers in

Hardware- A D T F and the hardware the settings under Control
ConfigSettings Panel → Vector Hardware can be used.
Warning: in A D T F the channels begin with 0, there-
fore, the MOST channel CAN1 matches channel 0 in
A D T F!
If this Property is set to “false”, the parameter num-
channels specifies the count of used channels.
numchannels 0 int Number of channels

0: All available channels are used.
n: The first n channels are used.
channel_<n>_mode “Slave” Selection Device mode for channel n.

The following modes can be selected:
I “Slave”: Channel is configured as slave.
I “Master”: Channel is configured as master.
I “Spy”: Channel is configured as spy.
channel_<n>_node- 0 int MOST node address of channel n

address
channel_<n>_group- 0 int MOST group address of channel n

address
add_hardware- false bool If “true”, the Device Original Time of a message will
time_info be transmitted with the MediaSample in info area.
VerifyDriverVersion true bool If “true”, the Filter will check if a tested driver is used
and interrupt initialization if this requirement is not
fulfilled.
Table 6.3.: Properties of the Vector MOST Device

Chapter 6. MOST
6.2 OptoLyzer G1 MOST Device
6.2.1 description
This OptoLyzer G1 MOST Device Filter serves to communicate with MOST hardware from SMSC. The
following devices are supported:
I OptoLyzer G1 (MOST25)
homepage http://www.smsc-ais.com/.
Windows Linux
X (32 and 64 bit) X (64 bit)
No additional driver is needed No additional driver is needed
Table 6.4.: Platform support of the OptoLyzer G1 MOST Device
6.2.3 Filter-GUID
adtf.io.most.optolyzer_g1
6.2.4 Pins

MEDIA_SUBTYPE_MOST
MEDIA_SUBTYPE_MOST
Table 6.5.: Pins of the OptoLyzer G1 MOST Device

Chapter 6. MOST
6.2.5 Properties
port 1 int Serial port number
channel_mode “Slave” Selection Device mode for the channel.

channel_nodeaddress 0 int MOST node address of the channel.
channel_groupaddress 0 int MOST group address of the channel.
add_hardwaretime_info false bool If “true”, the Device Original Time of a message

will be transmitted with the MediaSample in info
area.
Table 6.6.: Properties of the OptoLyzer G1 MOST Device
6.3 OptoLyzer G2 MOST Device
6.3.1 Description
This OptoLyzer G2 MOST Device Filter serves to communicate with MOST hardware from SMSC. The
following devices are supported:
I OptoLyzer OL3025o V1 (MOST25): Tested with Firmware 1.4.0.0
I OptoLyzer OL3025o V2 (MOST25): Tested with Firmware 2.0.3.0
I OptoLyzer OL3150o (MOST150): Tested with Firmware 1.8.0.0
homepage http://www.smsc-ais.com/.

Chapter 6. MOST
Windows Linux
X (32 and 64 bit) X (64 bit)
No additional driver is needed No additional driver is needed
Table 6.7.: Platform support of the OptoLyzer G2 MOST Device
6.3.3 Filter-GUID
adtf.io.most.optolyzer_g2
6.3.4 Pins

MEDIA_SUBTYPE_MOST
MEDIA_SUBTYPE_MOST
Table 6.8.: Pins of the OptoLyzer G2 MOST Device

Chapter 6. MOST
6.3.5 Properties
ipaddress 192.168.0.1 String IP address of the device
ipport 27999 int IP port of the device
timing_mode “Slave” Selection Device mode for the channel.

bus_speed “Automatic” Selection MOST bus speed.

The following speeds can be selected:
I “Automatic”: Speed is configured automati-

cally
I “MOST25”: Device is connected to

MOST25
I “MOST150”: Device is connected to

MOST150
bus_frequency “44.1 kHz” Selection MOST bus frequency.

The following frequencies can be selected:
I “44.1 kHz”: MOST operates at 44.1 kHz
I “48.0 kHz”: MOST operates at 48.0 kHz
add_hardware- false bool If “true”, the Device Original Time of a message

time_info will be transmitted with the MediaSample in info
area.
VerifyDriverVersion true bool If “true”, the Filter will check if a tested driver is
used and interrupt initialization if this requirement
is not fulfilled.
Table 6.9.: Properties of the OptoLyzer G2 MOST Device

Chapter 6. MOST
6.4 MOST Support Service
The MOST Support Service implements the MOST MediaSample class. It has to be used whenever
MOST data is processed.

7 Ethernet
Starting with Device Toolbox 2.2 the Ethernet Device UDP and Ethernet Device TCP are
marked as deprecated and will not supported any more !
Both filters will provided as source-code under src/plugins/ethernet_udp (_tcp).
If you want changes or enhancements, please feel free to do it by yourself.
7.1 Ethernet Device UDP
Starting with Device Toolbox 2.2 the Ethernet Device UDP is not supported any more !
Please see the hints at the beginning of chapter 7 Ethernet.
7.1.1 Description
This Ethernet Device UDP Filter serves to read in and output Ethernet data packets via the user datagram
protocol (UDP) in ADTF. The complete data packets received via the specified Ethernet port are packed
in a MediaSample of the type
(MEDIA_TYPE_NETWORK_DATA, MEDIA_SUBTYPE_NETWORK_DATA_IP)
and fed via the Output Pin into A D T F. If the device should be used on win32 platforms with multicast
addresses, have a look at the ADTF SDK Documentation (class cDatagramSocket).
It is in the nature of UDP connections that packages may be lost or reordered on their way
due to the quality of the physical connection.

Chapter 7. Ethernet
Windows Linux
X (32 and 64 bit) X (64 bit)
Table 7.1.: Platform support of the Ethernet Device UDP
7.1.3 Filter-GUID
adtf.io.ethernet_device_udp
7.1.4 Pins
input MEDIA_TYPE_NETWORK_DATA in Input Pin for the data packets to be sent via
Ethernet.
output MEDIA_TYPE_NETWORK_DATA out Output Pin for the received Ethernet data pack-
ets.
Table 7.2.: Pins of the Ethernet Device UDP

Chapter 7. Ethernet
7.1.5 Properties
BroadcastEnable false bool Activates the broadcast mode
MulticastIP “” String Optional IP of a multicast group for the reception of Ethernet

data.
RXPort 0 int The local host port number.
RXBufferSize 65535 UInt32 Size fo the receive buffer in bytes
TxHostName “” String Name of the recipient computer
TxIP “” String IP of the recipient computer (if TxHostName is not speci-

fied)
TxPort 0 int Port number of the remote port to which the data is sent.
Table 7.3.: Properties of the Ethernet Device UDP
7.2 Ethernet Device TCP
Starting with Device Toolbox 2.2 the Ethernet Device TCP is not supported any more !
Please see the hints at the beginning of chapter 7 Ethernet.
7.2.1 Description
This Ethernet Device TCP Filter serves to read in and output Ethernet data packets via the transmission
control protocol (TCP) in ADTF. The complete data packets received via the specified Ethernet port are
packet in a MediaSample of the type
(MEDIA_TYPE_NETWORK_DATA, MEDIA_SUBTYPE_NETWORK_DATA_IP)
and fed via the Output Pin into A D T F.

Chapter 7. Ethernet
Windows Linux
X (32 and 64 bit) X (64 bit)
Table 7.4.: Platform support of the Ethernet Device TCP
7.2.3 Filter-GUID
adtf.io.ethernet_device_tcp
7.2.4 Pins
input MEDIA_TYPE_NETWORK_DATA in Input Pin for the data packets to be sent via
Ethernet.
output MEDIA_TYPE_NETWORK_DATA out Output Pin for the received Ethernet data pack-
ets.
Table 7.5.: Pins of the Ethernet Device TCP

Chapter 7. Ethernet
7.2.5 Properties
ConstantPacketSize true bool “true”: new MediaSample is only transmitted when con-
figured PacketSize is reached
“false”: new MediaSample is always transmitted when
new data was received
PacketSize 16384 int Size of the data packets
Port 1718 int Port number of the remote port that is connected
HostName “” String Name of the server that is connected
IP “” String IP of the server to whicht the connection is made (if

Hostname is not set)
Table 7.6.: Properties of the Ethernet Device TCP

8 Camera
8.1 General Video Capture Device Options
All Video Capture Device Filters offer the following basic Properties:
Property default Type Use
AutoExposeControl true bool Automatic lighting control
AutoGainControl true bool Automatic amplification regulation
BitsPerPixel 0 int Color depth
BytesPerLine 0 int Line alignment
DeviceName “default” String Specifies the device which should be opened. The
input always depends on the concrete device that
is supported. Default is either a number of devices
starting with 1 with the specification “capture:1”, “cap-
ture:2”, etc. or the specification of the device names
or their serial numbers, e.g. “MVF-2371”.
FlipHorizontal false bool Mirror image horizontally
FlipVertical false bool Mirror image vertically
Height 0 int output height
NumBuffers 0 int Number of buffered used
PaletteSize 0 int Size of the color palette
RequestTimeout 0 int Timeout after which aborted

Chapter 8. Camera
SyncEnable true bool The MediaSample sync flag is not set
UpdateRate 0 int updates per second
UserConfig “” string Device specific config string
Width 0 int Output width
Table 8.1.: Common Properties of Video Capture Device Filters
8.2 Blue Fox Capture Device
8.2.1 Description
This Blue Fox Capture Device Filter serves to initialize cameras of the brand Matrix Vision BlueFOX and
play back the images in A D T F. The BlueFOX API is used to address various camera functions and to
make settings.
homepage http://www.matrix-vision.com/.
Windows Linux
X (32 and 64 bit) X (64 bit)
version 2.13.0.1629. version 2.13.0.1629.
Table 8.2.: Platform support of the Blue Fox Capture Device
8.2.3 Filter-GUID
adtf.io.bluefox_capture

Chapter 8. Camera
8.2.4 Pins
output MEDIA_TYPE_VIDEO out Video output

MEDIA_SUBTYPE_VIDEO_UNCOMPRESSED
Table 8.3.: Pin of the Blue Fox Capture Device
8.2.5 Properties
The Filter supports the basic Properties for Video Capture Devices (see ADTF User’s Manual, Section
6.2.1).

Chapter 8. Camera
devicename “” String The device to be used. Use serial number or device index
[1..n]. Serial number will be preferred and may contain
* as wildcard for single characters or rightmost string.
Examples: BF002215, BF*, ***02*, 1
After installing the Matrix Vision drivers the Serial can be
easily found by 2 ways:
1. After starting wxPropView within the installation-path
you can choose your camera in the upper left corner.
Now the Serial is shown within the Box you’ve chosen
the camera: it’s the part before the brackets. Example:
BF002215 (myBlueFox-1012dG, DeviceID: ’3’)
2. After starting mvDeviceConfigure within the installation-
path you see a list of all Devices. You can find the serial
in the column ’Serial’.
Height 0 int Height of output video. 0 takes value from current camera
settings or UserConfig property. If not 0 and value differs
from UserConfig the image will be stretched.
UserConfig “” String Filename of the device specific configuration file.

For further information consult the vendor’s camera docu-
mentation. If a configuration file is used, all settings made
in ADTF regarding the camera will be ignored and have
no effect.
Width 0 int Width of output video. 0 takes value from current camera
settings or UserConfig property. If not 0 and value differs
from UserConfig the image will be stretched.
Table 8.4.: Additional Property of the Blue Fox Capture Device

Chapter 8. Camera
8.3 Direct Show Video Device
8.3.1 Description
The Direct Show Video Device Filter serves to read in video images. Here, various cameras as video
sources are supported. For reading in, the functionality of DirectShow is used.
For importing video files (e.g. AVI or MPG) please use the Create New Dat File option in
ADTF-GUI (see ADTF User Manual section Creating a new DAT File) or with ADTF Datex-
porter Tool (see ADTF User Manual section Command line DAT Exporter/Importer/Repair).
For the use of some DirectShow video sources (e.g. Bluefox camera), the device assignment
is only possible without errors with administrator rights.
Windows Linux
X –
Table 8.5.: Platform support of the DirectShow Video Capture Device
8.3.3 Filter-GUID
adtf.io.direct_show_video_device
8.3.4 Pins
Name Type I/O Use
output MEDIA_TYPE_VIDEO out Output Pin for the read in video images
Table 8.6.: Pins of the DirectShow Video Device

Chapter 8. Camera
8.3.5 Properties
The Filter offers, in addition to the basic Properties, no additional Properties. The devices are numbered
starting with “capture:1”.
GreyMask not supported
PaletteSize not used
BytesPerLine not used
Table 8.7.: Properties of the DirectShow Video Device
8.4 µEye Capture Device
8.4.1 Description
This µEye Capture Device Filter serves to initialize cameras of the Imaging Development Systems and
play back the images in ADTF. The µEye API is used to address various camera functions and to make
settings.
homepage http://www.ids-imaging.com/.
Windows Linux
X (32 and 64 bit) X (64 bit)
version 4.40.1.0. version 4.40.1.0.
Table 8.8.: Platform support of the µEye Capture Device

Chapter 8. Camera
8.4.3 Filter-GUID
adtf.io.ueye_capture
8.4.4 Pins

Table 8.9.: Pin of the µEye Capture Device
8.4.5 Properties
The Filter supports the basic Properties for Video Capture Devices.
UserConfig “” String Filename of the parameter file or the EEPROM parameter

block, created by the µEye Demo application.
“/cam/set1” ⇒ EEPROM parameter block 1
“/cam/set2” ⇒ EEPROM parameter block 2
For further information consult the vendor’s camera docu-
mentation. If a parameter file or the EEPROM parameter
block is used, all settings made in ADTF regarding the
camera will be ignored and have no effect.
VerifyDriverVersion true bool If “true”, the Filter will check if a tested driver is used
and interrupt initialization if this requirement is not fulfilled.
Unchecking this flag when using parameter files may lead
to unexpected behaviour!
Table 8.10.: Additional Property of the µEye Capture Device

Chapter 8. Camera
8.5 Linux Video Capture Device
8.5.1 Description
The Linux Video Capture Device incorporates Video4Linux image sources into A D T F.
Windows Linux
– X
Table 8.11.: Platform support of the Linux Video Capture Device
8.5.3 Filter-GUID
adtf.io.linux_video_capture_device
8.5.4 Pins
Name Type I/O Use

Table 8.12.: Pins of the Linux Video Capture Device
8.5.5 Properties
The Filter —in addition to the basic Properties—also offers the some device-dependent Properties. These
are shown in Table 8.13 Properties of the Linux Video Capture Device.
The Property devicename can be set to any Linux Video Capture Device. The default for this is
/dev/video0”.

Chapter 8. Camera
devicename “default” String Video4Linux device
capturewidth -1 int Horizontal recording resolution
captureheight -1 int Vertical recording resolution
depth -1 float Color depth (-1, 0, . . . )
brightness -1 float Brightness (-1, 0, . . . )
contrast -1 int Contrast
format -1 int Color format
PaletteSize not in use
BytesPerLine not in use
Table 8.13.: Properties of the Linux Video Capture Device

9 Additional Service
9.1 External File Support Service
With the External File Support Service bus data can be imported from several custom file formats into
DAT Files or bus data recorded into DAT Files can be exported into various file formats (see ADTF User
Manual for further information about the ADTF DAT Exporter and how it works).
9.1.1 External Stream Sync
With the External Stream Sync Source of the External File Support Service you can create a valid
ADTF Dat file stream of type MEDIA_TYPE_STREAM_SYNC, which contains sync data for an external
multimedia stream in relation to ADTF SampleTime.
To do this, an external ASCII file containing the header line External_Stream_Sync and pairs of
ADTF timestamps and the appropriate multimedia-stream time (in seconds) of an external video/audio or
other multimedia stream has to be created before, as input for the External Stream Sync Source.
Format for timestamp and index:
I ADTF timestamp (in microseconds): tUInt
I multimedia stream time (in seconds): tFloat
I multimedia index: tUInt
Example for the ASCII file format:

External_Stream_Sync
1234066778;123.32;0
1234166779;124.32;1
1234266780;125.32;2
1234366781;126.32;3
1234466782;127.32;4

Chapter 9. Additional Service
All values have to be separated by semicolon.
The 3rd column containing an index into the external multimedia stream, is optional. The 1st and 2nd
columns with ADTF Timestamp and external stream time (in seconds) are mandatory.
For an usage example see section 9.2 ADTF MDF4 DeviceTB support for the Dat Exporter Service.
9.1.2 Usage of ADTF DAT Exporter
To find out the available ADTF DAT Exporter command-line switches, open a command-line in your
A D T F binary directory and type the following command.
adtf_datexporter --help
If you are using an A D T F version lower than 2.9.0 have a look at the following description. It illustrates
the use of the ADTF DAT Exporter command-line utility:
Command
adtf_datexporter [options] DATFILE
Command line options
-verbose - Print verbose log messages.

-service SERVICE - Instructs the exporter to load an additional
service.
-liststreams FILE - List all streams in a file and available sinks.
-listsampleinfo FILE - List all streams in a file and calculate sample
ratios.
-listextensionsinks FILE - List all available extension sinks for a file.
-listproperties ID - List all properties of a sink or source.
Dat conversion options
-createcompat DATFILE - Create a compatibility file for old 1.x

DAT Files.
To convert an ADTF 1.x DAT File use the import options below.
Dat export options

-exportdescription TXTFILE - Exports the description of the DAT File to

TXTFILE.
-export STREAM - Export stream from an ADTF DAT File.
-sinkid ID - The sink which shall be used to export the last
specified stream (if you do not specify one,
the first valid one will be used).
-output FILE - Set the name of the output filename for the
last specified stream sink.
-extensionsink ID - Enable the specified extension sink.
-property NAME=VALUE - Set a property of the last sink, both streams
and extensions (you can use multiple of these).
Import options
-setdescription TXTFILE - Imports the description of TXTFILE (can be

specified only once).
-import FILE - Import streams from FILE.
-sourceid ID - The source which shall be used to import the
last specified file (if you do not specify one,
the first valid one will be used).
-property NAME=VALUE - Set a property of the last source (you can use
multiple of these).
-stream STREAM - Import STREAM from the last file specified
before this option (by default all streams are
imported).
-importextension FILE - Import an extension from a file.
-extensionsourceid ID - The source which shall be used to import the
last specified extension file (if you do not
specify one, the first valid one will be used.
-name NAME - Sets the new name of the last stream specified
before this option (by default the name is not
changed).
-offset OFFSET - Specifies the time offset in microseconds of
the last stream specified before this option.
-start START - Specifies the lower timestamp limit for the
chunks of the last stream specified before
this option.
-end END - Specifies the upper timestamp limit for the
chunks of the last stream specified before
this option.
-streamdescription - Triggers media description generation for the
last stream specified before this option.
-digest - Create a MD5 digest file.
-createdescriptions - Create a Media Description for all streams.
Append options
For each file the first source that can handle the file is used
-append FILE - Append FILE to the output.
-append FOLDER - Append all files in FOLDER in alphabetical
order.

-pause=LIST - LIST is a ’:’ seperated list of delays in

microseconds that should be put between the
files.
-absolute=LIST - LIST is a ’:’ seperated list of absolute
starting points for all files but the first
(the first always starts at 0).
-skipstartgap - Skip start delay in input files.
-digest - Create a MD5 digest file.
-createdescriptions - Create a Media Descriptions for all streams.
Repair options
-repair BROKEN REFERENCE OUTPUT - Tries to repair BROKEN DAT File by using
the stream information from REFERENCE and
stores the result in OUTPUT.
9.1.3 Overview of sinks and sources
See the ADTF Device Toolbox SDK Documentation to get more information of all available
sinks and sources.
9.1.4 MOST
The following formats are supported:
Name MOST25 import MOST25 export MOST150 import MOST150 export
ASC X – – –
CCO X1 – – –
IMG X X X X
OP2 X1 – – –
OPD X1 – – –
Table 9.1.: Supported formats of the External File Support Service
1
Control and light/lock messages are imported only.

Please keep in mind: An import of ’base dec’ ASC-files is currently not supported for MOST.
So make sure to configure your ASC-exporting tool to write ’base hex’ ASC-files, at least for
MOST.
The following examples illustrate the use of the ADTF DAT Exporter command-line utility:
1. To export MOST data from the stream most stored in a DAT File named most_example.dat
the following command has to be issued:
adtf_datexporter -service <path>/external_file_support.srv
-service <path>/most_support.srv -export most most_example.dat
2. To import MOST data from a custom file named most_trace.asc into a DAT File named
most_custom.dat the following command has to be issued:
adtf_datexporter -service <path>/external_file_support.srv
-service <path>/most_support.srv -import most_trace.asc most_custom.dat
9.1.5 CAN
Currently exporting a DAT File to an ASC file and importing from ASC to a DAT File is supported.
Please keep in mind: An import of ’base dec’ ASC-files is currently not supported for CAN.
So make sure, to configure your ASC-exporting tool to write ’base hex’ ASC-files, at least
for CAN.
The previously used tCANMessage structure has been replaced with the more powerful tCANData
structure. Please see the ADTF SDK Documentation for details on the tCANData structure.
The following examples illustrate the use of the ADTF DAT Exporter command-line utility to export the
CAN stream as ASC file:
To export the new tCANData data from the stream can stored in a DAT File named
<path_to_dat_file>.dat into an ASCII File named <path_to_asc_file>.asc the following
command has to be issued:
adtf_datexporter -service <path_to>/can_support.srv
-service <path_to>/external_file_support.srv
-export <stream_name e.g. rawcan>
-sinkid adtf.export.asc_file_sink
-property DBCFiles4Channel0=<path_to_dbc_file>.dbc
-property DBCFiles4Channel1=<path_to_dbc_file>.dbc
-output <path_to_asc_file>.asc <path_to_dat_file>.dat
The token <path_to> has to be substituted by the installation path of the ADTF Device Toolbox bin
directory.

9.1.6 LIN
Currently exporting a DAT File to an ASC file and importing from ASC to a DAT File is supported.
LIN stream as ASC file:
To export the new tLINData data from the stream lin stored in a DAT File named
<path_to_dat_file>.dat into an ASCII File named <path_to_asc_file>.asc the following
adtf_datexporter -service <path_to>/can_support.srv
-service <path_to>/external_file_support.srv
-export <stream_name e.g. output>
-sinkid adtf.export.lin_asc_file_sink
directory.
9.1.7 FlexRay
Currently exporting a DAT File to an ASC file is supported.
FlexRay stream as ASC file:
To export FlexRay data from the stream flexray stored in a DAT File named
<path_to_dat_file>.dat into an ASC File named <path_to_asc_file>.asc the following
adtf_datexporter -service /path_to/flexray_support.srv
-service <path_to>/flexray_export.srv
-export <stream_name e.g. Flexray>
-sinkid adtf.export.flexray
-property flexray_fibex_filename=<path_to_xml_file>.xml
directory.

9.2 ADTF MDF4 DeviceTB support for the Dat Exporter

Service
With the ADTF MDF4 DeviceTB support for the Dat Exporter Service bus data recorded into DAT Files
can be exported into the MDF4 (MDF 4.0 Measurement Data Format) file format (see ADTF User Manual
to gain more information about the ADTF DAT Exporter and how it works). See subsection 9.1.1 External
Stream Sync for information about how to sync an external multimedia stream with the bus data.
The supported bus data formats are:
I tCANData
I tCANMessage (deprecated)
I tFlexRayData
9.2.1 Usage
This chapter covers the usage of the ADTF DAT Exporter regarding the ADTF MDF4 DeviceTB support
for the Dat Exporter Service. For information about the general usage of the ADTF DAT Exporter see
chapter Usage of ADTF DAT Exporter.
To use the MFD4 support, the ADTF DAT Exporter has to be called with the according options.
I Dat exporter call:

<AdtfBinDir>adtf_datexporter [MDF_OPTIONS]
-output <MDF_OUTPUT_FILE> <INPUT_FILE>
I [MDF_OPTIONS] for generating an MDF4-file containing CAN data

-service <DevTbBinDir>\bin\can_support.srv
-service <DevTbBinDir>\bin\mdf_devicetb_support.srv
-export <can_stream_name> -sinkid adtf.export.mdf_can_sample_sink
-property DBCFiles4Channel0=<dbc file>
-property DBCFiles4Channel1=<dbc file>
I [MDF_OPTIONS] for generating an MDF4-file containing FlexRay data

-service <DevTbBinDir>\bin\flexray_support.srv
-service <DevTbBinDir>\bin\mdf_devicetb_support.srv
-export <flexray_stream_name>
-sinkid adtf.export.mdf_flexray_sample_sink
-property flexray_fibex_filename=<fibex file>
I [MDF_OPTIONS] for generating an MDF4-file containing XCP data

-service <CalibTbBinDir>\adtf_a2l_support.srv
-service <CalibTbBinDir>\mdf_calibtb_support.srv
-export <xcp stream name> -sinkid adtf.export.mdf_xcp_sample_sink
-property A2L_File=<a2l file>
To export XCP data, the ADTF Calibration Toolbox has to be installed.
I For generating an MDF4-file containing external video reference data and synchronizing it with
the bus data, the External Stream Sync is used. See chapter External Stream Sync for
information about the <VIDEO_INDEX_FILE> ASCII file that will be used in the following steps.
To process the ASCII input file with external video sync-data and create a valid ADTF-Stream, call
the Dat exporter with the following options.
<AdtfBinDir>\adtf_datexporter [VIDEO_IMP_IDX_OPTIONS]
<VIDEO_IDX_INPUT_FILE>
[VIDEO_IMP_IDX_OPTIONS]:
-service <DevTbBinDir>\external_file_support.srv
-import <VIDEO_INDEX_FILE>
-stream External_Stream_Sync -name External_Stream_Sync
To generate the MDF4 file containing synchonized video reference data, call the Dat exporter with
the following options.
<AdtfBinDir>\adtf_datexporter [MDF_OPTIONS]
-output <MDF_OUTOUT_FILE> <VIDEO_IDX_INPUT_FILE>
[MDF_OPTIONS] for generating an MDF4-file containing video reference data

-service <DevTbBinDir>\external_file_support.srv
-service <DevTbBinDir>\mdf_devicetb_support.srv
-export External_Stream_Sync
-sinkid adtf.export.mdf_external_stream_sample_sink
-property use_time_as_syncvalue=true
-property at_tx_filename=<at_filename>
-property at_tx_mimetype=<at_mimetype>
-property at_md_comment_Videodevice=<at_videodevice>
-property at_md_comment_Audiodevice=<at_audiodevice>
-property at_md_comment_Videocodec=<at_videocodec>
-property at_md_comment_Audiocodec=<at_audiocodec>
The property at_tx_filename is mandatory, all other ’at_*’-properties are optional.
I To append an export of a ADTF-stream to an existing MDF4 file, add the following option to the
[MDF_OPTIONS]:

-property append_mdf=true
Filename and path of the existing MDF-file must be set as Output filename.
I If you want an additionally (and optionally) debug-log-file beside the MDF4 output file, e.g. if you
assume some failures during the MDF-conversion (or if the ADTF-Support requests this), add the
following option to the [MDF_OPTIONS]:
-property write_debug_log_file=true
For a quick start use the following example. The batch file covers all options described above.
I Copy the provided template batch script from <DevTbInstDir>/src/examples/src/
MDF_CAN_FR_XCP_VIDEO_export/MDF_CAN_FR_XCP_VIDEO_export.bat into your

working directory.
I Edit/change/adapt the necessary variables at the beginning of the script (paths, filenames, stream-
names etc. See description inside the file.)
I Call the script in a Windows cmd-shell with one parameter: the Input-DAT-file
I A file generated.mf4 (or with the name you have chosen inside the script) is created in the
same directory, which contains all exported streams:
. CAN
. FlexRay
. XCP
. External_Stream_Sync
If you want, you can append as many streams as you like to the generated.mf4
(more CAN, FlexRay, XCP and External-Video-syncs too). You only need to enhance
the batch-script. But keep in mind: Regarding the MDF-specification, there is only one
time-reference-base in the MDF HD-block, so all exported streams should be from the same
ADTF Input-DAT-file.

10 FAQ
I Error: If the ADTF Filters “VectorCANDevice” and “VectorFlexrayDevice” are in the same configura-
tion the start of the configuration fails.
Solution: The Filter “VectorCANDeviceXL” has to be used instead of “VectorCANDevice”.
I Error: If the device VN3600 from Vector Informatik is used with driver version 6.5.12 some FlexRay
frames are not received.
Solution: Use driver version 6.4.16 or version above 6.5.12 instead.
I If the device VN7600 from Vector Informatik with driver version 6.5.23 together with ADTF Filter
“VectorCANDeviceXL” is used the error message “VectorCANDeviceXL: Could not open driver!
Please check config!” is displayed on startup.
Solution: Update the driver of the VN7600 to a newer version.
I Error: The error message “Missed x cycles!” is displayed in console view.
Solution: The ADTF Filter “VectorFlexrayDevice” is not able to handle the cycle start events emitted
from the device fast enough. In the menu System configuration → Vector Hardware the value
for the Property Receive latency has to be set to a smaller value.
I What are the data structures behind the Media Types of Device Toolbox filters?
Solution:

Chapter 10. FAQ
Type Struct
MEDIA_TYPE_CAN tCANData
MEDIA_TYPE_LIN tLINData
MEDIA_TYPE_FLEXRAY tFlexRayData
MEDIA_TYPE_MOST tMOSTData
Table 10.1.: Struct used for each Media Type
Further information about these structs can be found in the ADTF Device Toolbox SDK Documen-
tation.

11 Abbreviations
Name Description
CAN Controller Area Network
ECU Electronic Control Unit
FIBEX Field Bus Exchange Format
IP Internet Protocol
LIN Local Interconnect Network
MOST Media Oriented Systems Transport
PDU Protocol Data Unit
TCP Transmission Control Protocol
UDP User Datagram Protocol

A Change Log
This list tracks the changes made within the ADTF Device Toolbox.
A.1 Version 2.7.1
Built against A D T F 2.12.0
Changes
I #ADEVTB-1591 ASC Export without FIBEX must be possible with warning
I #ADEVTB-1627 SCFE should resolve Macros
Bugfixes
I #ADEVTB-1577 Offset will be considered incorrectly
I #ADEVTB-1589 Macros are not resolved during init
I #ADEVTB-1620 Signal decoding error if value is near signal limits
A.2 Version 2.7.0

Chapter A. Change Log
Changes
I #22409 [External File Support Service]: provide option to import flexray data from ASC file to DAT
file
Reject reason: Duplicates #25920 - [External File Support, Flexray Support Service]: Implementa-
tion of flexray_asc_file_source {HD - TicketID 21859LKCMF}
I #33288 [Vector FlexRay Device Filter] Errors during playback of FlexRay-Frames if too many ECUS
were recorded
I #35723 [Vector CAN XL Device, Vector LIN Device, Vector FlexRay Device, Vector MOST Device]
Update to Vector XL Driver Library version 9.7 to support Vector Keyman License Dongle
I #37128 [flexray_export] FlexRay ASC Sink must set the correct cycle repetition value
Bugfixes
I #21078 [FlexRay Support Service]: IFIBEXDatabase method GetPDUID does not work properly -
{HD - TicketID 15633KFIMJ}
I #22856 [FlexRay Config Codec]: property "Handling of Signal Limits from Database" does not
work correctly (ignore, maybe clip too)
I #28888 [BaseCodec] Calculating Factor and Offset on a media buffer from type integer leads to a
loss of data
I #29456 [FlexRay Config Codec],[FlexRay Signal Config Filter Editor] $RAWVALUE$ macro does
not work in combination with Project-ID
I #33469 [CAN Signal Provider] Error Frames are interpreted as normal frames
I #34732 [CAN Signal Config Filter Editor, FlexRay Signal Config Filter Editor, LIN Signal Config
Filter Editor] Exporting Media Description in all Signal Config Filter Editors does not work
I #34759 [LIN Support Service] LIN to .asc export does not work
I #34849 [Vector FlexRay Device / Fibex Parser] Using of several flexray networks and device filters
in car can lead to unsyncable flexray networks - ADTFS-44108
I #35637 [MDF DeviceTB Support Service] MDF Flexray Sink ignores linked source for Flexray
Cluster
I #35724 [Vector CAN XL Device, Vector LIN Device, Vector FlexRay Device, Vector MOST Device]
Vector Keyman license stick not supported
I #37698 [MDF Flexray Sink] Crash if calculated Media-Sample timestamps are negative

I #38663 [PEAK-CAN Device] ADTF hangs on Linux64 if PEAK-CAN Device is not connected to a
CAN bus
I #38711 [FlexRay Config Codec] $RAWVALUE$ Macro calculates wrong values
A.3 Version 2.6.2
Changes
I #32511 [PROCESS] Add presentation of Elektrobit FlexRay Framework including EB 5200 Card to
public documentation
I #34118 [Usermanual] Downgrade PDF Version due to crash issue in some readers (PDF Error
131)
Bugfixes
I #28920 [FCC-Parser] FCC Parser does not support special signal-types and attributes {HD -
TicketID 26579LFKHH}
Reject reason: Workaround for this exists by implementing own parser - see #24574
I #31473 [Vector Flexray Device] FlexRay channel B data are sent via channel A if HILSendMode is
enabled - {HD - TicketID 27105LEPKE}
I #31900 [Vector FlexRay Device Filter] Optimize the internal data processing to avoid gaps on the
FlexRay bus during playback
I #31936 [Vector FlexRay Device Filter] Unable to send FlexRay-Frames via Slots which are marked
as ColdStart-Slots
I #32011 [MDF DeviceTB Support Service] Exported MDF file cannot be read in CANape with more
than one FlexRay channel enabled
I #32283 [FlexRay Config Codec],[FlexRay Signal Config Filter Editor] Provide option to trigger also
whole PDU - {HD - TicketID 28264LDPFL}
Reject reason: No direct user requirement
I #32812 [FlexRay Signal Provider, CAN Signal Provider, MOST Signal Provider, LIN Signal Provider]
Enable text entries for signals providing them

I #33428 [Can Trace View] Update of the cCANPinCombobox leads to a crash in Qt {ADTFS-44077}
Reject reason: Not reproducable
I #33461 [CAN Database] Calculation of start position of BE signals is wrong. {ADTFS-44076}
I #34691 [Vector FlexRay Device] Using of several flexray networks and device filters in car can lead
to unsyncable flexray networks - {ADTFS-44108}
A.4 Version 2.6.1
Bugfixes
I #29020 [CCC Parser] ADTF crashes when loading keyword value description greater than 4k - {HD
- TicketID 26626LFJNF}
I #29062 [Vector FlexRay Device] Vector FlexRay Device from Device Toolbox 2.6 is not compatible
with ADTF 2.13 - {HD - TicketID 26573LFKHN}
I #29489 [FlexCard Device] Support of 800kBit/s transfer rate
A.5 Version 2.6.0
(for compatibility reasons)
Changes
I #1680 MOST-Codec: Mark MOST Trace View and MOST List View as BETA
I #6526 [FlexRayConfigCodec] Enhance the FlexRay Config Codec to maintain several FlexRay
networks within ADTF
I #6714 [FlexraySupportService] Enhance the FlexRaySupportService to maintain several FlexRay


I #6716 [Vector FlexRay Device] Enhance the Vector FlexRay Device to maintain several FlexRay
I #6717 [Eberspaecher FlexRay Device] Enhance the Eberspaecher FlexRay Device to maintain
several FlexRay networks within ADTF
Reject reason: deprecated because of #26224
I #6718 [FlexRay Signal Provider] Enhance the FlexRay Signal Provider to maintain several FlexRay
I #6719 [FlexRay Trace View] Enhance the FlexRay Trace View to maintain several FlexRay networks
within ADTF
I #11034 Support of 8 CAN channels of the Eberspaecher device for all supported platforms
(especially linux 64)
I #11613 Support the Eberspaecher Device on 64 bit Linux, when official drivers are available
I #13234 [SDK Documentation] Create overview of Global Configuration Setting provided by Device
Toolbox
I #15900 [FCC] Enhance the FCC to handle default values
Reject reason: duplicates #17798
I #16047 Support for Flexray Ebersbaecher Device for Linux 64bit
I #17053 [UserManual] Improve Documentation of Direct Show Capture Device {HD - TicketID
12637KIFMF}
I #18159 Support for several FlexRay networks within ADTF
I #18307 [CAN Support Service] ICANSupportV2 is deprecated and will be removed in a further
version
I #18885 [FCC,LCC] Provide bus independent features on all ConfigCodecs (e.g. the feature
clear_after_transmit from the CCCExt)
I #19082 Remove the Cyclone II Flexray card from the Toolbox

I #21480 [common_video4linux] Provide the filter as example code (cf. common_directshowcapture)
I #22596 [CAN Config Codec Ext]: support of arrays of different initalized sizes using the content of
a CAN message (StopMessage has to be enhanced to SignalCount)
Reject reason: user defined protocols will not be provided by Device TB
I #25578 [CAN Config Codec Ext]: Calculate Offset and Factor before Type Conversion {HD -
TicketID 16763KEIKM}, {HD - TicketID 22816LJDQE} Product Ticket
I #25866 [FCC, Base Codec]: Provide the element properties corrective_factor and corrective_offset
in FCC {HD - TicketID 21775LKDJL}
I #26224 [Eberspaecher Flexray Device]: Eberspaecher FlexRay Devices are deprecated
I #26831 [Direct Show Capture Device], [cBaseIODeviceFilter]: Support of virtual camera devices
Reject reason: Do it yourself (the source is provided within the installation)
I #27133 Add information to all Vector Device Filter Documentation that only devices could be used
which are supported by XL Driver Library - {HD - TicketID 23589LIHGI}
I #28083 [CCCExt]: Ignore irrelevant Messages to increase performance
Bugfixes
I #12881 The MediaDescription-Infos were not correct updated from CanConfigCodecExt
I #15134 The Timeout Trigger Value in the CCCExt Codec is set to Zero during Filter::Stop {HD -
TicketID 11013KJKIH}
Reject reason: Base Codec implementation solved problem
I #15820 Checkboxes of combo boxes in trace list views are missing under Linux (Ubuntu)
I #23486 [CAN Support Service]: LoadCANDatabases does not work correctely when only global
settings are used
I #26018 [SCFE for CCCExt]: ADTF-Crash after using "Add struct from DDL" {HD - TicketID
22024LJLHH}
I #26028 [SCFE for CAN / LIN / FLEXRAY]: Add Database only supports .dbc (CAN) / .ldf (LIN) /
.xml (FLEXRAY) file format {HD - TicketID 22025LJLHG}

I #26331 [signal_config_editor_lib]: The configuration checker doesn’t resolve structs with indexed
signal names {HD - TicketID 17789KDJII}
I #26584 [FlexRay Support Service ],[FCC Parser]: FCC Parser and FlexRay Coder have Problems
with PDUs of Byteorder Motorola
I #27662 [CAN Support Service] Crash without error message when loading DBC file
A.6 Version 2.5.1
Bugfixes
I #26907 [CAN Media Coder]: The Enum Values of tCANSignalValue::eTypeTag have changed
between 2.4.0 and 2.5.0
A.7 Version 2.5.0
Changes
I #5701 CCCext: Support of signals with IEEEFloat or IEEEDouble format
I #9707 CCC: Take the sign signal from another messages.
Reject reason: Usecase makes no sense because of inconsistence
I #15899 [CCCExt] Enhance the CCCExt to handle default values
I #17722 Check and improve all tooltips on all Properties of the delivered Toolbox Filters
I #20932 Create possibility to get CAN information form ARXML instead of DBC (same for FLEXRAY
and LIN) - {HD - TicketID 15396KFLDM}
Reject reason: fullfilled by #24574

I #21043 [CAN Support Service]: Create possibility to get CAN information from FIBEX instead of
DBC
Reject reason: fullfilled by #24574
I #24300 [µEye Capture Device, Blue Fox Capture Device, PeakCan, VectorCan]: Devices should
support the latest driver and api version - {HD - TicketID 19619KBMOB}
I #24323 [FCC] improve documentation regarding FCC/FIBEX and PDU triggering - {HD - TicketID
19268KBQFH}
I #24574 [Parser]: The CAN/Fibex parser must be exchangeable for different file formats
I #24746 Improve the documentation of the FlexRay-Coder {HD - TicketID 19850KBKMO}
I #25295 [FlexCard Device] Mark the Filter as not supported
I #25071 [FlexCard Device]: provide option to measure delay in device {HD - TicketID 20683LLDHO}.
Reject reason: No possibility to measure in hardware and drivers.
Bugfixes
I #12649 CCCExt: Timestamps of incoming MediaSamples get distorted {HD - TicketID 9938SJPE}
(no longer reproducable)
I #24374 [CAN Config Codec Ext, FlexRay Config Codec, LIN Config Codec ]: trigger defined in
depends on ADTFTime, not StreamTime
I #25059 [FCC]: Signal cannot be found in FIBEX file {HD - TicketID 20325LLGKG}; see also #23081
I #25203 [adtfcomm]: Initializing a configuration using FlexRay Config Codec may lead to heap
corruption
I #25348 [CAN Signal Config Filter Editor ]: DBC file paths from globals are lost
A.8 Version 2.4.0

Changes
I #19679 [Flexray Signal Provider]: Evaluation of the PDU Update Bit (Clearance Monitoring Bit)
I #21824 Build the toolbox against ADTF 2.10 on the new/changed platforms and OS (Windows 7
64 Bit [win64_vc100], Windows 7 32 Bit [win32_vc90], Ubuntu 12.04 64 Bit [linux64])
I #22125 [Vector CAN XL Device,Peak CAN Device]: Remove deprecated Devices cVectorCANXL-
LegacyDevice and cPeakCanLegacyDevice
Bugfixes
I #14292 CANSignalProvider: Crash while starting and stoping several times
I #16004 CAN-ASC Dat-Importer does not work because of LANG-Variable and RegExResolver-Bug
{HD - TicketID 11947KJBOG}
I #18622 CCCExt: ChannelMask for dbc node in config.xml does not work properly - {HD - TicketID
14682KGHHP}
I #19715 cDom: Unable to load FIBEX file (no valid xml tag)
I #20518 [FIBEX Database]: Memory leak when playing configuration with different FIBEX files
I #20874 [CAN Support Service]: decoding multiplexed signals misses if signals of a message have
different byteorder - {HD - TicketID 15396KFLDM}
I #21965 [CAN Legacy Filter Out]: Wrong conversion of CAN-Message-ID using the CAN Legacy
Filter Out with extended CAN-Messages ⇒ unfortunately this corrupts the extended message ids
which will lead to wrong CAN-IDs
I #22157 [FlexrayConfigCodec]: signal is updated, but OutputPin buffer will not be sent ⇒ Problem
with unknown FlexRay-Frames within a FlexRayFrameVector (full vector was ignored by FCC)
A.9 Version 2.3.2
Bugfixes
I #20536 MDF-Exporter: change the content of si_tx_path (for Export of CAN + Flexray + Exter-
nal_Stream_Sync)

I #21029 [FlexRay Support Service]: ADTF crashes constantly when initializing config with certain
FIBEX files three times
A.10 Version 2.3.1
Changes
I #19635 [CAN_Support_Service]: disable merging of empty dbc-filenames into the MergedCan-

Database
I #19925 MDF-Exporter Enhancements: Save DAT-File-Description into the mf4
Bugfixes
I #18738 FCC does not encode/decode signals which computation information are not fully defined
in Fibex (e.g. no TEXTTABLE entries for all possible values)
I #18747 Fibex DB GetFrameInfo() may return the code "ERR_NOERROR" also when frameinfo are
not available
I #19300 CCCExt: wrong behaviour with sign_signal when Encoding (output buffer)
I #19631 CCCExt: Samples are transmitted while A D T F is paused
I #19636 [FlexRayConfigCodec]: Message "Wrong database loaded" is unclear
I #19703 [Flexray Trace View]: To few or to much ECUs displayed when using Flexray_ECU_Filter -
Bug in Fibex file
I #19766 [FibexParser]: Error when parsing FIBEX files with developer messages
I #19929 [FlexRayConfigCodec]: A D T F deadlock when starting Configuration with FCC under

WinXP
I #20185 [CCCExt]: Wrong generation of a mediasample on outputbuffer if start-/stop message is

set and received BUT the channel doesn’t match

A.11 Version 2.3.0
Changes
I #15980 All tCanMessage Filters are deprecated use tCANData instead . . . see documentation
I #16048 Extend the MDF-Export/Import
. #16847 Extend the MDF-Export for Flexray
. #17004 Extend the MDF-Export: Append to existing MDF-file
. #17007 Extend the MDF-Export: Introducing a ExternalStreamSync datexporter-source

module
. #17008 Extend the MDF-Export: Introducing MDF4 ExternalStreamSync datexporter-sink

module
I #16869 FlexRay_Support_Service: Introducing SetFIBEXDatabase in IFlexRaySupport
I #18100 cansupport service supports the new ICANSupportExtended interface to load DBC Files -
ICANSupportV2 is deprecated and will be removed in a further version
Bugfixes
I #15568 CAN Trace Tree View does not correctly decode incomming messages with a smaller DLC
than defined in the DBC
I #15838 missing media samples when using more than one PeakCAN device (basic) {HD - TicketID
11489KJGFI} - Device is deprecated, use new Peak Device Receiver
I #16019 CCCExt sets wrong timestamps if no signal of timestamp message is element of buffer
I #16358 Eberspächer Device does not support 100KB Baudrate for CAN
I #16574 FCC/FlexrayCoder: Correctly set HW timestamps of PDUs during encoding
I #16782 SignalConfigFilterEditor for CCCExt: value 0 is not accepted for CONSTANT macro
I #16783 CCCExt: Value type Int32 and Int16 are not supported
I #17306 FCC: Correctly Initialize RawValue before encoding data with coder

I #18095 Timing Problems - different behaviour in 2.1.3 and 2.2.0 {HD - TicketID 13120KHLIL}
I #18102 Mediasubtype is not shown on hoovering over the pin in the ConfigEditor when the pin
type is set to MEDIA_SUBTYPE_CAN_DATA {HD - TicketID 13042KHMFL}
I #18171 CCCExt: Data areas of a message which are not definded in a dbc, will not be initialized to
zero when generating a CAN message
I #18219 LCC: Data areas of a message which are not defined in a .ldf, will not be initialized to zero
when generating a LIN message
I #18267 FCC: Data areas of a message which are not defined in a fibex, will not be initialized to
zero when generating a message
A.12 Version 2.2.1
Bugfixes
I #17626 Memory Leak with HD Player and loaded CAN-Services {HD - TicketID 12938KICPE} -
Caused by build against ADTF 2.8.0
A.13 Version 2.2.0
Changes
I #5944 Connection establishment and termination of the TCP-Filter on request
I #10586 Support for Flexray Eberspächer Device for Windows 64bit
I #10736 Include TimingSpots in all Devices
I #12313 The CCC should not load files from CCCExt
I #12880 Support FIBEX-File-Standard Version ’3.1.0’
I #13151 Import of CANlog traces (CAN/LIN/MOST/FlexRay ?) has to support decimal values

I #13254 µEye-Device should be able to work with 10-Bit/channel colordepth
I #13309 Ethernet UDP: Add a warning message for buffer overflows
I #13704 Mark the Ethernet Devices as not supported any more!
I #13886 µEye-Device should support the latest driver and api version
I #13974 The Peakcan device should support additonal baudrates {HD - TicketID 10938KKAPE}
I #15233 Move the directshowcapture and video4linux device from adtf_core to the device toolbox
I #11430 CAN-List View: Support filtering on message IDs
I #13322 FlexrayCoder/FCC: Provide possibility to retrieve raw values
I #13516 FlexrayCoder/FCC: Provide possibility to change factor and offset in fcc or to get the error
codes of a signal
I #13670 CAN Support Service should inform about loaded dbc files
I #13797 Signal Config Editor does not show any self-made macros in the macro-list
Bugfixes
I #10076 A D T F hangs when PCAN PCI is not connected to bus {HD - TicketID 8402RNNH}
I #11250 Flexray Devices cannot send a PDU separately that is defined for channel A and B
I #12314 CCCExt: Wrong corrective_factor while loading CCC-Files
I #12881 The MediaDescription-Infos were not correct updated from CanConfigCodecExt
I #13237 SignalConfig: Documentation of trigger
I #13252 CCCExt crashes while playing configuration {HD - TicketID 10400KKFNJ}
I #13790 FCC & Scope Display {HD - TicketID 10783KKCIO}
I #13889 FCC doesn’t send any timestamp
I #14047 The time stamp of all media samples of a DAT File is 0
I #15134 The Timeout Trigger Value in the CCCExt Codec is set to Zero during Filter::Stop {HD -
TicketID 11013KJKIH}
I #15372 New Peak Devices: Cannot initialize on Linux.

I #15996 Flexray: Media Sample Serialization of PDU samples encodes wrong size.
A.14 Version 2.1.3
Changes
I #8721 Create an MDF File exporter / importer
Bugfixes
I #13300 Flexray Config Codec should support "old" (Flexray Toolbox 1.3) XML-Files configuration
files.
A.15 Version 2.1.2
Bugfixes
I #12675 Documentation: Commandline DatExporter for Export CAN → ASCII {HD - TicketID
9881SKJQ}
A.16 Version 2.1.1
Changes
I #12205 OptoLyzer G2 Fimware 1.6.0 adaptations

A.17 Version 2.1.0
Changes
I #12204 OptoLyzer G2 Busload Stress Period shall be inputable
I #11536 New MOST MediaType
I #11535 New FlexRay MediaType
I #11233 New spy mode for Vector LIN Device
I #11142 FlexRay Config Codec: New Signal Config Editor
I #11132 64-Bit support for Vector devices
I #11113 LIN Config Codec: New Signal Config Editor
I #11107 Signal Config: extend Gui for MIN/MAX handling
I #11062 Header import for all Signal Config Editors
I #11040 The contents of the FlexRay Toolbox are now integrated into the DeviceToolbox
I #11085 Signal Config Filter Editor for CCCExt: "Create Pins from Configuration" should be called
after the Filter Editor is closed
I #11008 CCCExt: IF_RECEIVED for multiplex frames
I #10850 New LIN Support Service
I #10780 Add an Option to ASC Can Importer to process the file sequentially
I #10001 CAN Wakeup Signal {HD - TicketID 8216RPKE}
I #9919 CCC: Add ’start_message_valid’-Attribute for Trigger (like ’stop_message_valid’)
I #9853 A LIN Trace View has been added
I #9707 CCC: algebraic sign of a signal from different message
I #9587 CCCExt shall set a MediaDescription to its Pin
I #9447 Added example for triggering the Harddisk Recorder with a CAN Message.

I #9446 Add a Random CAN data generator example
I #8903 CCC: Send several Multiplexed Messages (same ID, different Multiplex) with one Buffer {HD
- TicketID 7666QKJJ}
I #8896 Make the DeviceToolbox available for Windows 7 with Visual Studio 2010
I #8811 FCC: Support for unit conversion
I #8754 FCC: Support for timestamp macros
I #8596 DOC: The Linux Flexray Device is NOT realtime capable.
I #8533 CAN Trace View Ext: Improve the handling of multiplex signals
I #8693 CAN Trace View Ext: An additional list view has been added to see the time span of signals
I #8692 CAN Trace View Ext: Add a combo box to filter the view for root nodes and channels
I #7404 CCC: Decoded Data shall not be dismissed after transmit
I #6444 CCC: Implement a new macro to read a signal’s raw value ($RAWVALUE$)
I #6427 CCCext: Hardware-Timestamp Macro
I #5776 TZM Flexray Device available for Linux
Bugfixes
I #11830 New Vector CAN Device fails to init CANCardXLe
I #11364 LIN Config Codec: Missing Media Description {HD - TicketID 9138SRHE}
I #11095 CAN Signal Provider decodes extended signals wrong {HD - TicketID 8956RINI}
I #11007 CCCExt: tBool throws LOG_DUMP
I #11006 CCCExt: Multithreading crash
I #10810 CAN Signal Provider does not deliver correct raw values and multiplexed signal values
{HD - TicketID 8829RJPC}
I #10806 CAN Signal Provider does not deliver signals after second start of configuration
I #10381 PEAK Device does not define property ’devicename’ (Linux only) {HD - TicketID 8593RMFP}

I #10357 CAN Trace View Ext: No signal values visibile for extended CAN messages {HD - TicketID
8497RNEL}
I #9602 FlexRay Devices fails to send data if flexray frame is not completly defined by FIBEX {HD -
TicketID 8090RRAS}
I #9575 FIBEX file with missing DENOMINATOR tag fails to load {HD - TicketID 8073RRCN}
I #9574 Flexray Trace View: Incorrect display of data when multi channel mode is active {HD -
TicketID 8073RRCN}
I #7442 FlexRay Device does not initialize a restart
A.18 Version 2.0.0
Changes
I #5916 CAN Trace View Extended: Optimized new CAN Trace View, can show ErrorFrames and
bus load
I #8764 Added Empty CAN Device to examples
I #8847 Added SDK documentation
I #8866 CCC: Add documention and examples for sending Multiplexed Messages
I #8636 tCANData: Extend the CAN message struct
I #8924 CAN Trace View Ex: GUI update performance enhanced
I #6289 CCC: Support for channel masks in buffer
I #8913 Improved redesign of Signal Configurator for CCC
I #8313 Devices check if correct driver version is used
I #8389 New CMake configuration for Device Toolbox
I #8653 CAN Devices are separated into receiver and sender filter
I #8977 Added new CAN Media Type
I #8628 Added silent installer

I #9510 Watchdog did not work with Device Toolbox
Bugfixes
I #8235 SignalConfig: Default buffer name is not written to xml
I #8285 SignalConfig: Default can-channel in input tag is not written to config file
I #8484 uEye Camera Device does not work as debug version
I #8557 CCCext: The Info field of the incoming MediaSample is not copied to the sent MediaSample
I #9019 CAN ASC Importer fails to import CAN messages with message flags
A.19 Version 1.2.0
Changes
I #6362 Documentation added for MOST file import/export service
I #7212 New Examples: Vector CAN device and SYSTEC CAN device
I #7406 BlueFox/Linux: Support for driver version 1.11.27.205
I #3358 New Example: IXXAT-CAN-device for Linux/Windows
I #3951 SMSC OptoLyzer G2 device implemented
I #6826 MOST Support Service: Implementation of MOST Media Sample
I #7078 PEAK Device: Implementation changed to PCAN-Basic API
I #6702 MOST 150 IMG format dat-importer service implemented
I #6703 MOST 25/150 IMG format dat-exporter service implemented
I #7307 MOST MediaSample extended for new MOST150 lock status events
I #7308 MOST MediaSample extended for MOST 150 control messsages
I #7448 OptoLyzer 3150: supports busload stress feature

I #8146 OptoLyzer G2: Adapt Stress Function for firmware 1.5.4
I #8257 OptoLyzer G2: Messages for active node are received by INIC now
I #8376 OptoLyzer 3150: Adapt busload stress feature to firmware 1.5.4
I #8687 OptoLyzer 3150: Event Allocate Changed
I #8688 OptoLyzer 3150: Support for additional registers buffer precount, busload burst count,
busload retrycount
A.20 Version 1.1.4
Bugfixes
I #8544 Version information of external_file_support_service incorrect
I #8547 OptoLyzer G1: Invalid response to system control message
A.21 Version 1.1.3
Bugfixes
I #8155 OptoLyzer G2 Device: Incorrect node- / groupadress at startup
I #8159 OptoLyzer G2 Device: OL3025oV1 WakeUp command fails
I #8166 MOST Devices : Lock/Light event not created at startup
I #8214 OptoLyzer G1: Sporadic crash when system control messages are received
I #8354 VectorMOSTDevice: Invalid async. message may lead to crash

A.22 Version 1.1.2
Bugfixes
I #7338 OptoLyzer G2: Switching timing mode between slave <-> spy caused shutdown
I #8293 OptoLyzer G2: Incorrect size of received MOST150 Async. High Msg
A.23 Version 1.1.1
Changes
I #6897 Device peakcan linked is now with driver dll 1.55. Compatible with new driver 3.x
I #6871 Support of MOST OptoLyzer 3025o V2
I #6581 OptoLyzer G2 MOST 150 Control messages for synchonous channel allocation / deallocation
I #5771 OptoLyzer G2 Stress Function support
I #4911 VectorMOST and OptoLyzer G1 Devices Stress Function support
Bugfixes
I #7107 OptoLyzer G2 failes to change timing mode
I #6931 VectorCANDeciceXL: CAN channel ids are not used as configured in Vector Hardware
Confg
I #6921 SignalConfig failed to start due to missing init.xml file
I #6816 OptoLyzer G2 (OL3150o) handling of acknowledge codes fixed
I #6790 OptoLyzer G2 (OL3150o) did not reveive asynchronous messages as spy
I #6788 OptoLyzer G2 generated control message with length 0

I #6733 Only new hardware version of OptoLyzer G2 3150o will be supported
I #6727 Stress feature rx buffer control works now with OptoLyzer 3025 V1
I #6562 VectorCANXL Device could not send CAN message with id = 0
I #6529 VectorCANXL Device failed to init legacy configuration
I #5999 CAN Devices: Unsupported property ’syncenable’ removed
A.24 Version 1.1.0
Changes
I #5919 CCC: Additional Factor (f2) and Offset (o2) → f 2 · (f 1 · signal + o1) + o2
I #5917 CAN Signal Provider shall use the new CAN Support Service
I #5689 Enhance the documentation for the usage of multiplexed messages within the CanConfig-
Codec (CCC)
I #5199 EthernetDeviceUDP shall check the ReceiveBuffer size
I #4901 CCC: Using the IMacroRecorder interface resolving the DBC filepath if using macros
I #4651 VectorLIN Device: LDF file Filter Property shall be moved to the GlobalSettings
I #4444 Add a license check to the Device Toolbox
I #4004 Using the hardware time stamp as additional information. This will be put to the MediaSam-
pleInfo.
I #3947 A LinConfigCodec shall be implemented comparable to the CanConfigCodec.
Bugfixes
I #6232 VectorCANDevice: Combination of channelX_hwtype and usevirtual = true has been

corrected
I #6225 Optolyzer G1 reporting of node position corrected

I #6158 VectorLINDevice : Legacy configuration as master not possible
I #6144 VectorMOSTDevices generates wrong timing mode status events
I #5665 An external changed DBC file will not be reloaded automatically
I #5660 CCC does not show received/expected size on size mismatch
I #5639 uEye Camera: Device should support all camera framerates
I #5279 The SignalView does not work with more than one CAN
I #5206 EthernetDeviceUDP does start even a not valid IP address is input.
I #5068 Bluescreen when using wrong Vector Can Device Filter
I #4939 Peak CAN Device Hardware timestamps are not synchronized to the ADTF time.
I #4360 CAN Provider takes the settings only of the global settings and ignores the settings of the
system.xml
I #4390 CCC: Environmental variables will not be resolved.
A.25 Version 1.0.1
Changes
I Information: Due the compile with A D T F 2.2.2 the provided Device Toolbox Filters are more
perfomant.
I #4503 Documentation of provided templates.
I #4370 DeviceToolbox documentation (CanConfigCodec Example) for struct arrays.
Bugfixes
I #4598 CAN Signal Provider holds a reference to ADTF Kernel too long.

A.26 Known Problems
For known problems and open issues please have a look at known-problems.pdf inside directory
<INSTALL_DIR>/doc.

List of Figures
2.1. Context menu of the CCC Ext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

2.2. Signal Configurator of CCC Ext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16
2.3. File menu of the Signal Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.4. Mode menu of the Signal Configurator . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
2.5. Signal Configurator—Array of Structs . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
2.6. Signal Configurator—Import Structs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21
3.1. Decoding CAN Messages with CCCExt . . . . . . . . . . . . . . . . . . . . . . . . . . . 41

3.2. Encoding media samples with CCCExt . . . . . . . . . . . . . . . . . . . . . . . . . . . 42
3.3. Signal Configurator—Set database channel . . . . . . . . . . . . . . . . . . . . . . . . 49
3.4. CAN Trace Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54
3.5. CAN Trace List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
3.6. Settings for the CAN Trace View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 55
4.1. LIN Trace Tree View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63

4.2. LIN Trace List View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64
4.3. Settings for the LIN Trace View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65
5.1. Make sure that each ProjectID is unique, if you want to use more then one FIBEX-File! . 67
5.2. Hardware Configuration of several FlexRay Networks . . . . . . . . . . . . . . . . . . . 68
5.3. The ProjectID-Information is stored automatically, if you use Device Toolbox-Version >=
2.6.0. Configuration-Files, that have been generated with older Device Toolbox-Versions
must be edited by the user, if you want to make sure that the Signal-Information is taken
from a specific FIBEX-File! . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 74

List of Tables
1.1. Description of the templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
2.1. Property Description of the InputPin/OuputPin . . . . . . . . . . . . . . . . . . . . . . . 23

2.2. Property Description of the Struct . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24
2.3. Property Description of the Element . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25
2.4. Property Description of the Triggers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27
2.5. Property Description of the Description of built in Macros . . . . . . . . . . . . . . . . . 28
3.1. Platform support of the Vector CAN XL Receiver . . . . . . . . . . . . . . . . . . . . . . 30

3.2. Pins of the Vector CAN XL Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.3. Properties of the Vector CAN XL Receiver . . . . . . . . . . . . . . . . . . . . . . . . . 31
3.4. Platform support of the Vector CAN XL Sender . . . . . . . . . . . . . . . . . . . . . . . 32
3.5. Pins of the Vector CAN XL Sender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32
3.6. Properties of the Vector CAN XL Sender . . . . . . . . . . . . . . . . . . . . . . . . . . 33
3.7. Platform support of the Peak CAN Receiver . . . . . . . . . . . . . . . . . . . . . . . . 34
3.8. Pins of the Peak CAN Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34
3.9. Properties of the Peak CAN Receiver . . . . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.10.Platform support of the Peak CAN Sender . . . . . . . . . . . . . . . . . . . . . . . . . 36
3.11.Pins of the Peak CAN Sender . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.12.Properties of the Peak CAN Sender . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37
3.13.Pins of the CAN Legacy Filter In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38
3.14.Pins of the CAN Legacy Filter Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39
3.15.Platform support of the Can Config Codec Ext . . . . . . . . . . . . . . . . . . . . . . . 42
3.16.Pins of the Can Config Codec Ext . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 43
3.17.Properties of the Can Config Codec Ext . . . . . . . . . . . . . . . . . . . . . . . . . . 45
3.19.Platform support of the Can Config Codec . . . . . . . . . . . . . . . . . . . . . . . . . 51
3.20.Pins of the Can Config Codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
3.21.Properties of the Can Config Codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52
4.1. Platform support of the Vector LIN Device . . . . . . . . . . . . . . . . . . . . . . . . . 56

4.2. Pins of the Vector LIN Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.3. Properties of the Vector LIN Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 57
4.4. Pins of the LIN Config Codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 59
4.5. Properties of the LIN Config Codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60
5.1. General Configuration Settings for FlexRay . . . . . . . . . . . . . . . . . . . . . . . . . 66

5.2. Support of several FlexRay Networks . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

Chapter List of Tables
5.3. Platform support of the VectorFlexrayDevice . . . . . . . . . . . . . . . . . . . . . . . . 69

5.4. Pins of the VectorFlexrayDevice . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70
5.5. Properties of the VectorFlexrayDevice . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
5.6. Pins of the FlexRay ECU Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
5.7. Properties of the FlexRay ECU Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . 73
5.8. Properties of the FlexRay Config Codec . . . . . . . . . . . . . . . . . . . . . . . . . . 76
5.9. Pins of the FlexRay Config Codec . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77
5.10.FlexRay Specific Differences of Trigger-Properties . . . . . . . . . . . . . . . . . . . . . 77
5.11.FlexRay Specific Differences of Element-Properties . . . . . . . . . . . . . . . . . . . . 78
6.1. Platform support of the Vector MOST Device . . . . . . . . . . . . . . . . . . . . . . . . 81

6.2. Pins of the Vector MOST Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82
6.3. Properties of the Vector MOST Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 83
6.4. Platform support of the OptoLyzer G1 MOST Device . . . . . . . . . . . . . . . . . . . . 84
6.5. Pins of the OptoLyzer G1 MOST Device . . . . . . . . . . . . . . . . . . . . . . . . . . 84
6.6. Properties of the OptoLyzer G1 MOST Device . . . . . . . . . . . . . . . . . . . . . . . 85
6.7. Platform support of the OptoLyzer G2 MOST Device . . . . . . . . . . . . . . . . . . . . 86
6.8. Pins of the OptoLyzer G2 MOST Device . . . . . . . . . . . . . . . . . . . . . . . . . . 86
6.9. Properties of the OptoLyzer G2 MOST Device . . . . . . . . . . . . . . . . . . . . . . . 87
7.1. Platform support of the Ethernet Device UDP . . . . . . . . . . . . . . . . . . . . . . . . 90

7.2. Pins of the Ethernet Device UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 90
7.3. Properties of the Ethernet Device UDP . . . . . . . . . . . . . . . . . . . . . . . . . . . 91
7.4. Platform support of the Ethernet Device TCP . . . . . . . . . . . . . . . . . . . . . . . . 92
7.5. Pins of the Ethernet Device TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 92
7.6. Properties of the Ethernet Device TCP . . . . . . . . . . . . . . . . . . . . . . . . . . . 93
8.1. Common Properties of Video Capture Device Filters . . . . . . . . . . . . . . . . . . . . 95

8.2. Platform support of the Blue Fox Capture Device . . . . . . . . . . . . . . . . . . . . . . 95
8.3. Pin of the Blue Fox Capture Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 96
8.4. Additional Property of the Blue Fox Capture Device . . . . . . . . . . . . . . . . . . . . 97
8.5. Platform support of the DirectShow Video Capture Device . . . . . . . . . . . . . . . . . 98
8.6. Pins of the DirectShow Video Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . 98
8.7. Properties of the DirectShow Video Device . . . . . . . . . . . . . . . . . . . . . . . . . 99
8.8. Platform support of the µEye Capture Device . . . . . . . . . . . . . . . . . . . . . . . . 99
8.9. Pin of the µEye Capture Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100
8.10.Additional Property of the µEye Capture Device . . . . . . . . . . . . . . . . . . . . . . 100
8.11.Platform support of the Linux Video Capture Device . . . . . . . . . . . . . . . . . . . . 101
8.12.Pins of the Linux Video Capture Device . . . . . . . . . . . . . . . . . . . . . . . . . . . 101
8.13.Properties of the Linux Video Capture Device . . . . . . . . . . . . . . . . . . . . . . . 102
9.1. Supported formats of the External File Support Service . . . . . . . . . . . . . . . . . . 106
10.1.Struct used for each Media Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113

Index
µEye Capture Device, 99 VN3300, 69

VN3600, 69
Blue Fox Capture Device, 95 VN7600, 69
Can Config Codec, 50

Can Config Codec Ext, 40
CAN Trace List View, 54
CAN Trace Tree View, 53
CAN Trace View Extended Service, 53
DBC file, 40, 50, 58

Direct Show Video Device, 98
Ethernet Device TCP, 91

Ethernet Device UDP, 89
Extended CAN message, 38, 39, 43, 52
FIBEX, 9, 11
FlexRay Config Codec, 74
FlexRay DAT Exporter, 79
FlexRay Signal Provider, 74
FlexRay Trace View, 73
LDF database, 56, 58, 64

LIN Config Codec, 58
LIN Trace List View, 63
LIN Trace Tree View, 62
LIN Trace View Service, 62
Linux Video Capture Device, 101
OptoLyzer G1 MOST Device, 84

OptoLyzer G2 MOST Device, 85
Peak CAN Receiver, 33

Peak CAN Sender, 36
Vector CAN XL Receiver, 30

Vector CAN XL Sendeer, 32
Vector LIN Device, 56
Vector MOST Device, 81

ADTF Devicetoolbox

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

ADTF Devicetoolbox

Uploaded by

Copyright:

Available Formats

Discover the Experience

Device Toolbox 2.7

Elektrobit Automotive GmbH

EB Assist ADTF Support

2. Config Codec—Signal Configurator 14

8.4. uEye Capture Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 99

9. Additional Service 103

10. FAQ 112

11. Abbreviations 114

A. Change Log 115

A.21.Version 1.1.3 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 133

List of Figures 138

List of Tables 139

The supported systems are:

I CAN bus system (see chapter 3 CAN)

I LIN bus system (see chapter 4 LIN)

I FlexRay bus system (see chapter 5 FlexRay)

I MOST bus system (see chapter 6 MOST)

I Ethernet (see chapter 7 Ethernet)

I Cameras (see chapter 8 Camera)

The system requirements are described in chapter 1.1 of the ADTFUserManual.

The toolbox has no additional system requirements.

Basic knowledge about A D T F and the FlexRay protocol is required.

Device Toolbox – EB Assist ADTF 9

It is recommended to install the toolbox to <ADTF_DIR>/addons. If a manual installation with another

The following line has to be inserted below the tag <manifests>:

Device Toolbox – EB Assist ADTF 10

DirectShow Three Configurations (Live, Playback, Recording) with the corresponding

Table 1.1.: Description of the templates

1.5 Remarks regarding system configurations

1.6 Implementation specific restrictions

I Multiplexed signals or sub-frames are not supported

Device Toolbox – EB Assist ADTF 11

I PDU-TRIGGERING elements are ignored (FRAME and FRAME-TRIGGERING elements are

1.7 Driver version check

1.8 Special text formats and symbols

Windows, Dialogs and other elements of the user interface

Device Toolbox – EB Assist ADTF 12

File names, directory names, etc.

Cross reference section 1.8 Special text formats and symbols

Warnings indicate potential error sources.

This note symbol indicates useful information.

Tips provide additional information.

Device Toolbox – EB Assist ADTF 13

2 Config Codec—Signal Configurator

2.1 General usage

Device Toolbox – EB Assist ADTF 14

Figure 2.1.: Context menu of the CCC Ext

Device Toolbox – EB Assist ADTF 15

Figure 2.2.: Signal Configurator of CCC Ext

2.2 File menu

Device Toolbox – EB Assist ADTF 16

Figure 2.3.: File menu of the Signal Configurator

The following menu points are available:

2.3 Mode menu

Figure 2.4.: Mode menu of the Signal Configurator

The following menu points are available:

Device Toolbox – EB Assist ADTF 17

activated the text “Link Mode is active!” is shown in the statusbar.

2.4 Header menu

Device Toolbox – EB Assist ADTF 18

Figure 2.5.: Signal Configurator—Array of Structs

2.5 Databases Tree