Operation CHARM: Car repair manuals for everyone.

Transmission Control Systems: Application and ID

Tiptronic

Introduction

Tiptronic (automatic transmission)
Diagnosis software number: G 0210
Cayenne model year 2003

General instructions/safety instructions

CAUTION:
Danger of damage due to improper handling of batteries and control module plug connections.
- Never disconnect battery with engine running.
- Never start engine if battery terminal clamps are not connected securely.
- Never pull off or push on plug connections for the control modules or other electronic components when the ignition is switched on
- Always disconnect the negative terminal of the battery and pull off all plug connections to the 'vehicle electrical system control module' when carrying out welding work on the vehicle.


DANGER:
Danger of burns from hot ATF fluid.
Skin or clothing may burn following contact with hot ATF fluid.
- Always allow ATF fluid to cool before draining.
- Wear suitable protective clothing.
- Use a suitable collecting container.


WARNING:
Danger of injury and damage due to unusual vehicle handling when plugs or components are disconnected.
- Never disconnect plugs when the vehicle is in motion or drive the vehicle with plugs disconnected.
- Drive only with all parts fully installed and connected.


Communication between Tiptronic control module and Porsche System Tester II No. 9588

NOTE:
The following conditions must be met in order to establish communication between the Tiptronic control module and the Porsche System Tester II No. 9588:
- Porsche System Tester II No. 9588 connected to data link connector
- The battery voltage must be greater than 6.5 V

General information on the fault memory
The fault memory of the control module can save up to (80) different faults simultaneously. If the fault memory is full, the new fault overwrites the oldest fault. The fault memory content of the 'Tiptronic control module' is maintained even in removed state.

Fault code setting conditions
Fault codes can be set in various circumstances, e.g.:
- battery disconnected
- plug connections disconnected
- faulty coding
- power failure
- etc.

In these circumstances, no fault is present in the system and the fault memory must be erased.

Standard fault codes in accordance with ISO 15031
Diagnostic fault codes, which can be issued by the control module, are standardised in accordance with ISO 15031. This ISO standard is based on SAE J 2012.

The fault code (DTC = Diagnostic Trouble Code) is always a 5-character alphanumeric value, e.g. "P0100".

The first character of the code (a letter) identifies the system that set the code. In all, there are 4 system types:
- P for Powertrain (all OBD2 fault codes begin with this)
- C for Chassis
- B for Body
- U for future systems.

The P codes for powertrain are divided into two main categories in accordance with ISO 15031:
- Uniformly standardised codes: P0XXX and P2XXX; these are the same for all manufacturers
- Manufacturer codes: P1XXX and P3XXX; only the first three characters are standardised here (example: P13XX for ignition system diagnosis or misfire detection), the last two digits can be selected freely by the manufacturer.

Only the P codes are required for OBD II.

The standardised codes are subdivided as follows:

P001 to P0299 Fuel and air proportioning
P03xx Ignition system and misfire detection
P04xx Additional exhaust regulations
P05xx Speed and idle speed control
P06xx Computer and output signals
P0700 to P0999 Transmission

P2000 to P2299 Fuel and air proportioning
P23XX Ignition system and misfire detection
P24XX Additional exhaust regulations
P25XX Additional input signals
P26XX Computer and output signals
P27XX Transmission
P28XX Reserved
P29XX Fuel and air proportioning

Troubleshooting procedure
Troubleshooting can only be performed when the fault is present. In other words, specific troubleshooting can only be performed in accordance with instructions (given under Diagnosis/troubleshooting for each fault code) if the entry has the status 'present' in the fault memory.

If the fault is currently 'not present', please check the following:
- Diagnostic conditions are met
- All plug connections and ground points of the affected current path are OK.
- View the fault frequency counter in the Porsche System Tester II No. 9588 using the fault memory Info key [F8] under 'Extended fault memory' and try to reach conclusions about eliminating any loose contacts in the system.

Diagnostic conditions

NOTE:
IMPORTANT: Always connect a suitable battery charging device to the vehicle electrical system battery before starting diagnosis. All unnecessary loads must also be switched off.

NOTE:
The fault can only be identified if the requirements listed under 'Diagnostic conditions' are met. For this reason, the specified procedure must be observed after a fault is repaired:
1. Erase fault memory
2. Satisfy the requirements listed under 'Diagnostic conditions'.
3. Read out fault memory again

Possible causes of fault

NOTE: The 'possible causes of fault' that are responsible for the fault are listed here. Please note that in certain circumstances further faults can be stored in the fault memory after troubleshooting (e.g. if plugs are disconnected). After carrying out repairs, read out the fault memory of all control modules and erase any faults.

Diagnosis/troubleshooting

NOTE: The fault memory Info key [F8] on Porsche System Tester II No. 9588 can be used to access the 'extended fault memory'. The following information can be displayed:

Fault type
The following fault types are possible:
- no display
- upper limit value exceeded
- lower limit value not reached
- mechanical fault
- no signal/communication
- no or incorrect basic setting/adaptation
- short circuit to B+
- short circuit to ground
- implausible signal
- open circuit/short circuit to ground
- open circuit/short circuit to B+
- open circuit
- electrical fault in electric circuit
- please read out fault memory
- faulty
- cannot be checked now

Fault status
The following status types are possible:
- present
- not present

This information should be saved using the Save key [F4] and printed out.

NOTE:
Visual inspection: During troubleshooting, please check first that the affected pins on the control module plug connection are neither damaged nor corroded. The wires and plugs of the affected components must also be checked for external damage and correct contacts. Repair damaged or corroded pins it possible, otherwise replace affected pins. Repair or replace damaged wires.

NOTE:
Battery voltage: A battery voltage of between 11.4 and 14.5 V is required for troubleshooting. This must be checked and provided if necessary. Voltages as well as components or fuses (input side) must be guaranteed on the vehicle electrical system.

Freeze frame (frozen fault boundary conditions)
Freeze frame data is standardised and records operating conditions in the event of a fault. Freeze frames have different priorities, which can be important when output to a Scan Tool. These can be viewed in the "extended fault memory" of the Porsche System Tester II No. 9588.

Furthermore, various operating conditions can be stored for each fault. These can provide reference points for determining the cause of a fault in the case of difficult diagnosis. These can be viewed in the "extended fault memory" of the Porsche System Tester II No. 9588.

Fault deletion counter
An individual deletion counter runs for every fault detected. It determines the storage duration of the related fault.

When a fault is first detected, the deletion counter is set to 80, for example (suspected fault).

If a non-persistent fault is detected as having been remedied, the deletion counter is set to 10, for example (fault did not occur often enough to be confirmed).

Whenever a persistent fault is detected, the deletion counter is set to 40, for example. This value is retained until the fault is detected as having been remedied.

The deletion counter is decremented by 1 after every warm-up cycle if the fault in question is a non-persistent fault or is detected as having been remedied (faults that are confirmed, but are not detected as having been remedied are not decremented in the deletion counter). If the deletion counter reaches the value 0, the fault is deleted from the memory.

Fault frequency counter
This counter shows how often a fault has recurred following its first occurrence. If the frequency value is 1, the fault has only occurred once. It can now be either "present" or "not present". The fault frequency counter is incremented whenever this fault recurs (the fault correction counter was decremented in the meantime, i.e. a check was performed and found to be OK). A higher value in the fault frequency counter can therefore indicate a loose contact.