If you can’t establish a working connection with your vehicle, try the following troubleshooting procedures.
- Do you have the latest ProScan software installed
on your PC?
|
Yes: |
Continue to the next step. |
|
No: |
See the “Getting Started” section of this manual. |
- Are you able to launch the ProScan software?
|
Yes: |
Continue to the next step. |
|
No: |
Make sure that your PC meets the minimum system requirements provided in the “Getting Started” section of this manual. If you receive an error message when trying to launch ProScan, the problem is most likely due to the .NET Framework not being installed. See the “Getting Started” section for instructions on installing the .NET Framework. |
- Do you have compatible OBD-II interface hardware
attached between your PC and your vehicle?
|
Yes: |
Continue to the next step. |
|
No: |
The ProScan software requires OBD-II interface hardware to translate OBD-II communications into a format understandable by PC serial ports and vice versa. ProScan supports any OBD-II interface hardware using one of the following interpreter chips manufactured by Elm Electronics:
Make sure the OBD-II cable is securely attached from the vehicle’s 16-pin diagnostic connector into the OBD-II interface module. Make sure the serial cable is securely attached from the OBD-II interface module into your PC’s 9-pin serial port. If your PC does not have a serial port, you will need to attach a USB-to-Serial adapter (sold separately) between the end of the serial cable and your PC’s USB port. |
- Is the OBD-II interface module receiving power from
the vehicle as indicated by the LEDs?
|
Yes: |
Continue to the next step. |
|
No: |
Make sure the OBD-II cable is securely attached from the vehicle’s 16-pin diagnostic connector into the OBD-II interface module. Also make sure you have the vehicle’s ignition turned to the ON position, or go ahead and start the engine. |
- Have you edited ProScan’s communication settings
to work properly with your hardware configuration?
|
Yes: |
Continue to the next step. |
|
No: |
See the “Communication Settings” section of this manual. |
- Can you see the “Connect” button on ProScan’s
Vehicle Connection Manager?
|
Yes: |
Continue to the next step. |
|
No: |
Right-click on your desktop and click the “Properties” menu item. This will open the Display Properties dialog. Click the “Settings” tab and check your screen resolution setting. For best results, we recommend running a screen resolution of at least 800x600. Now click the “Advanced” button in the lower right corner of the same dialog. This will open another dialog. Make sure your DPI setting is set to “Normal size (96 DPI)”. If it was set to something else, you will need to restart your computer for the display changes to take effect. |
- Can you establish a connection with the vehicle
by clicking the “Connect” button on ProScan’s Vehicle Connection Manager?
|
Yes: |
Congratulations, you can begin using ProScan on your vehicle! |
|
No: |
Continue to the next step. |
- Are you receiving an error stating that the
serial port could not be opened?
|
Yes: |
Make sure that no other application is currently using the serial port. If you have previously used any other serial device, there may be another application using the serial port. Exit any such applications or command them to quit using the serial port. If you are using a USB-to-Serial adapter, make sure that you have installed the drivers according to the manufacturer’s instructions. Also make sure that the serial port being emulated by the adapter is the one selected under ProScan’s Communication Settings. |
|
No: |
Continue to the next step. |
- Are you receiving an error stating that the OBD-II
interface module could not be detected?
|
Yes: |
Make sure that you have selected the correct serial port under ProScan’s Communication Settings dialog. Make sure that the interface is receiving power as indicated by its LEDs. Make sure that the cables and interface are securely fastened between the vehicle and your PC. If you are using a USB-to-Serial adapter, make sure that you have installed the drivers according to the manufacturer’s instructions. Also make sure that the serial port being emulated by the adapter is the one selected under ProScan’s Communication Settings. If you are using an ELM327-based interface, make sure that the correct baud rate setting is selected under ProScan’s Communication Settings. This is typically 9600 baud, but it could be 38400. |
|
No: |
Continue to the next step. |
- Are you receiving an error stating that the OBD-II
interface module could not be initialized?
|
Yes: |
Make sure that your OBD-II interface module is selected under the Hardware section of ProScan’s Communication Settings dialog. |
|
No: |
Continue to the next step. |
- Are you receiving an error stating that the OBD-II
interface module was detected and initialized, but communication with the
vehicle could not be established?
|
Yes: |
Make sure that your OBD-II interface module is selected under the Hardware section of ProScan’s Communication Settings dialog. If you are using an ELM327-based interface, and the protocol is set to “Automatic” under ProScan’s Communication Settings, then you may need to specify the protocol to use. The automatic protocol detection usually works, but it is not guaranteed. If you are using an ELM327-based interface, you can also try bypassing initialization. To do this, select “Bypass Initialization” under the ELM327 configuration section of ProScan’s Communication Settings. |
|
No: |
Continue to the next step. |
- Did the preceding troubleshooting process help
you pinpoint and correct the problem you have been experiencing?
|
Yes: |
Congratulations, you can begin using ProScan on your vehicle. |
|
No: |
We’re sorry that you are experiencing difficulties using ProScan on your vehicle. If you have access to another OBD-II vehicle, we recommend that you first try using ProScan on it. This could rule out the possibility of a problem with your OBD-II interface hardware. One of our knowledgeable support representatives would be more than happy to assist you with this problem. Please see the “Contacting Technical Support” section of this manual for further assistance. |