User's Manual

Diagnostics Operations Generic OBD II Operations
51
Occasionally a flash update procedure may not complete properly. Common
causes of flash errors include poor cable connections between the display
tablet, VCI, and vehicle, turning off the vehicle ignition switch before the flash
procedure is complete, or low vehicle battery voltage.
If the process crashes, recheck all the cable connections to assure good
communications and reinitialize the flash procedure. The programming
procedure will automatically repeat if the previous operation does not
succeed.
4.9 Generic OBD II Operations
A fast-access option for OBD II/EOBD vehicle diagnosis is available on the
Vehicle Menu screen (Figure 4-1). This option presents a quick way to check
for DTCs, isolate the cause of an illuminated malfunction indicator lamp (MIL),
check monitor status prior to emissions certification testing, verify repairs, and
perform a number of other services that are emissions-related. The OBD
direct access option is also used for testing OBD II/EOBD compliant vehicles
that are not included in the Diagnostics database.
Functions of the diagnostics toolbar buttons at the top the screen are the
same as those available for specific vehicle diagnostics. See Table 4-2
Diagnostics Toolbar Buttons on page 28 for details.
4.9.1 General Procedure
 To access the OBD II/EOBD diagnostics functions
1. Tap the Diagnostics application button from the MaxiSys Job
Menu. The Vehicle Menu displays.
2. Tap the EOBD button. There are two options to establish
communication with the vehicle.
 Auto Scan – When this option is selected the diagnostic tool
attempts to establish communication using each protocol in
order to determine which one the vehicle is broadcasting on.
 Protocol – When this option is selected the screen opens a
submenu of various protocols. A communication protocol is a
standardized way of data communication between an ECM
and a diagnostic tool. Global OBD may use several different
communication protocols.