How to Install ELM327 WIFI OBD Scanner software on PC

SAFETY WARNING: Never start and run your engine inside of a closed garage. Always make sure there is good ventilation to prevent carbon monoxide poisoning. Carbon monoxide fumes are produced by your engine’s exhaust gases.

1. Locate your car’s OBDII diagnostic port and plug in your scanner. The location will vary on each car, but it’s usually found within arm’s reach under the driver’s side dashboard, under the steering wheel.

2. Turn on your ignition by turning your key to the 2nd turn. The engine will be off, but this provides power to your dash lights, radio and also the OBDII diagnostic port.
3. On your iPhone, iPad or iPod Touch, go to Settings, then Wi-Fi and connect to the scanner’s Wi-Fi signal. This is done in the same manner as connecting to your home WiFi Network.
4. Start your engine. Although the OBDII port is providing power to the scanner, in some cases you will not be able to retrieve any engine data without the engine running.
5. Go to your App. Go to the settings menu to configure the scanner. You want to make sure the IP Address is 192.168.0.10 and the Port is 35000. This information is normally setup automatically and nothing else needs to be done, but it’s a good idea to make sure the first time you’re setting it up.
6. Go to the App’s main page, start your first scan and enjoy seeing your engine’s available parameters.

If you cannot find the Scanner’s WiFi signal in Wireless Settings:

• Check to see if the LEDs are on. Some of the LEDs will flash to indicate an active Wi-Fi signal
• If your ignition is not on, turn your car key to the 2nd turn to turn on the ignition and try again
• Turn off your phone’s Wi-Fi in the settings and turn it back on

If you can connect to the WiFi signal, but cannot connect within the App:

• Make sure the connection is configured within the App’s settings. The IP should be 192.168.0.10and the Port is 35000
• In the iPhone settings, touch the blue arrow on the WiFi connection. By default, it will connect to the DHCP settings. Set it to Static and enter the IP Address “192.168.0.10” and Subnet Mask to “255.255.255.0”. Try again within the App.

How to setup ELM327 WiFi Diagnostic Scanner on iOS Apps

Why does your vehicle need it?

Have you ever thought about different vehicle parameters being displayed in your own Android application? If so, then you’ve come to the right place. We will discuss what it takes to develop an OBDII reader application.

First, let’s take a quick look at the protocols used in vehicles for diagnostics.

OBD is an acronym for “on-board diagnostics” and refers to vehicle’s self-diagnostics and reporting capability. Originally it was intended to help mechanics run quick vehicle diagnostics. The early versions of it allow checking for possible problems with the engine. Nowadays, in addition to preserving the “diagnostics” part, this system has been dramatically enhanced and allows a vehicle owner to be in control of different parameters like the current fuel consumption rate, gear and transmission modes, GPS module and so on. For a full understanding of how it works and the history behind it, you can read the full article on Wikipedia called “On-board diagnostics”.

Necessary materials

First of all, you would need a OBDII adapter to be able to use the OBDII interface. There are many adapters from different manufacturers. Some of them have a COM interface, others have a USB interface, and some have a Bluetooth interface. Theoretically, any adapter can be used by the Android application, but in practice, your best choice is the Bluetooth interface.Also, adapters can be differentiated by supported OBDII protocols (i.e. by supported vehicles).So if you have a car within reach and good OBDII adapter we can start developing OBDII reader application.

Hold on – do you really have a car close enough to your development environment? Actually we can use a simulator for a start. The one that worked for me is OBDSim: it is an open source project available for different platforms. Since Bluetooth is not supported on Windows, rebuilding it from scratch in Linux will be necessary. Please note that most likely it will require you to modify the source code and change RFCOMM channel to the first available instead of channel 1.

What’s more, a hardware emulator can be used instead of a real car. I used ECUsim 2000 standard with ISO 15765 (CAN) protocol enabled. As for the OBDII adapter – I used ELM327 v.1.5 adapter.

Developing the application

Let’s start with describing the protocol that is used for communication between Android device and OBDII adapter/vehicle. It is text-based polling type protocol. This means that all you need is to send a command to receive a response. And knowing what commands to send is key.

We will connect to the adapter through Bluetooth. It seems that Bluetooth Low Energy API is just the thing we should use. However, since it is now supported only by several devices, it is too early to use it.

The protocol supports some AT commands like turning echo and control line feed. Another part of the protocol is OBDII control protocol itself.

The general workflow of the application functionality should go like this:

1) connect to the OBDII adapter through Bluetooth;

2) initialize OBDII adapter with AT commands;

