1 troubleshooting basics – Bendix Commercial Vehicle Systems WINGMAN ADVANCED SD User Manual

Page 13

Advertising
background image

13

3.0 INTRODUCTION TO
TROUBLESHOOTING SECTION

Section Index
3.1

Troubleshooting Basics . . . . . . . . . . . . 13

3.2

Narrowing Down the Problem . . . . . . . 14-15

3.3

Overview of Possible Issues . . . . . . . . . . 16

This section introduces three initial steps to accurately
troubleshoot the Bendix

®

Wingman

®

Advanced

system.

We recommend reading this introductory section, as well
as the Troubleshooting/Diagnostics Section (4.0), before
performing any troubleshooting.
When diagnosing the Wingman Advanced system, in many
cases Bendix

®

ACom

®

Diagnostics software (version 6.3

or higher) will be required. This software is available as a
free download from www.bendix.com.

Troubleshooting Basics (3.1)

Questions

Next Steps

What color is the radar sensor?

The Wingman Advanced system has a black “eyeball” radar sensor (See
Section 1.02).

If the radar sensor is

fl

at-fronted, or is yellow, it is not a

Wingman Advanced radar sensor.

Have the driver run the Power-Up

Self-Test.

Power-Up Self-Test
This is a self diagnostic check, to determine if the system operation is normal.

1.
2.
3.

4.

5.

Park the vehicle. Power off.
Put the key into the ignition, and turn to the “ignition power” position.
Toggle the cruise control switch at least once, and leave it in the “on”
position.
Start the vehicle, but do not drive away.
Note that if the cruise control is in the “off” position, or if the
vehicle is moving, this test will not run.
The self-test will start after 15 seconds, and takes approximately fi

ve

(5) seconds to complete.
(Note that other vehicle system self-tests, e.g. the ABS “chuff” test,
may run during the initial 15 seconds after ignition “on.”)
As the Wingman Advanced self-test runs, the driver should hear a short
set of beeps. The test checks the engine, transmission, and brake
systems to make sure they are communicating. In addition, depending
on the vehicle, the test may briefl y display a distance alert message
and/or cause the Forward Vehicle Detected icon in the instrument
cluster to illuminate; this is normal.

Does the driver hear a

long warning beep?

If no problem is found and the test is passed, no additional beeps/lamps will
be displayed nor will a trouble code be set.
If the system has found an issue that will prevent it from functioning properly,
a long warning beep will sound

to alert the driver, and a Diagnostic Trouble

Code (DTC) will be logged in the system (typically with a status indicator/dash
icon illuminated). For descriptions of all DTCs, see Section 4.3: Diagnostic
Trouble Codes.

Have the driver describe the system

behavior that they believe shows it is not

working properly.

When diagnosing the system, especially in cases where there are no
diagnostic trouble codes logged, fi nd out which part of the system behavior
appears to be operating improperly. See Section 3.2: Narrowing Down the
Problem.

TABLE 3 - TROUBLESHOOTING BASICS

3.1 TROUBLESHOOTING BASICS

Advertising