Introduction - Transverse Lock Control Unit
Transverse interlockIntroduction - transverse lock control unit
Transverse lock
Diagnosis software number: QSP 0101
Cayenne as of model year 2003
General instructions/safety instructions
CAUTION:
Danger of damage due to improper handling of batteries and control unit 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 units 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 unit' when carrying out welding work on the vehicle.
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 transverse lock control unit and Porsche System Tester II No.9588
NOTE:
The following conditions must be met in order to establish communication between the transverse lock control unit 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 approx. 6.5 V
General information on the fault memory
The control unit can store up to (X) different faults simultaneously. If all (X) fault memories are occupied, the new fault overwrites the oldest fault. The fault memory content of the 'transverse lock control unit' is maintained even in the removed state.
Fault code setting conditions
Fault codes can be set in several circumstances, e.g.:
- when disconnecting battery
- when disconnecting plug connections
- fault/incorrect coding
- if the voltage drops
- etc.
In these circumstances, no fault is present in the system and the fault memory must be erased.
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.
- Observe the fault frequency counter in the Porsche System Tester II No.9588 using the fault memory Info key [F8] under 'Extended fault memory' and draw conclusions about 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 units 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 unit 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 to components and 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 diagnoses. 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.