3) continuously get data from the vehicle through issuing the corresponding PID codes.

Connecting to the OBDII adapter is straightforward. But one thing you need to do before connecting is to select the Bluetooth device. Displaying an alert dialogue with single choice items is a good way to go:

ShowShow code

Don’t forget to save the selected device address somewhere. Now we can connect to the selected device:

ShowShow code

The UUID I mentioned represents a “serial” interface through Bluetooth. Of course, this code should be executed in a non-UI thread. Also, I would recommend checking this article for details and a solution of a bug in Android that can lead to connection failure in some cases. We  can now make the data exchange. We will use a OBD-Java-API library for this. The library is pretty simple to use. It has several classes, which correspond to different OBD commands. Don’t forget to initialize the OBDII adapter first by issuing configuration commands:

ShowShow code

We are now ready to issue any other commands:

Here I should point that this library has some issues with parsing response and it often crashes because of poor error handling. The first flaw is the “performCalculations” method present in all command classes. It would be good to check the buffer size before accessing buffer data, because in some cases the response may be shorter than required. Of course, the problem of a shorter response is on the OBDII adapter/vehicle side, but the library should be ready for such issues.

Apart from this, there are some other issues, so this library still requires improvements or can be used simply as a reference.

The obtained data can be stored somewhere for further analysis, for example, on the ElasticSearchinstance.

Right now, we are working on a Hours of Service application for commercial vehicle drivers and will continue sharing our experience on OBDII in our blog. Meanwhile, you can find more information on developing applications for latest IoT gadgets in our experience section Apps for Connected Devices.

How to install Bluetooth ELM327 scan tool on pc?

1) Locate the diagnostic connector. The 16-pin D-shaped diagnostic link connector (DLC) should be located in the passenger or driver’s compartment in the area bounded by the driver’s end of the instrument panel to 300 mm (~1 ft) beyond the vehicle centerline, attached to the instrument panel and easy to access from the driver’s seat. The preferred location is between the steering column and the vehicle centerline.
2) Turn on the ignition switch and plug the elm327 into the diagnostic socket.
3) Install USB to Bluetooth adapter. Make sure Bluetooth is activated on your laptop or phone. Turn on the Bluetooth symbol and add a device.
4) Match the password and enter the device Bluetooth pairing code
5) Launch the software and select the appreciate COM port. The COM port is the port that your Bluetooth is setup on your computer to communicate with incoming devices. Had better write it down and you will need it later to configure the diagnostics software.
6) Start to scan the ECU and read data.

How to tell different ELM327 scan tools

The ELM327 is a programmed scanner produced by ELM Electronics for translating the OBD interface found in most modern cars. There are as many as 26 various elm327 products are available in aftermarket. They project almost the same function, but differ in some aspects. How to identify different elm327 items and choose a best one?
ELM327 can be divided into different categories according to the different ways
1) Operating system
ELM327 are designed to work on various systems, Android and PC system, Android and IOS system, Android, IOS and PC system, Android and Symbian system, IOS system only etc. Different system based elm327 scanners highlights different features, also differs in software installation and usage. Users had better to pick up one that meets their phone/PC requirements.
2) Connection Mode
ELM327 products are designed to work through multi communication ways, WIFI, USB, RS-232 and Bluetooth.
WIFI:
WIFI ELM327 interface is able to detect and interpret obd2 / eobd protocols automatically. It also provides support for high speed communications and a low power sleep mode. It is easy to communicate with a host device (PC, notebook, iPhone, iPod touch, iPad and so on).

USB:
USB ELM327 scanner can translate all the hard work of protocol into a simple ASCII character based view via the included serial cable. USB ELM327 is used as an interface to connect virtually all OBD-II compliant vehicles to a PC for on-board diagnostics (OBD).

