Subsection XX (DIAGNOSTIC AND FAULT CODES)

DIAGNOSTIC AND FAULT CODES

GENERAL When a minor or transient fault occurs, the fault
and beeper will cease automatically if the condi-
MONITORING SYSTEM tion that caused the fault no longer exists.
If a minor fault is active, the engine will operate
This system monitors the electronic components
without a noticeable loss of performance.
of the EMS (engine management system), the
multifunction gauge, and other components of Releasing the throttle and letting the engine re-
the electrical system to detect if they are faulty turn to idle speed may allow normal operation to
or defective. The monitoring system becomes resume. If this does not work, try the following:
active when the START button is pressed. – Remove tether cord from the engine cut-off
NOTE: Some components require the engine to switch.
be running to be monitored (fuel injectors for ex- – Wait 3 minutes to allow the ECM to shut down.
ample). – Start engine.
The following components or functions are moni- – Check if the fault code is still active.
tored. The electronic system will react differently de-
EMS MONITORING pending on the fault type. If a severe failure
occurs, the engine may not be allowed to be
Battery voltage started. In other cases, the engine may operate
EMS sensors (TAS, TPS, CPS, CAPS, in limp home mode (reduced RPM) or not be
MAPTS, CTS, OPS, EGTS, knock sensor). affected at all.
Throttle actuator, ignition coils and fuel injectors These strategies are used to protect the engine
ECM system from damage and to maintain safe opera-
tion of the vehicle.
Engine RPM
CAN
Limp Home Mode
When a major component of the EMS is not op-
Engine starter solenoid (STS) erating properly, limp home mode will be set. En-
Fuel pump (FP) gine speed (RPM) will be limited and therefore ve-
hicle speed.
O.T.A.S.
This mode allows the rider to return to shore
Multifunction gauge which would otherwise not be possible without
this advanced system.
MULTIFUNCTION GAUGE MONITORING
When this mode is active, the CHECK ENGINE in-
Multifunction gauge dicator will come on and a LIMP HOME message
Sport mode activation will be displayed in the multifunction gauge.
MODE switch Major Fault and Vehicle Reaction
CAN The following EMS conditions will trigger a limp
Fuel level sensor home mode.
ECM MAX ALLOWED
ENGINE PROBLEM
RPM
When a malfunction is currently detected, the re- High engine temperature
lated electronic module: 3800
(from 100°C (212°F))
– Sets an active fault code. High exhaust temperature
– Adapts the proper protection strategy accord- 3800
(from 95°C (203°F))
ing to the failure.
Low oil pressure
– Sends out warning signals to the multifunction (below 150 kPa ± 20 kPa 4500
gauge which provides beeper codes, fault indi- (21.76 PSI ± 2.9 PSI))
cators and fault messages to inform the rider of
a particular condition.

smr2014-027 1
Subsection XX (DIAGNOSTIC AND FAULT CODES)

Indicator Lights and Message Display Information

The fault indicators and messages displayed in the information center will inform you of a particular con-
dition or if an anomaly occurs.
PILOT LAMPS
MESSAGE DISPLAY DESCRIPTION
(ON)
HI ENGINE TEMPERATURE Engine overheating
HI EXHAUST
Exhaust system overheating
TEMPERATURE

CHECK ENGINE or LIMP Check engine (minor fault req. maint.) or

HOME MODE LIMP HOME MODE (major eng. fault)

LO OIL Low oil pressure

LOW FUEL level indicator, Low fuel level warning, approx. 12 L

NO message (3.2 U.S. gal.)remaining, or fuel level sensor disconnected.

MAINTENANCE REQUIRED Engine or vehicle maintenance required.

SPORT MODE Sport mode is active.

TOURING MODE Touring mode is active

