Page organisation in this revision
- Page type
- ECU hub
- Subject
- ECUs
- Parent
- Bosch
- Applies to
- No ECU-specific applicability
- Tool groups
- Not recorded in this older revision
- Manufacturers
- Not recorded in this older revision
Changes from revision 1 to revision 4
Removed text is struck through; added text is highlighted.
Family scope
This MED17 reference currently covers early Volkswagen Group MED17.5 examples. Keep the complete ECU designation and hardware/software identity with every application record. The examples below do not establish the specifications, sensor layout or programming method of every MED17 ECU.
Documented MED17.5 applications
ExampleWhat the OEM document establishesAudi A3 transverse chain-driven 1.8-litre TFSIAudi SSP 384, pages 2 and 46-49, describes the engine and its Bosch MED17.5 management. Other installations can require different specifications.Volkswagen chain-driven 2.0-litre TSI, CCTA and CBFAVW SSP 824803, pages 1-2, identifies MED17.5. Its introduction describes electronic throttle, direct injection, cylinder-selective knock control and demand-controlled fuel delivery.
Fuel-system distinction: the SSP 384 example
In the early 1.8 TFSI installation described by SSP 384, pages 38-40, low-pressure pre-supply is map controlled and the low-pressure fuel sensor used in earlier arrangements is omitted. High-pressure feedback uses G247, with N276 controlling fuel delivery at the high-pressure pump. The omission of the low-pressure sensor is intentional in this documented arrangement; do not diagnose a missing G410 solely by comparison with an earlier application. Confirm the actual vehicle's fuel-system equipment before using this example.
Lambda and hardware are application specific
SSP 384, page 48, describes an early arrangement using a switching oxygen sensor between the catalysts and model-based functions in place of the earlier continuously measuring pre-catalyst sensor. Retain that engine context when selecting log channels. The document also states that substitute behaviour depends on the fault and ECU software, page 49.
VW SSP 840293, page 50, describes an Infineon TriCore 1766 processor for its MED17.5 example. This identifies the documented hardware only; it is not a processor or memory specification for the whole MED17 family.
Working record and related families
Keep the original ECU read, diagnostic identity, engine and emissions version, sensor equipment, matching definition, source and tool version together. Check which channels are measured, calculated or unavailable. Use documented support for the exact unit before choosing a read/write or recovery method. Compare the MED9.1 example and Motronic overview without transferring their hardware or calibration assumptions.
Owner-catalogue model labelsThe active Bosch / MED17 catalogue browse showed these model labels on 10 November 2026. They are copied as identity labels for navigation. A label does not establish vehicle fitment, processor, shared hardware or programming compatibility.MED17MED17.0MED17.0.1MED17.0.7MED17.1MED17.1 TC1796MED17.1.1MED17.1.1 M&SMED17.1.1 TC1796MED17.1.1 TC1797MED17.1.1 TC1797 (2021)MED17.1.10MED17.1.11MED17.1.12MED17.1.1MSMED17.1.21MED17.1.27MED17.1.27 (2021)MED17.1.28MED17.1.6MED17.1.61MED17.1.62MED17.1.62.g2MED17.1.62MSMED17.1.6HYMED17.1.9MED17.2MED17.2 TC1766MED17.2 TC1796MED17.2.2MED17.2.3MED17.2.6MED17.2.9MED17.27MED17.3.0MED17.3.1MED17.3.3MED17.3.4MED17.3.5MED17.3.5 M&SMED17.3.5.g2MED17.3.8MED17.4MED17.4 TC1766MED17.4 TC1767MED17.4 TC1796MED17.4.2MED17.4.2 TC1767MED17.4.2 TC1797MED17.4.4MED17.5MED17.5.1MED17.5.2MED17.5.20MED17.5.21MED17.5.24MED17.5.25MED17.5.26MED17.5.27MED17.5.4MED17.5.5MED17.5.5 TC1766MED17.5.5 TC1767MED17.5.5_HW2MED17.5.6MED17.6.1MED17.6.9MED17.7MED17.7.1MED17.7.2MED17.7.3MED17.7.3.1MED17.7.5MED17.7.7MED17.7.8MED17.8.1MED17.8.10MED17.8.10 HW2MED17.8.10 TC1767MED17.8.10.1MED17.8.10.1 TC1782FMED17.8.2MED17.8.21MED17.8.3MED17.8.3.2MED17.8.31MED17.8.32MED17.8.32 (2021)MED17.8.33MED17.8.34MED17.8.XMED17.9.3MED17.9.3 (2021)MED17.9.3.g2MED17.9.30MED17.9.32MED17.9.63MED17.9.66MED17.9.7MED17.9.8MED17.9.9MED17.9.9 (2021)MED17.9.XMED17.X CANMED17.x.xMED17xxSee the TriCore Motronic 17 processor table for only the exact ECU/processor pairs identified by EVC.Sources
Audi SSP 384: Audi chain-driven 1.8 litre 4V TFSI engine, pages 2, 38-40 and 46-49.Volkswagen SSP 824803: The Volkswagen 2.0 Liter Chain-Driven TSI Engine, May 2008, pages 1-2.Volkswagen SSP 840293: Engine Management Systems, February 2010, pages 47-50.
These are OEM design/function training documents hosted on independent mirrors, accessed 2026-11-10. They are not current repair manuals; use the relevant service information for testing and repair. No connector pin assignment is established here.
Page organisation changed
Rendered revisions
Open each version to inspect formatting, tables and photographs.
Revision 1: Bosch MED17
Family scope
This MED17 reference currently covers early Volkswagen Group MED17.5 examples. Keep the complete ECU designation and hardware/software identity with every application record. The examples below do not establish the specifications, sensor layout or programming method of every MED17 ECU.
Documented MED17.5 applications
| Example | What the OEM document establishes |
|---|
| Audi A3 transverse chain-driven 1.8-litre TFSI | Audi SSP 384, pages 2 and 46-49, describes the engine and its Bosch MED17.5 management. Other installations can require different specifications. |
| Volkswagen chain-driven 2.0-litre TSI, CCTA and CBFA | VW SSP 824803, pages 1-2, identifies MED17.5. Its introduction describes electronic throttle, direct injection, cylinder-selective knock control and demand-controlled fuel delivery. |
Fuel-system distinction: the SSP 384 example
In the early 1.8 TFSI installation described by SSP 384, pages 38-40, low-pressure pre-supply is map controlled and the low-pressure fuel sensor used in earlier arrangements is omitted. High-pressure feedback uses G247, with N276 controlling fuel delivery at the high-pressure pump. The omission of the low-pressure sensor is intentional in this documented arrangement; do not diagnose a missing G410 solely by comparison with an earlier application. Confirm the actual vehicle's fuel-system equipment before using this example.
Lambda and hardware are application specific
SSP 384, page 48, describes an early arrangement using a switching oxygen sensor between the catalysts and model-based functions in place of the earlier continuously measuring pre-catalyst sensor. Retain that engine context when selecting log channels. The document also states that substitute behaviour depends on the fault and ECU software, page 49.
VW SSP 840293, page 50, describes an Infineon TriCore 1766 processor for its MED17.5 example. This identifies the documented hardware only; it is not a processor or memory specification for the whole MED17 family.
Working record and related families
Keep the original ECU read, diagnostic identity, engine and emissions version, sensor equipment, matching definition, source and tool version together. Check which channels are measured, calculated or unavailable. Use documented support for the exact unit before choosing a read/write or recovery method. Compare the MED9.1 example and Motronic overview without transferring their hardware or calibration assumptions.
Sources
These are OEM design/function training documents hosted on independent mirrors, accessed 2026-11-10. They are not current repair manuals; use the relevant service information for testing and repair. No connector pin assignment is established here.
Revision 4: Bosch MED17
Family scope
This MED17 reference currently covers early Volkswagen Group MED17.5 examples. Keep the complete ECU designation and hardware/software identity with every application record. The examples below do not establish the specifications, sensor layout or programming method of every MED17 ECU.
Documented MED17.5 applications
| Example | What the OEM document establishes |
|---|
| Audi A3 transverse chain-driven 1.8-litre TFSI | Audi SSP 384, pages 2 and 46-49, describes the engine and its Bosch MED17.5 management. Other installations can require different specifications. |
| Volkswagen chain-driven 2.0-litre TSI, CCTA and CBFA | VW SSP 824803, pages 1-2, identifies MED17.5. Its introduction describes electronic throttle, direct injection, cylinder-selective knock control and demand-controlled fuel delivery. |
Fuel-system distinction: the SSP 384 example
In the early 1.8 TFSI installation described by SSP 384, pages 38-40, low-pressure pre-supply is map controlled and the low-pressure fuel sensor used in earlier arrangements is omitted. High-pressure feedback uses G247, with N276 controlling fuel delivery at the high-pressure pump. The omission of the low-pressure sensor is intentional in this documented arrangement; do not diagnose a missing G410 solely by comparison with an earlier application. Confirm the actual vehicle's fuel-system equipment before using this example.
Lambda and hardware are application specific
SSP 384, page 48, describes an early arrangement using a switching oxygen sensor between the catalysts and model-based functions in place of the earlier continuously measuring pre-catalyst sensor. Retain that engine context when selecting log channels. The document also states that substitute behaviour depends on the fault and ECU software, page 49.
VW SSP 840293, page 50, describes an Infineon TriCore 1766 processor for its MED17.5 example. This identifies the documented hardware only; it is not a processor or memory specification for the whole MED17 family.
Working record and related families
Keep the original ECU read, diagnostic identity, engine and emissions version, sensor equipment, matching definition, source and tool version together. Check which channels are measured, calculated or unavailable. Use documented support for the exact unit before choosing a read/write or recovery method. Compare the MED9.1 example and Motronic overview without transferring their hardware or calibration assumptions.
Owner-catalogue model labels
The active Bosch / MED17 catalogue browse showed these model labels on 10 November 2026. They are copied as identity labels for navigation. A label does not establish vehicle fitment, processor, shared hardware or programming compatibility.
- MED17
- MED17.0
- MED17.0.1
- MED17.0.7
- MED17.1
- MED17.1 TC1796
- MED17.1.1
- MED17.1.1 M&S
- MED17.1.1 TC1796
- MED17.1.1 TC1797
- MED17.1.1 TC1797 (2021)
- MED17.1.10
- MED17.1.11
- MED17.1.12
- MED17.1.1MS
- MED17.1.21
- MED17.1.27
- MED17.1.27 (2021)
- MED17.1.28
- MED17.1.6
- MED17.1.61
- MED17.1.62
- MED17.1.62.g2
- MED17.1.62MS
- MED17.1.6HY
- MED17.1.9
- MED17.2
- MED17.2 TC1766
- MED17.2 TC1796
- MED17.2.2
- MED17.2.3
- MED17.2.6
- MED17.2.9
- MED17.27
- MED17.3.0
- MED17.3.1
- MED17.3.3
- MED17.3.4
- MED17.3.5
- MED17.3.5 M&S
- MED17.3.5.g2
- MED17.3.8
- MED17.4
- MED17.4 TC1766
- MED17.4 TC1767
- MED17.4 TC1796
- MED17.4.2
- MED17.4.2 TC1767
- MED17.4.2 TC1797
- MED17.4.4
- MED17.5
- MED17.5.1
- MED17.5.2
- MED17.5.20
- MED17.5.21
- MED17.5.24
- MED17.5.25
- MED17.5.26
- MED17.5.27
- MED17.5.4
- MED17.5.5
- MED17.5.5 TC1766
- MED17.5.5 TC1767
- MED17.5.5_HW2
- MED17.5.6
- MED17.6.1
- MED17.6.9
- MED17.7
- MED17.7.1
- MED17.7.2
- MED17.7.3
- MED17.7.3.1
- MED17.7.5
- MED17.7.7
- MED17.7.8
- MED17.8.1
- MED17.8.10
- MED17.8.10 HW2
- MED17.8.10 TC1767
- MED17.8.10.1
- MED17.8.10.1 TC1782F
- MED17.8.2
- MED17.8.21
- MED17.8.3
- MED17.8.3.2
- MED17.8.31
- MED17.8.32
- MED17.8.32 (2021)
- MED17.8.33
- MED17.8.34
- MED17.8.X
- MED17.9.3
- MED17.9.3 (2021)
- MED17.9.3.g2
- MED17.9.30
- MED17.9.32
- MED17.9.63
- MED17.9.66
- MED17.9.7
- MED17.9.8
- MED17.9.9
- MED17.9.9 (2021)
- MED17.9.X
- MED17.X CAN
- MED17.x.x
- MED17xx
See the TriCore Motronic 17 processor table for only the exact ECU/processor pairs identified by EVC.
Sources
These are OEM design/function training documents hosted on independent mirrors, accessed 2026-11-10. They are not current repair manuals; use the relevant service information for testing and repair. No connector pin assignment is established here.