01 Mil On, Cold Start Misfire DTCS P0301 - P0304 (GROUP 24, NO. 12-16)
Reference number: GROUP 24, NO. 12-16
Supersedes refnos: 2010930, GROUP 01, NO. 05-07, GROUP 01, NO. 08-14, GROUP 24, NO. 10-14
01 MIL ON, COLD START MISFIRE DTCS P0301 - P0304
TECHNICAL SERVICE BULLETIN
| AUDI: | A4, A4 Cabriolet 2003 - 2005 |
| GROUP: | 24 - Multiport Fuel Injection |
Service Information
24 12 16 2010930/5 February 20, 2012. Supersedes Technical Service Bulletin Group 24 number 10-14 dated April 5, 2010 for reasons listed below.
| Model(s) | Year | VIN Range | Vehicle-Specific Equipment |
|---|---|---|---|
| A4 | 2003 - 2005 | All | 1.8T Engine |
| A4 Cabriolet |
Condition
| REVISION HISTORY | ||
|---|---|---|
| Revision | Date | Purpose |
| 5 | - | Revised Service |
| 4 | 4/5/2010 | All sections revised for formatting Revised Service (SVM code available in place of CD update) |
| 3 | 11/24/2008 | Revised Title to include Repair Group |
- Sporadically after cold start, engine may run slightly rough for a few seconds. Condition disappears a few seconds after cold start and does not exist with a warm engine.
- MIL may illuminate.
- DTCs P0300, P0301, P0302, P0303 , and P0304 for misfire may be stored in the DTC memory.
Technical Background
Fuel quality may also affect this condition.
Production Solution
Vehicles are out of production.
Service
- Follow all instructions in the attached TSB 2011732 00 Software Version Management (SVM), operating instructions.
- Update the ECM (J623) using the SVM action code as listed in the table below if necessary.
Model Year Engine Old Software Part Number Old Software Version New Software Part Number New Software Version (or higher) SVM Action Code 2003 - 2004 1.8T AMB 8E0909518 AK * 8E0909518 BC 0040 NA8E24SB01 2005 1.8T AMB 8E0909518 BC * 8E0909518 BC 0040
Warranty
| Claim Type: | Use applicable claim type. If vehicle is outside any warranty, this Technical Service Bulletin is informational only. | ||
| Service Number: | 2470 | ||
| Damage Code: | 0039 | ||
| Labor Operations: | SVM update | 0150 0000 | 70 TU |
| Diagnostic Time: | GFF - Checking and clearing fault codes included in existing labor operations | No allowance | 0 TU |
| Road test prior to service procedure | No allowance | 0 TU | |
| Road test after service procedure | No allowance | 0 TU | |
| Technical diagnosis at dealer's discretion (Refer to Section 2.2.1.2 and Audi Warranty Online for DADP allowance details) |
|||
| Claim Comment: | As per TSB #2010930/5 | ||
All warranty claims submitted for payment must be in accordance with the Audi Warranty Policies and Procedures Manual. Claims are subject to review or audit by Audi Warranty.
Additional Information
All parts and service references provided in this TSB are subject to change and/or removal. Always check with your Parts Department and service manuals for the latest information.
00 Software Version Management (SVM), operating instructions
00 12 32 2011732/9 February 7, 2012. Supersedes Technical Service Bulletin Group 00 number 10 - 02 dated March 24, 2010 for reasons listed below.
| Model(s) | Year | VIN Range | Vehicle-Specific Equipment |
|---|---|---|---|
| All Audi | 2002 on | Not Applicable | Not Applicable |
Condition
| REVISION HISTORY | ||
|---|---|---|
| Revision | Date | Purpose |
| 9 | - | Revised header data (Added model years) Revised Technical Background Revised Service (Added image) |
| 8 | 3/24/2010 | Revised Technical Background Revised Service (Added Response Codes section) |
| 7 | 5/13/2009 | Revised Service (Step 6) |
| 6 | 12/15/2008 | Revised Service (Step 3 - added information concerning use of wireless VAS 5054A transmitter head) |
| 5 | 11/17/2008 | Revised Title to include Repair Group |
| 4 | 10/21/2008 | Revised Service (Step 3 - added information concerning Windows power savings settings) |
This Technical Service Bulletin (TSB) details the general process for carrying out a Software Version Management (SVM) software update for any TSB or Update.
Troubleshooting information is included in the Additional Information section.
Please refer to the upcoming TSBs covering detailed aspects of SVM. They will be listed under group "99".
Technical Background
SVM was developed with the main goal of ensuring each Audi vehicle has the correct electronic control units with the correct software versions installed when it leaves the dealership repair facility.
SVM is a feature of GFF that has a subset of functions or components as seen in Figure 1. These functions are explained below. A VAS 5051B, VAS 5052A, or VAS 6150(A/B/C) diagnostic tool is required to read out the vehicle control unit data and send it to the SVM server (also called an "SVM communication").
SVM - Specified/actual comparison
Goal: This function is designed to ensure all electronic control units installed in the vehicle have the correct part numbers, software versions, coding and parameterization. It will not suggest a control unit software update. During this SVM communication, the part numbers and software versions of the actual control units installed in the vehicle will be sent to the SVM servers. This "actual" data is then compared to the "specified" data in the SVM database for a particular vehicle. The specified data stored on the SVM servers is also referred to as the vehicle "reference".
What an SVM Spec/Actual can do:
- Document any changes to an electronic control unit's hardware/software part numbers, hardware/software versions, and provide feedback to the user if these changes are accepted or rejected.
- When new parts are installed, it will also calculate coding changes or parameterization1 changes. If a "hardware replacement suggestion" is given, then a conflict exists with the vehicle reference for that control unit (i.e. SVM expects a different part number or software version for the control unit in question).
- As a rule, SVM will not allow a control unit with the same part number as the original part to be installed if the new part contains an older software revision. In this situation, SVM will return a hardware change suggestion2 . In these special cases a new vehicle reference must be manually set by an Audi Product Support Engineer. Please contact the Technical Assistance Center Helpline if you suspect this is the case.
SVM - Direct Input: SVM code for problem related update
Goal: This function performs any additional functions which cannot be performed with an SVM Spec/Actual. Those functions include the following.
What an SVM code can do:
- Update the software in a flash-capable control unit if the SVM code3 is valid for the vehicle.
- After the software update is completed, an additional SVM Specified/Actual comparison will be performed to calculate a new coding and/or parameterization and to document all control unit changes as a new reference in the SVM database.
- SVM Codes should not be used to update a control unit without knowing the solution(s) the software update provides. To update control unit software, the technician must first diagnose the condition in the vehicle and find an applicable TSB that provides a valid SVM Code. Randomly trying out multiple SVM Codes wastes time and can sometimes cause conflicts in the SVM database.
- SVM codes can also be used to document manual software updates to the vehicle's systems, as in the case with MMI Software Package (ZUG) updates. These types of updates are performed manually with a CD/DVD/SDcard. An SVM code for an MMI update documents the changes in the SVM database and provides coding and/or parameterization suggestions. It does not perform any software updates.
SVM codes for MMI Software Package (ZUG) updates will only complete successfully if every control unit is updated to the correct software level. This is especially important when a control unit fails/dies during the manual software update process and is then later replaced, but not updated after it is installed. Since the new replacement control unit was not updated the SVM code will fail. The replaced control unit must be updated prior to running the SVM code.
- SVM Exchange (XCHG) Codes can also be used to aid in the installation of new service parts when an SVM spec/actual cannot code or parameterize the replacement control unit, as with all Audi airbag control units.
It is critical to note SVM XCHG codes must be run immediately after a new control unit is installed in the vehicle. If an SVM Spec/Actual is performed instead, it will create an invalid vehicle reference in the SVM database. Once this occurs the SVM XCHG code will not function properly. The only way to resolve this issue is to contact the Technical Assistance Center Helpline to have the vehicle reference manually set. To find the SVM XCHG code, follow the parts bulletin listed in ETKA or search for an applicable Technical Service Bulletin.
SVM - Direct Input: SVM code for vehicle conversion
Goal: This function allows for a factory approved retrofit of additional control unit(s) using a valid SVM Code for Vehicle Conversion.
- This type of SVM code is documented inside the installation instructions for the control unit and is typically performed as the last installation step. You can identify an SVM code for conversion by the way it is named. They are typically named "050XXX".
SVM - Activations
Goal: This function is designed to activate additional features or functions within an already installed control unit using an Activation Code and possibly additional PIN codes or Customer codes.
- This function is designed with a security system similar to installing a new operating system on a personal computer. Currently, SVM Activation codes are only being used with navigation map data updates for vehicles with MMI3G/3G+. The customer no longer needs to purchase the Navigation map data. Instead the customer must purchase an "Activation Packet" to unlock the map update in the MMI system. The Activation Packet consists of an Activation Code, Activate Number, and Pin Code. Once the Activation information is used, it becomes permanently tied to the customer's vehicle in the SVM database and cannot be reused with another vehicle.
SVM - communication, checking
Goal: This function allows the user to check the VAS Tester's SVM online connection status to ensure the tester is communicating with the SVM server.
Tips:
- 1Parameterization refers to data written into the control unit by SVM to customize the software functionality for the specific vehicle or country of operation. It is often referred to as the "calibration data." It is critical the parameterization is executed anytime it is suggested by SVM to ensure the proper functionality of the control unit. Not all control units are parameterized by SVM.
- 2 It is also important to note that if there are any "Hardware Change Suggestions" any time when an SVM code is run, a new vehicle "Reference" will NOT be set in the SVM database. This is to prevent any bad data from being documented in the reference. This can create an issue where repeat coding and/or parameterization suggestions are given with all subsequent SVM communications (Spec/Actual or SVM code). All "Hardware Change Suggestions" should be resolved prior to an SVM code being executed! Once the hardware issue is resolved, the SVM code must be run again to set the new reference.
- 3 It is important to note that almost all SVM codes will automatically perform a "Quick Test" to verify if the SVM code is valid for the vehicle prior to performing the software update. This is done to speed up the process and provide immediate feedback to the tech of whether or not SVM will be able to code/parameterize the control unit after the software update is completed. If SVM finds an issue it will indicate the SVM code is valid for the vehicle, but cannot be completed.
Production Solution
Not applicable.
Service
- Address or record any DTCs related to any additional customer concerns before continuing. The reason for this is that any sporadic DTCs could be automatically erased at the end of the SVM communication.
Tip: Sporadic communication DTCs will be created during the flash procedure and will be automatically erased along with all other pre-existing sporadic DTCs at the end of the SVM test plan.
Tuning is the addition or modification of any component that causes an Audi vehicle to perform outside the normal parameters and specifications approved by Audi of America, Inc. If you encounter a vehicle with a tuned engine control module (ECM) or transmission control module (TCM), your dealership must do the following before performing any procedure that updates ECM or TCM programming:
- Notify the owner that their ECM or TCM was found to have been tuned.
- Notify the owner that any damage caused by the tuning of the ECM or TCM (including any adverse emissions consequences) will not be covered by Audi of America, Inc. warranties.
- Obtain the owner's written consent (see attached Control Module Tuning form) for any requested repair - under warranty or outside warranty - that requires flashing that will automatically overwrite the tuned program.
Tip: Any programming update (flash) may overwrite any tuned ECM or TCM programming.
- Ensure the TSB stating the condition in the vehicle applies to the customer complaint. Ensure the VAS Tester operator has a valid GeKo user ID and password. Perform only operations explicitly stated in the TSB or Update.
- Verify that the following tester requirements are met
- VAS 5051B, VAS 5052A, or VAS 6150(A/B/C) with minimum Base CD Version 19.01 with Brand CD 19.36 installed.
- Tester is plugged into an 110V AC power supply at all times.
- Connect VAS 5051B and VAS 5052A to the local network via LAN/Ethernet cable.
- Connect VAS 6150(A/B/C) to the local network via LAN/Ethernet cable. A WiFi connection is not recommended due to the possibility of signal dropouts during the online communication.
- For B7 A4s after VIN 8E_5A400000, always use the 6017B K Line Adapter to ensure communication to all modules.
- If the Bluetooth wireless VAS 5054A transmitter head is used in conjunction with a VAS 5052A or VAS 6150(A/B/C) tester, the transmitter head MUST BE connected with a USB cable to the tester.
- Ensure the Windows power savings are set correctly (disabled) for VAS testers operating with an open Windows interface in which users have access to all regular PC operating system functions (implemented by running the Base V14.00.00 Recovery DVD).
- VAS 5051B, VAS 5052A, or VAS 6150(A/B/C) with minimum Base CD Version 19.01 with Brand CD 19.36 installed.
- Tester is plugged into an 110V AC power supply at all times.NOTE: If the Windows screensaver activates during a control module software update and the hard drive shuts down as a result of the power settings, a control module failure may result. Refer to Service Circular ATE-08-23 for more information.
01 Mil On, Cold Start Misfire DTCS P0301 - P0304 (GROUP 24, NO. 12-16)
Publication date: 2012-02-20
Reference number: GROUP 24, NO. 12-16
Supersedes refnos: 2010930, GROUP 01, NO. 05-07, GROUP 01, NO. 08-14, GROUP 24, NO. 10-1401 MIL ON, COLD START MISFIRE DTCS P0301 - P0304 01 MIL ON, COLD START MISFIRE DTCS P0301 - P0304
TECHNICAL SERVICE BULLETIN
Reference Number(s): GROUP 24, NO. 12-16 (2010930/5), Date of Issue: February 20, 2012
Superceded Bulletin(s): GROUP 24, NO. 10-14, Date of Issue: April 5, 2010AUDI: A4, A4 Cabriolet 2003 - 2005 GROUP: 24 - Multiport Fuel Injection Service Information
24 12 16 2010930/5 February 20, 2012. Supersedes Technical Service Bulletin Group 24 number 10-14 dated April 5, 2010 for reasons listed below.
Model(s) Year VIN Range Vehicle-Specific Equipment A4 2003 - 2005 All 1.8T Engine A4 Cabriolet Condition
REVISION HISTORY Revision Date Purpose 5 - Revised Service 4 4/5/2010 All sections revised for formatting
Revised Service (SVM code available in place of CD update)3 11/24/2008 Revised Title to include Repair Group - Sporadically after cold start, engine may run slightly rough for a few seconds. Condition disappears a few seconds after cold start and does not exist with a warm engine.
- MIL may illuminate.
- DTCs P0300, P0301, P0302, P0303 , and P0304 for misfire may be stored in the DTC memory.
Technical Background
Fuel quality may also affect this condition.
Production Solution
Vehicles are out of production.
Service
- Follow all instructions in the attached TSB 2011732 00 Software Version Management (SVM), operating instructions.
- Update the ECM (J623) using the SVM action code as listed in the table below if necessary.
Model Year Engine Old Software Part Number Old Software Version New Software Part Number New Software Version (or higher) SVM Action Code 2003 - 2004 1.8T AMB 8E0909518 AK * 8E0909518 BC 0040 NA8E24SB01 2005 1.8T AMB 8E0909518 BC * 8E0909518 BC 0040
Warranty
Claim Type: Use applicable claim type. If vehicle is outside any warranty, this Technical Service Bulletin is informational only. Service Number: 2470 Damage Code: 0039 Labor Operations: SVM update 0150 0000 70 TU Diagnostic Time: GFF - Checking and clearing fault codes included in existing labor operations No allowance 0 TU Road test prior to service procedure No allowance 0 TU Road test after service procedure No allowance 0 TU Technical diagnosis at dealer's discretion
(Refer to Section 2.2.1.2 and Audi Warranty Online for DADP allowance details)Claim Comment: As per TSB #2010930/5 All warranty claims submitted for payment must be in accordance with the Audi Warranty Policies and Procedures Manual. Claims are subject to review or audit by Audi Warranty.
Additional Information
All parts and service references provided in this TSB are subject to change and/or removal. Always check with your Parts Department and service manuals for the latest information.
00 Software Version Management (SVM), operating instructions
00 12 32 2011732/9 February 7, 2012. Supersedes Technical Service Bulletin Group 00 number 10 - 02 dated March 24, 2010 for reasons listed below.
Model(s) Year VIN Range Vehicle-Specific Equipment All Audi 2002 on Not Applicable Not Applicable Condition
REVISION HISTORY Revision Date Purpose 9 - Revised header data (Added model years)
Revised Technical Background
Revised Service (Added image)8 3/24/2010 Revised Technical Background
Revised Service (Added Response Codes section)7 5/13/2009 Revised Service (Step 6) 6 12/15/2008 Revised Service (Step 3 - added information concerning use of wireless VAS 5054A transmitter head) 5 11/17/2008 Revised Title to include Repair Group 4 10/21/2008 Revised Service (Step 3 - added information concerning Windows power savings settings) This Technical Service Bulletin (TSB) details the general process for carrying out a Software Version Management (SVM) software update for any TSB or Update.
Troubleshooting information is included in the Additional Information section.
Please refer to the upcoming TSBs covering detailed aspects of SVM. They will be listed under group "99".
Technical Background
SVM was developed with the main goal of ensuring each Audi vehicle has the correct electronic control units with the correct software versions installed when it leaves the dealership repair facility.
SVM is a feature of GFF that has a subset of functions or components as seen in Figure 1. These functions are explained below. A VAS 5051B, VAS 5052A, or VAS 6150(A/B/C) diagnostic tool is required to read out the vehicle control unit data and send it to the SVM server (also called an "SVM communication").
SVM - Specified/actual comparison
Goal: This function is designed to ensure all electronic control units installed in the vehicle have the correct part numbers, software versions, coding and parameterization. It will not suggest a control unit software update. During this SVM communication, the part numbers and software versions of the actual control units installed in the vehicle will be sent to the SVM servers. This "actual" data is then compared to the "specified" data in the SVM database for a particular vehicle. The specified data stored on the SVM servers is also referred to as the vehicle "reference".
What an SVM Spec/Actual can do:
- Document any changes to an electronic control unit's hardware/software part numbers, hardware/software versions, and provide feedback to the user if these changes are accepted or rejected.
- When new parts are installed, it will also calculate coding changes or parameterization1 changes. If a "hardware replacement suggestion" is given, then a conflict exists with the vehicle reference for that control unit (i.e. SVM expects a different part number or software version for the control unit in question).
- As a rule, SVM will not allow a control unit with the same part number as the original part to be installed if the new part contains an older software revision. In this situation, SVM will return a hardware change suggestion2 . In these special cases a new vehicle reference must be manually set by an Audi Product Support Engineer. Please contact the Technical Assistance Center Helpline if you suspect this is the case.
SVM - Direct Input: SVM code for problem related update
Goal: This function performs any additional functions which cannot be performed with an SVM Spec/Actual. Those functions include the following.
What an SVM code can do:
- Update the software in a flash-capable control unit if the SVM code3 is valid for the vehicle.
- After the software update is completed, an additional SVM Specified/Actual comparison will be performed to calculate a new coding and/or parameterization and to document all control unit changes as a new reference in the SVM database.
- SVM Codes should not be used to update a control unit without knowing the solution(s) the software update provides. To update control unit software, the technician must first diagnose the condition in the vehicle and find an applicable TSB that provides a valid SVM Code. Randomly trying out multiple SVM Codes wastes time and can sometimes cause conflicts in the SVM database.
- SVM codes can also be used to document manual software updates to the vehicle's systems, as in the case with MMI Software Package (ZUG) updates. These types of updates are performed manually with a CD/DVD/SDcard. An SVM code for an MMI update documents the changes in the SVM database and provides coding and/or parameterization suggestions. It does not perform any software updates.
SVM codes for MMI Software Package (ZUG) updates will only complete successfully if every control unit is updated to the correct software level. This is especially important when a control unit fails/dies during the manual software update process and is then later replaced, but not updated after it is installed. Since the new replacement control unit was not updated the SVM code will fail. The replaced control unit must be updated prior to running the SVM code.
- SVM Exchange (XCHG) Codes can also be used to aid in the installation of new service parts when an SVM spec/actual cannot code or parameterize the replacement control unit, as with all Audi airbag control units.
It is critical to note SVM XCHG codes must be run immediately after a new control unit is installed in the vehicle. If an SVM Spec/Actual is performed instead, it will create an invalid vehicle reference in the SVM database. Once this occurs the SVM XCHG code will not function properly. The only way to resolve this issue is to contact the Technical Assistance Center Helpline to have the vehicle reference manually set. To find the SVM XCHG code, follow the parts bulletin listed in ETKA or search for an applicable Technical Service Bulletin.
SVM - Direct Input: SVM code for vehicle conversion
Goal: This function allows for a factory approved retrofit of additional control unit(s) using a valid SVM Code for Vehicle Conversion.
- This type of SVM code is documented inside the installation instructions for the control unit and is typically performed as the last installation step. You can identify an SVM code for conversion by the way it is named. They are typically named "050XXX".
SVM - Activations
Goal: This function is designed to activate additional features or functions within an already installed control unit using an Activation Code and possibly additional PIN codes or Customer codes.
- This function is designed with a security system similar to installing a new operating system on a personal computer. Currently, SVM Activation codes are only being used with navigation map data updates for vehicles with MMI3G/3G+. The customer no longer needs to purchase the Navigation map data. Instead the customer must purchase an "Activation Packet" to unlock the map update in the MMI system. The Activation Packet consists of an Activation Code, Activate Number, and Pin Code. Once the Activation information is used, it becomes permanently tied to the customer's vehicle in the SVM database and cannot be reused with another vehicle.
SVM - communication, checking
Goal: This function allows the user to check the VAS Tester's SVM online connection status to ensure the tester is communicating with the SVM server.
Tips:
- 1Parameterization refers to data written into the control unit by SVM to customize the software functionality for the specific vehicle or country of operation. It is often referred to as the "calibration data." It is critical the parameterization is executed anytime it is suggested by SVM to ensure the proper functionality of the control unit. Not all control units are parameterized by SVM.
- 2 It is also important to note that if there are any "Hardware Change Suggestions" any time when an SVM code is run, a new vehicle "Reference" will NOT be set in the SVM database. This is to prevent any bad data from being documented in the reference. This can create an issue where repeat coding and/or parameterization suggestions are given with all subsequent SVM communications (Spec/Actual or SVM code). All "Hardware Change Suggestions" should be resolved prior to an SVM code being executed! Once the hardware issue is resolved, the SVM code must be run again to set the new reference.
- 3 It is important to note that almost all SVM codes will automatically perform a "Quick Test" to verify if the SVM code is valid for the vehicle prior to performing the software update. This is done to speed up the process and provide immediate feedback to the tech of whether or not SVM will be able to code/parameterize the control unit after the software update is completed. If SVM finds an issue it will indicate the SVM code is valid for the vehicle, but cannot be completed.
Production Solution
Not applicable.
Service
- Address or record any DTCs related to any additional customer concerns before continuing. The reason for this is that any sporadic DTCs could be automatically erased at the end of the SVM communication.
Tip: Sporadic communication DTCs will be created during the flash procedure and will be automatically erased along with all other pre-existing sporadic DTCs at the end of the SVM test plan.
Tuning is the addition or modification of any component that causes an Audi vehicle to perform outside the normal parameters and specifications approved by Audi of America, Inc. If you encounter a vehicle with a tuned engine control module (ECM) or transmission control module (TCM), your dealership must do the following before performing any procedure that updates ECM or TCM programming:
- Notify the owner that their ECM or TCM was found to have been tuned.
- Notify the owner that any damage caused by the tuning of the ECM or TCM (including any adverse emissions consequences) will not be covered by Audi of America, Inc. warranties.
- Obtain the owner's written consent (see attached Control Module Tuning form) for any requested repair - under warranty or outside warranty - that requires flashing that will automatically overwrite the tuned program.
Tip: Any programming update (flash) may overwrite any tuned ECM or TCM programming.
- Ensure the TSB stating the condition in the vehicle applies to the customer complaint. Ensure the VAS Tester operator has a valid GeKo user ID and password. Perform only operations explicitly stated in the TSB or Update.
- Verify that the following tester requirements are met
- VAS 5051B, VAS 5052A, or VAS 6150(A/B/C) with minimum Base CD Version 19.01 with Brand CD 19.36 installed.
- Tester is plugged into an 110V AC power supply at all times.
- Connect VAS 5051B and VAS 5052A to the local network via LAN/Ethernet cable.
- Connect VAS 6150(A/B/C) to the local network via LAN/Ethernet cable. A WiFi connection is not recommended due to the possibility of signal dropouts during the online communication.
- For B7 A4s after VIN 8E_5A400000, always use the 6017B K Line Adapter to ensure communication to all modules.
- If the Bluetooth wireless VAS 5054A transmitter head is used in conjunction with a VAS 5052A or VAS 6150(A/B/C) tester, the transmitter head MUST BE connected with a USB cable to the tester.
- Ensure the Windows power savings are set correctly (disabled) for VAS testers operating with an open Windows interface in which users have access to all regular PC operating system functions (implemented by running the Base V14.00.00 Recovery DVD).
- VAS 5051B, VAS 5052A, or VAS 6150(A/B/C) with minimum Base CD Version 19.01 with Brand CD 19.36 installed.
- Tester is plugged into an 110V AC power supply at all times.NOTE: If the Windows screensaver activates during a control module software update and the hard drive shuts down as a result of the power settings, a control module failure may result. Refer to Service Circular ATE-08-23 for more information.
01 Mil On, Cold Start Misfire DTCS P0301 - P0304 (GROUP 24, NO. 12-16)
Publication date: 2012-02-20
Reference number: GROUP 24, NO. 12-16
Supersedes refnos: 2010930, GROUP 01, NO. 05-07, GROUP 01, NO. 08-14, GROUP 24, NO. 10-1401 MIL ON, COLD START MISFIRE DTCS P0301 - P0304 01 MIL ON, COLD START MISFIRE DTCS P0301 - P0304
TECHNICAL SERVICE BULLETIN
Reference Number(s): GROUP 24, NO. 12-16 (2010930/5), Date of Issue: February 20, 2012
Superceded Bulletin(s): GROUP 24, NO. 10-14, Date of Issue: April 5, 2010AUDI: A4, A4 Cabriolet 2003 - 2005 GROUP: 24 - Multiport Fuel Injection Service Information
24 12 16 2010930/5 February 20, 2012. Supersedes Technical Service Bulletin Group 24 number 10-14 dated April 5, 2010 for reasons listed below.
Model(s) Year VIN Range Vehicle-Specific Equipment A4 2003 - 2005 All 1.8T Engine A4 Cabriolet Condition
REVISION HISTORY Revision Date Purpose 5 - Revised Service 4 4/5/2010 All sections revised for formatting
Revised Service (SVM code available in place of CD update)3 11/24/2008 Revised Title to include Repair Group - Sporadically after cold start, engine may run slightly rough for a few seconds. Condition disappears a few seconds after cold start and does not exist with a warm engine.
- MIL may illuminate.
- DTCs P0300, P0301, P0302, P0303 , and P0304 for misfire may be stored in the DTC memory.
Technical Background
Fuel quality may also affect this condition.
Production Solution
Vehicles are out of production.
Service
- Follow all instructions in the attached TSB 2011732 00 Software Version Management (SVM), operating instructions.
- Update the ECM (J623) using the SVM action code as listed in the table below if necessary.
Model Year Engine Old Software Part Number Old Software Version New Software Part Number New Software Version (or higher) SVM Action Code 2003 - 2004 1.8T AMB 8E0909518 AK * 8E0909518 BC 0040 NA8E24SB01 2005 1.8T AMB 8E0909518 BC * 8E0909518 BC 0040
Warranty
Claim Type: Use applicable claim type. If vehicle is outside any warranty, this Technical Service Bulletin is informational only. Service Number: 2470 Damage Code: 0039 Labor Operations: SVM update 0150 0000 70 TU Diagnostic Time: GFF - Checking and clearing fault codes included in existing labor operations No allowance 0 TU Road test prior to service procedure No allowance 0 TU Road test after service procedure No allowance 0 TU Technical diagnosis at dealer's discretion
(Refer to Section 2.2.1.2 and Audi Warranty Online for DADP allowance details)Claim Comment: As per TSB #2010930/5 All warranty claims submitted for payment must be in accordance with the Audi Warranty Policies and Procedures Manual. Claims are subject to review or audit by Audi Warranty.
Additional Information
All parts and service references provided in this TSB are subject to change and/or removal. Always check with your Parts Department and service manuals for the latest information.
00 Software Version Management (SVM), operating instructions
00 12 32 2011732/9 February 7, 2012. Supersedes Technical Service Bulletin Group 00 number 10 - 02 dated March 24, 2010 for reasons listed below.
Model(s) Year VIN Range Vehicle-Specific Equipment All Audi 2002 on Not Applicable Not Applicable Condition
REVISION HISTORY Revision Date Purpose 9 - Revised header data (Added model years)
Revised Technical Background
Revised Service (Added image)8 3/24/2010 Revised Technical Background
Revised Service (Added Response Codes section)7 5/13/2009 Revised Service (Step 6) 6 12/15/2008 Revised Service (Step 3 - added information concerning use of wireless VAS 5054A transmitter head) 5 11/17/2008 Revised Title to include Repair Group 4 10/21/2008 Revised Service (Step 3 - added information concerning Windows power savings settings) This Technical Service Bulletin (TSB) details the general process for carrying out a Software Version Management (SVM) software update for any TSB or Update.
Troubleshooting information is included in the Additional Information section.
Please refer to the upcoming TSBs covering detailed aspects of SVM. They will be listed under group "99".
Technical Background
SVM was developed with the main goal of ensuring each Audi vehicle has the correct electronic control units with the correct software versions installed when it leaves the dealership repair facility.
SVM is a feature of GFF that has a subset of functions or components as seen in Figure 1. These functions are explained below. A VAS 5051B, VAS 5052A, or VAS 6150(A/B/C) diagnostic tool is required to read out the vehicle control unit data and send it to the SVM server (also called an "SVM communication").
SVM - Specified/actual comparison
Goal: This function is designed to ensure all electronic control units installed in the vehicle have the correct part numbers, software versions, coding and parameterization. It will not suggest a control unit software update. During this SVM communication, the part numbers and software versions of the actual control units installed in the vehicle will be sent to the SVM servers. This "actual" data is then compared to the "specified" data in the SVM database for a particular vehicle. The specified data stored on the SVM servers is also referred to as the vehicle "reference".
What an SVM Spec/Actual can do:
- Document any changes to an electronic control unit's hardware/software part numbers, hardware/software versions, and provide feedback to the user if these changes are accepted or rejected.
- When new parts are installed, it will also calculate coding changes or parameterization1 changes. If a "hardware replacement suggestion" is given, then a conflict exists with the vehicle reference for that control unit (i.e. SVM expects a different part number or software version for the control unit in question).
- As a rule, SVM will not allow a control unit with the same part number as the original part to be installed if the new part contains an older software revision. In this situation, SVM will return a hardware change suggestion2 . In these special cases a new vehicle reference must be manually set by an Audi Product Support Engineer. Please contact the Technical Assistance Center Helpline if you suspect this is the case.
SVM - Direct Input: SVM code for problem related update
Goal: This function performs any additional functions which cannot be performed with an SVM Spec/Actual. Those functions include the following.
What an SVM code can do:
- Update the software in a flash-capable control unit if the SVM code3 is valid for the vehicle.
- After the software update is completed, an additional SVM Specified/Actual comparison will be performed to calculate a new coding and/or parameterization and to document all control unit changes as a new reference in the SVM database.
- SVM Codes should not be used to update a control unit without knowing the solution(s) the software update provides. To update control unit software, the technician must first diagnose the condition in the vehicle and find an applicable TSB that provides a valid SVM Code. Randomly trying out multiple SVM Codes wastes time and can sometimes cause conflicts in the SVM database.
- SVM codes can also be used to document manual software updates to the vehicle's systems, as in the case with MMI Software Package (ZUG) updates. These types of updates are performed manually with a CD/DVD/SDcard. An SVM code for an MMI update documents the changes in the SVM database and provides coding and/or parameterization suggestions. It does not perform any software updates.
SVM codes for MMI Software Package (ZUG) updates will only complete successfully if every control unit is updated to the correct software level. This is especially important when a control unit fails/dies during the manual software update process and is then later replaced, but not updated after it is installed. Since the new replacement control unit was not updated the SVM code will fail. The replaced control unit must be updated prior to running the SVM code.
- SVM Exchange (XCHG) Codes can also be used to aid in the installation of new service parts when an SVM spec/actual cannot code or parameterize the replacement control unit, as with all Audi airbag control units.
It is critical to note SVM XCHG codes must be run immediately after a new control unit is installed in the vehicle. If an SVM Spec/Actual is performed instead, it will create an invalid vehicle reference in the SVM database. Once this occurs the SVM XCHG code will not function properly. The only way to resolve this issue is to contact the Technical Assistance Center Helpline to have the vehicle reference manually set. To find the SVM XCHG code, follow the parts bulletin listed in ETKA or search for an applicable Technical Service Bulletin.
SVM - Direct Input: SVM code for vehicle conversion
Goal: This function allows for a factory approved retrofit of additional control unit(s) using a valid SVM Code for Vehicle Conversion.
- This type of SVM code is documented inside the installation instructions for the control unit and is typically performed as the last installation step. You can identify an SVM code for conversion by the way it is named. They are typically named "050XXX".
SVM - Activations
Goal: This function is designed to activate additional features or functions within an already installed control unit using an Activation Code and possibly additional PIN codes or Customer codes.
- This function is designed with a security system similar to installing a new operating system on a personal computer. Currently, SVM Activation codes are only being used with navigation map data updates for vehicles with MMI3G/3G+. The customer no longer needs to purchase the Navigation map data. Instead the customer must purchase an "Activation Packet" to unlock the map update in the MMI system. The Activation Packet consists of an Activation Code, Activate Number, and Pin Code. Once the Activation information is used, it becomes permanently tied to the customer's vehicle in the SVM database and cannot be reused with another vehicle.
SVM - communication, checking
Goal: This function allows the user to check the VAS Tester's SVM online connection status to ensure the tester is communicating with the SVM server.
Tips:
- 1Parameterization refers to data written into the control unit by SVM to customize the software functionality for the specific vehicle or country of operation. It is often referred to as the "calibration data." It is critical the parameterization is executed anytime it is suggested by SVM to ensure the proper functionality of the control unit. Not all control units are parameterized by SVM.
- 2 It is also important to note that if there are any "Hardware Change Suggestions" any time when an SVM code is run, a new vehicle "Reference" will NOT be set in the SVM database. This is to prevent any bad data from being documented in the reference. This can create an issue where repeat coding and/or parameterization suggestions are given with all subsequent SVM communications (Spec/Actual or SVM code). All "Hardware Change Suggestions" should be resolved prior to an SVM code being executed! Once the hardware issue is resolved, the SVM code must be run again to set the new reference.
- 3 It is important to note that almost all SVM codes will automatically perform a "Quick Test" to verify if the SVM code is valid for the vehicle prior to performing the software update. This is done to speed up the process and provide immediate feedback to the tech of whether or not SVM will be able to code/parameterize the control unit after the software update is completed. If SVM finds an issue it will indicate the SVM code is valid for the vehicle, but cannot be completed.
Production Solution
Not applicable.
Service
- Address or record any DTCs related to any additional customer concerns before continuing. The reason for this is that any sporadic DTCs could be automatically erased at the end of the SVM communication.
Tip: Sporadic communication DTCs will be created during the flash procedure and will be automatically erased along with all other pre-existing sporadic DTCs at the end of the SVM test plan.
Tuning is the addition or modification of any component that causes an Audi vehicle to perform outside the normal parameters and specifications approved by Audi of America, Inc. If you encounter a vehicle with a tuned engine control module (ECM) or transmission control module (TCM), your dealership must do the following before performing any procedure that updates ECM or TCM programming:
- Notify the owner that their ECM or TCM was found to have been tuned.
- Notify the owner that any damage caused by the tuning of the ECM or TCM (including any adverse emissions consequences) will not be covered by Audi of America, Inc. warranties.
- Obtain the owner's written consent (see attached Control Module Tuning form) for any requested repair - under warranty or outside warranty - that requires flashing that will automatically overwrite the tuned program.
Tip: Any programming update (flash) may overwrite any tuned ECM or TCM programming.
- Ensure the TSB stating the condition in the vehicle applies to the customer complaint. Ensure the VAS Tester operator has a valid GeKo user ID and password. Perform only operations explicitly stated in the TSB or Update.
- Verify that the following tester requirements are met
- VAS 5051B, VAS 5052A, or VAS 6150(A/B/C) with minimum Base CD Version 19.01 with Brand CD 19.36 installed.
- Tester is plugged into an 110V AC power supply at all times.
- Connect VAS 5051B and VAS 5052A to the local network via LAN/Ethernet cable.
- Connect VAS 6150(A/B/C) to the local network via LAN/Ethernet cable. A WiFi connection is not recommended due to the possibility of signal dropouts during the online communication.
- For B7 A4s after VIN 8E_5A400000, always use the 6017B K Line Adapter to ensure communication to all modules.
- If the Bluetooth wireless VAS 5054A transmitter head is used in conjunction with a VAS 5052A or VAS 6150(A/B/C) tester, the transmitter head MUST BE connected with a USB cable to the tester.
- Ensure the Windows power savings are set correctly (disabled) for VAS testers operating with an open Windows interface in which users have access to all regular PC operating system functions (implemented by running the Base V14.00.00 Recovery DVD).
- VAS 5051B, VAS 5052A, or VAS 6150(A/B/C) with minimum Base CD Version 19.01 with Brand CD 19.36 installed.
- Tester is plugged into an 110V AC power supply at all times.NOTE: If the Windows screensaver activates during a control module software update and the hard drive shuts down as a result of the power settings, a control module failure may result. Refer to Service Circular ATE-08-23 for more information.
Supporting Diagrams & Locations
Reference material from the factory manual for this diagnostic procedure.
Location00 Software Version Management (SVM), Operating Instructions (GROUP 00, NO. 21-55)
Location00 Software Version Management (SVM), Operating Instructions (GROUP 00, NO. 21-55)
Location00 Software Version Management (SVM), Operating Instructions (GROUP 00, NO. 21-55)
Location00 Software Version Management (SVM), Operating Instructions (GROUP 00, NO. 21-55)