DD4-2 Diagnostico Frenos DW63239201 - DD4 - 2

Trainer document/guide:
Diagnostic methodology: Brakes, DD4/2

©201629 DAF Trucks N.V., Eindhoven,
The Netherlands.
In the interest of continuing product development,
DAF reserves the right to change specifications
or products at any time without prior notice.
No part of this publication may be reproduced
and/or published by printing, by photocopying, on
microfilm or in any way whatsoever without the
prior consent in writing of DAF Trucks N.V.
The content of this training material is solely
meant for training purposes and can therefore not
be used for actual “life” situations. The
information in this document is subject to
changes. For the correct chassis specific
technical data it is imperative to consult the
service documentation via Service Rapido.
©
201629 DW63239201
STRUCTURE
TRAINING SUPPORT INFORMATION

Structure
©
201629
Table of contents
TABLE OF CONTENTS
Training support information
Page Date 0
1. HOW TO USE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 . . . . . 201629
1.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1 . . . . . 201629
1.2 Icon definition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2 . . . . . 201629
2. TRAINING CHARACTERISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 . . . . . 201629

2.1 Learning objectives DD4/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 . . . . . 201629
2.2 Brief description DD4/2 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-2 . . . . . 201629
3. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 . . . . . 201629

3.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 . . . . . 201629
4. DIAGNOSTIC VEHICLE INFORMATION FILE. . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 . . . . . 201629

4.1 Diagnostic vehicle information file . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 . . . . . 201629
5. FAULT FINDING CASES / PREPARATION INFORMATION . . . . . . . . . . . . . . 5-1 . . . . . 201629

5.1 Fault finding case: EBS-3 DTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1 . . . . . 201629
5.2 Fault finding case: EBS-3 DTC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-4 . . . . . 201629
5.3 Fault finding case: Brake performance . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-6 . . . . . 201629
5.4 Fault case: Trailer Modulator. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-13 . . . . 201629
5.5 Fault case: Front axle modulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-17 . . . . 201629
5.6 Fault case: Rear axle modulator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-18 . . . . 201629
6. REQUIRED MATERIALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 . . . . . 201629

6.1 Room arrangements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 . . . . . 201629
6.2 Required material for the trainer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2 . . . . . 201629
6.3 Required material for the participants . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-3 . . . . . 201629
6.4 Required training material to support the training . . . . . . . . . . . . . . . . . . . 6-4 . . . . . 201629
©
201629 1
Table of contents
©
2 201629
How to use
1. HOW TO USE
1.1 INTRODUCTION 0
This document contains practical cases, which
can be used to support an in-depth practical
diagnosis training.
The practical cases must be carried out and
solved according to the DAF Diagnostic
Methodology (GE2/3).
Because the in-class training only consists of
solving fault finding cases, a trainee document is
not applicable and for this reason not available.
NOTE: Always consult Service Rapido
for the correct technical data,
diagnostic procedures and repair
instructions!
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
©
201629 1-1
How to use
1.2 ICON DEFINITION

0 The icons included in this document have the
following meaning:
Animation on e-Campus trainer site
On the e-campus trainer site, an E-presentation is available on the subject.
Question/assignment
This is a question/assignment for the student. This question/assignment is also in-
cluded in the trainee document.
Practical assignment
Practical assignment for the trainee.
Teaching method
Recommendation for the teaching method.
Practical explanation/demonstration for the entire group.
Notes
Space for writing notes.
©
1-2 201629
Training characteristics
2. TRAINING CHARACTERISTICS
2.1 LEARNING OBJECTIVES DD4/2 0
On completion of this training module, the
following learning objectives are achieved.
The student is able to:
Knowledge
- state the purpose and significance of the
DAF diagnostic methodology flow chart.
Understanding
- understand the importance of a correct use
of complaint handling for the customer.
Application
- apply the DAF diagnostic methodology in the
correct sequence.
- apply the DAF diagnostic methodology to
solve the customer complaint.
Analysis/diagnostics
- collect and investigate the information
needed for each step in the DAF diagnostic
methodology.
- analyse the data information and
measurement results.
- locate and resolve the fault which caused the
customer complaint.
©
201629 2-1
Training characteristics
2.2 BRIEF DESCRIPTION DD4/2

