North American Institute

Mack Advanced
Vehicle Diagnostics
M-4b

Instructor Manual

Mack
Advanced
Vehicle
Diagnostic
s
 North American Institute

Mack
Advanced
Vehicle
Diagnostics

Welcome to the Mack Advanced Vehicle Electronics. This course is designed to teach and
demonstrate advanced diagnostic procedures. This course will also help identify the systematic
methods for troubleshooting. This course will cover the driver interview, diagnostic process
development, and application of detailed troubleshooting steps, tests and calibrations for Mack heavy
duty trucks.

1
 Course Agenda -
Mack Advanced Vehicle Diagnostics

Agenda: (Day One)

1. Course Agenda
2. Course Description
3. Design and Purpose of Vehicle Diagnostics
4. Basic Diagnostic Processes, Standards, and Methods
5. Mack Diagnostic Service Information

Agenda: (Day Two)

1. Mack Component Diagnostics
2. Vendor Application Diagnostic Information
3. Mack Diagnostic Software
4. Mack Vcads Pro Workshop

Agenda (Day Three)

1. Mack Vcads Pro Workshop

Agenda (Day Four)

1. Methods Workshop and Diagnostic Skills Evaluation

2. Course Exam and Evaluation

2
 Course Description and
Objectives – Mack Advanced
Vehicle Diagnostics
Course Description:

Teach, demonstrate, and practice diagnostic procedures to improve the technician’s

diagnostic skills. This course will teach the Mack vehicle component diagnostics
architecture and function. This course will include basic and advanced diagnostic
methods and procedures to aid in finding the root cause of the customer’s
complaint and vehicle function problems. This course will demonstrate how fast,
methodical diagnostic thinking "Triage Diagnostics" can improve diagnostic
troubleshooting and shorten customer downtime.

Course Objectives (Student should be able to describe and perform the

following upon the completion this course):

1. Understand the design and purpose of Mack vehicle diagnostics

2. Locate and use the Mack diagnostic service information
3. Acquire, read, and understand the Mack component diagnostics and functions
4. Perform basic and advanced diagnostic processes and methods
5. Use Mack diagnostic software and tooling to perform diagnostic tests and
calibrations
6. Develop “fast” methods of troubleshooting (Triage Diagnostics) using the vehicle’s
electronics to improve diagnostic skills and shorten customer downtime
7. Identify and evaluate vendor diagnostics messages, identify vendor diagnostic
software, and service information resources

3
 Design and Purpose of Vehicle
Diagnostics

Design and Purpose of Vehicle Diagnostics

4
 Design and Purpose of Vehicle
Diagnostics

Design:

Diagnostic monitoring technologies are used in vehicles to assist in electronic

and mechanical self-diagnosis. These diagnostics systems notify the driver of
problems identified by each system’s controller. The on board diagnostic
capability allows the driver to monitor the vehicle’s operation and conditions.
These diagnostic systems also assist the technician with faster and more
accurate troubleshooting of vehicle systems and customer complaints.

Purpose:

To accurately locate the root cause of a customer’s complaint, operational

condition, mechanical or electronic fault in a timely manner.

Goal:

To provide the customer a description of the problem, repair options, and the
time required for repair in a short time period. Shorten customer downtime!

Notes:
1. Two hour diagnostic time is used to give the customer a satisfactory time frame of diagnosis.
2. The two hour time frame is also a “flag” to contact Mack technical support if the diagnostic
procedures have not revealed the most probable root cause of the customers complaint.

*** Instructor Note: Inform students that E-Service should be the primary means of technical support.

5
 Design and Purpose of Vehicle
Diagnostics

Service Triage Diagnostics Process

Purpose:

Expedite the diagnostic and repair process to improve repair times and communications
with the customer and technician.

Objective:

Provide a high level of customer satisfaction with increased profitability.

Facility:

1. Assigned service bay, or service drive in close proximity to the Service Write-up desk
and parts department.

2. “Mobile/Floater” Diagnostics: Dealer may not be able to allocate a specific bay to the
triage diagnostics. With the use of wireless technologies, the technician is able to
perform the diagnostic steps anywhere on the dealership grounds.

3. Area will have necessary computers, tools and equipment stored close by:
a. VCADS laptop
b. Computer/s with access to TDP, EIS, Mack service publications, and Mack
networks.
c. Diagnostic tools.

Notes:

6
 Design and Purpose of Vehicle
Diagnostics

Personnel:
1. Qualified Technician. Highly proficient in mechanical and computer-aided
diagnostics

Triage Process:
1. When a vehicle arrives at the dealership for repair the Service Writer accompanies
driver to truck for preliminary verification of complaint, VIN, Mileage and vehicle
damage. A repair order is written, keys are tagged, then immediately given to the
Triage Technician for diagnosis. Customer is informed of possible diagnostic fee
and/or possible warranty coverage. A “General Check” could be performed at this
time. Up selling should be encouraged.

2. Customer is informed of time, cost and/or possible warranty coverage and

authorization is obtained.

3. If any repairs can be performed within one hour, he then makes those repairs. If he
cannot make repairs in that hour, he orders all required parts and sends truck to
shop foreman to be dispatched into the workflow of the main service department. He
only orders parts if he can verify need.

4. All labor performed and parts consumed in the Triage Bay are billed to the repair
order.

5. This bay may also be used as for Quality Inspection or Quick Lube for increased
facility utilization.

Notes:

7
 Design and Purpose of Vehicle
Diagnostics

Expected results:

1. Increased customer satisfaction with improved timely communications and

minimized down time.

2. Increased efficiency due to reduced lost time waiting on ordered parts through
better communication.

3. Clear descriptions to repairing technicians.

4. Improved workflow. Increased bay utilization.

5. Increased gross profit on repair orders due to efficient diagnosis, reduction of lost
time, better technician communication and possible up sales.

6. Cross training between technicians on diagnostic’s processes and methods.

Notes:

8
 Basic Diagnostic Processes,
Standards, and Methods

Basic Diagnostic Processes,

Standards, and Methods

9
 Basic Diagnostic Processes,
Standards, and Methods

Criteria to use when performing “Triage”

diagnostics:

1. Customer Complaint

LISTEN to the customer!

2. Loss of vehicle functions

Validate the complaint!

Notes:
Listen! The customer/driver has a wealth of information to offer in most cases. Information gathering
is the key to good diagnostics. Asking detailed questions and recording the information normally
draws the diagnostic map for the technician. Knowing what questions to ask is a problem.
Two main pieces of information are critical to for the technician to use the process of elimination to
simplify the diagnostics process.
1. The customer’s complaint – Use the Basic Data Gathering form or equivalent form of questioning.
2. Validate the complaint – The customer will have some type of symptom or complaint about a
vehicle function that has a problem or no longer operates. If possible, check the truck while the
customer is there to make sure there is really a problem.
These two items should be compared to each other to validate the problem. In some cases, the
customer has a complaint but there are no visible problems, symptoms, or faults. These cases
create difficulty in troubleshooting but are often resolved through communication with the driver
or customer to bring the vehicle back when the problem is occurring or when the customer has
recorded information the dealer technician can use to perform more thorough symptom
diagnostics.

10
 Basic Diagnostic Processes,
Standards, and Methods

Diagnostic Process Flow

1. The identification or recognition of errors or problems by signs and

symptoms.

Customer Complaint / Symptom Fault Tracing

2. A distinguishing feature serving as supporting evidence in a diagnosis.

Fault Code Diagnostics

3. A method or a technique used in technical diagnosis.

“TRIAGE DIAGNOSTICS PROCESS”

Notes:
1. Problem solving by symptoms..
2. Problem solving by using the fault codes (distinguishing features) and failure mode identifiers
(FMIs).
3. This methodical thinking process of applying diagnostic procedures to the vehicles symptoms
and faults is called the “Triage” diagnostics process. FAST!
Two characteristics that should align when performing any diagnostics steps are:
1. The customer’s complaint
2. Loss of vehicle, engine, or system functions

11
 Basic Diagnostic Processes,
Standards, and Methods

Beware of preconceived ideas!

Think…Analyze…Diagnose!

Notes:
Poor communication between the customer and the service writer usually creates many issues during
troubleshooting. The lack of information from the customer as well as a lack of thorough
questioning by the service writer may prevent the technician from accurately diagnosing a
problem. An increased amount of diagnostic time can also be the result of poor data gathering. In
most cases, technicians must depend on their technical knowledge of the truck, and a clear
understanding of the diagnostic process. THINK BEFORE YOU ACT! Many troubleshooting steps
could be eliminated by listening and gathering good information. The customer and/or driver are
the best resources for this information.
Other sources for information gathering are:
1. Customer work history
2. Warranty work history
3. Service history

12
 Basic Diagnostic Processes,
Standards, and Methods

1. Operator Interview
2. Gather Data (What Sources?)
3. Audio/ Visual Inspection
4. Identify and separate vehicle systems
5. Identify and use the appropriate diagnostic symptom checklist and
fault code diagnostic procedures provided in the Mack service
literature.
6. Apply basic methods of fault tracing to determine the root cause of
the customer complaint, vehicle symptoms (function loss or
interruption), or fault.
7. Use the vehicle to perform “quick” self diagnostics.
8. Use the appropriate diagnostic tools such as VCADS Pro
to perform tests and calibrations.
9. Validate results and inform the customer.

Notes:
The Basic Data Gathering form is a very good source of questions and is a means of recording the
data gathered. This form has form fields as well as pictures to remind the service writer and the
technician to “think out of the box”. There are so many different questions to ask. This form is the
foundation for performing thorough diagnostics.
Refer to the Mack EIS online service literature to view the data gathering, symptom based, diagnostic
fault trees.

See the following pages for a view of this form.

Instructor note: Click on the document picture in the presentation to open the document for
viewing.

13
 Basic Data
Gathering Form

14
Fault Tracing

Basic Data Gathering

This information provides the guidelines and checklists for basic data gathering as a
start to vehicle fault tracing.

Contents
“Basic Data Gathering, Fault Tracing”

“Checklist, Basic Data Gathering”

NOTE: Information is subject to change without notice.

Illustrations are used for reference only and may differ slightly from the actual vehi-
cle being serviced. However, key components addressed in this information are
represented as accurately as possible.

15
2000-20-03-01
The driver should be able to provide answers to the fol-
Basic Data Gathering, Fault lowing questions:
Tracing • Are any fault codes present?

• Description of the fault.

• When the fault occurred.

• How was the fault discovered and what hap-

pened prior to this?
General Guidelines
The gathering of basic data is the first step in all fault
• Does the fault reoccur?

tracing work. • How often does the fault reoccur?

In addition to information about the vehicle and customer • How long does the fault last when it does occur?
it is important to gather as much information as possible
about the sequence of events in conjunction with the oc- • Does the fault always occur under the same
currence of the fault. conditions, and if, so what are they?

The driver can often provide valuable information con- • Does the driver have any idea of the possible
cerning the circumstances surrounding the occurrence of cause of the fault?
the fault. The driver is nearly always the one who first
discovers a fault. • Is the fault still active?

Try to gain an understanding of the circumstances sur- For symptom lists or diagnostic and fault tracing check-
rounding the fault. lists, refer to the appropriate service literature.

Since you can seldom recreate the problems experi-

enced, without creating exact similar conditions, the
driver’s information is of the greatest importance in order
to be able to make the correct assessments in fault trac-
ing.

Photocopy the forms. Fill in the answers to the questions

and save the form with the work order.

16
Checklist, Basic Data Gathering

Basic Data
Dealer’s name ......................... Customer’s name . . . . . . . . . . . . . . . . . . . . . . . .
No. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . ......................................
Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
..................................... ......................................
..................................... ......................................
Country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Country . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Tel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Tel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Fax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Fax . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Memo . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . E-mail . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Driver’s name . . . . . . . . . . . . . . . . . . . . . . . . . .
Date when the information was given .........

Vehicle specification
Vehicle type . . . . . . . . . . . . . . . . . . . . . . . . . . . . Year model .............................
Chassis no. . . . . . . . . . . . . . . . . . . . . . . . . . . . . Delivery date . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Mileage . . . . . . . . . . . . . . . . . . . . . . . . km / miles Normal routes . . . . . meters / feet above sea level
Vehicle, number of axles........x........ Type of transport . . . . . . . . . . . . . . . . . . . . . . . . .
Average combination weight . . . . . . . . . . . . . . tons

Type of vehicle

Type of trailer

For any other types of vehicles or vehicle combinations, describe here . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

....................................................................................
....................................................................................
Perform a tire check of the whole vehicle combination and describe any abnormal wear . . . . . . . . . . . . . . . . . . . .
....................................................................................
....................................................................................

17
Engine model . . . . . . . . . . . . . . . . . . . . . . . . . . .
Engine serial no.. . . . . . . . . . . . . . . . . . . . . . . . .

Transmission . . . . . . . . . . . . . . . . . . . . . . . . . . . Retarder Yes / No . . . . . . . . . . . . . . . . . . . . . . . . .

Transmission no. ........................ Retarder type . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Differential type . . . . . . . . . . . . . . . . . . . . . . . . . Power Take-Off Yes / No . . . . . . . . . . . . . . . . . . . .

Gear ratio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Power Take-Off type . . . . . . . . . . . . . . . . . . . . . . .

Note any fault codes

MID
PID/PPID
SID /PSID
FMI
Number of oc-
currences
Status
First
occurrence (h)
Last
occurrence (h)
Total engine hours

Other information
....................................................................................
....................................................................................
....................................................................................
....................................................................................
....................................................................................
....................................................................................

18
Description of the Fault
Brief description of the complaint and any prior maintenance or repairs. . . . . . . . . . . . . . . . . . . . . . . . . . . .
....................................................................................
....................................................................................
....................................................................................

When was the fault discovered for the first time?

Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Mileage . . . . . . . . . . . . . . . . . . . . . . . . . km/miles

How was the fault discovered? ...........................................................

....................................................................................
....................................................................................

What happened prior to the fault occurring?

Describe the sequence of events . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
....................................................................................
....................................................................................

Does the fault reoccur?

....................................................................................
....................................................................................

How often does the fault reoccur?

....................................................................................
....................................................................................

How long does the fault last when it does occur?

....................................................................................
....................................................................................

Does the fault always occur under the same conditions and, if so, what are they?
....................................................................................
....................................................................................

Does the driver have any idea of the possible cause of the fault?
....................................................................................
....................................................................................

Is the fault still active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

19
Engine
Under what driving conditions does the fault occur?

Uphill Downhill Top of hill Depres- Flat road Uneven Independent

sion road of these

Outside influences that affect the fault. What is the outside temperature when the fault occurs?

Winter Summer High humidity  

.................... C ( F)
temperature temperature

 
What temperature is the engine while the fault is occuring? ................................... C ( F)

Is the engine considered to be difficult to start? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Describe the starting process . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
....................................................................................

Is there any abnormal smoke present? If yes, what color: white, gray, black, blue? . . . . . . . . . . . . . . . . . . . . . . . .
....................................................................................

Do abnormal sounds come from the engine? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

....................................................................................

Have any changes in fuel consumption, oil consumption or power output been determined? . . . . . . . . . . . . . . . . .
....................................................................................
....................................................................................
What grade of fuel is used? ...............................................................
Are additives used in the fuel? If yes, what are they? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
....................................................................................

What repairs or previous actions have been performed on the engine? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

....................................................................................
Other information
....................................................................................
....................................................................................

20
Transmission and Differential
Under what driving conditions does the fault occur?

Uphill Downhill Top of hill Depres- Flat road Uneven Independent

sion road of these

What is the outside temperature when the fault occurs?

 
.................... C ( F)

What type/grade of oil is used? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

....................................................................................

Are additives used in the oil? If so, what are they? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

....................................................................................

 
What is the temperature of the transmission/differential while the fault is occurring? . . . . . . . . . . . . . . . . . . C ( F)

When was the last oil change performed? Date . . . . . . . . . . . Mileage . . . . . . . . . . . . . . . . . . . .

