OBD-II Scan Tool Software
Home
   
Order ProScan
   
Check Order Status
   
ProScan Details
   
Software Downloads
   
FAQ
   
User's Manual
   
DTC Database
   
Vehicle Protocols
   
Testimonials
   
Links
   
Contact Us

ProScan Help - Troubleshooting

Troubleshooting

If you are having a problem with ProScan, you can use this procedure to determine the cause of your problem.

Step 1

Make sure that your vehicle is not running and that the key is in the OFF position.

Connect the OBD-II cable to your vehicle and then to the appropriate electrical interface. Then connect the 25-pin connector of the serial cable to the electrical interface, and plug the 9-pin connector into your computer's serial port. If your computer does not have a serial port, use a USB to Serial converter.

Now that you have a physical connection between your vehicle and your computer, it is time to troubleshoot the electrical interface and your vehicle.

Step 2

Launch the program “HyperTerminal” on your computer.

It should be located at:

Start->Programs->Accessories->HyperTerminal

or

Start->Programs->Accessories->Communications->HyperTerminal

HyperTerminal is a program that is included with Windows, but it may not be installed by default. If you do not have HyperTerminal installed, it can be found on Microsoft's web site.

When asked for a name for the connection, you can simply enter anything that you wish. As you can see above, I just typed "blah."

You will then need to specify that you want to connect via the serial port. This will probably be COM1, but could be different depending upon your computer's configuration.

COM port Properties:

  • Bits per second: 9600

  • Data bits: 8

  • Parity: None

  • Stop bits: 1

  • Flow control: None

After clicking "OK", you should be connected to the serial port that you specified. You can verify this by checking the status bar in the lower left corner of the window.

Anything that you type will be sent directly to the interface via the serial port connection. Likewise, anything that the interface sends to the computer will be displayed on the screen. You may or may not be able to see what you type.

Step 3

At this time, turn the vehicle key to the ON position. This will provide power to the electrical interface, and it should echo the name and version number of its internal ELM microcontroller. You should see something like: "ELM322 v1.1" appear in the HyperTerminal window. If nothing appears, type: "ATI" and press ENTER. This is a command that will force the interface to identify itself.

If nothing appears, check your cable connections, and verify that you are using the appropriate interface for your vehicle. Click the "File" menu and choose "New Connection". Repeat the above procedure, but try a different COM port this time. If you used COM1 the first time, try COM2 this time. If you don't see any text within a few seconds, type: "ATI" and hit ENTER. If you still can't get the interface to respond, you can try yet another COM port setting.

Once you have tried all possible COM port settings, you can conclude that the electrical interface is not functioning properly. This is either because it is not working properly or it is not the appropriate interface for the vehicle. If you have another type of interface, you can try the above process with it.

If you can successfully get the interface to respond and print a message to the screen, then you can conclude that the cables are attached properly and that the correct interface is being used for the vehicle.

Step 4

Once you have verified that the hardware is attached properly, you need to verify that the interface can communicate with the vehicle's OBD-II system.

To verify this, type: "0101" and press ENTER.

You should receive a response such as this: "41 01 81 07 65 04". The numbers will vary, but it should begin with "41 01". If you received a similar response, then you can conclude that the hardware is working properly.

If you did not receive a response, or if you received an error message, then the interface is having problems communicating with your vehicle. This could be because the interface is of the wrong protocol (VPW, PWM, or ISO), it could be a malfunctioning interface, or it could be a problem with your vehicle's OBD-II system.

Need additional support?

If the above troubleshooting guide did not help you correct the problem, please contact us via our web site. Be as detailed as possible in stating your question, and we will respond as soon as possible.