Questions and answers

(0) What is the warrantee or guarantee?
(1) I want to diagnose and repair airbags and/ or abs brake systems. Will this interface do the job?
(2) I have an xyz automobile. Does the interface fully support every possible data that my xyz car can yield?
(4) Can I make my own OBDII scantool?
(5) How to test a serial port (click here for instructions)
(6) My vehicle displays trouble code PXXXX. What part should I replace?
(7) My vehicle is a 1995 model made by xyz motor company. Is it OBDII?
(8) International orders
(9) Can I have source code or pic code or hex files?
(10) Does the interface work with handhelds (palms pda, pocket PC ....)?
(11) Notes on Certain Vehicles
(12) My PC doesn't have a serial port. What can I do?
(13) Manufacturer specific data or trouble codes
(14) Can I "Tune" or reprogram my car, or change internal operating tables/parameters?
(15) Do you have anything for OBD 1 cars (pre 1996)?
(16) Why do I get installation errors related to the roundgauge files?
(17) Does the software work with other scanners? Can I use other software ?

What is the warrantee or guarantee?

There is no specific warranty or guarantee. There are several reasons. In some cases, you may have built your own hardware or written your own software, so there is no way to know what your capabilities are. It is also likely that these devices will be used to diagnose vehicles which are already having problems, and there is no way to foresee all circumstances. Again, there is no way to know your personal capabilities. Therefore the policy is that all information, software, and hardware items are to be used at your own risk. Having said that, if you are not happy, you can return undamaged items within 21 days. Back to Top

I want to diagnose and repair airbags and/ or abs brake systems. Will this interface do the job?

No, It won't help. The device only querries powertrain controllers. Most of these functions are manufacturer specific. If your airbag or abs system shows a fault, you should probably take it to your dealer and have them troubleshoot it for you. There are also professional scantools that you could look into. Back to Top

I have a model xyz automobile. Does the interface fully support every possible data that my car can yield?

Probably not. The interface reads OBDII data as defined by SAE J1979. The specifications define some data that are mandated, and some optional data. But manufacturers are also allowed to present other data in nonstandard ways that are specific to the particular model. You may need a more fully featured professional scan tool. Back to Top

Can I build my own OBDII scantool?

Yes, you can order a partial kit of the essential parts, and construct your own, though you will need some additional commonly available parts. These kits do NOT contain step-by-step instructions, and they are NOT suitable for beginners.
You must have knowlege and experience with electronic circuits; know how to read schematics and troubleshoot problems with them, or you may not have good results. Back to Top

My vehicle displays trouble code PXXXX. What part should I replace?

It would be hard to say. The diagnostics that you get from your vehicle's ECU can go a long way in guiding you, but it is not a 'plug and play' parts replacement sort of thing. When you get a trouble code, it is an indication of a problem that the vehicle's ECU has detected, but often, you must play the part of detective to find the root cause. Be sure to look in the help file for a definition of the trouble code, but still, you may have to do some thinking to arrive at the root cause of a given problem. Trouble codes above P1000 may be defined differently by each manufacturer, so be sure to check in a manual which is devoted to the particular model. ( batauto.com also has a very good online collection of these codes for each make and model.) Back to Top

My vehicle is a 1995. Is it OBDII?

Immediately before OBDII was mandated, some manufacturers implemented it, either partially, or fully on certain selected models. Some of them went to the 16 pin connector, but all the data lines were the same older bus .... ie, only the connector changed, but was not OBDII. On some models, there actually was a partial implementation, and some were completely OBDII compatible even though they were not required by law. Generally, 1995 vehicles are not OBDII, so don't assume the interface will work, even if the vehicle is supposed to be OBDII. Back to Top

International orders:

We discourage orders outside the USA or territories for several reasons:
(1) In many countries, there were no requirements for OBDII or EOBD (though this is slowly changing). Therefore it is difficult to know if a particular vehicle is compatible or not, especially older cars.
(2) International mail is very slow, and can't be tracked except for very expensive methods of shipping.
(3) Many countries charge additional fees and duties when they deliver to the end user. It is hard to predict what charges you will have to pay. Back to Top

Can I have source code or pic code?

No, sorry, source code or pic code is not available. Back to Top

Does the interface work with palms or other handheld computers?

No. In general, these devices use different operating systems, and they don't have a standard connector for the serial link. Since there are so many different types, it is impossible to provide a universal solution. Back to Top

Notes on certain vehicles:
The interface may not work with motorcycles, heavy duty trucks (works with some, but not all), and farm or construction equipment. Back to Top

My PC doesn't have a serial port. What can I do?

Some laptop computers don't have serial ports, but they do usually have at least one USB port. There are a number of very inexpensive converter cables available. They use a device driver to create a serial port under windows operating system. The driver that comes with the converter cable must be compatible with your version of windows of course, and the USB ports must be functioning, both in hardware and in the operating system and in the drivers for the convertor cable. In general, obtaining a proper convertor and setting it up may be easy, but sometimes requires a bit of expertise and knowledge of your particular computer system. If you have a converter cable installed, you can test it without an OBDII interface to see if the port is basically working. These port testing instructions may be helpful. Back to Top

Manufacturer specific data or trouble codes

The interface works for data that is defined in SAE J1979. Manufacturers can also provide additional data that they may define in a proprietary manner.
The powertrain diagnostic trouble codes are a completely different matter. The interface will report any diagnostic trouble code that the vehicle sends under mode 3. This includes manufacturer specific powertrain trouble codes. The only difference between these codes is that they are numerically higher than P1000. The codes below P1000 are generically defined by SAE for convenience and commonality.
To avoid confusion, please note that there are also trouble codes which are not powertrain trouble codes. These do not have a P prefix, and are chassis, body, or network codes (C, B and U prefixes). Typically, these codes are used for systems such as antilock brakes, ride control systems and the like, and cannot be read by the interface. Back to Top

Can I reprogram my car, or change internal operating tables/parameters?

No, it will NOT reprogram the vehicle ECU, or change any operating parameters. The only data that it can change is clearing diagnostic data, such as trouble codes or on-board test results. Back to Top

Do you have anything for OBD 1 cars (1995 and earlier)?

No. OBD 1 systems are completely different, and were not particularly standardized for different vehicles. You will need to search for something that will work for your specific vehicle.
In most cases, these earlier vehicles will at least allow you to read trouble codes without any special instrument. The methods vary, but are usually specified in repair manuals (even aftermarket manuals such as haynes or chilton), as well as many online webpages. Back to Top

Why do I get installation errors related to the round gauge files?

The gauge routines are written in microsoft C and needs support files which may not have been automatically installed with older versions of windows, especially windows 95. The files that you need are msvcrt.dll and mfc42.dll. Check to be sure these files are in the C:\windows\system directory. For windows 98, these files are on your windows cdrom. You may also be able to find them at microsoft's web site or other online sources. (Note that these files are specific to windows 95/98/ME (The files for any NT based version of windows such as NT/2K/XP will not work.) After copying the files, you may have to register it with your windows system (click the windows start button, select RUN, then type regsvr32 mfc42.dll in the dialog box. Reboot and then install the software once again to allow it to detect the runtime files. Back to Top

Does the software work with other scanners? Can I use other software ?

In general, you can't mix and match various scanners and their software. The software on this web page was designed for BR series tools only. It won't work with other devices such as ELM. Likewise, most other programs won't work with BR tools. If you would like to explore other software, and enjoy programming, the Sourceforge FreeDiag open source program may be of interest. Back to Top


If you have a question which is not addressed in the faq, you may EMAIL your question.

Back to OBDII Automotive Diagnostics Home page