0 This training module contains the following
topics:
- fault finding on brake systems according to
the DAF diagnostic methodology.
Training method
- Classroom and practical based
©
2-2 201629
Introduction
3. INTRODUCTION
3.1 INTRODUCTION 0
Purpose
The DAF Diagnostic Methodology is the method
for a structured and logical way to solve customer
complaints.
The DAF Diagnostic Methodology results in
efficient process steps, effective fault-finding and
repair of electrical, electronic and mechanical
systems.
NOTE: The term 'service advisor'
discussed in these chapters can be
anyone who meets the specific role in
the process.
By applying the DAF Diagnostic Methodology,

the service advisor is able to perform the
diagnosis and document it.
Structured documentation makes sure that the
diagnosis, carried out by the organisation, is the
same in each workshop which ensures
consistency and is clear and understandable to
the customer.
The DAF Diagnostic Methodology prevents
unnecessary work, emerged from wrong
thoughts, it is always possible to return to the
point where the work made progress.
A properly executed diagnosis has a positive
influence on:
- The processes in the workshop
The work can be taken over from another
colleagues, it is clear what all the colleagues
had done in the process.
You can always see what the colleagues did
in what step, so if there rises a question, you
can directly contact the right person.
- first-time right
A proper executed diagnose helps
increasing first-time right repairs and bring
down the down-time.
- clear explanation of the work done
Once the DAF Diagnostic Methodology is
finished, every step in the process is
documented en therefore easy to process in
the invoice administration.
- customer satisfaction
The quality of the customer feedback
improves and gives better information
regarding the solution of the concern, or
extra information not related to the concern.
©
201629 3-1
Introduction
0 Vehicle ID Card
does not match
c 1. Identify vehicle
o VCD update required
n Contact Service Helpdesk Vehicle ID Card matches
c
e
r Non-reproducable concern
n 2. Understand & Verify customer’s concern
Reproducable concern
Operates as designed
3. Customer expectation mismatch
Does not operate as designed
Abnormality identified
Contact Service Helpdesk

4. Perform visual and operational primary checks
No abnormality identified
c
a
u
s 5. Perform diagnostic quick check
e
Publication identified
6. Check for relevant bulletins
No publication identified
7.1 Identify cause

-Rationality type 7.2 Identify cause
DTC -Communication 7.3 Identify cause 7.4 Identify cause
concern or DTC -Plausibility type 7.5 Identify cause
DTC -Symptom no
DTC -No published
diagnostics
c
o
r
r 8. Repair & Validate remedy
9. Re-examine customer’s
e concern
c
t Concern solved Concern not solved
i
o
n 10. Provide feedback to customer of findings
G005010-5
©
3-2 201629
Introduction
Sequence of the steps

The sequence of the DAF Diagnostic
Methodology is based on:
0
- Processes in the workshop
The steps are based on the normal
workshop processes
- Easy steps first
To prevent that simple concern are
overlooked.
The DAF Diagnostic Methodology is divided in
three phases: c
Vehicle ID Card
does not match
1. Identify vehicle
- 'Concern' represented in yellow. This phase o
n
VCD update required
Contact Service Helpdesk Vehicle ID Card matches
gives an overview: c
e
To make sure that the diagnostic information

r Non-reproducable concern
n 2. Understand & Verify customer’s concern
is relevant and specific for this vehicle. Reproducable concern
To understand the customers concern and Operates as designed

3. Customer expectation mismatch
can it reproduced Does not operate as designed
- 'Cause' represented in blue. This step gives

an overview:
Abnormality identified
Contact Service Helpdesk

4. Perform visual and operational primary checks
To make sure that the vehicle operates as c

a
No abnormality identified
designed or not u
s 5. Perform diagnostic quick check
To identify if there are abnormalities, or not e
To check if there is publication available for Publication identified

this specific problem, yes or no 6. Check for relevant bulletins
Of the DTC's No publication identified
- 'Correction' represented in green. This step 7.1 Identify cause

-Rationality type 7.2 Identify cause
gives an overview of: DTC -Communication 7.3 Identify cause
concern or DTC -Plausibility type 7.4 Identify cause
-Symptom no 7.5 Identify cause
The concern that is solved or not

DTC -No published
DTC
diagnostics
Feedback provided to the customer c

o
r
r 8. Repair & Validate remedy
9. Re-examine customer’s
e concern
c
t Concern solved Concern not solved
i
o
n 10. Provide feedback to customer of findings
G005148-3
©
201629 3-3
Introduction
flow chart (without text)

0
1.
2.
3.
4.
5.
6.
7.1
7.2
7.3
7.4
7.5
8. 9.
10.
G005184
©
3-4 201629
Introduction
The image above represents the DAF

