With Manufacturer's Scan Tool

Diagnosis/Troubleshooting

The fault memory Info key [F8] on the 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.

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

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. On the vehicle electrical system, voltage to the components and fuses (input side) must be guaranteed.

Freeze frame

Freeze frame data is standardised and secures operating conditions in the event of a fault. Freeze frames have varying priorities, this can be significant when outputting to a scan tool. They can be seen in the "extended fault memory" of the Porsche System Tester II No. 9588.

Different operating conditions can also be saved for each fault. These can provide reference points to the cause of the fault in difficult diagnoses. These can be seen 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 memory storage time of the respective fault.

The deletion counter is set to 80 (presumed error), for example, the first time a fault is detected.

If an unshedded fault is recognised as healed, the fault deletion counter is set to 10, for example (fault did not occur often enough to be confirmed).

The deletion counter is set to 40, for example, each time an unshedded error is identified. It retains this value until fault healing is identified.

The deletion counter is decremented by 1 after every warm-up cycle, if it is an unshed fault or a fault that has been identified as healed (faults that have been confirmed but not identified as healed are not decremented in the deletion counter). If the deletion counter has reached the value 0, the fault is deleted from the fault memory.

Fault frequency counter

This shows how often a fault has occurred since the first time it appeared. If the value given is 1, the error has only occurred once. It may therefore be "present" or "not present". Whenever this fault occurs again (in other words, whenever the fault healing counter has been decremented in the meantime, i.e. an OK test took place) the fault frequency counter is incremented. A higher value in the fault frequency counter can therefore indicate a loose contact.