LEMON Manuals: Even more car manuals for everyone
Home >> Audi >> 2017 >> A7 Quattro Competition >> Repair and Diagnosis >> External Pages >> Different car >> Section 109 (Fuel Injection System (Diesel - Service Information - TDI 3.0L - CPNB)) >> 23 Diesel Fuel Injection >> Engine Control Module >> Wiring And Components

Wiring And Components

WARNING: This page is about a different car, the 2016 Audi A7 Quattro. However, it is still accessible from the selected car via links, so may be relevant.

Special tools and workshop equipment required 

NOTE:

Always make sure the cables are connected correctly.

Never use any damaged or worn tools or accessories.

See operating instructions.

-- Connect both the :VAS6606/7-1  and :VAS6606/7-2  completely to the three :VAS6606  .

-- Use the following sheets:

NOTE:

Make sure all connection bridges are connected completely on all breakout boxes.

-- Connect the Ground (GND) wire to a breakout box and to a GND point on the vehicle.

-- Remove the Engine Control Module (ECM). Refer to Engine Control Module -J623-, REMOVING AND INSTALLING .

-- Connect the ECM to the :VAS6606/7-1  .

-- Connect the wiring harness from the vehicle to the :VAS6606/7-2  .

The connection on the ECM consists of a large and small connector.

The large connector has 105 pins and is assigned from "A 1 through A 105" on the breakout box sheet.

The smaller connector has 91 pins and is assigned from "B 1 through B 91" on the breakout box sheet.

The connection will get interrupted when the connection bridge is disconnected.

NOTE:

The "In contact" -1- (red socket) goes to the ECM.

The "Out contact" -2- (blue socket) goes to the wiring harness.

GWWA24-10954Courtesy of AUDI OF AMERICA, LLC

-- Perform test as described in relevant repair sequences.

Installing the ECM 

Install in reverse order of removal.

The procedures to follow after connecting the new ECM are described in Guided Fault Finding  and Guided Functions  . Use a Vehicle Diagnostic Tester.

NOTE:

When ending Guided Fault Finding  , the tester attempts to erase the Diagnostic Trouble Code (DTC) memory of all control modules. If this is not successful, the remaining DTCs stored in memory must be corrected until all DTCs can be erased.