Corsa B
|
Diagnosis
System Specific Features Trouble Codes Features In a few cases, the diagnostic tester may display a trouble code status or description that looks unfamiliar. Trouble code status and trouble code description are concerned. Trouble Code Status: Instead of the known PRESENT, INTERMITTENT, and NOT PRESENT message, you may read UNKNOWN in the tester display. This tells you that the diagnostic software or control unit contains a piece of incorrect information that is unknown to the diagnostic tester and that it is unable to read or evaluate. Both the trouble code number and the trouble code description are not changed in this case. Trouble Code Description: The diagnostic tester displays a trouble code number that is unknown to the diagnostic software, or the trouble code number and fault symptom do not lead to a plausible result when they are being diagnosed. In both cases, the diagnostic tester will display TROUBLE CODE NOT DEFINED. A combination of both above described messages is also possible. There are basically two reasons for this: the diagnostic program you are using is outdated, or there is a fault in the electronic control unit. All of the above special cases have one thing in common: The corresponding fault cannot be removed by means of a diagnostic tester function.
Service-Programming SPS The new FLASH-Programming makes it possible to cover different software variants with one hardware version of a control unit. System-dependent calibration values, curves and mappings can be programmed into a specific control unit type. In order to program those specific vehicle data into the control unit, you need a diagnostic tester and a TIS (Tech Information System) unit. Up to now, that could only be done by replacing the program memory (EPROM) or even the complete control unit. The newest programming data is published with the TIS CD. Programming Procedure:
• Insert MSC cartridge into diagnostic tester and connect it to the vehicle diagnostic connector. • Start the SPS service programming application. • Download vehicle data and security access from control unit to diagnostic tester. • Connect diagnostic tester to TIS. • Upload vehicle data and security access from diagnostic tester to TIS. • The TIS checks the security access and compares the vehicle data with the data stored on the TIS CD. • If the security check fails or a wrong unit is installed, programming will be interrupted. • If the security check is passed, the relevant data will be copied from the CD to the diagnostic tester. • Connect the diagnostic tester with the required program copy to the vehicle. • The program download to the control unit is executed. • The SPS service programming procedure is completed, the diagnostic tester recognises whether the data has been properly transferred or not.
Service-Programming SPS The diagnostic tester together with the MSC cartridge is the interface between the storage device (TIS with latest CD) and the control unit to be programmed. A direct connection between TIS and control unit is not possible. Note: After service programming the control unit must be labelled with the current calibration identifier. |
