EASE Simulation Inc. WI-916 Manuel D’Utilisation
160
2) I have an OBD II Subaru vehicle and the I/M monitors always say not completed. Is there something wrong
with my vehicle?
• Some Subaru vehicles clear the I/M monitors when the vehicle is turned off. After driving the vehicle, leave it
• Some Subaru vehicles clear the I/M monitors when the vehicle is turned off. After driving the vehicle, leave it
running and plug in the scan tool to check you monitors.
3) I have an OBD II BMW vehicle and my Hand Held QuikCode will not communicate. What can I do?
• Some BMW vehicles will not connect to the Hand Held QuikCode until the vehicle is warmed up. Warm up the
vehicle and then try again.
4) I have an OBD II Ford vehicle and some of the generic data is reading 0 when there should be a value (O2
sensors, or vehicle speed for example). What is the problem and what can I do?
• Some OBD II Ford vehicles, even though they support a generic parameter, will never send any data other than
• Some OBD II Ford vehicles, even though they support a generic parameter, will never send any data other than
zero. However, the Ford Enhanced Parameter signal set typically does include enhanced parameter data for the
non-valid generic data. Also note, some Ford vehicles will start sending valid O2 data once the vehicle is
warmed up.
non-valid generic data. Also note, some Ford vehicles will start sending valid O2 data once the vehicle is
warmed up.
5) I tried using my GM OBD II Enhanced tool but almost all of the parameters fell out of the list after I
connected to the vehicle. Why aren’t they supported?
• The exact vehicle that you are trying to connect to with GM OBD II Enhanced tool must be vehicle selected
• The exact vehicle that you are trying to connect to with GM OBD II Enhanced tool must be vehicle selected
when you try to connect the software. Check the VIN of the vehicle you are trying to read data from and select
the appropriate vehicle (year, make, model, and engine size) from the Select New Vehicle screen. If the
incorrect vehicle is selected, all but the generic parameters will fall out of the list. When the correct vehicle is
selected, the parameters stay in the list.
the appropriate vehicle (year, make, model, and engine size) from the Select New Vehicle screen. If the
incorrect vehicle is selected, all but the generic parameters will fall out of the list. When the correct vehicle is
selected, the parameters stay in the list.
• The vehicle does not support the way the scan tool requests the information. If you have the Professional
Version 1.0.6.53 or earlier, or the Personal version 1.0.6.57 or earlier, then create an icon on the desktop for the
easescan.exe (or the gmobd2.exe if you have the GM OBD II Enhanced tool). Right click on the icon and select
Properties from the menu that is displayed. On the Properties window, select the Shortcut tab. Where is says
Target: , you will see the path to the exe. At the end of what is already typed in there (if there is a double quote
there, enter the following after that), enter a space and then type nodpid. Click OK on the properties window
and start the software using the icon you created. The parameters should now stay in the list. If you have
Professional version 1.0.7.62 or later, or Personal version 1.0.7.65, then under the Options menu on the
parameter grid screen, select Fast Data Packets so that the check box is no longer on and then reset the tool.
The parameters should now stay in the list.
easescan.exe (or the gmobd2.exe if you have the GM OBD II Enhanced tool). Right click on the icon and select
Properties from the menu that is displayed. On the Properties window, select the Shortcut tab. Where is says
Target: , you will see the path to the exe. At the end of what is already typed in there (if there is a double quote
there, enter the following after that), enter a space and then type nodpid. Click OK on the properties window
and start the software using the icon you created. The parameters should now stay in the list. If you have
Professional version 1.0.7.62 or later, or Personal version 1.0.7.65, then under the Options menu on the
parameter grid screen, select Fast Data Packets so that the check box is no longer on and then reset the tool.
The parameters should now stay in the list.
6) I have a 1996 General Motors vehicle and the scan tool won’t connect or all the values won’t display with my
Generic OBD II Scan Tool or my GM Enhanced OBD II scan tool. What can I do?
• Most GM vehicles allow packing of parameter data for faster information. Some vehicles do not. If the scan
• Most GM vehicles allow packing of parameter data for faster information. Some vehicles do not. If the scan
tool cable status says ‘Connected’ and you have the correct COM port selected and you still won’t connect, you
can try the following: If you have the GM Enhanced professional version 1.0.6.53 or earlier, or the GM
Enhanced personal version 1.0.6.57 or earlier, or the Generic professional version 1.4.5.38 or earlier, or Generic
personal version 1.4.5.41 or earlier, then create an icon on the desktop for the easescan.exe (or the gmobd2.exe
if you have the GM OBD II Enhanced tool). Right click on the icon and select Properties from the menu that is
displayed. On the Properties window, select the Shortcut tab. Where is says Target: , you will see the path to
the exe. At the end of what is already typed in there (if there is a double quote there, enter the following after
that), enter a space and then type nodpid. Click OK on the properties window and start the software using the
icon you created. The tool should now connect. If you have GM Enhanced professional version 1.0.7.62 or
later, or GM Enhanced personal version 1.0.7.65, or OBD II Generic professional version 1.4.10.42, or OBD II
Generic personal version 1.4.10.45 or earlier, then under the Options menu on the parameter grid screen, select
Fast Data Packets so that the check mark is no longer on and then reset the tool. The tool should now connect.
can try the following: If you have the GM Enhanced professional version 1.0.6.53 or earlier, or the GM
Enhanced personal version 1.0.6.57 or earlier, or the Generic professional version 1.4.5.38 or earlier, or Generic
personal version 1.4.5.41 or earlier, then create an icon on the desktop for the easescan.exe (or the gmobd2.exe
if you have the GM OBD II Enhanced tool). Right click on the icon and select Properties from the menu that is
displayed. On the Properties window, select the Shortcut tab. Where is says Target: , you will see the path to
the exe. At the end of what is already typed in there (if there is a double quote there, enter the following after
that), enter a space and then type nodpid. Click OK on the properties window and start the software using the
icon you created. The tool should now connect. If you have GM Enhanced professional version 1.0.7.62 or
later, or GM Enhanced personal version 1.0.7.65, or OBD II Generic professional version 1.4.10.42, or OBD II
Generic personal version 1.4.10.45 or earlier, then under the Options menu on the parameter grid screen, select
Fast Data Packets so that the check mark is no longer on and then reset the tool. The tool should now connect.
7) I’m connected to a GM OBDI RWAL controller and can’t determine what the error codes are. How do I
figure it out?
• For the RWAL controller, the possible DTCs are listed on the Main DTC screen, however, the status (Fault or
• For the RWAL controller, the possible DTCs are listed on the Main DTC screen, however, the status (Fault or
OK) is not displayed. To determine the RWAL DTC number, observe the flashing brake lamp on the vehicle
dash. In counting the brake lamp flashes, count the number of short flashes starting from the long flash. Include
the long flash as a count. Note that sometimes the first count sequence is short because the flashout started with
the count already in progress. Subsequent counts, however, will be accurate. If there is more than one failure,
only the first recognized failure code will be retained and flashed.
dash. In counting the brake lamp flashes, count the number of short flashes starting from the long flash. Include
the long flash as a count. Note that sometimes the first count sequence is short because the flashout started with
the count already in progress. Subsequent counts, however, will be accurate. If there is more than one failure,
only the first recognized failure code will be retained and flashed.