Do abnormal sounds come from the transmission / differential? .....................................

....................................................................................

Is the engine power affected by the transmission fault? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

....................................................................................

What repairs or previous actions have been performed on the transmission/differential? . . . . . . . . . . . . . . . . . . . .

Other information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
....................................................................................
....................................................................................

21
Brakes
ABS/Vehicle Specification

Yes No
ABS on tractor (type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Are any fault codes active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

ABS on trailer (type) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Are any fault codes active? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Yes No
Does the vehicle pull to the left or right? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
Yes No
Are the mechanical aspects of the brake system OK? .........................

Tire Dimension

Yes No
Are the differences in tire circumference less than 14%? .......................

First front axle Second front axle Leading rear axle Second rear axle Third rear axle

Yes No
Are the tires inflated to manufacturer’s specifications? .........................

Tire Wear

Yes No
Are any tires worn more than the others? ..................................

First front axle Second front axle Leading rear axle Second rear axle Third rear axle

Other information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
....................................................................................
....................................................................................
....................................................................................

22
Air Suspension
Type of air suspension:

Full air suspension . . . . . . . . . . . . . . . . . . . . . . . . . .

Rear air suspension . . . . . . . . . . . . . . . . . . . . . . . . .

Number of air bags, rear . . . . . . . . . . . . . . . . . . . . . . . . . .

Circumstances that affect the fault

 
Outside temperature . . . . . . . . . . . . . . . . . . . . . . . . C ( F)

Yes No
Does the vehicle lean to one side? . . . . .

Front Rear Right Left

If the vehicle leans, does it lean .......

Do any of the air bags leak (hissing sound)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Does the vehicle regulate itself when it shouldn’t? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Does the switch in the cab function (air dump)? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .

Does the air suspension occasionally cease to function? ..........................................

Other information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
....................................................................................
....................................................................................
....................................................................................

23
 Basic Diagnostic Processes,
Standards, and Methods

Use the Driver’s interview information

to gather as much information as possible.
(Basic Data Gathering Form)
(Filter out information that is not pertinent to the
complaint or diagnostic process)

Use the DID (Driver Information Display) to collect data.

(Keep the job as simple as possible.
Compare the interview information to the DID information)

Identify the most probable cause of problem or condition.

(Separate the information by systems or groups to narrow the
path of diagnostics)

Separate the systems by using the MID, PID, SID, PSID, PPID identifiers
(Refer to service literature) MID 128
PID 100
FMI 5

Notes:
The information gathered from the customer should be used to narrow down the areas on the vehicle
that may need diagnostic procedures. Using the vehicle to access this information is another way to
speed up the process of diagnostics. This is the “Triage” process. Working logically, methodically,
and accurately should be the goal of the technician. This builds a trusting relationship between the
customer and the dealer.
Use the information display in the truck to access vehicle status, ECU communication, and fault
information. To speed up the diagnostic steps, identify the most probable area of trouble based on
the FACTS gathered from the customer. If the problem is electronic (intermittent, active, or inactive)
break down the vehicle systems by the control group and function area and customer complaint.

24
 Basic Diagnostic Processes,
Standards, and Methods

Basic diagnostic processes require system separation:

1. Mechanical System:
(Fuel, Coolant, Air, Lube)

2. Electronic System:
(Controller, wiring, inputs and outputs)
Customer Complaint
3. Controllers:
(Electronic Control Units and Software) LISTEN to the customer!

4. Wiring:
(Circuits, terminals, and connectors) Loss of vehicle functions
Validate the complaint!
5. Inputs:
(Sensors and switches)

6. Outputs:
(Solenoids and motors)

Notes:
Diagnostic troubleshooting steps can often be split into sub-groups.

Mechanical verses Electronic (or both) - One may compliment the other.
Iron or Maintenance item – component failure or problem or filter, fluids, etc.
Harness, sensor, motor, or controller – Determine by the type of problem indicated by the FMI
recorded.

Understanding the basics of the diagnostic process flow is very important in being efficient during
the diagnostics process.
Remember the goals:
1. Listen to diagnose with accuracy = less wasted time.
2. Use the vehicle = built in service tool.
3. Timely diagnosis = improved customer trust and satisfaction.

25
 Basic Diagnostic Processes,
Standards, and Methods

SAE Diagnostic Messages MID 128

1. MID: Message Identification Description

2. PID: Parameter Identification Description

3. PPID: Proprietary Parameter Identification

SID 4
Description

4. SID: Subsystem Identification Description

5. PSID: Proprietary Subsystem Identification

Description
PID 91 MID 144
PPID 86
6. FMI: Failure Mode Identifier

Notes:
The Society of Automotive Engineers set an industry standard list of diagnostic messages and fault
codes. Mack follows the SAE standards for fault codes. The vendor application software utilize
these standards as well, but their descriptions may be displayed differently as designed by the
manufacturer. These messages are used to communicate information concerning problems
detected by ecu programming and circuitry. Some manufacturers also use a proprietary system of
diagnostic descriptions to identify specific system or component problems.
1. SAE diagnostics are designed to indicate/divide vehicle system problems into smaller groups to
pinpoint specific problems.
2. Application of SAE diagnostics messages will assist in developing a path of diagnostics.
Instructor note: Demo Impact or ID: (MID 128 or MID 144) Show the list of PIDs, PPIDs, SIDs, PSIDs to
explain the difference.
*** PIDs are parameter identifiers – These parameters are part of the ECU main software/datasets and are added
to provide fault or condition descriptions for a particular system of a MID. These software parameters must
not be confused with customer parameters. Example: the engine oil pressure system has fluid, mechanical
parts, sensor, wiring, and logic in the eecu. The assigned PID or PPID number describes a possible problem
or condition measurement for that system. This could be mechanical or electronic. In addition to the PID, the
FMI indicated determines the type of problem or condition within a system. The problem may not necessarily
be any specific component. In short, an ecu recognizes there is a problem within a system but doesn’t know
exactly what part/component has the problem.
*** SIDs are subsystem identifiers – These parameters (not to be confused with customer parameters) are part of
the ecu main software/datasets. In most cases these parameters are fault or measured voltages descriptions
as compared to other parameters within the software. These are typically for required system components.
Example: a unit injector is a required component for operation. The eecu provides the circuit control logic
and monitors it electronically. The eecu can only determine that the circuit is intact or is not operating
electrically. When other inputs or control functions measurements (example: engine speed) are used in
conjunction with the unit injector circuit outputs, a subsystem (SID or PSID) problem description is
generated for evaluation. In addition to the SID or PSID, the FMI indicated determines the type of problem or
condition within a controller’s subsystem.

26
 Basic Diagnostic Processes,
Standards, and Methods

Analyze system operation to determine diagnostic action plan:

Basic Systems – Oil, Coolant, Air, Fuel

Notes:
Decide where to begin detailed diagnostic steps.

What is the complaint?

What systems are involved?

Separate the troubleshooting by vehicle systems or areas to simplify the diagnostics process.
Mechanical or electrical?
Fault active or inactive?
Intermittent problem?

27
 Basic Diagnostic Processes,
Standards, and Methods

Basic diagnostic processes require system separation:

MID 128 – Fault List
PSID 201
Customer Interview FMI 9
(Complaint) MID 128
Mechanical? SID 231
FMI 2

Air
Electronic?
MID 144 – Fault List
???
Fuel PSID 200
Faults? FMI 9

Oil

Active Inactive
Coolant

MID 136 – Fault List

SID 231
FMI 5 or FMI 6
Customer Interview
(Vehicle Function Loss)

Notes:
The basic diagnostic steps are very simple. The customer complaint from the interview form will start
the process. Determine if the problem is possible mechanical, electronic or both. The electronic
system is designed to provide details about a recorded problem. This information will indicate the
area that is complaining about a problem as well as the controller that is being complained about.
Comparisons between the recorded faults and the vehicle function loss can possibly lead the way to a
root cause of the complaint.
The MID, PID, SID, PPID, PSID and FMI system will help pinpoint the area of trouble. Some FMIs are
written to display a problem with communication. The ECUs are programmed with code that indicates
when another ecu or input is not present.

28
 Basic Diagnostic Processes,
Standards, and Methods

FMI Table and Description

FMI Display Text SAE Descriptions

Electrical
0 Value too high Data applicable, but above normal operating range
or
1 Value too low Data applicable, but below normal operating range
Mechanical
Abnormally high voltage or short-circuit to higher
Faults?
3 Electrical fault
voltage
Abnormally low voltage or short-circuit to lower
Conditions? 4 Electrical fault
voltage
5 Electrical fault Abnormally low current or open circuit

6 Electrical fault Abnormally high current or short-circuit to ground

7 Mechanical fault Incorrect response from the mechanical system

Mechanical fault or
8 electrical fault
Abnormal frequency

Mechanical fault or
10 electrical fault
Abnormally high variations

13 Incorrect calibration Values outside calibration values

2 Incorrect Data Intermittent or incorrect data

9 Communication fault Abnormal Update Rate

11 Unknown fault Unidentifiable fault

12 Component fault Defective intelligent unit or component

Data, data
14 Unknown fault Special instructions
link, or ecu
15 Unknown fault Reserved for future use
Faults?

Notes: Condition or fault?

Conditions are software features that measured data that is converted into information that the
instrument cluster can display to the driver. This data is also used by the service tool for data
gathering and diagnostics. These data measurements are used by the different electronic controls
to make changes in operation to control and protect the vehicle and driver. Typically conditions
are indicated by FMI’s 0, 1, and sometimes a mechanical fault FMI 7. These FMIs indicate a value
that is either low or high. A condition such as FMI 7 indicates a mechanical problem may be a
result of a value that is out of range for the monitoring sensor.
Example: Fuel pressure low (FMI 7) This indicates that the system has measured a low fuel
pressure reading. This root cause may be the fuel lines, pump, aeration of the fuel, etc.
Faults are voltages measurements as well as data measurements, data comparisons, and mechanical
system monitoring. Fault FMIs indicate a recognized problem with circuitry, sensors, and other
electrical components. These may be in the form of iron failures, component adjustments or
calibrations that are not within specifications. The ranges for the values to trigger a specific fault
are determined by the software programmed for each circuit monitored.

29
 Basic Diagnostic Processes,
Standards, and Methods

Basic FMI Circuit Descriptions

Signal or supply
wire
(Short Circuit)
Signal, supply,
or ground wire
(Open Circuit)

Signal or supply
wire
(Grounded Circuit)

Notes:
Three basic circuit problems to remember when diagnosing electrical problems.
1. Open circuit
2. Short circuit
3. Grounded circuit

It is very important to understand the FMI descriptions of a fault or condition.

A fault depends on how the ecu is monitoring the wiring or sensor circuit. (input or output circuitry?)
An ecu may be programmed to look for voltage drops, voltage shorted high, high or low current
values, voltage shorted low, etc. These measurements are compared to set parameters for each
sensor circuit within the ecu software. When a voltage is out of the “normal” range the ecu
considers it to be a fault or condition.

30
 Basic Diagnostic Processes,
Standards, and Methods

FMI Function and Design

Sensor or component FMI is
part of ECU software
programming

Notes:
Example circuit – A Volvo D12C engine air filter restriction sensor circuit.
1. FMIs are programmed into ECU software to provide “self diagnostics”.
2. The voltage/current/resistance ranges that indicate diagnostic messages are different per sensor
or component.

Instructor note: Explain the example above to show the different FMIs programmed for the air filter
restriction sensor circuit.

31
 Basic Diagnostic Processes,
Standards, and Methods

List of applicable
(programmed) FMIs for
this Fault code

Notes:
The applicable FMIs for a specific sensor can be found in EIS diagnostics service literature. These FMI
listings can be found within any of the ECU fault code descriptions.

Instructor note: Demonstrate the EIS program to show how to read the applicable FMIs for any
sensor.

32
 Basic Diagnostic Processes,
Standards, and Methods

Analyze system operation to determine diagnostic action plan:

Basic Electrical and Electronic Systems

Click to add text

Notes:
Deciding where to begin the diagnostic steps is sometimes difficult to determine. Following the
customer’s complaint can provide a very good pathway to the root problem. However, when this
information is not readily available, the technician must rely on basic vehicle systems operation to
aid in the diagnostics process.
There are several things to remember:
1. Keep it simple – Don’t make the situation more complicated that it is. Remain focused on the real
complaint.
2. Determine if there are any faults to support the route of diagnostics.
3. Think about the operation of the system having trouble.
4. Isolate the specific area, circuit, or mechanical check to be performed.

Mack provides diagnostic symptom based checklists, and fault code tables to assist the technician
during the troubleshooting process. These symptom based checklist and fault code information
are found in Mack’s EIS program.

33
 Basic Diagnostic Processes,
Standards, and Methods

Analyze system operation to determine diagnostic action plan:

Faults? Use fault code diagnostics – VMAC

Notes:
Example screen of the fault code based troubleshooting for the VMAC systems.

***Instructor note: Demonstrate the EIS program to view this information.

34
 Basic Diagnostic Processes,
Standards, and Methods

Analyze system operation to determine diagnostic action plan:

Faults? Use fault code diagnostics – VMAC II

Notes:
Example screen of the fault code based troubleshooting for the VMAC II systems.

***Instructor note: Demonstrate the EIS program to view this information.

35
 Basic Diagnostic Processes,
Standards, and Methods

Analyze system operation to determine diagnostic action plan:

Faults? Use fault code diagnostics – VMAC III

Notes:
Example screen of the fault code based troubleshooting for the VMAC III systems.

***Instructor note: Demonstrate the EIS program to view this information.

36
 Basic Diagnostic Processes,
Standards, and Methods

Analyze system operation to determine diagnostic action plan:

Faults? Use fault code diagnostics – VMAC IV

Notes:
Example screen of the fault code based troubleshooting for the VMAC IV systems.

***Instructor note: Demonstrate the EIS program to view this information.

37
 Basic Diagnostic Processes,
Standards, and Methods

Analyze system operation to determine diagnostic action plan:

Mechanical checks? Use symptom based troubleshooting methods – VMAC

Notes:
Example screen of the symptom based troubleshooting for the VMAC systems.

***Instructor note: Demonstrate the EIS program to view this information.

38
 Basic Diagnostic Processes,
Standards, and Methods

Analyze system operation to determine diagnostic action plan:

Mechanical checks? Use symptom based troubleshooting methods – VMAC II

Notes:
Example screen of the symptom based troubleshooting for the VMAC II systems.

***Instructor note: Demonstrate the EIS program to view this information.

39
 Basic Diagnostic Processes,
Standards, and Methods

Analyze system operation to determine diagnostic action plan:

Mechanical checks? Use symptom based troubleshooting methods – VMAC III

Notes:
Example screen of the symptom based troubleshooting for the VMAC III systems.

***Instructor note: Demonstrate the EIS program to view this information.

40
 Basic Diagnostic Processes,
Standards, and Methods

Analyze system operation to determine diagnostic action plan:

Mechanical checks? Use symptom based troubleshooting methods – VMAC IV

Notes:
Example screen of the symptom based troubleshooting for the VMAC IV systems.

***Instructor note: Demonstrate the EIS program to view this information.

41
 Basic Diagnostic Processes,
Standards, and Methods

Perform basic “Quick” checks

Perform Basic “Quick Checks” to test sensor, harness and ECU integrity.

Allow the vehicle to diagnose itself!

(The vehicle’s electronics has the capability to indicate a change in fault status
when the circuit is manipulated)
Note: Look up the applicable FMIs for the circuit be tested. Create a different FMI
from the list to test circuit.
(Example: Open circuit fault FMI 5 – create a FMI 3 short circuit and recheck fault
codes. Look for a change in the FMI indicated.)

Existing condition Harness and

MID 128 PID 100 controller are
FMI 1
Low Oil Pressure
working properly

Perform detailed
Unplug sensor
diagnostic tests on
sensor and perform oil
pressure checklists
New fault code
procedures to check
MID 128 PID 100
FMI 5 lubrication system
Low Oil Pressure

Notes:
The “Triage” process can be used to speed up the time of diagnosing a problem by using the vehicle
to test itself.
A “quick check” can be used to evaluate controller, wiring, an sensor integrity. This can be done by
manipulating the controller’s circuits to create new fault codes and indicate an FMI status change.
This creates a “process of elimination” strategy for troubleshooting. This method is fast and very
accurate. These “quick check” results can then be used and compared to more thorough tests
performed in Vcads Pro and system checklists. Note: Refer to the service literature to find the list of
applicable FMIs for the system or circuit being tested.
NOTE: If an FMI is listed in the ecu software, it can be created by the technician. Refer to the
diagnostics fault code tables to see the list of applicable FMIs for each controller.

42
 Mack Diagnostic Service
Information

Mack Diagnostic Service Information

Notes:
Mack provides many resources for diagnostic information. The diagnostics process is dependent on
the technician’s ability to work fast, methodically, and with skilled detail. These skills will provide
faster diagnosis of problems to shorten customer downtime and improve customer satisfaction. Our
systems give the technician the capability to perform diagnostic methods without leaving the vehicle.
After a thorough data gathering session by the service writer, the technician reviews the customer’s
complaint and starts the troubleshooting process. The Mack systems and programs are primarily
electronic in form. However many of the resources are available in printed form.

43
 Mack Diagnostic Service
Information - Resources

Notes:
Mack offers several sources of diagnostic service information.
1. Vcads Pro – User id and password required.

2. EIS (Electronic Information System) – Network connection required. Access to Trucks Dealer
Portal or Macknet is required.

3. E-Service – This program is used to create and record technical support requests from the
dealers to Mack Technical Service Support. This program is accessed through the Trucks dealer
Portal and requires a user id and password.

4. Macknet – This website is used to view vehicle information, vehicle history, as well as
downloading ecu software for VMAC III and earlier versions.

5. Parts and Service Publications – This website is used to order Mack service literature. Access to
EIS is also available from this website.

44
 Mack Diagnostic Service
Information – VCADS Pro

Notes:
Vcads Pro offers many “view” or “monitor” screens.
Sensor values can be read to compared to mechanical gauge readings to separate electronic
components from hardware components.
Within these screens there are information buttons that provide details about the sensor’s purpose
and location for faster diagnostics.

45
 Mack Diagnostic Service
Information – VCADS Pro

Select the “Info” button

to view more details
about the component
in question

Select the link to view

the location of the
specific component

Notes:
Diagnostic information available within the tests.
•Click on the “Information” icon.
•Component details can be read.

Technical service information within VCADS Pro will indicate many sources for troubleshooting
methods. These sources may refer to simplified wiring diagrams, component identification codes, as
well as “test specific” system diagnostic references.

46
 Mack Diagnostic Service
Information – VCADS Pro

Refer to the Mack service

literature for the specific
component’s diagnostic
information (EIS)

Notes:
Picture references for each component.

Note: Refer to EIS for the specific diagnostic information for each component.

47
 Mack Diagnostic Service
Information – VCADS Pro

Select the “Information” icon

to display the details for the
specific circuit or test.

Notes:
When performing a test or calibration within Vcads Pro, the information icon may be selected to view
details about the test or calibration. This information may include items such as test specifications,
test procedures, and component locations.

48
 Mack Diagnostic Service
Information – VCADS Pro

Notes:
The Vehicle information test may need to be performed to view all ecus that are communicating on
the J1587 data link. This information includes items such as controller part numbers (hardware),
data set part numbers (software numbers), etc.

49
 Mack Diagnostic Service
Information – E-Service

Notes:
E-Service is a technical support tool used by the technician to get advice on diagnostic procedures
that have not led the technician to the most probable trouble area or root cause of the problem. The
recommendation from Mack is that there be a case submitted in E-Service during the first two hrs of
troubleshooting. The technician should exhaust all resources of diagnostics prior to contacting Mack
Technical Support. Using E-Service is the best method of correspondence with tech support because
it records all transactions made during the case. These records can be accessed at a later date for
reference on recurring problems or for historical data. A user id and password is required and is set
up at the dealer level through the dealer management.

50
 Mack Diagnostic Service
Information – E-Service

Notes:
Instructor note: Demonstrate an E-Service case submittal for the class.
Instructor note: Notify students of the “how to” guide in trucks dealer portal. (it is located under the
Service tab for Mack)

51
 Mack Diagnostic Service
Information – Electronic
Information System

Select the link to view

the Mack Class 8
service information

Notes:
Mack’s EIS (Electronic Information System) program is used to quickly access service information
while at the vehicle. This program does require network connection. Symptom based as well as
fault code based diagnostic information can be found in EIS.

***Instructor note: Demonstrate EIS for class viewing.

52
 Mack Diagnostic Service
Information – Electronic
Information System

Notes:
Mack’s EIS system allows the technician to search for and view technical service information to
expedite the diagnostic process.
The EIS program gives the technician the capability to select many different component, publication
types, models, service categories, as well as information type.

Note: The Complete Service Manuals icon will link the technician to a different view of the same
service literature.

Instructor note: Demonstrate EIS for class viewing.

53
 Mack Diagnostic Service
Information – Electronic
Information System

Notes:
The troubleshooting information for any model may be found in the EIS program .

54
 Mack Diagnostic Service
Information – Electronic
Information System

Select the diagnostic

code for
troubleshooting
steps

Notes:
Within the diagnostic service literature in EIS, a specific fault code may be selected to provide
additional information about the circuit and component. This will assist in the diagnostic process.

55
 Mack Diagnostic Service
Information – Electronic
Information System

Select the camera link

to view the schematic
of the specific
component

Notes:
Selecting the “camera” icon will open a picture window to give a detailed view of the circuit.

56
 Mack Diagnostic Service
Information – Macknet

Select the applicable link to view vehicle information,

download data files, software, and upload verification
files. Vehicle history may also be viewed.

Notes:
The Macknet website is used to view vehicle information, vehicle history, as well as downloading ecu
software for VMAC III and earlier versions.

Note: The Macknet download software is for VMAC, VMAC II, and VMAC III versions only. The VMAC
IV software must be programmed with Vcads Pro.

57
 Mack Diagnostic Service
Information – Service Publications

Notes:
The Parts and Service Publications website is used to order Mack service literature. Access to EIS is
also available from this website.

58
 Mack Component Diagnostics

Mack Component Diagnostics

59
 Mack Component Diagnostics
J1939 Data Link

Terminating Resistors

Notes:
The J1939 data link is a pair of wires that provides a path for high speed communications between
each ecu on the vehicle. Each ecu has connected to the 1939 link monitors and interprets messages
that may be viewed in the instrument cluster display as well as the Vcads Pro service tool. The
software programming that provides diagnostic information is designed to indicate a problem with a
component, control unit, data link wiring, and or data. These are displayed as PSIDs
These PSIDs are tools for diagnostic mapping. The PSID identification numbers point to a particular
area of the data link or specific problem concerning data on the high speed communication link.

Example:
MID 128 - PSID 201 – Points to MID 144 (common)
(common) MID 144 – PSID 200 – Points to MID 128
Look for common indicators in the list of codes. The common indicators may possibly match the
customer’s complaint about vehicle function problems. (Compare fault codes to customer complaint
and vehicle function loss or interruption)
Refer to the Data Link Fault Tracing information within EIS. Remember to separate the vehicle
systems when a data link problem is suspected.

See the following pages for a view of this document.

***Instructor note: Click on the document picture in the presentation to open the document for
viewing.

60
J1939 Data Link
Diagnostics

61
MID 128 SID 231 — CAN1 J1939 COMMUNICATION LINK A

Figure 1 -- J1939 Data Line

Figure 2 -- J1939 Data Line

When performing electrical tests, wiggle wires and connectors to find intermittent
problems.

Failure Mode Identifier (FMI): 2 (Data Erratic)

Parameter Identification (PID): S231

Message Identification (MID): 128

Circuit Description: The V-MAC IV system uses the J1939 data lines to control
functions and communicate between the Vehicle Electronic Control Unit (VECU),
Engine Management System (EMS) Module, Instrument Cluster Module (ICM) and
accessory systems, depending on vehicle model and option content. The J1939
data lines consist of an expandable data bus allowing the addition of accessory
control modules. The J1939 data lines are the primary data bus. Data is prioritized
and then transmitted across the J1939 data lines to the appropriate control
module. The V-MAC IV system is designed to allow limp home engine operation
with the loss of the J1939 data signal as long as the J1587 data lines are still
operational.

Code Setting Conditions: Code SID 231 will set when the Engine Management
System (EMS) Module is unable to send and/or receive information across the
J1939 data line. If either the Vehicle Electronic Control Unit (VECU) or the Engine
Management System (EMS) Module loses communication on the J1939 data line,
code SID 231 will set and the Electronic Malfunction Lamp (EML) will turn on. The
fault will become inactive if communication resumes. If communication is lost on
both the J1587 and J1939 data lines, the engine will NOT run.

Test 1 — Checking for Code SID 231

1. Verify that code SID 231 is set.

62
 If code SID 231 is set, go to Test 2 — Checking the Resistance at Data Link
Connector.

If code SID 231 is NOT set, wiggle the EMS Module harness and connectors to
try to set the code. Visually inspect the EMS Module connectors and wires for
poor connections.

Test 2 — Checking the Resistance at Data Link Connector

Figure 3

1. Turn the ignition switch OFF.

2. Measure the resistance between pins C and D of the Data Link Connector
(DLC) (see Figure 3).

3. Is the resistance between 50–70 Ohms?

If the resistance is between 50–70 Ohms, go to Test 3 — Checking for a

Short to Power or Ground in the Data Link Connector.

If the resistance NOT is between 50–70 Ohms, go to Test 10 — Checking the

CAN-BUS Termination Resistor.

Test 3 — Checking for a Short to Power or Ground in the Data

Link Connector

Figure 4

1. Turn the ignition switch ON.

2. Measure the voltage between pin C of the Data Link Connector (DLC) and a
good ground (see Figure 4).

If the measured voltage is battery voltage or 0 volts, go to test Test 5 —

Checking for a Short in the Engine Management System (EMS) Module.

If the measured voltage is NOT approximately battery voltage or 0 volts, go

to Test 4 — Checking for a Short to Power or Ground in the Data Link
Connector.

Test 4 — Checking for a Short to Power or Ground in the Data

Link Connector

63
 Figure 5

1. Turn the ignition switch ON.

2. Measure the voltage between pin D (CAN L) of the Data Link Connector (DLC)
and a good ground (see Figure 5).

If the measured voltage is battery voltage or 0 volts, go to test Test 5 —

Checking for a Short in the Engine Management System (EMS) Module.

If battery voltage is NOT battery voltage or 0 volts, go to test Test 5 —

Checking for a Short in the Engine Management System (EMS) Module.

Test 5 — Checking for a Short in the Engine Management System

(EMS) Module

1. Turn the ignition switch OFF.

2. Disconnect the Engine Management System (EMS) Module connector B.

3. Turn the ignition switch ON.

4. Connect the diagnostic computer and check for code SID 231.

If code SID 231 is still active, go to Test 6 — Checking for a Short in the Vehicle
Electronic Control Unit (VECU).

If code SID 231 is NOT active, check the Engine Management System (EMS)
Module harness and all connections for loose, corroded or damaged terminals and
repair or replace as necessary. If no loose, corroded or damaged terminals are
found, replace the Engine Management System (EMS) Module and retest the
system. If code SID 231 is still set, go to Test 9 — Checking Continuity on the
Data Line.

Test 6 — Checking for a Short in the Vehicle Electronic Control

Unit (VECU)

1. Turn the ignition switch OFF.

2. Reconnect the Engine Management System (EMS) Module connector B.

3. Disconnect the Vehicle Electronic Control Unit (VECU) connector C.

4. Connect the diagnostic computer and check for code SID 231.

If code SID 231 is still active, go to Test 7 — Checking for a Short in the

64
Instrument Cluster Module (ICM).

If code SID 231 is NOT active, check the Vehicle Electronic Control Unit (VECU)
harness and all connections for loose, corroded or damaged terminals and repair
or replace as necessary. If no loose, corroded or damaged terminals are found,
replace the Vehicle Electronic Control Unit (VECU) and retest the system. If code
SID 231 is still set, go to Test 9 — Checking Continuity on the Data Line.

Test 7 — Checking for a Short in the Instrument Cluster Module

(ICM)

1. Turn the ignition switch OFF.

2. Reconnect the Vehicle Electronic Control Unit (VECU) connector C.

3. Disconnect the Instrument Cluster Module (ICM) connector A.

4. Turn the ignition switch ON.

5. Connect the scan tool and check for code SID 231.

If code SID 231 is still active, go to Test 8 — Pin to Pin Test at Engine
Management System (EMS) Module.

If code SID 231 is NOT active, check the Instrument Cluster Module (ICM) harness
and all connections for loose, corroded or damaged terminals and repair or replace
as necessary. If no loose, corroded or damaged terminals are found, replace the
Instrument Cluster Module (ICM) and retest the system. If code SID 231 is still
set, go to Test 9 — Checking Continuity on the Data Line.

Test 8 — Pin to Pin Test at Engine Management System (EMS)

Module

Figure 6

1. Turn the ignition switch OFF.

2. Disconnect the Engine Management System (EMS) Module connectors A and

B.

3. Check for continuity between Engine Management System (EMS) Module

connector B pin 51 and all other pins (except Engine Management System
(EMS) Module connector B pin 55) on connectors A and B. Then check for
continuity between Engine Management System (EMS) Module connector B
pin 55 and all other pins (except Engine Management System (EMS) Module
connector B pin 51) on connectors A and B (see Figure 6).

65
 If continuity exists, repair or replace the damaged data line harness or
connectors.

If continuity does not exist, replace the Engine Management System (EMS)
Module.

Test 9 — Checking Continuity on the Data Line

Figure 7

1. Turn the ignition switch OFF.

2. Disconnect the Engine Management System (EMS) Module connector B.

3. Check for continuity between Engine Management System (EMS) Module

connector B pin 55 and pin D of the Data Link Connector (DLC). Then check
for continuity between Engine Management System (EMS) Module connector
B pin 51 and pin C of the Data Link Connector (DLC).

If the continuity exists, replace the Engine Management System (EMS)

Module (see Figure 7).

If the continuity does not exists, locate and repair the open in the data line
and retest the system.

Test 10 — Checking the CAN-BUS Termination Resistor

Figure 8

1. Turn the ignition switch OFF.

2. Disconnect the CAN-BUS Termination Resistor connector.

3. Check for continuity between pins 1 and 2 of the CAN-BUS Termination

Resistor (see Figure 8).

If the resistance is between 115–125 Ohms, go to Test 11 — Checking Engine

Management System (EMS) Module Resistance.

If the resistance is NOT between 115–125 Ohms, replace the CAN-BUS

Termination Resistor.

Test 11 — Checking Engine Management System (EMS) Module

Resistance

66
 Figure 9

1. Turn the ignition switch OFF.

2. Disconnect the Engine to Front Chassis harness connector.

3. Check the resistance between pins B and K on the Engine Management

System (EMS) Module side of the Engine to Front Chassis connector (see
Figure 9).

If continuity is between 115–125 Ohms, locate and repair an open in the data
line.

If continuity is NOT between 115–125 Ohms, check the Engine Management

System (EMS) Module harness and all connections for loose, corroded or
damaged terminals and repair or replace as necessary. If no loose, corroded
or damaged terminals are found, replace the Engine Management System
(EMS) Module.

© Copyright 2006 Mack Trucks, Inc. All rights reserved. Terms of Use

67
 Mack Component Diagnostics
J1587 Data Link

NO Terminating Resistors

Notes:
The J1587 data link is a pair of wires that provides path of communication between the each of the
vehicle’s controllers. This data link has a much slower speed that the J1939. It has four functions that
do not require high speed data transfer.
Functions:
1. Diagnostics
2. Gauge operation
3. Programming
4. Back-up for the J1939 (when the J1939 link has a failure)
Refer to the Data Link Fault Tracing information within EIS. Remember to separate the vehicle
systems when a data link problem is suspected.

See the following pages for a view of this document.

***Instructor note: Click on the document picture in the presentation to open the document for
viewing.

68
J1587 Data Link
Diagnostics

69
MID 140 SID 250 — J1587 DATA LINK

Figure 1 -- J1587 Data Line

Figure 4

When performing electrical tests, wiggle wires and connectors to find intermittent
problems.

Failure Mode Identifier (FMI): 9 (Data Absent)

Parameter Identification (PID): S250

Message Identification (MID): 140

Circuit Description: The V-MAC IV system transmits fault codes and warning
messages across the J1587 data line. In the event of a J1939 data line failure,
critical system data is prioritized and then transmitted across the J1587 data lines
to the appropriate control module. The V-MAC IV system is designed to allow limp
home engine operation with the loss of the J1939 data signal as long as the J1587
data lines are still operational.

Code Setting Conditions: Code PSID 250 will set when the Instrument Cluster
Module (ICM) loses all communication on the J1587 data line. The fault will
become inactive if communication resumes.

Test 1 — Checking for Code SID 250

1. Verify that code SID 250 is set.

If code SID 250 is set, go to Test 2 — Checking for an Open between the
Instrument Cluster Module (ICM) and Vehicle Electronic Control Unit (VECU).

If code SID 250 is NOT set, wiggle the EMS Module harness and connectors to
try to set the code. Visually inspect the EMS Module connectors and wires for
poor connections.

70
Test 2 — Checking for an Open between the Instrument Cluster
Module (ICM) and Vehicle Electronic Control Unit (VECU)

1. Turn the ignition switch OFF.

2. Disconnect the Instrument Cluster Module (ICM) connector A.

3. Disconnect the Vehicle Electronic Control Unit (VECU) connector C.

4. Check for continuity between Instrument Cluster Module (ICM) connector A

pin 18 and Vehicle Electronic Control Unit (VECU) connector C pin 1. Then
check for continuity between Instrument Cluster Module (ICM) connector A
pin 17 and Vehicle Electronic Control Unit (VECU) connector C pin 2.

If continuity does not exist, locate and repair the open in the data line and
retest the system.

If continuity does exist, go to Test 3 — Checking for an Open between the

Instrument Cluster Module (ICM) and Engine Management System (EMS)
Module.

Test 3 — Checking for an Open between the Instrument Cluster

Module (ICM) and Engine Management System (EMS) Module

1. Turn the ignition switch OFF.

2. Disconnect the Instrument Cluster Module (ICM) connector A.

3. Disconnect the Engine Management System (EMS) Module connector A.

4. Check for continuity between Instrument Cluster Module (ICM) connector A

pin 18 and Engine Management System (EMS) Module connector A pin 34.
Then check for continuity between Instrument Cluster Module (ICM)
connector A pin 17 and Engine Management System (EMS) Module connector
A pin 33.

If continuity does not exist, locate and repair the open in the data line and
retest the system.

If continuity does exist, the Instrument Cluster Module (ICM) may have to be
reflashed. Contact Mack reliability engineering.

© Copyright 2006 Mack Trucks, Inc. All rights reserved. Terms of Use

71
 Mack Component Diagnostics
Instrumentation

Notes:
The instrument cluster control unit provide a viewing display for accessing diagnostic messages.
These messages are displayed in the SAE format. Vendor application may have different message
descriptions when viewed in the vendor diagnostic tool. The Mack instrument cluster has internal
diagnostic tests for gauges, dash lights, and the display.
When diagnosing the instrument cluster, remember it is a read only unit. It displays the data it
receives. The cluster samples the J1587 data for any messages that are sent from other ecu’s on the
link. The fault codes utilized by the instrument cluster follow the SAE standards.

72
 Mack Component Diagnostics
Mack Engine

Mechanical Problem?

Symptom based problem?

Electronic?

Fault Code based problem?

Notes:
Engine diagnostics can be performance, mechanical, or electronic in nature. The engine electronic
system is capable of monitoring several components, sensors, and wiring. The sensors are used to
monitor conditions such as pressures, temperatures, and levels. This provides more details for more
accurate engine diagnostics. The software has been programmed to monitor data and data link
problems as well.
The fault codes utilized by the engine ecu follow the SAE standards.
Note: VMAC, VMAC II, and VMAC III electronic diagnostics use the blink code system. The SAE
standards may be viewed in the descriptions of the fault code in the service literature. The VMAC IV
system uses the MID, PID, SID, PSID, PID, PSID, and FMI as indicated in the SAE standard.
Note: When viewing the blink codes, refer to the Mack service literature for details about the particular
fault. The description of the fault will have the SAE standard description listed.

73
 Mack Component Diagnostics
Vehicle ECU

Notes:
The vehicle ecu monitors and controls cab inputs and outputs from the driver. These inputs include
ignition key status, cruise control switch inputs, accelerator pedal inputs, etc. There are many tests
within Vcads Pro to evaluate the switch inputs and functions of the vecu and it components. The fault
code descriptions include component input monitoring, control status, and data and data link
diagnostics.
The fault codes utilized by the vecu follow the SAE standards.

74
 Mack Component Diagnostics
Software and Parameters

Software and Parameters

Other factors that affect vehicle performance:

Software Parameters and Design

Software programming: Datasets
(How does the customer want the vehicle to operate?)

Parameter settings
(Understand the parameter and how it affects the vehicle’s operation)

Notes:
Customer complaints may be caused by specific mechanical or electronic problems. Many times a
problem can be the result of improperly programmed customer level parameters. When
troubleshooting a performance complaint or a lack of functionality complaint, the customer
parameters should be checked and adjusted to correct the problem. A software problem can also be
the root cause of a complaint. Normally these software issues are handled through campaigns or
service programs. If a software problem is suspected, an E-Service should be submitted to Mack
Technical Support to ask for assistance. Be sure to include the currently programmed software
information in the E-Service notes.
1.Check customer parameters
2.Check software versions
• Vehicle Information test
• Service tools to read software versions (information display or Vcads Pro)

75
 Mack Component Diagnostics
Follow Up and Repair

Results…..Validation…..Communication

Validate your results

Inform the customer of repair options

Repair vehicle

Notes:
The diagnostics process is not complete until every test has been validated. Informing the customer
of needed repairs and the costs involved is a very important part of triage diagnostics. The
relationship between the customer and the dealer is greatly influenced by the ability of a service shop
to accurately diagnose a problem within a reasonable time.
Repairing the vehicle is of course the customer’s decision. However, our ability to diagnose a
problem timely and efficiently demonstrates to the customer the technical capability of the dealer.
This builds a strong relationship between the customer and the Mack dealer. Customer satisfaction
comes first!

76
 Vendor Application Diagnostic
Information

Vendor Application Diagnostic Information

77
 Vendor Application
Diagnostics Information -
Bendix

Notes:
Bendix service tools:
ACom Diagnostics V4.0 (Diagnostic Software) RDU (Remote Diagnostics tool for reading, clearing,
and reconfiguring ecu. Refer to Bendix.com for the following materials:
Product information, service data sheets, part cross reference, air brake training registration, Bendix
field representatives, order literature.
Refer to myBendix.com to view documents such as quick reference catalog, warranty information,
troubleshooting guides, etc.

78
 Vendor Application
Diagnostics Information -
ArvinMeritor

Notes:
ArvinMeritor service tools:
TransSoft Diagnostic software. Refer to www.perks-web.com/transSoft/ to access information and
download the TranSoft diagnostic software.
This service tool provide diagnostic tests for the ZF Freedonline transmission.

79
 Vendor Application
Diagnostics Information -
Eaton

Notes:
Eaton Roadranger service tools: Service Ranger (Diagnostic Software)
Refer to http://sr.eaton.com for the following materials:
Product information, parts information, and Service Ranger software information. Select the tab for
Service Ranger to view Eaton’s diagnostic website.

80
 Mack Diagnostic Software

Mack Diagnostic Software

Notes:
The diagnostic procedures listed in the Mack service literature will instruct the technician
to make accurate measurements of circuit resistances and voltages to determine where a specific
problem may be. This data may also be used for warranty authorizations as well as reference material
during a technical support call.

81
 Mack Diagnostic Software –
VCADS Pro General
VCADS Pro General

VCADS Pro General Operation

Notes:
• See the following pages for a view of this document.

***Instructor note: Click on the document picture in the presentation to open the document for
viewing.

82
General Operation,
Functions, Updates,
and Setup

83
VCADS Pro menu
All operations and job cards are opened from the menu. In addition, a number of administrative settings can be
made.

Below you find an overview displaying some useful short commandos and shortcuts, to access a number of
common functions in VCADS Pro.

Key type Keys Function

Access key Alt Toggle between the menu— and the window
layout.

Access key Alt + letter Opens the menu which name contains the
underlined letter.

Access key Alt + F4 Closes active window.

Access key Alt + F6 Toggles between operation— and job card view.

Access key Alt + Tab Displays next primary window (or application).

Access key Space bar Starts and stops an operation.

Access key Esc Closes the opened operation and have the same
functionality as Close and Cancel buttons in
secondary windows.

Access key Y Answers Yes in a Yes/No dialogue.

Access key N Answers No in a Yes/No dialogue.

Shortcut key Ctrl + C Copy command.

Shortcut key Ctrl + V Paste command.

Shortcut key Ctrl + S Toggles between Simulator mode or Normal mode.

Shortcut key Ctrl + L Lock/log on command.

Shortcut key Ctrl + P Print command.

Shortcut key Ctrl + E Displays the notes window.

Shortcut key Ctrl + Q Displays prerequisites.

Shortcut key Ctrl + O Opens the job card search dialogue.

Shortcut key F1 Displays contextual Help window.

Detailed description

84
Position Name Description

1 VCADS Pro menu with the following

sub-menus. In some cases there are
also icons in the menu, for instance
Intermediate Storage.

File The following options are available from this menu.

z Identify – Identifying the vehicle.

z Print – Prints the current screen.
z Printer set up – Selecting the printer.
z Print labels – Prints labels to the engine electrical
control unit (EECU).
z Lock / Log on – Activates the VCADS Pro
security lock. A new user can now log onto
VCADS Pro
z Exit – Exits VCADS Pro.

View The following options are available from this menu.

z Operation view Displays the operation view.

z Job card view – Displays the job card view.
z Test – Displays / hides test operations.
z Calibration – Displays / hides calibration
operations.
z Programming – Displays / hides programming
operations.

85
 z Information text – Displays / hides text and image
field.

Operation The following options are available from this menu.

z Open – Opens an operation.

z Open as simulated – Opens an operation in
simulation mode. Re-identification does not need
to be carried out.
z Start – Starts an operation.
z Stop – Stops an operation.
z Start playback – Starts playing back the selected
operation.
z Pause playback – Pauses the playback of the
selected operation.
z Stop playback – Stops the playback of the
selected operation.
z Rewind – Rewinds an operation manually.
z Previous session – Skips to previous session
manually.
z Next session – Skips to next session manually.
z Fast forward – Fast forwards an operation
manually.
z Notes – Select to add a note to the operation.
The note is saved to the job card.
z Basic information – Displays the basic
information for the operation.
z Conditions – Displays the conditions for the
implementation of the operation.
z Close – Closes the operation view.

Job card The following options are available from this menu.

z Open – Opens a job card.

z Delete – Deletes a job card.
z Import – Imports job cards
z Export Exports job cards
z Close – Closes the job card.
z Name on active job card – Name on the active
job card is displayed.

Tools The following options are available from this menu.

z Simulator – Activates/deactivates VCADS Pro

simulation mode.
z Intermediate Storage – Handles intermediate
stored software.
z Administrate software... – Handles ordered,
available and used software.
z Update VCADS Pro – Downloads a new software
version.

86
 z Options – Selected to customize program
settings.

Help The following options are available from this menu.

z Contents – Displays help text.

z Update information – List of updates for the
VCADS Pro application.
z Parameter information – List of available
parameters.
z Software information – Here is the information
found on current conversion kits and emission
level changes.
z Last logged fault – Displays the last logged fault.
z About VCADS Pro – Shows a dialog window with
the current application version of VCADS Pro.

2 Toolbar The following function buttons are available in the

toolbar.

Identify – click the button to identify a new vehicle.

Print – click the button to print the current screen.

Operation view – click the button to display the

operation view.

Job card view – click the button to display the job card
view.

Test – click the button to display/hide test operations.

Calibration – click the button to display/hide calibration

operations.

Programming – click the button to display/hide

programming operations.

Information text – click the button to display/hide the text

and image field.

Open – click the button to open an operation.

Close – click the button to stop an operation and return

to the previous view. Alternatively use the ESC key.

Start– click the button to start the current operation.

Alternatively use the SPACEBAR key.

Stop – click the button to stop the current operation.

Alternatively use the SPACEBAR or ESC keys.

Notes – click the button to insert a note into the current

87
 operation. The note is saved to the job card.

Basic information – click the button to display the same

information in the text and image field as when the
operation was started.

Conditions – click the button to display the conditions for

the implementation of the operation and the status of
conditions.

Start playback – click the button to start playing back

the selected operation.

Pause playback – click the button to pause the playback

of the operation. Restart the playback of the operation
by clicking Start playback..

Stop playback – click the button to stop playing back the

operation.

Rewind — Press the button to rewind the operation

manually.

Previous session — Press the button to skip to the

previous session manually.

Next session — Press the button to skip to the next

session manually.

Fast forward — Press the button to fast forward the

operation manually.

Session number — which session are played.

Session time — how far into one session are you.

3 Status bar Left-hand side: The model and VIN number of the
relevant vehicle is displayed here.Right-hand side: The
status of communication between the PC tool and the
vehicle and between the PC- tool and the central
system is displayed. When communication has been
established a connection icon is displayed. The text
Simulator (in a yellow field) is displayed here if the
program is in simulator mode.

88
Operations, general
The operations that can be carried out depends on the vehicle connected to the PC tool and the authorization of
the user. Note that the screen images shown in the help text may differ from those in the PC tool. This depends
on the vehicle being tested and the level of authorization of the user.

Note: The screen images shown in the help text may differ from those in the PC tool depending on the vehicle
being tested and the level of authorization of the user. By the time of this manual being written not all functionality
was set, and that is also a reason that some of the images are not exactly shown in the manual as in the PC tool.

Because most operations are built up of standard components the same method can be used for all operations.
Instructions for undertaking individual tests are available in the application.

The first time you select an operation which requires communication with control units after manual matching, the
program reads off information from the control units. This may take a minute or two. The program checks that the
control units that store the vehicle's identity and serial number all contain the same vehicle identity and serial
number.

Note: If the EECU and VECU contain software that is not compatible with each other, only a subset of
programming operations will be shown. There is a risk that the result of the operation could be incorrect or that
the functionality might be affected.

Operations, implementation

Operations, start-up
1. Connect the PC-tool to the communication socket in the vehicle. Switch on the power supply.
2. Start VCADS Pro.

Identification

Identification, implementation

Depending on wether you are a single-or a dual dealer, different dialogue are shown.

Note: The PC-tool must be connected to the vehicle before identification is carried out.

1. The dialogue box for a single dealer looks like this.

2. Supported company is listed here (1).
3. Check the box Connect to vehicle (2) to continue, or select Electrical system here (3).
4. Click OK (4).

89
 1. The dialogue box for a dual dealer looks like this.
2. Select which company the vehicle is from (1).
3. Select the Electrical system (3) to continue, or check the box Connect to vehicle (2).
4. Click OK (4).

Activate job card

To carry out operations a new job card must be created or an existing job card, that has not been finalized, must
be opened as active.

Create a new, active, job card (1)

1. Enter the repair order number (3).

2. Enter the registration number (optional) (4).
3. Enter the reason that the job card is being created (optional) (5).
4. Click OK.

90
Open an existing job card as an active job card (2)

1. Select the job card you want to work with from the list. Only job cards that have not been finalized are
contained in the list. And only job cards that match the vehicle on which the work is to be undertaken. If
there are no suitable job cards this option cannot be selected. It is also possible to search for job cards.
2. Highlight the job card. The reason that the job card was started is displayed in field (6).
3. Click OK.

Selecting operation
1. Highlight the desired function group in the Function group field (1). The associated operations are now
displayed in field (2). In front of the operation title is a symbol that denotes the type of operation. If there is
a red box around the symbol the operation is being carried out by an external program.
2. Start the operation.

Note: It is also possible to start an operation in simulation mode by right clicking the operation and selecting Open
as simulated.

91
The image is not showing actual conditions.

Operation number

All operations have an operation number. This is indicated before the operation title.

Warning messages
Certain operations have graded warning messages depending on the type of operation. To continue the operation
the user must confirm that the warning has been noted. Click Yes in the dialogue box to continue.

92
Detailed description, operations
This section describes the functions available in the window when an operation has been opened. The illustration
shows a typical test/calibration operation. When programming a programming list or parameter presentation are
shown in field 5.

93
The image is not showing actual conditions.

Position Name Description

1 Function group field This shows the function group to which the operation belongs.

2 Title field This shows the current operation title.

3 Text box This shows text information about either the entire operation
or a single sub-operation. Enlarge the text field by clicking the
magnifying glass icon. In certain operations, further
information, such as wiring diagrams, can be displayed using
a link.

4 Sub-operation Each operation consists of one or more standardized sub-

operations. The illustration shows a typical test/calibration
operation. When programming a programming list or
parameter presentation are shown in this field.

5 Scroll bar The scroll bar is only available when the operation is greater
than the window. Use the scroll bar to see the entire
operation.

Wiring diagrams
The wiring diagrams, viewed by clicking a link in the text field, should be used as a description of the function. The
illustrations show the conditions that apply when the function is active.

94
Note: The wiring diagrams cannot be used as a basis for taking readings on the circuit.

Cable colors

Cables in the wiring diagrams have four colors, red, blue, green and black

z Red is only used for power supply, irrespective of whether it is battery voltage or a supply from a control
unit, for example 5 V.
z Blue is used for cables connected to a ground terminal, even if they are indirectly connected (via a control
unit for example).
z Green is used for signal cables, primarily to indicate the signal cable from a sensor.
z Black is used where the function of the cable is not relevant or where the cable cannot be categorized
according to the other colors.

Checking conditions

Click this button to check the conditions status. Checking the conditions can be carried out at any time except
when the actual operation is being run. If the button is grayed out there are no conditions for the operation.

Once an operation has been started, the conditions for implementing the operation are checked. In certain cases
conditions are checked even after an operation has been exited.

A window containing conditions and their status is displayed. The following status markings are available.

z Green marking – Condition fulfilled.

z Red marking – Condition not fulfilled.
z Grey marking – Condition not yet checked
z Check box – Condition that must be checked manually, for example blocked wheels. When a manual
check has been carried out the check box must be checked.

In certain conditions the sensor value on which the status marking is based is displayed.

Click Cancel to exit the check.

95
Playing back operations
Playing back operations can take place immediately an operation has been completed or saved to a job card.
Programming operations cannot be played back.

Playing back saved operations can be undertaken in the job card menu.

Use the playback buttons illustrated below to play back an operation immediately after it has been completed.

Start playback

Click this button to play back the operation that has been selected.

Pause playback

Click this button to pause the playback of the operation. Restart the playback by clicking Start.

Stop playback

Click this button to stop the playback of the operation.

Play back the operation manually

Click the four button to rewind or fast forward operations, or alter between sessions manually. In the small
windows to the right you see the session number and session time. This operation is only possible when playback
is stopped.

96
Tools

Simulator
Select Simulator in the Tools menu or Ctrl+S, to put the program into simulation mode. In simulation mode
Simulator appears in a yellow field on the status bar at the bottom of the screen.

Note: Random values are used in simulation mode. This means that test and calibration results are not realistic
and only simulated job cards are displayed.

Update VCADS Pro

If more than 14 days have passed since VCADS Pro was last updated, a dialogue box appears when VCADS Pro
is started. The dialogue box asks whether the system is to be updated now.

Select Yes to update. Select No to start VCADS Pro as normal and prevent VCADS Pro updating.

You can also select Update VCADS Pro in the Tools menu to update VCADS Pro.

When you chose to update VCADS Pro, a connection is made with the central system and a check is performed
to see if the software needs updating. If the software does not need to be updated, this is shown in a dialogue
window.

If an update is required, a dialogue box appears with information about the size of the required data packet.

Select Yes to start the file transfer. Select No to cancel and transfer the files later. File transfer starts
automatically if no alternative is selected within the given time.

97
If more updates must be downloaded, a dialog box will advise of this and the file transfer procedure will be
repeated.

A dialog box opens when all the file transfers are complete. Select OK to install the update.

If only the databases have been updated VCADS Pro does not need to be restarted.

If you update other software, the application closes down VCADS Pro automatically. When updating is finished,
the User ID and Password must be given after which VCADS Pro starts.

Options
Select Options in the Tools menu to customize user or PC-specific settings in the application.

General
General settings for language, units and start-up.

Note: If unit settings are changed when an operation is open, the operation must be closed and reopened for the
change to be applied.

1. Select the General tab (1).

2. Highlight the desired language in the list (2).
3. Select either Metric or US units (3).
4. Select desired size of the buttons in the tool menu (4).
5. Check the box if an identification box should appear automatically when the program is started (5).
6. Select desired size of the operation texts (6).
7. Click OK (7).

98
Screen
Selecting background and setting security lock delay is described below. The recommended delay is 20 minutes.

Note: The security lock delay only locks VCADS Pro. When the lock has been activated it is still possible to use
other programs on your PC.

1. Select the Screen tab (1).

2. Select the desired background from the list (2). The preview is updated (3) after each new selection.
3. Enter the desired security lock delay in the Security lock delay field (4) or click on the arrow beside the
field.
4. Click OK (5).

Note: The Windows screensaver must not be activated when VCADS Pro is in use.

99
Connection
If a user requires a telephone number outside their own area (when traveling for example) they can decide the
order in which telephone numbers will be called when dialing the central system.

To obtain the telephone numbers that are required, the user contacts the Helpdesk and orders new telephone
numbers. The user is asked to update the telephone directory by updating VCADS Pro.

Connection can be found in Options in the Tools menu.

The connection settings are divided into two tabs:

z Connection (1)
{ Selecting connection type.
{ Changing the priority of the telephone numbers VCADS Pro calls when connecting to the central
system.
z Locations (2)
{ Selecting country.
{ Selecting area code.
{ Selecting the prefix for national and international calls.
{ Selecting GSM (mobile phone), tone or pulse dialing.

If the user changes the standard settings VCADS Pro will remind the user that they are not selected every time it
is started. The user can choose to restore the standard settings or keep their current settings.

100
Connection type

Select the button corresponding to the central system connection type to be used (3).

Telephone number

1. Highlight the telephone numbers to be moved (4).

2. Use the arrows (5) to move the highlighted telephone number up or down the list. VCADS Pro will call the
telephone numbers in the selected order.
3. To move more numbers, highlight the next number to be moved and repeat point 2.
4. When the priority of the numbers has been changed, go into Location (2) and check that the location and
equipment settings are correct.

Location

Settings for dial up using a GSM telephone (mobile phone)

1. Click the box (7) if a GSM telephone (mobile phone) is being used. Fields (9) and (12) cannot be selected
as these settings are not used for GSM telephones (mobile phone).
2. Select the country from the list (8).
3. Press the OK button (6) to save the new settings and close the window.

101
Settings for dial up using a landline telephone

Note: Dial-up should be over direct analog line. If the telephone is connected via an exchange, communication
between the central system and VCADS Pro cannot be ensured.

1. Check that GSM (mobile phone) (7) is not selected.

2. Select the country from the list (8).
3. Enter the area code (9).
4. If dial-up is via an exchange a prefix may be required. Enter the prefix in (10). Leave the field empty when
no prefix is needed.
5. If a prefix is necessary to dial a national call enter it in (11). Leave the field empty when no prefix is
needed.
6. Mark for tone or pulse dialing (12).
7. Press the OK button (6) to save the new settings and close the window.

Communication Unit Settings

Communication Unit RP 1210A

Here the RP1210A Adapter is configured.

1. Select the Comm. unit configuration tab (1).

2. Select to configure communication unit RP1210A Adapter (2).
3. Select hardware for RP1210A Adapter from the drop down menu (3).
4. Select Port number from the drop down menu (4).
5. Select Protocol from the drop down menu (5).
6. Click the OK button (6) to save your settings and close the window.

102
Communication unit 9998555

The following is a description of the settings in communication unit 9998555.

1. Select tab Comm. unit configuration (1).

2. Mark the communication unit by clicking on communication unit 9998555 (2).
3. Select settings in the dropdown menu for communication unit 9998555 (3).
4. Click OK to save settings and close window (4).

103
Communication Unit 88890020

Here is a walkthrough of configurations and selections of unique communication units for 88890020.

Note: It is only necessary to configure the communication unit WLAN (wireless communication) is going to be
used!

1. Select the Comm. unit configurationtab (1).

2. Select to configure communication unit 88890020 (3).
3. Here is a presentation of information about the communication unit (communication units in case you have
several) (4).
4. Click the Settings button (5) to see your settings for each unique communication unit.
5. To change your settings click the Configuration button (6).
6. Click the OK button (7) to close the window.

104
Note: By clicking the button Signal (2) a window is opened showing the strength of the signal. See picture below.

Basic configurations
1. Choose a nickname (1).
2. Choose which type of communication you would like to use (2). If you choose Directly to adapter a new
window will open where you can see which IP-addresses you connect to and you can also change these
IP-addresses. If you choose Via accesspoint a new window will open where you should fill in IP-addresses,
security level and authentication.
3. Click the Settings button (3) to get to communication type specific configurations.

105
 4. Here you can choose if you would like to use only USB or USB in combination with one of the other
options. (4).
5. In the basic configurations window you can click the Status button (5) to see software version number,
driver version number, WLAN-dongle, vendor ID, product ID and device ID. You can also see error codes.
6. Click the button Update Software (6) to check the possibility to update the software for the communication
unit.
7. Click the OK button (7) to close the window.

Note: When clicking the button Update Software (6), a window pops up instructing the user through the update,
see picture below. Older versions of the software will be saved on the PC for use in case the newer software
contain errors preventing use of communication unit 88890020. Normally the latest software should be used and
downloaded to communication unit 88890020.

106
Configuration: Directly to adapter
Note: You must have a WLAN-card installed on the PC. Contact Help Desk to find out which cards that are
recommended. If you use the Panasonic CF–29, you are equipped with a WLAN-card.

1. On this tab (1) you can view the settings that the system have generated automatically. These settings only
need to be altered if a conflict occurs between different WLAN-units. Reset of the automatically generated
settings is done by clicking the Restore Default button (5).
2. You can change SSID and channel for both adapter and PC here (2).
3. You can change the IP-address and Net Mask for the adapter here (3).
4. You can change the IP-address and Net Mask for the client here (4).
5. Click the OK button (6) to save changes and close the window.

107
Configurations: Via Accesspoint
Note: Consult your PC-expert before making this configuration!

1. On this tab (1) you can set the parameters demanded to run via accesspoint.
2. Enter IP-address, Net Mask and SSID here (2).
3. Enter your user name, password and level of security here (3).
4. Click the OK button (4) to save changes and close the window.

108
Status
1. In the basic configurations window you can click the Status button to see software version number, driver
version number, WLAN-dongle, vendor ID, product ID and device ID (1). You can also see fault codes (2).
See also chapter Fault tracing below.
2. Click the OK button (3) to close the window.

109
Fault tracing

Two chapters follow below which describe known problems and fault code descriptions for communication unit
88890020.

Known problems
Following problem might occur when using the communication unit 88890020:

z The message Power surge on hub port, is shown in the status field on some PCs. The message might
appear when the USB-cable is connected to the communication unit 88890020. The Communication unit
will start and function properly despite this message.

Fault code description

The table below lists fault codes, their reason for occurring and preventive solutions.

Fault codes Reason Action

1 Application flash area fault Send your adapter to be repaired

2 Bootstrap flash area fault Send your adapter to be repaired

3 Parameter flash area fault Send your adapter to be repaired

4 Parameter flash area worn- Send your adapter to be repaired

110
 out

5 Internal RAM fault Send your adapter to be repaired

6 External RAM fault Send your adapter to be repaired

7 There is some problem Send your adapter to be repaired

accessing the USB chip

8 There is some problem Send your adapter to be repaired

accessing the temperature
sensor

9 There is some problem Send your adapter to be repaired

accessing the SDIO serial
bus

10 There is some problem Send your adapter to be repaired

accessing the SPI bus
serial bus

11 There is some problem in Send your adapter to be repaired

the CPU

12–19 There is some problem with Send your adapter to be repaired

the HW.

20 There is a power fail, Check the voltage supply to the adapter first. If the supply is
detected in the adapter OK, send your adapter to be repaired.

21 Supply-voltage is too low Check the voltages supply to the adapter

22 Supply-voltage is too high Check the voltages supply to the adapter

23 Temperature is too low Warm up the adapter and try again

24 Temperature is too high Cool the adapter and try again

25–29 There is some problem with Consult the support for further information
the adapter environment

30 No USB supply voltage First check USB cable. If this do not work send the 0020
available adapter to be repaired.

31 Power surge on USB host The USB device that is inserted in host port #1 draws to
port #1 much current and is powered down.

32 Power surge on USB host The USB device that is inserted in host port #2 draws to
port #2 much current and is powered down.

33 Unsupported USB device in The USB device that is inserted in host port #1 is not
host port #1 supported by this firmware. Change firmware or see if you
may get a device that is supported.

34 Unsupported USB device in The USB device that is inserted in host port #2 is not
host port #2 supported by this firmware. Change firmware or see if you

111
 may get a device that is supported.

35–39 There is some problem with Consult the support for further information
the USB connections

40 Unsupported SD card Change the SD card

41 Error accessing SD card There is a problem reading or writing the SD card. Change
SD card.

42 SD card is FULL Empty the SD card or exchange to another SD card

43–49 There is some problem with Consult the support for further information
the SD card

50 There is no WLAN card Insert a WLAN card into any host port
present

51 The WLAN card is not Change the WLAN card

working correctly

52 There were no access point Move the adapter to where it is better reception
reachable

53 WLAN signal strength is too Move the adapter to where it is better reception
low

54 An error was detected by Restart the adapter

the WLAN handler

55 An error was detected Consult the configuration and verify correct parameter setup
during authentication to the for current network
network

56–59 An error was detected by Consult the support for further information
the WLAN handler

60 There was a problem during Check the authentication method and involved security keys
the authentication process

61 There was a problem during Check the encryption method and involved security keys
the encryption process

62–65 There was a problem with Consult the support for further information
the security manager

66 There was a problem when The port may already been opened for transfer. Restart the
accessing the TCPIP port adapter.

67 There is a TCPIP collision Change the TCPIP number to avoid the collision
on the network

68 Time-out occurred during Communication has been lost. This DTC is just for tracing
wait for a TCPIP package problems. Continue normal usage of the adapter.

69 There was a error reported Restart the adapter

112
 from the TCPIP stack

70–75 There is a problem related Consult the support for further information
to the TCPIP stack

76 There is some problem with Check the network so that it is not shorted. Otherwise
the SAE J1708 exchange the adapter.
communication

77 There is some problem with Check the network so that it is not shorted. Otherwise
the ISO 9141 exchange the adapter.
communication

78 There is some problem with Check the network so that it is not shorted. Otherwise
the ISO 9141 5Volt exchange the adapter.
communication

79 There is some problem with Check the network so that it is not shorted. Otherwise
the CAN communication exchange the adapter.

80 Wrong login The key given during start of communication was wrong

81–89 There is a general fault Consult the support for further information

Trouble shooting
This is under development. By the next update of the manual, is will be presented here.

Communication Unit Selection

Select RP1210A

Select communication unit for the electrical system.

1. Select the Communication Unit Selection tab (1).

2. Select electrical system in the list (2).
3. Select RP1210A Adapter communication unit (3).
4. Click the OK button (4) to save your settings and close the window.

113
Select communication unit 9998555

1. Select the Communication Unit Selection tab (1).

2. Select electrical system in the list (2).
3. Select communication unit 9998555 (3).
4. Click the OK button (4) to save your settings and close the window.

114
Select Communication Unit 88890020

Warning
When working with a vehicle using a wireless communication interface, it may not be apparent to others
that work with the vehicle is underway. Some activities, such as activation of certain vehicle components
or systems, could cause injury to someone at the vehicle who is unaware that the activity is about to take
place. When using a wireless communication interface, always keep the connected vehicle in clear view
and inform others around the vehicle about the activities.

1. Select the Communication Unit Selection tab (1).

2. Select electrical system in the list (2).
3. Select which communication unit to be used for the chosen electrical system (3).
4. Click the OK button (4) to save your settings and close the window.

115
 Mack Diagnostic Software –
VCADS Pro Fault Codes

Fault Code
Tab

Notes:
The fault code screen has a wealth of knowledge that can assist in the diagnostics process. This
information includes the fault descriptions, number of occurrences, and fault status.
The fault codes tab can be selected to view the only the fault codes and their descriptions. Fault
codes stored in the vehicle’s electronic control units can be read out and cleared using this test.
The information for each fault code includes the control unit that is reporting the fault code (MID), a
description of the fault (PID, PPID, SID or PSID), a description of the nature of the fault (FMI), the
status (active or inactive) and the number of times that the fault has occurred.
The service information in the fault code screen displays the function groups for each of the
controllers on the vehicle. This provides a faster method of looking up fault code descriptions and
troubleshooting steps.

116
 Mack Diagnostic Software –
VCADS Pro Fault Codes

Notes:
READ FAULT CODES - MID Filter:
The control units to be read from are selected in the MID Filter before the test is started. All control
units are selected by default.
Selecting only the ecus in question may isolate and narrow down the list of trouble areas.

117
 Mack Diagnostic Software –
VCADS Pro Fault Codes

Fault
Reporter
Tab

Notes:
FAULT REPORTER:
Fault Reporter information is available for any fault code that has an indicator in the column identified
by the camera icon. To view more detailed information about these particular fault codes from the
Fault Reporter, click on the Fault Reporter tab at the top of the fault codes table. The information
recorded by the ecu consists of many different inputs and sensor readings. It works much like a
“snapshot” of information. This information may help the technician with intermittent or inactive code
troubleshooting.

118
 Mack Diagnostic Software –
VCADS Pro Fault Codes

Reporter
Setup Tab

Notes:
FAULT REPORTER: (Setup)
Settings for the fault reporter may be adjusted to record specific data to help pin point diagnostic
steps. Time, occurrence, and ecu to be monitored are some of the parameters that may be adjusted to
improve diagnostic data logging.

119
 Mack Diagnostic Software –
VCADS Pro Fault Codes

Notes:
Fault codes, Test Mode:
Press the “Settings” button to select which ECU’s to monitor for fault codes. Test performance is
best when fewer ECU’s are selected, therefore select to view only ECU’s that are involved with the
suspected problem circuit. It is possible to place a check mark in the Test Mode selection box only for
ECU’s that are capable of being placed into Test Mode.

Monitor fault codes while attempting to recreate the fault condition, such as moving the suspected
wiring harness. When the problem area of the harness is moved, a fault code corresponding to that
circuit may become momentarily active.
When a fault codes occurs, or the status of a fault code changes, the chart will be updated with a !
symbol and a tone will be heard from the PC.

Although the engine must be OFF when entering Test Mode, the vehicle can be operated when an
ECU is in Test Mode. To do this, enter the Test Mode with the engine OFF. After the test has started,
the engine can be started. The vehicle can then be operated in order to recreate the suspected fault
condition.

120
 Mack Diagnostic Software –
VCADS Pro Sensor Values

Monitor sensor values

to diagnose customer
complaint

Monitor sensor values

and compare to
symptoms and fault
codes.

Notes:
Sensor Values, Monitoring
The engine controller’s sensors may be monitored to compared to customer complaints. This
information can assist the technician during the diagnostic process to evaluate electronic problems
as compared to mechanical problems.

121
 Mack Diagnostic Software –
VCADS Pro Programming

Vcads Pro

1. Tests

2. Calibrations

Notes:
Vcads Pro Tests and Calibrations

• See the following pages for a view of this document.

***Instructor note: Click on the document picture in the presentation to open the document for
viewing.

122
Vcads Pro Tests
and Calibrations

123
Test/Calibration

Presentation element
This section gives a general description of the available presentation elements.

General construction
Most presentation elements contain the following components.

z Start/Stop (1): Buttons to start and stop the current operation.

z Information (2): Button to show text and image information related to the current presentation element in
the text and image box.
z Graphic element (3): This displays measurements in graphic form.
z Evaluation (4): When the operation is complete an evaluation can be made. In certain cases the evaluation
is automatic. In other cases the User must fill in whether the result was OK or not. The result is stored on
the job card.
z Status box (5):

Displayed when a sub-operation is stopped.

Displayed when a sub-operation has been started.

Displayed when a sub-operation can not be started because the signal can not be read.

Displayed when a sub-operation is started but is not working fully because of some of the signals can not be read.

124
Evaluation
This presentation element is used to evaluate the operation.

Read/send digital value

This presentation element is used for a continuous readout of values (speed, temperature and pressure for
example). This presentation element is also used to set a parameter to a specific value and then to check how the
vehicle reacts.

Read/send digital values (without start and stop buttons)

This presentation element is a variant of Read / send digital value element. It is smaller and does not have a
separate start button.

Read the value and status

This presentation element is used to read several values and several statuses at the same time.

125
Read value, bar chart
This presentation element is used for a continuous readout of a value. A bar chart and a minimum and maximum
line display the current value and minimum and maximum value. The values are also displayed numerically next
to the bar chart.

Activate signal output

This presentation element is used to activate a signal output on a control unit.

Choose sub-operation
This presentation element allows you to choose which sub-operations you wish to activate from the drop-down
box instead of having all sub-operations included in the main operation presented side by side in a sequence.

126
Read values with limits
This presentation element is used to read off a parameter and at the same time display its minimum and
maximum limits. Presentation is graphical and numerical.

Read several values with limits

This presentation element is a variant of the Read values with limits element. The presentation element can
process several values and limits.

Status reading
This presentation element is used to read digital signals. The digital signals are linked with various figures. This is
for reading status signals in the vehicle control unit for example.

Below is a list of the various status symbols and what they mean. Other symbols are used in certain operations.
These symbols are described in the operations.

127
Active

The list below indicates the different colors that the lamp can have. The different colors depends on how they are
defined in the test.

z Green lamp
z Red lamp
z Yellow lamp
z Orange lamp

Inactive

Grey lamp. Signal not active

Read error

Error message. A fault has occurred.

Not available

Grey lamp. Signal not active

Status reading (without start and stop buttons)

128
This presentation element is a variant of the Status reading element. It is smaller and does not have a separate
start button.

Status reading several signals

This presentation element is a variant of the Status reading element. Several signals can be read at the same
time.

Deactivate injectors
This presentation element is used to deactivate injectors. Click the corresponding button to deactivate the desired
injector. A selected button indicates that the injector is deactivated.

129
Graph, parameter/time (1–2 values)
This presentation element is used to graphically represent how one or two analog signals vary with time. The
scales for the various parameters are displayed on the left and right vertical axes respectively. Vertical lines
indicating the presence of an external change may occur in this presentation element.

130
Graph, parameter/time (3–4 values)
This presentation element is used to show graphically how analog signals vary with time. The scales for the
various parameters are displayed on the left and right vertical axes respectively. Vertical lines indicating the
presence of an external change may occur in this presentation element.

Three or four signals can be displayed in the graph at the same time. To facilitate evaluation, the curves can be
turned on and off by checking the boxes under the graph.

131
Bar chart
Bar charts exist for various purposes (cylinder compression tests and cylinder balancing tests for example). There
may be horizontal lines in the diagram. These indicate the minimum and maximum levels obtained during the
tests.

A table is displayed next to the bar graph in which the test values are displayed numerically.

Examples of test/calibration operations

This section contains a few typical examples of how test/calibration operations are carried out. The procedures
may differ somewhat depending on whether all the sub-operations are started from the toolbar or if they are

132
started separately.

Sensor and Parameter values, monitoring

Allows the user to monitor a selection of sensor values read from the J1587 serial communications bus. The user
may select the desired sensors from the Available signals list to monitor engine and vehicle operation.

Display available signals

Select the ECU/ECUs in the Display available signals field (1), that have the sensor values required to be
monitored. Each selected ECU will populate the Available signals field (2) with their respective parameters.

Available signals

Scroll through the list of parameters in the Available signals field (2), to locate the ones to be monitored. Click on
the desired parameter to be monitored to highlight it. To add it to the Selected signals field (3), click on the right
arrow button located at number (5). Repeat the process till all the required signals are selected. Multiple
parameters can be selected at one time by making the initial parameter selection and then holding the control
(Ctrl) button down while selecting the other parameters, and then click on the Top Arrow button to enter all the
selections to the Selected signals field (3).

Selected signals

The parameters in the Selected signals field (3), will have their data displayed and recorded during the monitoring

133
process. To remove a parameter from the Selected signals field (3), click on the desired parameter to be removed
to highlight it, and then click on the Bottom Arrow button located left of number (5) to return it to the Available
signals field (2). To remove all parameters from the Selected signals field (3), click on the Clear button located in
between the two fields.

Advanced setup

Selecting the Advanced setup button (4) brings up the Settings and Trigger options tabs.

Settings

z Save to job card (1), allows the user to choose not to save the data to the job card.
z X-axel calibration (2), allows the user to select the calibration of seconds for the X-axis of the parameter
display chart.

Trigger options

134
 z The Trigger options tab allows the user to enable triggers for up to two parameters that start the recording
of data based on the value of the parameter signal.

Example

z When a defined value for the parameter has been achieved (1), recording of data begins.
z The And / Or (2) feature, allows the user to determine if the recording starts when both parameters meet
their trigger criteria (the And option). Or the recording starts when either one of the select signals meet its
trigger criteria (the Or option).
z Pre trigger (3) and Post trigger (4) settings can be selected to determine the window of time to be recorded
before and after the trigger has been tripped.

Templates

All the four options for templates are accessed from the Sensor and Parameters values basic screen, by choosing
from the buttons to the right of number (5).

z Retrieve Template Allows the user to import a previously saved selected signals list.
z Save Template Allows the user to save a selected signals list to a file on the computer hard drive for use at
a later date. The user can save any number of selected signals lists to a folder on the computer hard drive.
The saving of a selected signals list eliminates the need to recreate a particular parameter list each time
the user needs to connect to a vehicle for diagnostic parameter monitoring.
z Remove Template Allows the user to delete a selected signals list from the folder on the computer hard
drive.
z Import Template Allows the user to import a template from a source external to the computer hard drive.

Run Test

135
Selecting Run Test displays the Sensor and Parameters values second screen, which has 3 sections.

1. The graph field (1), which displays the recorded data for the selected parameters values versus elapsed
time displayed on the X-axis.
2. The Parameter name and value field (2), which displays the selected parameters name, PID and their
current graph value.
3. The parameter name and color ID field (3), which identifies the color used to represent the parameter on
the graph. The parameter name and color ID has a check box associated with each parameter that will
remove that specific parameter from the graph when the associated box is unchecked.

Recording data
To begin recording the data for the selected parameters, click on the Start button, (4). When triggers have been
set, the recording will begin automatically based on the trigger criteria. The recording can be stopped at any time
by clicking on the Stop button, (4). Recording can be resumed at any time by again clicking on the Start button.

Playback
Playback of the captured data is possible by clicking on the Start playback button, (5). The playback can be
paused or stopped at any time during the playback by use of the Pause playback and Stop playback buttons, (5).
Manual playback is performed with the use of the slider bar located to the right of the buttons. Moving the slide
bar pointer along its axis will take the playback to a specific point of the recorded data. Clicking on the Start
playback button will resume the playback from that point.

Template

136
Selecting the Template button (6), will return the user to the Sensor and Parameters values basic screen.
Captured data can only be viewed from the job card when the user chooses to return to the Sensor and
parameters values screen, except if the user selected not to save the data to the job card on the Settings option
tab.

Fault codes
The purpose of this test is to read out fault codes stored in the vehicle control units. The fault can be selected
from either individual or all control units. A fault code table is a history of all faults that a controller has detected
since the table was last cleared. Fault codes can be erased together or individually.

General

Note: All logged fault codes are erased when parameters are programmed or read off using VCADS Pro. The
fault codes should be read off first and then saved to a job card to ensure that the fault code information is still
available later.

The fault code function is started from function group 1 in the function group field.

The fault codes contain the following information.

z MID (Message Identification Description): The control unit which transmitted the fault code message. The
designation of the control unit is also displayed in plain text (Engine control unit for example).
z PID (Parameter Identification Description): The parameter that the fault code applies to (accelerator pedal
for example).
z SID (Subsystem Identification Description): The component the fault code applies to.
z FMI (Failure Mode Identifier): Type of fault, physical description.
z Number of occurrences: The number of times that the fault code has been stored.
z Status: Whether the fault code is active or inactive.
z Blink code: The blink code for a particular fault is a two-digit information. Each different fault type for the
same fault can have a different blink code.
z Severity: How serious is the fault.
z First occurrence: Time when the fault code was first stored.
z Last occurrence: Time when the fault code was last stored.
z Odometer: The vehicles total travelled distance.

Fault codes tab

z Start Fault codes. Fault codes are available under group 1 in the function group field. When Fault codes
have been started the following screen is displayed.

137
The following functions can now be carried out:

Read fault codes

1. Select the top option, Read fault codes in field (1).
2. Select the control units from which the fault codes will be read by clicking the button MID filter (2). A
dialogue box opens. Select the check boxes for the control units from which the fault codes will be read.
3. Click the start button. The fault codes are read off.
4. Click the Print button to print directly. All information displayed to the user from the Fault Code operation
can be printed out later from the job card.
5. New faults occurring while viewing the fault code tables will automatically be displayed in the field (3). Click
the Stop button to stop the session and go to the Fault Reporter tab.

Delete all fault codes

1. Select the bottom option, Clear all fault codes in field (1).
2. Click the start button. All the fault codes are deleted.

Note: If a fault occurs after the fault table is cleared and before the power to the controller is cycled (turned OFF
and then ON again), the fault may not be entered into the controller's fault table. Therefore, a request to view the
fault table immediately after it has been cleared may not accurately display faults that occurred after the table was
cleared. To ensure all active and inactive faults are displayed in the Fault Table, turn the ignition off, allow the
accessories relay to disengage, turn the ignition back on and select the Start button.

Fault code information

138
 1. Highlight a fault code in the list (3).
2. Information about the selected fault code is displayed (4).
3. If there is a camera in the column (5), it means that Fault Reporter information is available for the fault
code. Double click the line or go in under the Fault Reporter tab to see these.

Note: The spacebar can be used instead of the start button.

Wiggle wire mode

z Wiggle wire mode is a kind of sensibility device that allows the mechanic to decide under what
circumstances the system shall report the faults.
z It can only be enabled when fault code reading is stopped.

Fault Reporter tab

Fault Reporter information is available for any fault code in which there is an indicator in the camera column. To
view more detailed information from the fault reporter, click on the Fault Reporter tab (1), at the top of the display
object.

The Fault Reporter logs detailed information during the time when a fault occurs, according to the Fault Reporter
Setup.

Two types of information

1. The Fault Reporter will log information about current vehicle conditions when a fault occurs. To do this, the

139
 Occurrence Mode has to be set in the Fault Reporter Setup tab.
2. Fault Reporter will log information about vehicle conditions just before a fault occurs. To do this, the History
Mode has to be set in the Fault Reporter Setup tab.

The picture shows information on Vehicle ECU (2), and Engine ECU (3).

Setup tab

Here the user configures the Fault Reporter to run under Occurrence Mode or History Mode (2) and define the
MID, SID/PID and FMI filters capture to specific fault information. Click on the Setup tab (1), at the top of the
display object, to start the settings.

Occurrence Mode
1. Select what types of faults should be captured by defining the MID, SID/PID, and FMI filters and the
snapshot time that elapses between each record for up to four fault events.
2. Occurrence 1 is default set for MID 128 and Occurrence 2 is default set for MID 142.
3. Occurrence 3 and 4 can be defined by the user to record any available MID fault record, (3).

History Mode
1. Select what type of faults should be captured by defining the MID, SID/PID, and FMI filters and the
snapshot time between recorded fault events.
2. When in History mode, data is being constantly entered and refreshed into columns 1, 2 and 3 of the Fault
Reporter.

140
 3. When a fault occurs that meets the criteria in the Fault Reporter Setup, the data in columns 1, 2 and 3 is
saved and column 4 is populated with the data reported at the time the fault occurred.

Retrigger delay
Retrigger delay operation for both Occurrence and History Modes, determines how long a record should be saved
before being overwritten.

Therefore if the Retrigger delay is set to 200 seconds and a fault that meets the setup criteria occurs at 199
seconds after the Fault Reporter was last written, the parameter data will not be overwritten. However a record of
the time and date the code occurred, will be saved in the Fault Reporter Occurrences field.

Occurrence Mode time elapse can be programmed to a different time setting for each of the four occurrence fields
in the Fault Reporter.

History Mode time elapse is programmable only for the single event it is able to record.

Note: Only SAE J1587 knowledgeable personnel should change the configuration. Incorrect configuration will fail
to record desired fault code events. When the desired settings for the Fault Reporter Setup have been made, click
the run button to save to memory.

Vehicle Maintenance, configuration and reports

Here the user can view, edit and reset the current Maintenance Monitor schedule.

141
Status tab

1. To reset one or more of the Maintenance Monitor schedule items, click on the check box beside each item
(1)
2. Click on the Reset button (2).
3. In the Guard Dog field (3) the user can make a priority list on which systems to watch.

Configuration tab

Set maintenance intervals according to distance, engine hour, or date. A maintenance alarm can also be set for
each interval. This alarm is based on a percentage of the interval.

1. Type in the distance, engine hours, and date interval for each item (1).
2. If a maintenance alarm is desired, enter the appropriate percent for each interval (2).
3. Click on the Set button (3).

Note: To set Maintenance Intervals to MACK defaults, click on Load Defaults and select the appropriate option.

If the Predictive Oil Change feature is installed and enabled, the Oil and Filter Change maintenance item data will
be replaced with Predictive Oil Change maintenance item data.

Predictive Oil Change uses average vehicle speed and average fuel economy since the last oil change to predict
the oil change interval.

Note: The Predictive Oil Change function will revert to a short haul schedule if the oil change interval or average

142
vehicle speed drop below predefined thresholds.

Unit pump, calibration

Test Unit pump calibration codes

To verify the calibration codes in the ECU you do as follows.

1. Select Test in the field (1).

2. Enter the calibration code for each Unit pump into its respective field, far left from (4).
3. Click on the Play button(2).

The Engine ECU will be queried for the calibration codes in memory. Those that match the entries made by the
user will be identified by a green symbol, left of (4). A red symbol indicates the calibration code in memory does
not match the calibration code entry made by the user.

Calibrate Unit pump calibration codes

To calibrate the calibration codes in the ECU you do as follows.

1. Select Calibrate in the field (1).

2. Enter the calibration code for each Unit pump into its respective field, far left from (4). Calibration codes for
all Unit pumps, or a select number of Unit pumps, can be entered and programmed at the same time
3. Click on the Play button(2).

143
Successful programming of the calibration codes is indicated by the green symbol, left of (4). A red symbol
indicates the calibration code is incorrect for that Unit pump, and programming was not successful.

Note: The four-digit calibration codes and the serial numbers are stored in the ECU memory and can be displayed
on the Unit Pump Calibration screen.

Clear all Unit pump calibration codes

To clear the calibration codes in the Engine ECU you do as follows.

1. Select the Clear all button (1).

This does not perform any programming of the Engine ECU.

Print displayed calibration codes

All information displayed to the user from the Calibration Code operation can be printed out later from the job
card.

Vehicle information
The purpose of this operation is to display information that is known about the vehicle control units and part
numbers of their hardware and software. The information displayed may be the VIN number / Manufacture
number, hardware number and date of manufacture for example. See the illustration for further examples.

144
Implementation

1. Start Vehicle information and click the Play. Vehicle information is available under group 1 in the function
group field.
2. The vehicle information for the vehicle is displayed.
3. Double click an MID to obtain more information about the control unit.

Vehicle information includes Vehicle ECU (software version, data file number and serial number), vehicle serial
number, VIN, unit number, and programming history.

Engine information includes Engine ECU (software version, data file number and serial number), rated power,
rated speed and engine model, serial number, and programming history.

Cylinder compression, test

Construction

This test isolates and tests the compression of each individual cylinder, to diagnose low power complaints and
problems with rough running. Engine should be at operating temperature to perform this test to rule out a cold
engine start.

It characterizes each cylinder's compression stroke via a ratio (compression time/expansion time). An engine with
good compression has a ratio between 1.85 and 1.95.

Each cylinder should be compared with other cylinders in the engine, but not with those from other engines.

145
Conditions

A dialogue box containing the conditions is displayed when the test is started. When the conditions have been
checked, the test is started.

Implementation

1. Read the information in the text field.

2. Start the test and follow the instructions.
3. When the start button is clicked, the technician will be instructed to engage the starter. The test mode will
prevent engine fueling.
4. When the test has been stopped, the user can specify whether the results are OK or Not OK.
5. The screen can now be printed. The operation is saved to the job card automatically.

Cylinder number

For certain engines with in-line pumps, the cylinder compression test cannot determine the cylinder number. This
is marked by the texts Cyl1–Cyl6 at the bars being replaced by Cyl-.

Accelerator pedal position, calibration

Construction

Calibrating the accelerator pedal requires that the Vehicle ECU is notified of the intent to calibrate the pedal. The

146
pedal must be held at full throttle and then idle three times. If the three pedal movements are not correctly
completed within the wait period for the calibration, you will be notified that the calibration was unsuccessful.

You may repeat the procedure as often as necessary to complete the calibration. If the pedal movements are
completed as required, you will be notified that the calibration was successful.

Implementation

1. Read the information in the text field.

2. The ignition must be on with the engine not running.
3. Start the test and follow the instructions.
4. Fully depress and fully release the throttle pedal three times starting from minimum throttle position to
maximum throttle position.
5. Complete the calibration process within five seconds, while briefly maintaining throttle position at both
minimum and maximum throttle.
6. The screen can now be printed. The operation is saved to the job card automatically.

A successful pedal calibration will be indicated by the green status symbol. An unsuccessful pedal calibration will
be indicated by the red status symbol.

147
 Mack Diagnostic Software –
VCADS Pro Programming

Vcads Pro Programming

1. Vcads Pro Programming Descriptions

2. Customer Parameter Programming

3. Control Unit Programming

4. Conversion Kit Programming

Notes:
Vcads Pro Programming

• See the following pages for a view of this document.

***Instructor note: Click on the document picture in the presentation to open the document for
viewing.

148
 Vcads Pro
Programming

149
Programming
When programming is carried out the workshop ID is stored in the control unit. This makes it possible to check
which workshop carried out programming last. The VCADS Pro user is responsible for ensuring that programming
is carried out correctly according to the requirements of the vehicle owner or other authorized persons. This
mechanic is also responsible for ensuring that the correct label is affixed to the engine control unit

Programming, electronic control system

Parameter programming
Note: When reading off parameter values the parameter values of parameters in other control units are checked.
If there are parameters with differing values these are reported in a dialogue box. This dialogue box displays a list
of values which can be adjusted there. The list is active until all differences are remedied. Click this button to
display the list.

Detailed description

Position Name Description

1 Toolbar The following function buttons are available.

150
 Display the Group view - Presents the parameters in different
logical groups.

Display the MID view - Presents the parameters by control

unit.

Customer parameters - Only displays customer parameters.

Vehicle parameters - Only displays vehicle parameters.

All parameters - Displays all parameters.

All parameters to job card - Saves all parameters to the job

card.

Min - Shows the parameter's minimum value and contingent

limited parameters.

Max - Shows the parameter's maximum value and contingent

limited parameters.

2 Logical group/Control unit This field contains a function tree used to select a logical
window group or control unit depending on the active view.

3 Split line Drag the line to change the relative sizes of the Logical
group/Control unit window and the Parameter list.

4 Continue button Click this button to continue programming.

5 Parameter description A more detailed description of a parameter is displayed in the

introductory text field if the parameter is highlighted. To return
to the basic information in the introductory text field select
Basic information in the Operation menu.

6 Parameter list This lists the parameters available for the logical group or
control unit.

7 Status bar The status of communication between the PC tool and the
vehicle and between the PC- tool and the central system is
displayed. When communication has been established a
connection icon is displayed. The text Simulator (in a yellow
field) is displayed here if the program is in simulator mode.

Group presentation of parameters

Click this button to present the parameters by group in logical function groups.

151
This method of presentation displays a logical group division. Below are examples of groups.

Logical group

Cruise control

Engine

Instrument Cluster

Power take off (PTO)

Security

Speed

Transmission

Vehicle

This lists the parameters available for the logical group. A parameter in a logical group can occur in several
different control units.

MID presentation of parameters

Click this button to present parameters by control unit.

This method of presentation lists the vehicle/machine control units in the Logical group/Control unit window.
Below are examples of control units.

Control unit

Engine control unit

Instrument Cluster

Vehicle control unit

Parameter list
The right-hand field displays a parameter list when the Group or control unit presentation of parameters is
selected.

The field is divided into a number of columns.

152
 Column heading Description

ID The ID of the parameter. The ID is the same, irrespective of language.

Name A description of the parameter.

Min The minimum parameter value.

Value The current parameter value.

Max The maximum parameter value.

Unit The type of unit used for the parameter.

The parameter list can contain two types of parameter, customer and vehicle parameters. Either one or both
types of parameter can be displayed.

To differentiate between customer and vehicle parameters, an icon is displayed to the left of the vehicle
parameter IDs. See the illustration. The icon indicates that you must be connected to the central system in order
to program that parameter.

Vehicle parameters are displayed only if the user is authorized to modify them

The parameters in the parameter list are either numerical or multiple choice.

Numerical parameters

153
Entering a new value overwrites the old one.

Multiple choice parameters

The user can only select one of a number of predefined values (Yes or No for example).

A multiple choice parameter looks like this when selected.

Setting the contents of the parameter list

To make the parameter list easier to read and search, it is possible to display customer and/or vehicle
parameters. Both the customer and vehicle parameters can be displayed at the same time.

Selecting the type of parameter for display in the parameter list is described below.

Customer parameters
Click this function button to display only the customer parameters in the parameter list.

Vehicle parameters
Click this function button to display only the vehicle parameters in the parameter list.

All parameters
Click this function button to show both the customer and vehicle parameters in the parameter list.

All parameters to job card

When this button is pressed, all read parameters is saved to the job card. When it is released, only the changed
parameters will be saved.

154
Note: Parameters can be sorted by clicking the column headings.

Minimum/Maximum limit

The minimum/maximum numerical parameters may be contingent on the value of another parameter. The
Minimum/Maximum limit function displays the limits and the values of the dependent parameters. The buttons are
placed in the tool bar.

Display value
To access the dialogue boxes follow the instructions below.

1. Click the parameter in the parameter list.

2. Point the cursor at the Minimum or Maximum column on the highlighted parameter. Click the right-hand
mouse button. It is also possible to use the left arrow (minimum value) or right arrow (maximum value).

Description

Dialogue box for the Minimum value of a selected parameter. The dialogue box for the Maximum value is similar

155
to the Minimum value dialogue box.

z Selected parameter (1) displays the ID of the selected parameter.

z Value (2) displays the present value of the selected parameter in the parameter list.
z Minimum limit value / Maximum limit value (3) displays the lowest or the highest limit value that the
selected parameter can have.
z Limited parameters (4) displays the parameter(s) which limit the value of the selected parameter.

Parameter description

For a more detailed description of the parameter do as follows.

1. The parameter description is displayed by clicking on a parameter (1).

2. The description is displayed in the text field (2).

Programming parameters

Programming of parameters is carried out in two stages:

z Assigning new values to parameters.

z Programming dialogue.

Assigning new values to parameters

1. Choose if the parameters are to be shown in logical groups (Group-view) or per control unit (MID-view).

156
 See group presentation of parameters.
2. Click the desired logical group or control unit (1). The associated parameters are displayed in the
parameter list (2).
3. Double click the parameter to be reprogrammed.
4. Change the parameter value.
{ Numerical parameter: Enter the new value for the parameter.
{ Multiple choice parameter: Select the desired alternative from the list.
{ Press Enter.
5. Assign a new value to a new parameter from the group view or MID view. Alternatively click on Continue to
proceed to the programming dialogue.

Programming dialogue
When a parameter value has been modified, the programming dialogue is started by clicking Continue. Dialogue
box Parameter, programming is opened. The following are displayed in the dialogue window.

z Connection symbol if required (The symbol is displayed when connection to the central system is required).
z ID (Parameter ID)
z Name
z Old
z New
z Unit

157
The following actions can be carried out in the dialogue box.

z Program the current parameters by clicking Program (1). The customer parameters are programmed
locally without connecting to the central systems. The vehicle parameters can only be programmed after a
password is entered in the appeared dialogue box.
z Click Cancel (2) to cancel the dialogue. It is now possible to assign new values to additional parameters or
modify the existing parameters in the list. Those parameters that have already been assigned new values
are not deleted, they remain when the dialogue is opened again. Delete a parameter by resetting it to its
old value.

Programming vehicle parameters

The following is carried out when Program has been selected from the programming dialog.

A dialogue box is displayed in which a password must be entered.

1. Generate a password using the DigiPass.

2. Enter the 8–digit password into box (1).
3. Click OK (2). Data transfer takes place. Programming is complete.

Note: After parameter programming the parameter may not have exactly the same value, if another unit is
selected for display.

158
Print

Start printing by clicking on this button. Alternatively select Print from the File menu.

When printing parameters, select whether to print the selected group / control unit or all groups / control units.

MID XXX Control unit, programming

Warning
Under no circumstances may control units be switched between vehicles/machines for fault tracing or
repairs without reprogramming them. Incorrect settings in the control unit can lead to personal injury or
damage to the vehicle.

159
Programming

Note: This operation requires connection to the central system. Connect the PC-tool to a suitable telephone line
or network cable.

1. Select MID XXX, control unit, programming in the relevant function group.
2. Start the operation and follow the instructions.

Note: Check that the printer is operational. A new label is printed out when replacing the ECU. First select which
chassis number you wish to print the label for, see figure below. Load the printer with labels. Once the label is
printed, cut it out and stick it to the control unit. Then stick the transparent protective film on top to cover the label
completely.It is important that the protective film overlaps the label by a few millimeters all the way around.

MID XXX Control unit, campaign

Campaign programming is only possible when the appropriate message has been sent.

Programming

Note: This operation requires connection to the central system. Connect the PC-tool to a suitable telephone line
or network cable.

1. Select MID XXX control unit, campaign in the relevant function group and follow the instructions.

Note: In certain campaigns, when replacing hardware or part numbers, the conversion is carried out
automatically without the user noticing anything. In campaigns where the user must carry out the
conversion themselves, the user will be notified.

2. The following window is displayed where a campaign for a selected operation is presented. Select OK to

160
 implement the operation. Otherwise select Cancel. Other campaigns for other operations are displayed in
the lower field.

Conversion kit
All available conversion kits are displayed under Software information in the Help menu.

Programming

Note: This operation requires connection to the central system. Connect the PC-tool to a suitable telephone line
or network cable.

1. Select Conversion kit under function group 1. Start the operation and follow the instructions.
2. A dialogue box opens.
{ For accessory kit mark (1) and enter the number of the accessory kit (2).

161
 { For Conversion kit mark (3) and select the conversion kit to be used (4) from the list.

3. Click OK.

After the completed operation the new software/hardware is now prepared for the current chassis ID / Serial no.

162
The operations MID XXX Control unit, programming or MID XXX Control unit, campaign can be used to download
software.

Theft ID, programming

Construction

This operation is constructed around one main presentation element.

When the operation is run, the user will be asked to input the Fleet Data password for this vehicle. No attempt will
be made to read the programmed settings until the password has been entered and validated.

Implementation

1. Read the information in the text field and follow the instructions.
2. Start the test and follow the instructions.
3. Enter Driver Ids, and view or set restriction levels. The user can also clear existing Ids, or change the
length of the data to be entered by the driver.
4. The screen can now be printed. The operation is saved to the job card automatically.

Six to fifteen Driver Ids may be entered depending upon the Driver Id length specified.

163
 Mack Diagnostic Software –
VCADS Pro Programming

Vcads Pro Programming

1. Intermediate Storage

Notes:

There are times when a controller may need to be programmed and the vehicle is not present. The
Vcads Pro tool offers a special program designed to allow the download of a controller’s software
for future programming.

NOTE: When an Intermediate storage download has been performed, several things must be done to
complete the process (this applicable to the VMAC IV only):
1. Program the vehicle within 28 days and send in a report via the network. (an invoice will be
generated and sent to the dealer that downloaded the software regardless of the programming
status)
2. If a software download cannot be programmed within 28 days of the intermediate storage
download, a report must be performed to put the software back in stock. Note: After an intermediate
storage download has been made to a dealer’s Vcads Pro, the software is now locked in the
Volvo/Mack VDA system. The software may not be downloaded or programmed by any other Vcads
Pro until is either put back in stock or programmed and a report has been submitted to VDA.

• See the following pages for a view of this document.

***Instructor note: Click on the document picture in the presentation to open the document for
viewing.

164
 Vcads Pro
Intermediate
Storage Programming

165
Intermediate storage (IS)

Intermediate storage (IS), description

The intermediate storage function makes it possible to download software to the PC tool and then program the
control units at a later time without being connected up to the central system.

Intermediate storage is only used in those cases when there are no opportunities for connection to the central
system. Of the operations which normally require connection to the central system, only programming of vehicle
parameters, replacing control units and control unit campaigns can be carried out.

Note: Only users authorized to use intermediate storage can activate the function.

Activate intermediate storage (IS)

Perform the following to activate the intermediate storage function. In menu Tools, select icon Intermediate
storage.

A symbol of a laptop computer appears in the lower right hand corner of the screen when the intermediate
storage function is activated.

Order software
Select Administrate software in the Tools menu. A window opens.

166
Fill in the following information under the tab Ordering Software (1):

z Company (4)
z Electrical system (5)
z Chassis ID (6) or VIN (7)
z MID (8)
z Action (9)
z Click Add.
z The software to be ordered is listed in field (10).
z When the order form is complete, click Send order (11).

A connection to the central system is established. Enter the digipass generated password when requested. The
software is downloaded.

Note: Reporting back is required between downloads in order to download the same software to the same chassis
ID more than once.

You can check which software is available under tab Available software (2), once software downloading is
complete.

z The software in field (4) is available for programming the given control units at any time during the following
28 days.
z If you highlight a software in field (4), information about it is shown in field (6).
z Information showing if the software is supported or not is shown in field (7).

167
Program the control unit
No connection to the central system is established to program the control units. Otherwise operations are carried
out as usual.

If a engine control unit is programmed, a label is printed.

Note: Check that the printer is working. Load the printer with a sheet of labels. After printing the label can be cut
out and stuck on to the control unit. Cover the label with transparent protective film.The protective film must
overlap the label by a few millimeters all the way round.

Send report
A report must be sent as soon as connection to the central system is possible.

If a report is not sent all the downloaded software will be treated as used. It is important that the report is sent.

Twenty one (21) days after downloading, a message is shown in VCADS Pro explaining that there is software to
report.

Note: If feedback is not carried out in time the downloaded software becomes unusable. The User will be charged
whether the software is used or not. If feedback is not carried out in time it may also lead to faults in VDA.

Report unused software

168
 z In menu Tools, select Administrate software.
z All software that has not been used, and is therefore still available, is listed under tab (2) Available
software.
z Check the box in column Report (4) for the software you wish to report as unused.
z Click Send rapport (5).

Report used software

z In menu Tools, select Administrate software.

z Enter tab (3) Used software.
z Select the software you wish to report from the table (4).
z More information is available in field (5) for each software.
z Click Send report (6).

You are connected up to the central system. State the password generated in the digipass when requested. The
report is now sent to the central system.

169
170
 Mack Diagnostic Software –
VCADS Pro Programming

Vcads Pro Programming

1. Vcads Pro Jobcard

Notes:
Job cards are used in VCADS Pro to document all work carried out on a vehicle in accordance with a
repair order. The result of the completed operations is stored on the job card. Parameter changes and
replaced data sets are also stored. The job cards are saved in the PC-tool.
Note: A job card is linked to a specific repair order and must be finalized as soon as all work on the
repair order is complete.

•See the following pages for a view of this document.

***Instructor note: Click on the document picture in the presentation to open the document for
viewing.

171
Vcads Pro
Jobcard

172
Job card
Job cards are used in VCADS Pro to document all work carried out on a vehicle in accordance with a repair order.
The result of the completed operations is stored on the job card. Parameter changes and replaced data sets are
also stored. The job cards are saved in the PC-tool.

Note: A job card is linked to a specific repair order and must be finalized as soon as all work on the repair order is
complete.

Job card menu

Select Job card in the VCADS Pro menu. This displays the job card menu with the following functions:

Open Used to open a job card.

Delete Used to delete a job card.

Import Used to import one or more job cards from another computer
(via a floppy disk or network for example). You are only
allowed to import the job card that you are authorized to
import.

Export Used to export one or more job cards to another computer (via
a floppy disk or network for example). You can export the job
card as an xml-file or a txt-file.

Close Closes a job card.

The menu also lists all open job cards. The job card displayed in the job card view is highlighted with a dot in front
of it. The active job card has the text Active behind it. Click on a job card in the menu to display this in the job card
view.

Job card status

A job card can have different status:

Current job card A current job card can be active or inactive. An active job card
is the job card that was selected on identification. You can
have several job cards open at the same time, but only one
active job card. A finalized job card cannot be active.

Finalized job card A finalized job card cannot be edited. However, it is possible
to open both finalized and non-finalized job cards for
information.

Detailed description
Select Job card view in the menu View to display the job card view. Or use the job card view button.

173
The job card view is based on two tabs.

Above the tabs a text indicates which job card is displayed (1). Beside the text are buttons which can be used to
scroll between open job cards or to close the job card being displayed.

Vehicle tab.

Working status

This field contains the following information:

z The repair order number (2)

z Dealer ID (3)
z The user that created the job card (4)
z License number (can be edited) (5)
z The date the job card was created (6)
z The date the job card was last altered (7)
z Status, active or finalized job card (8)
z The reason for creating the job card (can be edited) (9)

Vehicle identity

174
This field contains the following information about the selected vehicle:

z VIN number (10)

z Model (11)
z Description (12)
z Vehicle information (13). You can page through the various operations that have effected the vehicles part
number in this field (if there are any). The part number is shown in the table below (14).
z Table where part numbers for hardware, software, complimentary software, chassis ID, dataset 1 and
dataset 2 are shown to the vehicles' control units (14). Changes are marked with red text.
z Tree structure where part numbers for hardware, software, complimentary software, chassis ID, dataset 1
and dataset 2 are shown to the vehicles' control units (15).

Result tab.

Finished operations

This field contains information about the operations that have been saved onto the job card. The table shows the
following.

z These two columns (2) display if there are notes for the operation (note symbol in the first column) and if
the operation can be played back (play back arrow in the second column).
z Operation number (3)
z The name of the operation (4)
z Date (5)
z User (6)

175
Double clicking one of the operations which can be played back opens that operation. The operation can now be
played back. See Playing back saved operations.

Notes

Displays notes associated with the operation. New notes can be added if the job card is not finalized (7).

Sub-operation

The operation highlighted in the Completed operations field is displayed in a tree structure (8). This displays sub-
operations and the time they were completed.

Result

A result table for the sub-operation highlighted in the Sub-operation field (9) is displayed. The contents of the
result table varies depending on the type of operation highlighted.

Evaluation

The evaluation of the operation is displayed in the sub-operation field. It is possible to make an evaluation if the
job card is not finalized and evaluation of the operation is available (10).

Functions
The following are the functions that can be carried out in the job card.

Start an active job card

When VCADS Pro has been started and identification is complete, a window is displayed in which you can
choose to create a new job card or open an existing, non-finalized, job card. The results of the completed
operations are stored on the active job card.

176
Create a new, active, job card (1)

z Enter the repair order number (3).

z Enter the registration number (optional) (4).
z Enter the reason that the job card is being created (optional) (5).
z Click OK.

Open an existing, active job card (2)

1. Select the job card you want to work with from the list. Only job cards that have not been finalized are
contained in the list. And only job cards that match the vehicle on which the work is to be undertaken. If
there are no suitable job cards this option cannot be selected. The list can be sorted by clicking the
respective column title. It is also possible to search for job cards.
2. Highlight the job card. The reason that the job card was started is displayed in field (6)
3. Click OK.

Save to active job card

The active job card is the job card on which the repair order information is saved. You can have several job cards
open while work is ongoing, but only one active job card. Information is saved automatically to the active job card
during work on the repair order. You do not need to manually save results or other information to the job card.

Open an existing, job card (non-active)

177
 1. Select Open from the Job card menu.
2. The Job card dialogue box opens. This lists all the job cards that match the selected vehicle. The list can
be sorted by clicking the respective column title. Highlight one or more job cards in the list. Hold down the
Ctrl or Shift keys to mark several job cards.
3. Click Open.

Note: If identification has not been carried out all job cards can be opened.

Delete job card

1. Select Delete from the Job card menu.
2. The Job card dialogue box opens. This lists all finalized job cards. Highlight one or more job cards in the
list. Hold down the Ctrl or Shift keys to mark several job cards.
3. Click Delete.

Import job cards

Insert a floppy disk or ensure that the job cards to be imported are accessible from the computer to which they are
to be imported.

1. Select Import from the Job card menu.

2. A dialogue box opens. Browse and select one or more job card files. Hold down the Ctrl or Shift keys to
mark several job card files.
3. Click Open.
4. Then the imported job card can be opened (see Open existing job card (not active)).

If the repair order number on the job card to be imported is the same as a work number on a job card already in
the computer a dialogue box will open. This dialog box can be used to select whether the existing job card is to be
overwritten by the import or whether the import is to be cancelled.

Note: You can only import the job cards that you are authorized to import, and only in the format xml.

Export job cards

If using a floppy disk place the disk in the floppy drive.

1. Select Export from the Job card menu.

2. The job card dialogue box opens. This lists all job cards. Highlight one or more job card files in the list.
Hold down the Ctrl key to select several job cards. You can choose to export to txt-file by marking the
check box Export to txt-file.
3. Click Export. If an ongoing job card has been selected for export you will be asked to finalize it.
4. A dialogue box opens. Browse and select where on your computer you want to save the files. If you have
chosen to export many files at the same time, a dialogue for every job card will be displayed. If using a
floppy disk, select A:/.
5. Click Save.

Close job card

178
To close the job card displayed select Close from the Job card menu or the cross in the job card view.

If the job card is already finalized it will close immediately.

If the job card is not finalized a dialogue box will be displayed.

The VIN number must be filled in to finalize a job card. If the has been read off automatically it will be displayed in
the window. If the window is empty you must fill in the VIN number yourself (1).

Select whether you wish to finalize the job card or not (2). If you have finished all operations in the repair order it
is important to finalize the job card. If you finalize the job card you cannot go into it later to save further operations
or change information on it.

Edit job card

You can edit a job card that is not finalized. The job card does not need to be active to be edited. If you choose
not to carry out identification the job card will not be active. You can only go in and open existing job cards.

Search for a job card

In the job card window (displayed under Open job card, Delete job card and Export job card) there is a Search
button. The Search button is also available in the job card window. This button is used to search/filter one or more
job cards in the list.

179
 1. Click the Search button.
2. Search existing job cards by selecting one or more of the following criteria:
{ VIN number
{ Model
{ Repair order number
{ Operation number
{ Registration number
{ Created
{ User
3. Click OK.

Only the job cards that meet the search criteria are displayed in the job card window.

Print job card

Select display job card view.

Select Print from the File menu. This displays the Print job card window.

You can choose between the following examples:

z Print all operations.

z Print selected operations.
z Print sub-operations.

180
If you choose to print selected operations you can indicate if you want to print notes or results.

If you choose to print a sub-operation, you can indicate if you want to print the result.

Click OK.

Sort job card

Job cards can be sorted in ascending or descending order.

Click the column headers in the various windows to sort the job cards. Click once for ascending order and twice
for descending order.

Playing back saved operations

1. Open the job card in the job card view.
2. Double click the operation which can be played back in the list of completed operations. The operation
opens.
3. Use the buttons illustrated below to playback the operation.

To return to the previous view click Close.

Start playback

Click this button to play back the operation that has been selected.

Pause playback

181
Click this button to pause the playback of the operation. Restart the playback by clicking Start.

Stop playback

Click this button to stop the playback of the operation.

Play back the operation manually

Click the four button to rewind or fast forward operations, or alter between sessions manually. In the small
windows to the right you see the session number and session time. This operation is only possible when playback
is stopped.

Exiting VCADS Pro

When you want to exit VCADS Pro or want to carry out a new identification a new dialogue box is displayed.

The VIN number must be filled in to exit VCADS Pro or carry out a new identification.

If the VIN number has been read off automatically it will be displayed in the window.

If the window is empty you must fill in the VIN number yourself (1).

Select whether you wish to finalize the job card or not (2). If you have finished all operations in the repair order it
is important to finalize the job card. If you finalize the job card you cannot go into it later to save further operations
or change information on it.

182
183
 Course and Objectives – Mack
Advanced Vehicle Diagnostics

Course Objectives (Student should be able to describe and perform the

following upon the completion this course):

1. Understand the design and purpose of Mack vehicle diagnostics

2. Locate and use the Mack diagnostic service information
3. Acquire, read, and understand the Mack component diagnostics and functions
4. Perform basic and advanced diagnostic processes and methods
5. Use Mack diagnostic software and tooling to perform diagnostic tests and
calibrations
6. Develop “fast” methods of troubleshooting (Triage Diagnostics) using the vehicle’s
electronics to improve diagnostic skills and shorten customer downtime
7. Identify and evaluate vendor diagnostics messages, identify vendor diagnostic
software, and service information resources

184
 Mack Vcads Pro Workshop

Mack Vcads Pro Workshop

185
 Methods Workshop and
Diagnostics Skills Evaluation

Methods Workshop and Diagnostics Skills

Evaluation

186
 Course Exam

Course Exam

187
©2006 North American Institute
PV772-161I-002 July 22, 2006