Operation CHARM: Car repair manuals for everyone.

Campaign - Air Bag Control Module Software Update

Subject:
Update Programming For Airbag Warning Light ON (II)

Group: 69
Number: 06 05
Date: Oct. 13, 2006

Model(s):
A6 3.2/4.2 w/Control 2005
Module 4F0 910 655* 2006 to VIN 4F_6N115108

Instructions:
Perform this procedure on all applicable vehicles within the Limited New Vehicle Warranty.

Supersedes T.B. Group 69 number 06-03 dated March 3, 2006 due to updated information.

Tip:
This Technical Bulletin is in effect for 15 months from date of publication as listed above. After that date, this Technical Bulletin will expire and no longer be in effect.

Condition
- Airbag warning light illuminates due to sporadic fault entry.
- The following fault codes could be present "sporadic" in airbag control module: 01211, 01212, 01213, 01638 and 01639.
- The rear seatbelt pretensioner igniters will continue to function as designed if fault codes are set as sporadic faults.

Production
Improved software for airbag control module introduced as of VIN: 4F_6N115109.

Service

Requirements:
Vehicle must meet ALL of the following criteria.
1. - Procedure is valid only for vehicles that show the II code in the OTIS View Campaign inquiry screen on the day of repair.
2. - Vehicle must be within the Limited New Vehicle Warranty.
3. - Procedure must be performed within the allotted time frame stated in this Technical Bulletin.

Procedure must also be performed on applicable vehicles in Dealer inventory.

Vehicle requirements:
Battery MUST have minimum no-load charge of 12.5V (failure to maintain voltage during update process can lead to Control Module failure).

Minimize any voltage draw to vehicle (radio, and other accessories switched OFF, apply Emergency brake to switch running lights OFF if applicable)

Procedure MY 2005/2006:
- MY 2005, update software for airbag control module Part No: 4FO 910 655 A/B/F, SW level 220/230 to SW level 310 using Software Version Management (SVM). (Refer to Technical Bulletin number 01-06-02 for SVM instructions).
- MY 2006 update software for airbag control module Part No: 4FO 910 655 F, SW level 260/270 to SW level 300 using Software Version Management (SVM). (Refer to Technical Bulletin number 01-06-02 for SVM instructions).
- Via GFF use SVM Test plan for Problem related Hardware and Software update and follow instructions in test plan.
- MY 2005 - use following SVM Code:
NA4F6905II.
- MY 2006 - use following SVM Code:
NA4F69JBII.

The test plan will automatically load the new software container from the AoA server to the tester; under normal conditions the CD is not needed. Only in the event the update can not be loaded the following message will appear "No Flash container for control module has been located on workshop server", in this case continue with

- Insert update CD into VAS 5051/5052 (part No: W42A6SWU310 MY2005 or W42A6SWU300 MY 2006) and select 1. Repeat search. This will load the flash container from the CD.

If the update was completed using the CD, continue with the SVM test plan to code the Airbag control module.

- ONLY perform update and coding for Airbag module, ignore other updates. DO NOT exit the session, use prompt to continue.

After software update has completed:
- Choose prompt (1) to view changes, print screen to confirmation update, and attach screen print to vehicle service file.
- The airbag control module needs to be coded once the update has been flashed. Therefore, the test plan will automatically interrogate all control modules again, so the test plan can establish the correct code for, the airbag module.
- Follow test plan to code airbag control module.
- Interrupting the test plan or changing function during the test plan can cause an failure to successfully transfer of update and coding information from and to the SVM databank.

After coding has completed:
- Choose prompt (1) to view changes, print screen to confirm successful coding.
- Continue to exit GFF which will clear stored DTCs generated by the software update.
- OBD II related faults may not clear automatically; therefore you must clear those faults manually. It is not necessary to generate a readiness code.
- At prompt to print GFF diagnostic report, choose "YES" and print short version of diagnostic report, attach printout to vehicle warranty file.

Tip:
Vehicles with satellite radio option that is not activated by the customer will have a fault code stored "not active" Please ignore this fault entry if customer has not activated the satellite radio feature. IMPORTANT! The program may loop back for additional updates to other control modules. ONLY update software for valid customer concern as outlined in the Technical Bulletin from which the Action Code comes from. Warranty does not cover time expended on updating (flashing) modules not explicitly stated in the bulletin.

Warranty:

Tip:
AoA is verifying software update and coding data for each vehicle daily, unsuccessful updates or coding will prompt follow up from AoA and can void warranty payment for update.

Required Vehicle Update Technical Bulletin Time
Requirements/Reimbursement

To ensure prompt and proper payment, be sure to enter, immediately upon completion of the repair work, the applicable reimbursement code listed below. Claims will only be paid for vehicles that show the II code in the OTIS View Campaign inquiry screen on the day of repair.




The system automatically enters parts and labor applicable to the above listed code.

For vehicles that, according to your information, cannot be corrected or reached, and one of the codes below best describe the reason, please enter one of the applicable codes into the system:
- II 20 Customer Refused Repairs
- II 30 Total Loss
- II 40 Vehicle Stolen
- II 50 Vehicle Exported

Additional Required
Vehicle Update Technical Bulletins

Some of the affected vehicles may be involved in additional Required Vehicle Update Technical Bulletins. Please check your OTIS View Campaign inquiry screen so that any additional required work can he done simultaneously

Required Vehicle Update Technical
Bulletin Verification

For verification, always check the OTIS View Campaign inquiry screen. The OTIS system is the only binding inquiry and verification system; other systems are not valid and may result in non-payment of a claim.

Help for Claim
Input

For questions regarding claim input, contact your appropriate Warranty Claim specialist. Please do not contact the Campaign Helpline regarding claim input.

Required Customer
Notification

Inform your customer in writing by recording on the Repair Order any and all work that was conducted on the vehicle, including any and all updates completed under this Technical Bulletin.

Required Parts and Tools:

Approved Battery Charger

VAS 5051 A, 5051 B and VAS 5052:
- Minimum Base CD V.08.00.00 installed.
- Brand CD V.08.44.00 or later installed (see Service Circular ALS-05-27).
- URL update performed (see Service Circular ALS-05-21). To check connectivity see page 12 of Software Version Management (SVM) Technical Bulletin 01-06-02.
- Operator must have a valid GeKo user ID and password.

Additional Information
- For technical related questions: Call the AUDI Technician Helpline.
- Service Department Applications (this includes: GeKo, ELSA, Hotline Channel, Telediagnosis, and Service Net)
- VAS 5051/5052 Software Subscriptions
- VAS 5051/5052 Software Support
- For warranty claim input questions, contact your appropriate Warranty Claim specialist.