Diagnostic Methodology flow chart (no
text). Write down in your own words the 0
meaning of every step.
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
©
201629 3-5
Introduction
©
3-6 201629
Diagnostic Vehicle Information File
4. DIAGNOSTIC VEHICLE INFORMATION FILE

4.1 DIAGNOSTIC VEHICLE INFORMATION FILE 0
To support the process of the diagnostic
methodology, a 'Diagnostic vehicle information
file' must be filled in.
Step 1: Identify vehicle
Name: ………..................................................................................
To make sure that the diagnostic information is relevant and specific for this vehicle.
Customer name:
Chassis number:
Mileage:
Date:
Complaint description:
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
Step 2: Understand & verify customer’s concern
Name: ……….................................................................................. (same as step1) □

To enable validation of the remedy at the final step of the diagnostic method.
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
©
201629 4-1
0 Step 3: Customer expectation mismatch
Name: ……….................................................................................. (same as step1) □

To verify if the vehicle operates as designed or not and therefore if the concern is valid or not.
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
Step 4: Perform visual and operational primary checks
Name: ……….................................................................................. (same as step1) □

To identify if something “obvious” is causing the previously validated concern.
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
Step 5: Perform diagnostic quick check
Name: ……….................................................................................. (same as step1) □

To investigate commonalities in the faults and warning messages and set priorities to identify the cause
of them.
DTC: System: Description:
©
4-2 201629
Step 6: Check for relevant Bulletins

Name: ……….................................................................................. (same as step1) □
0
To identify whether this is a “known concern” for which a bulletin with solution is available.
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
Step 7.1: Identify cause - Rationality type DTC
Name: ……….................................................................................. (same as step1) □

A Diagnostic Trouble Code related directly to a component of which one or more parameters is found to
be incorrect.
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
Step 7.2. Identify cause - Communication concern or DTC
Name: ……….................................................................................. (same as step1) □

Communication concerns or DTCs provide a communication disorder in the vehicle communication
network.
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
©
201629 4-3
0 Step 7.3. Identify cause - Plausibility type DTC
Name: ……….................................................................................. (same as step1) □

The plausibility type DTC is used for failures where the ECU compares two or more input parameters for
plausibility.
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
Step 7.4. Identify cause - Symptom - no DTC
Name: ……….................................................................................. (same as step1) □

With this type of concern the technician must come to a list of suspected components or systems.
After analysing the information obtained and the diagnosis-related information in Service Rapido the
symptom must be reproduced by taking tests and measurements.
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
Step 7.5. Identify cause - no published diagnostics
Name: ……….................................................................................. (same as step1) □

The cause must be identified with the information provided from the customer and by tests and meas-
urements.
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
©
4-4 201629
Step 8: Repair and validate remedy
Name:
Step 9: Re-examine customer' s concern
Name:
0
................................................... (same as step1) □ ................................................ (same as step1) □
Step 10: Provide feedback to customer of findings
Name: ……….................................................................................. (same as step1) □
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
Step 11: Customer recommendations
Name: ……….................................................................................. (same as step1) □
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
...................................................................................................................................................
©
201629 4-5
0 Component tests Measured value Checking data value Service Rapido
©
4-6 201629
Fault finding cases / preparation information
5. FAULT FINDING CASES / PREPARATION INFORMATION

5.1 FAULT FINDING CASE: EBS-3 DTC 0
Fault finding case Training module Date
DD4/2 Diagnostic methodology; Brakes DD 4/2 25/02/2016
Training material / support used for the test case

Vehicle series and type XF_E6, FT
Chassis number 0E986120
Component front axle modulator (D377)
System EBS-3
Description of the complaint or the

instruction related to the test case
Red EBS-3 warning and yellow VSC warning on
the display DIP-5..
NOTE:
- Occurrence of warnings depends
on the vehicle (execution of
systems)
- Root cause is a bad earth
connection (wire 9164) of the front
axle modulator (D377)
- DTC 924-1
Use the diagnostic methodology steps

and method plan.
Failure description
The EBS-3 system generates a warning when the
brake pedal is pressed.
©
201629 5-1
Preparation of the failure

0
S705021
- Connect the training brake out box 1903015
to the vehicle.
- Locate connector 78H and connect the
training brake out box.
- Remove bridge 1 and replace with resistor
(self-made).
- Resistor self-made (example: WH50,
27R5%)
R605103
©
5-2 201629
- Connect mini brake out box.

