DESPERATE! Elm327 and toyota avensis verso problems

**Illy Billy** · 08-04-2011, 12:39 PM

hi guys,

i've just bought an Elm327 bluetooth for my toyota avensis verso 2.0 D-4D diesel (54 plate - registered in 2004).

Sometimes the engine management light comes on and the car starts juddering. Most likely its an EGR valve, but i thought my own obd tool would be handy to have to quickly check for common faults.

I've managed to setup everything and the elm327 seems to be communicating fine with the laptop, but all software is reporting either that the vehicle is not communicating or that there is a compliance error.

I've definately rang many garages and they've said that my avensis should be obd2 compliant, so the only thing i can think of is either i'm not doing something right or the obd connector might be faulty. :'(

I've attached some pics, showing the type of connector and the error i get below.

PLS PLS could someone advice..thanks!

**scaryoldcortina** · 08-15-2011, 05:38 PM

Hi, I have the same module and have encountered the same setup problems.. The ELM327 is supposed to auto-detect the correct OBD protocol for the car, but I have found that some vehicles (mainly ISO, mode3) do not autodetect, so the ELM just responds with "UNABLE TO CONNECT" to all OBD commands.

My workaround was to issue command AT SPA3 at startup which forces the chip into mode 3 and only tries other protocols if mode 3 fails to initialize.

To do the commands, you need a serial terminal program (as a windows user, hyperterm is probably your best bet) set the port to whatever your adapter is connected to and baud rate/protocol to 9600,8n1.
type ATX in the window, you should get a reply "ELMscan 327 v1.4b" or similar, and a prompt. Type 0100. If it responds "UNABLE TO CONNECT" type ATSPA3 and retry. If you get a string of hex starting "41" then it worked. Close the terminal, restart your software.

hope that helps

**macarmand** · 11-09-2012, 02:39 PM

Originally Posted by scaryoldcortina

Hi, I have the same module and have encountered the same setup problems.. The ELM327 is supposed to auto-detect the correct OBD protocol for the car, but I have found that some vehicles (mainly ISO, mode3) do not autodetect, so the ELM just responds with "UNABLE TO CONNECT" to all OBD commands.

My workaround was to issue command AT SPA3 at startup which forces the chip into mode 3 and only tries other protocols if mode 3 fails to initialize.

To do the commands, you need a serial terminal program (as a windows user, hyperterm is probably your best bet) set the port to whatever your adapter is connected to and baud rate/protocol to 9600,8n1.
type ATX in the window, you should get a reply "ELMscan 327 v1.4b" or similar, and a prompt. Type 0100. If it responds "UNABLE TO CONNECT" type ATSPA3 and retry. If you get a string of hex starting "41" then it worked. Close the terminal, restart your software.

hope that helps

My ELM 327 USB-OBD 2 is not recognized my EFI LIVE. i tried what you said with the hyperterminal but i can barely enter these commands because so weird character pop on the screen in lieu of ATX.
So i don't know how you did get it to work.
Please can you give me a detail step of what window 7 hyperterminal you are using and how do you get your elm 327 to connect to EFL LIVE 7.5

**scaryoldcortina** · 11-10-2012, 09:31 AM

Originally Posted by macarmand

My ELM 327 USB-OBD 2 is not recognized my EFI LIVE. i tried what you said with the hyperterminal but i can barely enter these commands because so weird character pop on the screen in lieu of ATX.
So i don't know how you did get it to work.
Please can you give me a detail step of what window 7 hyperterminal you are using and how do you get your elm 327 to connect to EFL LIVE 7.5

wierd characters in the serial terminal is normally incorrect baud rate - try 38400 instead of 9600.

I'm not using windows, or hyperterminal - I'm using linux

but the principle is the same. If you can talk to the ELM with a serial terminal and get it to connect to the car then the problem is with the software which I can't help with, sorry)

To recap,

Set port and baud rate in hyperterm
>ATX
ELMscan 327 v1.4b
>0100
CONNECTING.....
41 xx xx xx xx
>

This is what you get if it worked. If you get COMM ERROR or ? it didn't and you should try and set the protocol manually.

I find the ELM327 datasheet 9pdf here) is very useful and well worth reading.