Bluetooth:
OBD-II Software for ELM327 Bluetooth is a free program that allows you to use your PC and a hardware interface to get the information from your car`s computer.

3) Communication Protocol
Some elm327 products are special designed for CAN BUS protocol vehicle models, some fits for OBD?and EOBD? vehicles, most of them support all OBD?protocols vehicles. Make sure pick up a correct elm327 to meet the requirement of your vehicle communication protocol.
How to identify the communication protocol of your vehicle?
As a rule of thumb, GM cars and light trucks use SAE J1850 VPW (Variable Pulse Width Modulation). Chrysler products and all European and most Asian imports use ISO 9141 circuitry. Fords use SAE J1850 PWM (Pulse Width Modulation) communication patterns.
There are some variations among captive imports such as the Cadillac Catera, a German Opel derivative, which uses the European ISO 9141 protocol.
On 1996 and later vehicles, you can tell which protocol is used by examining the OBD II connector:
J1850 VPW–The connector should have metallic contacts in pins 2, 4, 5, and 16, but not 10.
ISO 9141-2–The connector should have metallic contacts in pins 4, 5, 7, 15, and 16.
J1850 PWM–The connector should have metallic contacts in pins 2, 4, 5, 10, and 16.

4) Outlook Design
The outlook design of elm327 scanners turns to get smaller and smarter. MINI elm327 takes over the elm family. Some even special designed with an ignition switch to expand service life. Some elm327 scanners are offered different color alternative.

Why OBDII Reader App is necessary for Phones

Why does your vehicle need it?

Have you ever thought about different vehicle parameters being displayed in your own Android application? If so, then you’ve come to the right place. We will discuss what it takes to develop an OBDII reader application.

First, let’s take a quick look at the protocols used in vehicles for diagnostics.

OBD is an acronym for “on-board diagnostics” and refers to vehicle’s self-diagnostics and reporting capability. Originally it was intended to help mechanics run quick vehicle diagnostics. The early versions of it allow checking for possible problems with the engine. Nowadays, in addition to preserving the “diagnostics” part, this system has been dramatically enhanced and allows a vehicle owner to be in control of different parameters like the current fuel consumption rate, gear and transmission modes, GPS module and so on. For a full understanding of how it works and the history behind it, you can read the full article on Wikipedia called “On-board diagnostics”.

Necessary materials

First of all, you would need a OBDII adapter to be able to use the OBDII interface. There are many adapters from different manufacturers. Some of them have a COM interface, others have a USB interface, and some have a Bluetooth interface. Theoretically, any adapter can be used by the Android application, but in practice, your best choice is the Bluetooth interface.Also, adapters can be differentiated by supported OBDII protocols (i.e. by supported vehicles).So if you have a car within reach and good OBDII adapter we can start developing OBDII reader application.

Hold on – do you really have a car close enough to your development environment? Actually we can use a simulator for a start. The one that worked for me is OBDSim: it is an open source project available for different platforms. Since Bluetooth is not supported on Windows, rebuilding it from scratch in Linux will be necessary. Please note that most likely it will require you to modify the source code and change RFCOMM channel to the first available instead of channel 1.

What’s more, a hardware emulator can be used instead of a real car. I used ECUsim 2000 standard with ISO 15765 (CAN) protocol enabled. As for the OBDII adapter – I used ELM327 v.1.5 adapter.

Developing the application

Let’s start with describing the protocol that is used for communication between Android device and OBDII adapter/vehicle. It is text-based polling type protocol. This means that all you need is to send a command to receive a response. And knowing what commands to send is key.

We will connect to the adapter through Bluetooth. It seems that Bluetooth Low Energy API is just the thing we should use. However, since it is now supported only by several devices, it is too early to use it.

The protocol supports some AT commands like turning echo and control line feed. Another part of the protocol is OBDII control protocol itself.

The general workflow of the application functionality should go like this:

1) connect to the OBDII adapter through Bluetooth;

2) initialize OBDII adapter with AT commands;

3) continuously get data from the vehicle through issuing the corresponding PID codes.

Connecting to the OBDII adapter is straightforward. But one thing you need to do before connecting is to select the Bluetooth device. Displaying an alert dialogue with single choice items is a good way to go:

ShowShow code

Don’t forget to save the selected device address somewhere. Now we can connect to the selected device:

ShowShow code

The UUID I mentioned represents a “serial” interface through Bluetooth. Of course, this code should be executed in a non-UI thread. Also, I would recommend checking this article for details and a solution of a bug in Android that can lead to connection failure in some cases. We  can now make the data exchange. We will use a OBD-Java-API library for this. The library is pretty simple to use. It has several classes, which correspond to different OBD commands. Don’t forget to initialize the OBDII adapter first by issuing configuration commands:

ShowShow code

We are now ready to issue any other commands:

Here I should point that this library has some issues with parsing response and it often crashes because of poor error handling. The first flaw is the “performCalculations” method present in all command classes. It would be good to check the buffer size before accessing buffer data, because in some cases the response may be shorter than required. Of course, the problem of a shorter response is on the OBDII adapter/vehicle side, but the library should be ready for such issues.

Apart from this, there are some other issues, so this library still requires improvements or can be used simply as a reference.

The obtained data can be stored somewhere for further analysis, for example, on the ElasticSearchinstance.

Right now, we are working on a Hours of Service application for commercial vehicle drivers and will continue sharing our experience on OBDII in our blog. Meanwhile, you can find more information on developing applications for latest IoT gadgets in our experience section Apps for Connected Devices

More Other Relation Auto scanner Product http://www.worldobd2.com/

2013 Buick Excel Review On WIFI VXDIAG GM

Other Relation Auto scanner Product :Foxwell        

Relation News Search : Autel Maxisys    

Just to share my experience of Chinese diagnostic tool VXDIAG here.

For diagnosis on my 2010 Buick Excel, purchased GM VXDIAG scanner from www.wobd2.com DHL shipping for one week.

Package seemed packed well. Every item looked in a good condition, the main unit, two disks with software Tech2win and GDS2 (sounds with scratch), one cable also. Worried about the software damaged because of a little scratch on the GDS2 disk, so installed GDS2 first.

Easy to install gds2 in Win7 64bit, 3 steps only— install VMware, set COM Port & install VXDIAG GM Driver.
For the detail, go on reading…
–Step 1 Install VMware
Open GDS2 software CD
Open “VMware-player-6.0.6-2700073” and install VMware-player
Install wizard for VMware Player
Click Next
Accept license agreement
Click Next
Click Next
Tick “Check for product updates on startup”, click Next
Click Next, Create desktop shortcuts, click Next
Press Continue
Setup Wizard complete, press Finish
Copy GDS2 VM folder on CD to Local Disk (E;)
Open VMware Player on desktop
Open a Virtual Machine->select E:/GDS2 VM->Win_XP_GDS2_11_2014
Select Play virtual machine
Click OK
Press “I copied it” if the system asks have you moved or copied the virtual machine
Click OK
Click OK
–Step 2 Set COM Port
Make a full screen of VMware
Open Computer->Manager->Device Manager->Ports&LPT to check device is well connected to the computer
Click VMware, back to host machine, disconnect VCX Wifi connection
Open virtual machine again, go to Computer->Manager->Device Manager->Ports&LPT to check USB Serial Port is set to COM3
–Step 3 Install VXDIAG GM Driver
Open VX Manger driver on desktop
Select “Configure” button
Select Connection Type as “USB”

Installation completes!

Then i go to basically diagnose my car.
I successfully read & clear trouble codes of airbag, ECM, etc.
Also, i read VIN, ECU part numbers and software numbers.
Record, store and replay stored data…it’s ok.
Sbc reset i did so.
But control and monitor output control functions and freeze frame data function…i haven’t tried. And record or display history of the previous vehicle diagnostic sessions… should no much trouble, i think

Here, take one diagnosis as an example, ECM codes reading.
connect VXDIAG interface to EXCEL via the cable, to laptop via wireless connection.
Connect VCX WIFI wireless connection

Open VX Manager on desktop
Press “Configure” function
Set Connection Type to “WLAN” and save it

Open GDS2 software on desktop and diagnose 2010 Buick Excel.

Module Diagnostics, click Enter
Engine Control Module, click Enter
Engine identifier: select 1.6L (LDE) and click Enter
Diagnostic Trouble Codes (DTCs) and click Enter
DTC display, click Enter
Click Details

Read and click Back
Go to Home page and Close Applications

All in all, basic diagnosis on EXCEL 2010 was ok!! Content with this purchase from China.

Install VXDIAG VCX NANO Ford/Mazda IDS V95

New Arrival VXDIAG VCX NANO for Ford and Mazda 2 in 1 diagnostic scanner comes with V95 IDS. Here is the step-by-step software instruction provided.

Software version: Ford IDS V95, Mazda IDS V95

Language:

English/German/French/Italian/Spanish/Dutch/Slovenian/Finnish/Danish/Norwegian/Portuguese(European)/Portuguese(Brazil)

Operating system:

Win XP SP3 PC made 2000 year up

Computer has at least 4GB Memory

Install VXDIAG Ford & Mazda IDS V95 software on VMware:

Video guide:

1) Install VMware Player

Open CD Driver

Install VMware player

Click “Next”

Accept license agreement, click “Next”

Click “Next”

Uncheck the software updates notice, press “Next”

Uncheck and click “Next”

Click “Next”

Click “Continue”

Click “Finish” when VMware player is well installed

2) Configure VMware

Copy Ford IDS95 VM file to disk C://

Open VMware on deaktop

Select open a Virtual Machine

Select “Play virtual machine”

Run VMware

3) Connect VXDIAG scanner

Connect VXDIAG VCX NANO Ford/Mazda scanner interface with computer

Select “Connect” tab

If you want to perform programming functions, you need to connect the network.

Open “VCM II Manager” on the desktop to check the connection

4) Run Ford/Mazda IDS V95 software

Open “IDS” setup on desktop

Check communication in Wireless Device Manager interface

Select Information option to check software version and VXDIAG firmware information

Click car icon to establish communication to PCM

After well communication is built, the IDS will display vehicle information

Stat to run Self- Test and read codes

Select specific control module and view freeze frame, live data etc

 

More VXDIAG VCX NANO Products: www.wobd2.com

Install VXDIAG VCX NANO Ford/Mazda IDS V95

Hot sale VXDIAG VCX NANO for Ford and Mazda 2 in 1 diagnostic scanner comes with V95 IDS. Here is the step-by-step software instruction provided.

Software version: Ford IDS V95, Mazda IDS V95

Language:

English/German/French/Italian/Spanish/Dutch/Slovenian/Finnish/Danish/Norwegian/Portuguese(European)/Portuguese(Brazil)

Operating system:

Win XP SP3 PC made 2000 year up

Computer has at least 4GB Memory

Install VXDIAG Ford & Mazda IDS V95 software on VMware:

Video guide:

1) Install VMware Player

Open CD Driver

Install VMware player

Click “Next”

Accept license agreement, click “Next”

Click “Next”

Uncheck the software updates notice, press “Next”

Uncheck and click “Next”

Click “Next”

Click “Continue”

Click “Finish” when VMware player is well installed

2) Configure VMware

Copy Ford IDS95 VM file to disk C://

Open VMware on deaktop

Select open a Virtual Machine

Select “Play virtual machine”

Run VMware

3) Connect VXDIAG scanner

Connect VXDIAG VCX NANO Ford/Mazda scanner interface with computer

Select “Connect” tab

If you want to perform programming functions, you need to connect the network.

Open “VCM II Manager” on the desktop to check the connection

4) Run Ford/Mazda IDS V95 software

Open “IDS” setup on desktop

Check communication in Wireless Device Manager interface

Select Information option to check software version and VXDIAG firmware information

Click car icon to establish communication to PCM

After well communication is built, the IDS will display vehicle information

Stat to run Self- Test and read codes

Select specific control module and view freeze frame, live data etc

 

More VXDIAG VCX NANO Products:http://www.wobd2.com

Review of Cheapest way to read VAG Pin code

My brother-in-law Jeff called me last week and asked what the cheapest and most efficient way was to find out the importers code and the workshop, as well as the immobilizer PIN code of his Audi A3 of the year 2003, so that he could change them.

Pin code immobilizer is actually the 4-digit code, which can be read by using plenty of tools on the aftermarket. As he was looking for a cheapest but efficient one, I recommended him US$14.99 VAG Tango 3.01+ Opel Immo Airbag, free shipping on wobd2.com

The tool supports PIN code reading for VW Polo, VW Passat B6, Bora/Jetta, Polo to 2004 year, Golf 4, Skoda Octavia/ Fabia to 2004 year, some Seat dashes up to 2004 year, etc. I had bought one before to read PIN code for a 2000 Audi A6 V6. The tool worked well.

Knowing the PIN code of your vehicle will allow you to encode transponders keys and other things. If you have kept the small black label on the key, you can also find the 4-digit code immobilizer on it. It is OK still if you take it off. The cost to know the PIN code is merely US$15.

Jeff bought a VAG Tango interface the next day and got it this afternoon. He called just now to say thank you. He told me that he had used the tool to get Pin code, and then made a new key with the code by following tutorials on Youtube – no problem at all.

Launch x431 iDiag installation

Compare with Autel Maxidas ds708，x431  is also a good equipment

X431 iDiag accessories have DBScar adapter, Auxiliary connector, Password envelope Protective casing(optional).In the following, it would use x431 iDiag for IPAD as an example, in order to better familiar with X431 idiag.

iPad protective casing:

DBScar adapter:  

Place the connector in its place on the back of the protective casing when it is no in use. See the process as shown below.

iPad installation :

Put the iPad into protective casing. Follow the process shown in following picture to complete the installation:

DBScar adapter connection:

Find out the vehicle’s DLC socket, plug DBScar adapter into DLC socket and the DBScar adapter power indicator will light up.

Note: vehicle’s DLC socket is generally located on drive’s side, about 12 inches away from the center of dashboard, see the picture.If you can’t find it, please refer to vehicle’s repair manual.

Source : http://www.worldobd2.com/