- Measure the voltage loss in earth connection
(wire 9164) of the front axle modulator 0
(D377)
R605104
Necessary tools
- DAVIE4 diagnostic tool
- Training brake out box 1903015
Additional information
The collected information should include:
- Fault codes and session report
- Warning history DIP-5 (stored in report)
NOTE:
©
201629 5-3
5.2 FAULT FINDING CASE: EBS-3 DTC

0
Training material/support used for the test case

System EBS-3

Red EBS-3 warning and yellow VSC warning on
the display of DIP-5.
NOTE:
- Occurrence of warnings depends
on the vehicle (execution of
systems)
- Root cause is interruption wire
3934 (CAN-L) of the front axle
modulator (D377)
- DTC 904-8 / 1047-9 / 3198-8

and method plan.
Failure description
The EBS-3 system generates a warning in the
moment the brake pedal is pressed.
to the vehicle.
- Locate connector 78H and connect the
training brake out box.
- Disconnect bridge 17.
to the vehicle.
- Disconnect bridge 17.
©
5-4 201629
- Connect mini brake out box.

- Measure the CAN signal of the front axle
modulator (D377) 0
R605104
Necessary tools
- Training brake out box 1903015
- Oscilloscope
The collected information should include:
- Fault codes and session report
- Warning history DIP-5 (stored in report)
- Analyse measurement with the aid of an
oscilloscope
NOTE:
©
201629 5-5
5.3 FAULT FINDING CASE: BRAKE PERFORMANCE

0

Component Unknown
System EBS-3

NOTE:
- Drivers concern: 'Brake
Performance Low' during braking.
After releasing brake pedal the
message disappeared.
- DTC 1070-7
Failure description
- EBS-3 activates the warning 'Brake
Performance Low'.
and method plan

NOTE: IMPORTANT:For this
assignment it is not necessary to use
truck/trailer combination to set this
brake performance warning. It is
possible to carry over the information
included in this case in class. This
assignment will be supported by:
- A warning log report

- A session report
- A Davie monitor recording made during the
drive session
During the drive session the next steps were
taken to set the warning 'Brake Performance
Low':
- Connect a trailer with a conventional brake
system.
- Connect DAVIE4 and start the EBS-3
monitor.
- During the test the service brakes were
activated for several times under pre defined
set conditions.
©
5-6 201629
- After the adaption phase (A) the combination

stopped and the first axle of the trailer was
pneumatically disconnected. 0
- During the next brake events (C, D and E)
the pressure levels changed to a higher
level.
NOTE: The used set conditions during
test drive:
- Start speed at the beginning of the
brake event is 50 km/h
- Brake pedal stroke during brake
event 30 %
R605106
CAUTION: If truck is equipped with

AEBS, driving with non ABS trailer is
not permitted!
©
201629 5-7
Report warning logger DAVIE4

0 After the drive session the warning logger data
was collected from VIC-3 and saved in the
report..
R605105
- Row 14: 'Brake Performance Low':
Occurrence: 1 time.
©
5-8 201629
Session report
After the drive session the warning logger data
was collected from VIC-3 and saved in the
0
warning logger report..
R605105
- Row 14: 'Brake Performance Low':
Occurrence 1 time.
©
201629 5-9
Test results roller brake test bench

0 Truck
R605107
©
5-10 201629
Trailer
0
R605108
Necessary tools
The participant must make a 'step by step' plan
how to solve the problem.
©
201629 5-11
NOTE:
0
©
5-12 201629
5.4 FAULT CASE: TRAILER MODULATOR.

0
DD4/2 Diagnostic methodology: Brake systems, DD4/2 1/03/2016

Vehicle series and type XF_E6, FT/ CF_E6, FTP/ LF_E6, FA
Chassis number 0e986120 / 0e989618 / 0L434510
Component Trailer modulator (D380)
System EBS-3

The trailer is in redundancy mode. The EBS-3
system will set a fault in the main display of DIP-5.
Use the DIAGNOSTIC
METHODOLOGY STEP AND
METHOD plan.
After execution of this practical case the
participant is able to:
- Read out DTC information, save
DTC information and analyse the
DTC information,
- Locate the cause of the problem,
- Measure and understand the input
of the component involved using
Fluke 123,
- Locate the correct wiring diagram
and locate the components and
wiring involved,
- Clear the DTC memory and save
the DTC data,
- After repair, check the functionality
of the component involved.
Failure description
- Yellow EBS truck warning,
- The trailer circuit is in backup mode,
- DTC EBS-3 trailer modulator 1058 -4.
©
201629 5-13

