00 09 07 (371) Specified Process For Diagnosis
00 09 07 (371) Specified Process For Diagnosis
BMW, MINI
Situation:
The programs and documents in the BMW diagnosis systems contain information about troubleshooting on vehicles of the BMW Group. The technical contents have been agreed both within the BMW Group and with suppliers
Professional repairs on vehicles are only guaranteed if this information is observed and the operations involved in a repair are performed in accordance with the instructions given.
In the event of a warranty or goodwill claim, incorrectly performed diagnosis can lead to the reimbursement for the examination or repair not being accepted in its entirety or at all.
Procedure:
Diagnosis programs are available for all electric and electromechanical vehicle systems. In addition, there are diagnosis programs for purely mechanical systems and fault patterns (e.g. unwanted noise).
Troubleshooting with the BMW diagnosis system is necessary whenever:
a. The fault is in the functional area of the electric components (= components connected to the wiring harness)
b. The fault is in the area of the drive system (engine or automatic transmission)
c. The fault has caused a Check-Control message or an indicator lamp to light up
d. A corresponding instruction (Service Information bulletin, PuMA action or similar) has been given to perform diagnosis on a mechanical system
Correct diagnosis application is essential if all information needed for troubleshooting and the subsequent repair to the vehicle.
Overview of diagnosis procedure
1. Connect BMW diagnosis system to the network.
2. Connect vehicle / start diagnosis.
3. Perform
4. In the event of a specific customer complaint, select the appropriate fault pattern in the fault pattern selection.
5. Work through the DIS testing schedule .
Notes on working through the DIS testing schedule :
- Evaluate stored fault
- Perform test modules
- Observe current technical information
6. If the fault could not be located, draw up and work through your "own testing schedule".
Notes on processing your "own testing schedule":
- Use control unit functions
- Perform test modules
- Observe current technical information
7. Rectify faults and perform function test.
8. Clear all fault memories with
Diagnosis procedure
Note the following points when performing diagnosis:
1. Starting diagnosis
The current software status for diagnosis programs, including program and data updates must be loaded in the BMW diagnosis system.
The BMW diagnosis system must be connected to the workshop network so that diagnosis data can be transmitted to BMW AG. If the Group Tester
One is used outside the workshop environment, the BMW diagnosis system must be reconnected to the workshop network after at most 40 diagnosis sessions to that the data stored in the equipment can be transmitted.
NOTE: Diagnosis data recorded during troubleshooting are important information for BMW's quality processes. Moreover, the diagnosis protocol is verification that diagnosis has been properly performed. Warranty claims may be rejected if there is no diagnosis protocol (cf. current warranty guidelines).
2. Brief test
After vehicle identification, a
NOTE: Because of the increasing degree of networking of vehicle systems, it is not enough to simply read off the fault memories of individual control units when troubleshooting, as faults affecting several systems (e.g. bus errors) are evaluated and analysed by more than one control unit.
3. Fault pattern selection
In the event of a specific customer complaint, first perform a brief test to check whether a corresponding fault pattern is available in the fault pattern selection. This fault pattern must be selected with
NOTE: Fault pattern selection contains known fault patterns caused by software errors, mechanical faults and faults that do not cause a fault memory entry.
4. Working through the "DIS testing schedule"
Based on the faults stored in the vehicle and the selected fault patterns, the diagnosis system will draw up a testing schedule, the so-called "DIS testing schedule".
In the test modules listed in the "DIS testing schedule", first check which test modules are directly associated with the customer complaint or the identified malfunction. These test modules should be called up and worked through with priority.
Once started, test modules must be completely processed. Processing is only completed when the message "Test module completed. Continue in testing schedule" is given and you return to the testing schedule with the right arrow key.
If the diagnosis user is prompted in the test module to send feedback about the test result obtained, this prompt must be followed.
A test module may only be cancelled prematurely is one of the following reasons is given:
a. Test module was selected by mistake
b. Programming error makes cancellation necessary
Test modules that are obviously not directly associated with the customer's complaint or the malfunction identified should be ignored (please refer to section 5. Dealing with stored faults).
The "DIS testing schedule" is completed when:
a. The cause of the fault has been identified
or
b. No malfunction or component fault can be identified with the test modules listed in the testing schedule.
5. Dealing with stored faults
For technical reasons, it can happen that a control unit stores a fault even though no malfunction can be detected. Moreover, faults may be stored in the vehicle whose causes have already been eliminated.
For this reason, it is not uncommon for faults to be stored that are not directly associated with a customer complaint or with an identified fault pattern, especially on high-mileage vehicles. When performing diagnosis, you should therefore use the fault memory details to check which fault memory entries can be ignored.
The following fault memory details are especially significant here:
- Current fault status (fault currently present / not currently present)
- km reading (time) of last occurrence of the fault
- Fault frequency
Replacing a component on the basis of the fault memory entry is only justified if the fault memory details clearly show that the stored fault is directly associated with the customer complaint or the fault pattern.
6. Drawing up and processing your "own testing schedule"
Your "own testing schedule" can be used to select test modules for checking functions and component on the basis of your own experience.
This is always advisable when the cause of the fault cannot be identified unambiguously with the "DIS testing schedule". The test modules are selected in the
The following rules apply when performing test modules:
- Once started, test modules must be completed (please refer to section 4. Working through the "DIS testing schedule").
- Premature cancellation is only permissible if a test module was selected by mistake or if a programming error is present.
- If the diagnosis user is prompted in the test module to send feedback about the test result obtained, this must be followed.
Your "own testing schedule" is completed when the cause of the fault has been identified or when no function or component faults can be detected using the test modules in the testing schedule.
7. Use of control unit functions
The
Using the control unit functions is not however a substitute for performing the test modules, as the control unit functions ...
- ... do not contain detailed information or instructions.
- ... do not contain all diagnosis and testing options for the functions and components.
8. Observing current technical information
In addition to the diagnosis programs, information about current technical problems are published through special media and systems (e.g. Service Information bulletins or PuMA actions). It is essential that such information is also taken into account when performing vehicle diagnosis. At the latest when replacing components, it must be checked whether any additional information is available.
If the repair/servicing actions recommended in the test module differ from the current information, this should be noted in the remarks field on the warranty or goodwill claim.
9. Quick delete
After identifying a fault and repairing the faulty components, all faults stored in the vehicle must be cleared with the
NOTE: As not all fault memory entries are shown by the service diagnosis programs or a summary of fault groups is given (e.g. bus faults), only the
10. Reporting faults in diagnosis programs
If during diagnosis faults are identified in the diagnosis programs or documents, these must be reported through the known feedback channels.
Benefits for the dealerships in the BMW dealer organisation
System-based diagnosis is the most important tool available to workshop staff in the dealer organisation.
Increasingly complex systems and their networking within modern BMW automobiles make fault elimination without electronic diagnosis systems increasingly more difficult or even impossible.
Correct diagnosis application gives the dealerships in the BMW dealer organisation important competitive advantages. These are described below:
- The high degree of networking between the increasing number of control units means that when faults occur, the relationship between fault cause and effect can no longer be intuitively identified.
This means that the cause and effect of a fault may be found in different vehicle components.
Diagnosis unearths these complex relationships and supports the fast and direct search for the cause of a customer complaint.
- Relying on experience and repair procedures practiced for years increasingly results in unnecessary work being performed, and may even fail to produce a lasting fault elimination.
Ongoing adaptation and expansion of diagnosis mean that fault elimination in the dealerships of the dealer organisation are constantly updated on the basis of knowledge gained in the worldwide quality improvement processes for vehicle and workshop systems.
This applies in particular to essential electric, electronic and electromechanical systems in the vehicle.
But purely mechanical systems are also increasingly being covered by diagnosis.
- The complex documentation needed for processing warranty claims can result in queries and delays in reimbursement if diagnosis is not used or if diagnosis data is not transmitted.
When performing diagnosis with the BMW diagnosis system, diagnosis data are automatically generated. These can be evaluated by the specialists at BMW AG and then used to derive measures aimed at the continual improvement of tester diagnosis.
- Fast, direct and lasting elimination of faults is the most important basis for the reputation of a dealership and thus for long-term customer loyalty.
The lower the number of unscheduled vehicle failures and the shorter the resulting downtimes are kept, the more trustworthy and competent the dealer appears in the eyes of the customer.