FAULT MESSAGES
LO OIL Engine low oil pressure detected
HI EXHAUST TEMPERATURE High exhaust temperature detected
HI ENGINE TEMPERATURE High engine temperature detected
Engine management system malfunction or
CHECK ENGINE
maintenance required
HI BATTERY VOLTAGE High battery voltage detected
LO BATTERY VOLTAGE Low battery voltage detected
LIMP HOME Major fault detected, engine power limited
FUEL SENSOR DEFECTIVE Fuel level sensor fault
GPS signal synchronization with navigation satellites
UNSYNC GPS
not acquired
CALIBRATION CHECKSUM ERROR Information center programming corrupted
MAINTENANCE REQUIRED Watercraft maintenance required
Message when a function is not or cannot be properly
FUNCTION CANNOT BE ACTIVATED
activated
O.T.A.S. sensor failure (or not detected), or O.T.A.S.
O.T.A.S. FAILURE
system failure

2 smr2014-027
 Subsection XX (DIAGNOSTIC AND FAULT CODES)

Beeper Signals
When one of the following conditions occurs, the monitoring system emits the associated beep signal.
BEEPER CODES DESCRIPTION
A 2 second beep
Engine management system fault.
every 15 minute interval
Low fuel level.
Refill fuel tank. If problem persists, check sensor and circuit. Refer to FUEL
A 2 second beep every 5 minute TANK AND FUEL PUMP subsection.
interval Fuel tank level sensor or circuit malfunction.
Check sensor and circuit. Refer to FUEL TANK AND FUEL PUMP
subsection.
High engine coolant temperature.
Refer to COOLING SYSTEM subsection.
High exhaust temperature.
Continuously beeps Refer to ELECTRONIC FUEL INJECTION (EFI) subsection.
Low oil pressure.
Turn off engine as soon as possible. Check oil level and refill. Refer to
LUBRICATION subsection.

smr2014-027 3
Subsection XX (DIAGNOSTIC AND FAULT CODES)

FAULT CODES 2. Click on the Read Data button.

A fault code is an indication that a malfunction has 3. Click on the Faults tab.
been detected by the monitoring system of the
vehicle.

Fault Code Categories

A fault code consists of an alphanumeric designa-
tor followed by a hexadecimal number of 3 digits.
The alphanumeric designator defines the category
of the fault code while the hexadecimal number
refers to a unique fault.
FAULT CODE CATEGORIES
EXAMPLE
ALPHANUMERIC MODULE/
OF FAULT
DESIGNATOR SYSTEM
CODE
rmr2011-070-011_a
Body TYPICAL
(include 1. Fault tab
From B0 to B3 multifunction B2230
gauge and switch 4. Click on the drop-down list on the LH lower cor-
faults) ner.
Power train 5. Choose the fault state to display.
and related
From P0 to P3 P0520
system faults
(includes ECM)
Communication
From U0 to U3 between modules U16A9
and sensors

rmr2011-021-001_a

RELATED MODULE AND FAULTS TYPICAL

1. Drop down list
FAULT CODE
MODULE
CATEGORY FAULT
INFORMATION
STATE
ECM Stores mainly “P” codes
(engine control module) and some “U” codes Display all possible faults regardless
All faults
of state
Stores mainly “C” codes
Multifunction gauge
and a few “U” codes Active Display only faults matching this state.
faults Empty area if there is no active fault
Reading Fault Codes Using the Active and
Display only faults
Multifunction Gauge occurred
that have either state.
Empty area if there is neither
Fault codes cannot be displayed in this multifunc- faults
active nor occurred fault
tion gauge.

Reading Fault Codes Using B.U.D.S.

Software
NOTE: All fault code types can be read with
B.U.D.S.
1. Connect vehicle to the latest applicable
B.U.D.S. software. Refer to COMMUNICA-
TION TOOLS AND B.U.D.S. subsection.

4 smr2014-027
 Subsection XX (DIAGNOSTIC AND FAULT CODES)