0 CF/XF vehicle
G001663-2
- Connect DAVIE to the vehicle and erase the
DTCs,
- Locate the wire 3616 in the bulkhead or use
the Front Connection Box (FCB),
- Disconnect wire 3616 from location 56H:23,
- Switch contact on, wait for warning on the
main display DIP-5,
- Connect DAVIE and read out the DTC
information.
NOTE:
- Save the DTC information and
read the pdf information.
- Check and save the freeze frame
data,
- Check the DTC in Service Rapido,
- Check the pressure sensor trailer
modulator (D378),
©
5-14 201629
- Measure the output on the EBS-3 ECU
-
(D376),
Measure the input on the trailer modulator 0
(D378),
- Locate and repair the broken wire,
- Check the functionality of the trailer
modulator,
- Erase the DTCs
©
201629 5-15
LF vehicle
0 AA AB AC AD AE AF
BA BB
CA CB CC CD CE CF
DA DB
EA EB EC ED EE
FA FB FC FD FE
GA GB GC GD GE
HA HB
JA JB JC JD JE
1A 1B 1C 1D 1E 1F 1G
2A 2B 2F
3A 3B 23D 23E
E504762-4
©
5-16 201629
-
DTCs,
Locate the wire 3616 in the bulkhead, 0
- Disconnect wire 3616 from location 1D:5,
main display DIP-5,
information.
Necessary tools
- Break-out box bulkhead connectors,
- Extension tool,
- DAVIE diagnostic tool,
- Fluke 123.
The technician must plan how to solve the
problem using the DIAGNOSTIC
METHODOLOGY STEP AND METHOD plan.
NOTE:
©
201629 5-17
5.5 FAULT CASE: FRONT AXLE MODULATOR

0

System EBS-3

The front axle modulator (D377) is replaced by a
new one. While testing the front axle modulator
(D377) it generates a DTC.
Failure description
Front axle modulator (D377).
and method plan.

Swap the lines (2) on the front axle modulator
(D377) to the ABS modulators .
Necessary tools
The participant must find the problem by testing
the front axle modulator / ABS valves.
NOTE:
©
5-18 201629
5.6 FAULT CASE: REAR AXLE MODULATOR

0

Component Rear axle modulator (D378)
System EBS-3
Failure description
The rear axle is in redundancy mode. The EBS-3
system will set a fault in the main display of DIP-5.
and method plan.

After execution of this practical case the
participant is able to:
- Read out DTC information, save DTC
information and analyse the DTC
information,
- Locate the cause of the problem,
- Measure and understand the input of the
component involved using Fluke 123,
- Locate the correct wiring diagram and locate
the components and wiring involved,
- Clear the DTC memory and save the DTC
data,
- After repair, check the functionality of the
component involved.
NOTE: There is a warning on the main
display of DIP-5. The fault must be
located with the help of the tools
included in this description.
©
201629 5-19

0 CF/XF vehicle
G001663-2
DTCs,
- Locate the wire 5158 in the bulkhead,
- Disconnect wire 5158 from location 56H:29,
main display DIP-5,
information.
NOTE:
- Save the DTC information and
read the pdf information.
- Check and save the freeze frame
data,
- Check the DTC in Service Rapido,
- Check the pressure sensor rear
axle modulator (D378),
©
5-20 201629
- Measure the output on the EBS-3 ECU
-
(D376),
Measure the input on the trailer modulator 0
(D378),
- Locate and repair the broken wire,
- Check the functionality of the trailer
modulator,
- Erase the DTCs
©
201629 5-21
LF vehicle
0 AA AB AC AD AE AF
BA BB
CA CB CC CD CE CF
DA DB
EA EB EC ED EE
FA FB FC FD FE
GA GB GC GD GE
HA HB
JA JB JC JD JE
1A 1B 1C 1D 1E 1F 1G
2A 2B 2F
3A 3B 23D 23E
E504762-4
©
5-22 201629
-
DTCs,
Locate the wire 5158 in the bulkhead, 0
- Disconnect wire 5158 from location 23D:15,
main display DIP-5,
information.
Necessary tools
The technician must plan how to solve the
problem.
NOTE:
©
201629 5-23
©
5-24 201629
Required materials
6. REQUIRED MATERIALS
6.1 ROOM ARRANGEMENTS 0
See the requirements on the DAF Academy
share point site, accessible via ePortal (Chapter
"Partners & Facilities").
©
201629 6-1
Required materials
6.2 REQUIRED MATERIAL FOR THE TRAINER

