Faults

Navigation:  EvDiagnostics > Windows, Forms, Frames and Dialogs > Diagnostics >

Faults

Previous pageReturn to chapter overviewNext page

 

 

Navigation: Windows, Forms, Frames and Dialogs > Diagnostics >

Faults

 

 

 

"Active Faults" describe an abnormal condition which are current. "Historical Faults" and "Occurred Faults" describe present or past abnormal conditions. However, "Occurred Faults" are different from "Historical Faults" in that "Historical Faults" cannot be cleared as they provide a running history for the engine.

 

Active Faults

 

Diagnostics_Faults_Active_Faults

(Figure 1)

 

        If the engine is running, "Active Fault" detection will generate an "Occurred Fault".

        When an "Active Fault" is selected from the list, the information fields below the list will provide further information about the selected fault.

        All columns (except the images column) are sortable (either ascending or descending) by clicking on the column header.

 

Occurred Faults

 

Diagnostics_Faults_Occurred_Faults

(Figure 2)

 

        Describes the fault by code number and description and the number of times this fault has been detected. In addition, the time of first occurrence for that code (in engine operating hours) and the last occurrence for that code is recorded. If there is only one occurrence of a particular fault, the length of time the fault condition was present can be determined by subtracting the last time from the first time. NOTE: If "Times" reaches 256, the next time a fault occurs for that code, "Times" will roll back to 1.

        "Occurred Faults" may be cleared when the engine is not running.

        When an "Occurred Fault" is selected from the list, the information fields below the list will provide further information about the selected fault.

        On selected engine models, additional engine information is stored in the EMM (see "Selected Fault Freeze Frame Information" in Figure 2). When a fault occurs, values of the following are valuable assets in trouble shooting: Speed (RPM), Throttle Position Sensor (TPS), Pressure - Barometric, Exhaust (if installed) and Water (if installed), Temperatures - Air Inlet, Port (or Single), Starboard (if installed) and EMM, Voltage - System and Battery.

        All columns (except the images column) are sortable (either ascending or descending) by clicking on the column header.

 

Controls

 

Control

Type

Description Comments

Comments/Special Functions

Clear Faults

Button

        Clear all occurred faults.

 

 

Historical Faults

 

Diagnostics_Faults_Historical_Faults

(Figure 3)

 

        Describes the fault by code number and description and the number of times this fault has been detected. In addition, the time of the last occurrence for that code is recorded. NOTE: If times for that code reaches 256, the next time a fault occurs for that code, the times for that code will roll back to 1.

        When a "Historical Fault" is selected from the list, the information fields below the list will provide further information about the selected fault.

        Not available for OMC ECU/EMM.

        For BRP D.I. engines, "Last" is shown as hours and minutes.

        For E-TEC ® engines, "Last" is shown as hours only.

        All columns (except the images column) are sortable (either ascending or descending) by clicking on the column header.

 

Speed Controls

 

Image

Description

D.I.

E-TEC ®

Action Key

Action

stop

        Stop engine crankshaft rotation and reset the EMM.

        Enabled for E-TEC ® engines only.

        Disabled if engine is stopped.

 

X

F3

Button

clear_hslt

        If visible, it will clear high speed/low throttle condition for E-TEC ® Inline (575cc) engines.

        Also known as "Fault 57 - ATAC (High RPM with low TPS setting)" which issues an engine shutdown.

X

X

F5

Button

Units_EnglishUnits_Metric

        Toggle between English or metric units.

        Enabled if "Occurred Faults" is showing and the EMM has "freeze frames".

        Disabled if "Active Faults" or "Historical Faults" is showing.

X

X

F6

Toggle

camera

        Take a snapshot of this frame.

        Saved as a "JPEG" in the "Exports" folder.

X

X

F8

Button

questionquestion_asterisk

        Open/Closes the information frame. If image is orange, there is special information.

X

X

F11

Toggle

close

        Closes this frame.

X

X

F12

Button

 

Popup Menu Items

 

Item

Short Cut

Description

Stop Engine

F3

        Stop engine crankshaft rotation and reset the EMM.

        Visible for E-TEC ® engines only.

        Disabled if engine is stopped.

Clear High Speed / Low Throttle

F5

        If visible, it will clear high speed/low throttle condition for E-TEC ® Inline (575cc) engines.

        Also known as "Fault 57 - ATAC (High RPM with low TPS setting)" which issues an engine shutdown.

Change Units

F6

        Toggle between English or metric units.

        Enabled if "Occurred Faults" is showing and the EMM has "freeze frames".

        Disabled if "Active Faults" or "Historical Faults" is showing.

Take Snapshots

F8

        Take a snapshot of this frame.

        Saved as a "JPEG" in the "Exports" folder.

Open Info/Help

F11

        Open/Closes the information frame.

Close

F12

        Closes this frame.

 

Dynamic Troubleshooting

 

        When it comes to troubleshooting a problem there really is no set “right or wrong” approach.

        If the process you use, follows a logical progression, and moves towards a solution, the process is usable.

        With that being said, it helps if you use a system that you can apply in almost all-diagnostic situations.

        One example would be: “Symptom to System to Component to Root cause of failure (SSCR)”.

        Here is a quick overview.

        The first step in any diagnostic situation is to verify the customer complaint.

        Is it occurring now?

        Does it occur as the customer stated?

        Are there any Fault codes?

        If the answer is yes to any of these you have now been pointed in a direction.

        Remember; just because you have a fault code(s) does not necessarily mean you have found the solution.

        It may simply be a byproduct of the problem that exists.

        With that in mind, you must next consider which system(s) could cause the symptom to occur, i.e.: fuel, ignition, electrical, etc.

        Now working with this information you would begin your investigation of the system(s) using wiring diagrams and following shop manual test and procedures.

        This will help you narrow it down to a specific component i.e. relay, fuel injector, sensor, etc.

        Another caution here: a component may fail, but there can also be other circumstances that make the component appear not to function properly.

        Examples: bad connection, open wire, short, etc.

        By understanding how the component works as well as the system it functions in, you can get a picture of what is happening or not happening.

        This will lead you to the root cause of the customer concern.

 

 

 

Copyright © 2004-2012  BRP US, Inc.