FAULT NOMENCLATURE
COLUMN INFORMATION
Fault code number.
When 2 stars (**) precedes the
Code code, detailed conditions when the
fault occurred, can be displayed by
clicking the "More details" button
Display the fault state (active, occurred,
State
inactive)
Displays the module that
rmr2011-070-001_b reports the fault code.
TYPICAL FAULT PAGE This is the module that detects
1. Fault tab
2. Fault indicator light or has received a message
Module
3. Fault code state drop box of an anomaly and reports it.
4. Fault nomenclature List of modules:
5. More details button
6. Clear occurred faults button Multifunction gauge
7. Selected fault ECM (engine control module).
8. More information indicator
Number of times this fault
FAULT PAGE DESCRIPTION Count occurred within the driving cycle
Value: From 0 to 255
ITEM INFORMATION
Not to be used
Fault tab Click tab to display the fault page Cycle time
Value: From 0 to 255 minutes
Fault When flashing, it indicates there is Not to be used
indicator light an active fault(s) Total time
Value: From 0 to 64 255 minutes
Fault code Description Provides a short description of the fault
Click drop box to select the type of
state drop
faults to display
box
When reading a fault code in B.U.D.S., pay partic-
Fault Display specific information and ular attention to which module reports a fault. It
nomenclature statistics related to the fault is indicated in the Module column.
More details
To display possible causes and The Description column gives a short description
service actions related to the of the fault.
button
selected fault
Clear
To clear all occurred faults in related
occurred
ECU(s)
faults button
When a fault is selected, additional
information pertaining to that
fault will be displayed when
Selected
clicking the "More details" button.
fault
To select a fault, click on the fault
with the mouse or use the cursor up
or down to scroll to the desired fault

rmr2011-021-002_a

SOME COLUMNS REMOVED FOR CLARITY

1. Module that reports a fault
2. Fault description

Click on the More Details button, on the RH lower

corner, to display the "Possible Causes" and the
"Service Actions" to step further in the diagnosis.

smr2014-027 5
Subsection XX (DIAGNOSTIC AND FAULT CODES)

rmr2011-021-001_a

TYPICAL
1. Drop down list

rmr2011-021-050_a
FAULT
TYPICAL INFORMATION
STATE
1. Click here
Display all possible faults regardless of
All faults
state
Active Display only faults matching this state.
faults Empty area if there is no active fault
Active
Display only faults that have either state.
and
Empty area if there is neither active nor
occurred
occurred fault
faults

Active Fault Codes

An active fault code is an indication of a fault that
rmr2011-070-002_a
is currently triggered.
TYPICAL — MORE DETAILS PAGE
1. Possible causes related to the selected fault The active fault may or may not compromise nor-
2. Service actions
3. Operating conditions when fault occurred mal operation of the related system(s). Service
action in B.U.D.S. should be used to correct the
MORE DETAILS PAGE DESCRIPTION problem that caused the fault code.
ITEM INFORMATION Once the fault condition(s) of the active fault is no
longer present, its state will change to "occurred".
Possible List the possible causes that
causes triggered the fault Occurred Fault Codes
Service List the possible actions to perform An occurred fault code indicates a fault that was
actions to solve the fault active, but no longer is.
Conditions List the operating conditions of the The occurred fault does not presently affect sys-
when fault engine and/or vehicle when the fault tem or component operation but is retained as a
occurred was triggered history of the faults that were detected.
Inactive Fault Codes
Fault Code States
An inactive fault code represents a fault code that
The various electronic control units (ECUs) used in is neither active, nor occurred. It is simply part of a
the vehicle can generate a variety of fault codes list of all possible faults which may be monitored
depending on the level of monitoring they are ca- by the various ECUs, which may become active
pable of. Fault codes have 3 possible states: or occurred if the monitoring system detects an
– Active applicable fault.
– Occurred
– Inactive. How to Clear Fault Codes Using
Click the Fault tab then click on the drop-down list B.U.D.S.
on the LH lower corner. Connect vehicle to the latest applicable B.U.D.S.
Choose the fault code state you want to display. software version. Refer to COMMUNICATION
TOOLS AND B.U.D.S. subsection.
Click on the Read Data button.

6 smr2014-027
 Subsection XX (DIAGNOSTIC AND FAULT CODES)

Click on the Faults tab.

NOTE: Only the Occurred state faults can be
cleared.
Click the "Clear Occurred Faults" button.

rmr2008-039-009

CLEAR OCCURED FAULTS

This will reset the appropriate counter(s) and will lmr2010-019-001