0 - Laptop/desktop
- Projector and projector screen
- Markers for writing on the flipchart/
whiteboard
- Trainer document/guide
- Participant attendance list (TMS)
©
6-2 201629
Required materials
6.3 REQUIRED MATERIAL FOR THE PARTICIPANTS
- Notebook
0
- Name card
- Pen
- Diagnostic vehicle information file
©
201629 6-3
Required materials
6.4 REQUIRED TRAINING MATERIAL TO SUPPORT THE TRAINING

0 This is a summary of the materials required to
support this training module.
Generic training materials are listed in the DAF
Academy sharepoint site (Partner & Facilities).
Required materials:
- All components relevant to this subject.
(EAS-3 module with sensors etc.)
- EAS-3 model to support the theoretical
exercise
- DAVIE diagnostic tool
- Multimeter
- Scope meter Fluke 123
- MX11/MX 13 engine
- Prepared trucks for the practical exercises
(Trucks must be prepared and tested before
the training)
- AdBlue Dosing system Bosch Denoxtronic
2.2
©
6-4 201629
Required materials
Advised materials:
- breakout box for PCI. This tool fits on the PCI
connectors of the PCI for MX-11 and MX-13.
0
- Part number Breakout Box: 1785372
- Part number cable: 1696719
T00210
- PICO scope meter with integrated DAF

software.
I403276
I403277
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
.....................................................................................................................................................
©
201629 6-5
Required materials
©
6-6 201629

DD4-2 Diagnostico Frenos DW63239201 - DD4 - 2

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

DD4-2 Diagnostico Frenos DW63239201 - DD4 - 2

Uploaded by

Copyright:

Available Formats

Trainer document/guide:

Diagnostic methodology: Brakes, DD4/2

TRAINING SUPPORT INFORMATION

2. TRAINING CHARACTERISTICS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1 . . . . . 201629

3. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1 . . . . . 201629

4. DIAGNOSTIC VEHICLE INFORMATION FILE. . . . . . . . . . . . . . . . . . . . . . . . . . 4-1 . . . . . 201629

5. FAULT FINDING CASES / PREPARATION INFORMATION . . . . . . . . . . . . . . 5-1 . . . . . 201629

6. REQUIRED MATERIALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-1 . . . . . 201629

1.2 ICON DEFINITION

2.2 BRIEF DESCRIPTION DD4/2

By applying the DAF Diagnostic Methodology,

Does not operate as designed

Contact Service Helpdesk

7.1 Identify cause

Sequence of the steps

To make sure that the diagnostic information

is relevant and specific for this vehicle. Reproducable concern

To understand the customers concern and Operates as designed

- 'Cause' represented in blue. This step gives

Contact Service Helpdesk

To make sure that the vehicle operates as c

To check if there is publication available for Publication identified

Of the DTC's No publication identified

- 'Correction' represented in green. This step 7.1 Identify cause

The concern that is solved or not

Feedback provided to the customer c

flow chart (without text)

The image above represents the DAF

4. DIAGNOSTIC VEHICLE INFORMATION FILE

Step 1: Identify vehicle

Step 2: Understand & verify customer’s concern

Name: ……….................................................................................. (same as step1) □

0 Step 3: Customer expectation mismatch

Name: ……….................................................................................. (same as step1) □

Step 4: Perform visual and operational primary checks

Name: ……….................................................................................. (same as step1) □

Step 5: Perform diagnostic quick check

Name: ……….................................................................................. (same as step1) □

Step 6: Check for relevant Bulletins

Step 7.1: Identify cause - Rationality type DTC

Name: ……….................................................................................. (same as step1) □

Step 7.2. Identify cause - Communication concern or DTC

Name: ……….................................................................................. (same as step1) □

0 Step 7.3. Identify cause - Plausibility type DTC

Name: ……….................................................................................. (same as step1) □

Step 7.4. Identify cause - Symptom - no DTC

Name: ……….................................................................................. (same as step1) □

Step 7.5. Identify cause - no published diagnostics

Name: ……….................................................................................. (same as step1) □

Step 8: Repair and validate remedy

Step 10: Provide feedback to customer of findings

Name: ……….................................................................................. (same as step1) □

Step 11: Customer recommendations

Name: ……….................................................................................. (same as step1) □

0 Component tests Measured value Checking data value Service Rapido

5. FAULT FINDING CASES / PREPARATION INFORMATION

Training material / support used for the test case

Description of the complaint or the

Use the diagnostic methodology steps

Preparation of the failure

- Connect mini brake out box.

5.2 FAULT FINDING CASE: EBS-3 DTC

Training material/support used for the test case