also record that the problem has been fixed in the TYPICAL — MODULE SUBMENU LIST
related module memory.
6. Refer to the following table to find the appropri-
Observe the "Occurred" fault(s). They should all ate subsection in this manual to diagnose the
disappear. Otherwise, follow this procedure. missing module.
– Remove tether cord cap from engine cut-off
switch. MISSING
SECTION TO REFER TO
MODULE
– Wait 3 minutes.
– Repeat procedure to clear faults again. ECM ELECTRONIC FUEL INJECTION (EFI)
Cluster MULTIFUNCTION GAUGE
FAULT CODE DIAGNOSTIC
Missing Module Diagnostic Tips Using B.U.D.S.
If a module is missing, several fault codes will ap- History Page
pear. HISTORY PAGE DESCRIPTION
The number of modules read by B.U.D.S. can be
ITEM INFORMATION
seen in the status bar at the bottom right hand
corner of the B.U.D.S. screen. Last Displays several parameters recorded
minute in the last minute of engine operation
Display the minimum and
Minimum/ maximum values encountered.
Maximum Click "Clear Min/Max" to reset the
values
Display the time proportion in what
Run time
mode the engine was running in
tmr2011-019-002_b

STATUS BAR RPM Display the RPM range proportion in

1. Number of modules profile which the engine was running in

To quickly find which module is missing, perform To see the last minute of operating conditions,
the following: click on the History tab in B.U.D.S.
1. Connect vehicle to the latest applicable
B.U.D.S. software. Refer to COMMUNICA-
TION TOOLS AND B.U.D.S. subsection.
2. Click on the Read Data button.
3. Click Module in the menu bar.
4. Look at the list of modules.
5. If a module is not visible, then it is not commu-
nicating through the CAN bus (controller area
network).

smr2014-027 7
Subsection XX (DIAGNOSTIC AND FAULT CODES)

smr2011-023-001_a

1. History tab
2. Additional history pages
3. Drop-down list in Last Minute page

Last Minute Drop-Down List:

From the Last Minute page, click on the drop-
down list on the LH lower corner.
Choose the values to display.

smr2011-023-002_a

TYPICAL
1. Drop down list

8 smr2014-027
 Subsection XX (DIAGNOSTIC AND FAULT CODES)

Troubleshooting Guidelines Using Fault Codes

CONDITION ACTION

Use B.U.D.S. to:

Read fault codes.
Display "Active" faults to see components currently not operating normally.
Display "Occurred" faults to troubleshoot intermittent problems.
Monitor system(s), sensor(s), switches and actual conditions.
Troubleshooting vehicle
Activate component(s) for troubleshooting.
Set components etc.
Know the last minute of operating conditions by using the "History" page.
Know the operating conditions, if available, when a fault code occurred by
using the "More details" button in the fault page.
Check sensor connections for solidity or for mixed up connections.

Before vehicle maintenance:

Read the electronic modules with B.U.D.S.
Save and print the B.U.D.S. file (keep faults option only).
New fault(s) appear after a vehicle
maintenance or repair After vehicle maintenance:
Read the electronic modules with B.U.D.S.
Compare the fault code(s) before and after the maintenance
using the printed copy and the current B.U.D.S. reading.
Investigate only the newly fault codes.
Clear all occurred faults in B.U.D.S.
Communication faults displayed as Normal behavior when flashing a module.
"Occurred" after module flashing Clear all occurred faults and check again.
Read the fault description in B.U.D.S.
Click on the "More Details" button.
Sensor "Active" fault Look at the "Conditions" when available.
Read the "Possible Causes".
Apply the "Service Actions".
Several fault codes active at the
Likely to be caused by burnt fuse(s) or bad bus bar connection(s).
same time
Check related fuse(s) and relay.
Check related power and ground wires.
Low system voltage
Check for common power supply to several sensors/modules
on one module
(refer to POWER DISTRIBUTION AND GROUNDS).
Power problem on sensor(s)
NOTE: Some sensors are supplied by the battery while others are
supplied by a module.
Low system voltage
Check battery condition and connections.
on several modules
Check related fuse(s) and relay.
(several communication faults
Check voltage regulator/rectifier.
will also appear)
A battery charger has likely been used to substitute the vehicle battery.
High system voltage on several
Clear all occurred faults and check again.
modules
Check voltage regulator/rectifier.
Check the module that is reported as missing.
When all modules report that a
Check related fuse(s) and relay.
module is missing
Check related power and ground wires.
When several modules are in fault Search for a common problem such as a faulty sensor.

smr2014-027 9
Subsection XX (DIAGNOSTIC AND FAULT CODES)

CONDITION ACTION
When several modules and sensors report that a module is missing.
The missing module may report CAN bus failure, CAN bus off.
Check related CAN wires (continuity, short to
CAN bus failure, CAN buss OFF
ground, short between CAN low and high).
Check module pins and wiring terminals.
Then, the other modules should stop reporting that module is missing.
May have been generated due to a system or component that was
momentarily operating outside normal parameters.
May be generated when disconnecting and reconnecting a component,
replacing a burnt fuse, or may be due to a momentary high or low voltage.
Before being "Occurred", a fault has always been "Active"
Occurred fault(s) for a certain time, indicating that an unexpected condition
or problem has been present during the driving cycle.
A frequent momentarily fault or an intermittent fault may never
be seen as "Active" in B.U.D.S. while there is still a pending problem.
This type of malfunctions can be discovered by looking at
the "Occurred" faults and then by evaluating the fault count.
As long as a fault is present, it is displayed as "Active".
Low value: Suggests handling problems
Fault count (connections, terminal contact/shape etc.).
(0 - 255) High value: Suggests a frequent and unsolved problem.
The problem should be investigated.
Fault conditions
Look for abnormal, excessive values.
(More details button)
When the basic troubleshooting has been done and the fault
code(s) persists, often the problem is related to the wiring
harness, connections or electromechanical components.
Hard to find problems Short to ground, to battery or between wires.
Wire splices, chafing, terminal problems
(pulled out, bent, out of shape, corroded etc.).
Bad contacts in switch or relay.

10 smr2014-027
 Subsection XX (DIAGNOSTIC AND FAULT CODES)

GUIDELINES TO SOLVE SPECIFIC Fault Code P1172

FAULT CODES Additive mixture adaptation below lower limit
--> mixture too rich. An open signal on the en-
Several Fault Codes Are Active gine coolant temperature (CTS) can trigger that
Simultaneously fault. Refer to ELECTRONIC FUEL INJECTION
If this occurs, check the following: (EFI) subsection.
– Check connections common to more than one
system. Fault Code U0300
– Check diagnostic connector for the presence of Incorrect ECM or multifunction gauge for the
water or corrosion. engine. Installed part is not appropriate for the ve-
– Check CAN wires. hicle. Using BUDS, check if the security coding of
the cluster is matched with the ECM security cod-
– Check wire junctions or splices (JT xx).
ing. Engine will crank but will not start. Refer
Fault Code P0562 to PARTS CATALOGS for proper part according to
vehicle.
Battery voltage too low. It occurs when both
battery voltage and engine RPM conditions are
met. See following chart. Refer to CHARGING
HOW TO FIND FAULT CODE
SYSTEM subsection. DESCRIPTIONS
BATTERY VOLTAGE ENGINE SPEED For the latest fault code table, use the Info Cen-
Lower than 11.5 Vdc Greater than 1200 RPM ter submenu in BOSSWeb and enter the following
search criteria:
Fault Code P0563 – Enclose the search within quotes " "
– Enter: "2014 Sea-Doo PWC DTC Table".
Battery voltage too high. It occurs when battery
voltage is above 16 Vdc when engine is running.
Refer to CHARGING SYSTEM.

Fault Code P0171

Multiplicative mixture adaptation exceeds up-
per limit--> mixture too lean. An open signal
on the engine coolant temperature (CTS) can
trigger that fault. Refer to ELECTRONIC FUEL
INJECTION (EFI) subsection.
Fault Code P0172
Multiplicative mixture adaptation below lower
limit--> mixture too rich. An open signal on the
engine coolant temperature (CTS) can trigger that
fault. Refer to ELECTRONIC FUEL INJECTION
(EFI) subsection.
Fault Code P1171
Additive mixture adaptation exceeds upper
limit--> mixture too lean. An open signal on the
engine coolant temperature (CTS) can trigger that
fault. Refer to ELECTRONIC FUEL INJECTION
(EFI) subsection.

smr2014-027 11