Technical OBD II readers

Currently reading:
Technical OBD II readers

TourquePro, from here and a bluetooth adaptor.

screenshotai.jpg
 
This post contains affiliate links which may earn a commission at no additional cost to you.
This post contains affiliate links which may earn a commission at no additional cost to you.
I think that with an engine light fault, the lesser readers will probably not produce a code but will allow you to erase codes which can be helpful and if you do get a reader that will give you a code these are not completely helpful. There are many, many posts on the engine light subject and the possible causes identified given the inconclusive nature of codes in the first place and they way people describe their faults on this forum. This can lead to confusion
It all depends on when you light comes on and goes off or if it stays on all the time. The likely faults are: 1. The boost control valve; the EGR is bunged up with soot and the solenoid jammed; the variable vanes in the turbo jammed with soot or hopefully not, the DPF bunged up. I have listed these in order of likelihood - the first being the most likely etc.
Although, there are a few other things that can create the light and limp to activate, these are the most likely causes of your issue.
You debate on code readers is very interesting and I can see you are taking it very seriously but I think you may be expecting too much from whichever gadget you end up with.
Regards
Stephen
 
Re: OBD II readers & 2003 Multipla

Ok I have bought an OBD2 bluetooth device that I am assured works with Smartphones and Torque. I have followed the instructions to pair my phone and the device without problem. But it will not connect to the ECU.
Does this mean my 2003 1.9JTD Multipla is not OBD2 compatible or am I doing something obviously wrong?
Not sure if this is helpful, but Torque is showing a port connection set at 35000
 
Your Multipla is OBD II compliant and it uses the ISO9141 Protocol.
Regards
Stephen
 
Re: OBD II readers & 2003 Multipla

how can you tell that your adapter works fine? you cheched in other car? usualy it's adapter fault
 
Re: OBD II readers & 2003 Multipla

In #21 I very particularly said Torque Pro not the Torque Lite, the Lite version is known to have issues with Bluetooth pairing & subsequent connectivity. Port 35000 as far as I'm aware is the internet - as in - Torque trying to connect with its parent / mothership and or GPS etc.
 
I've got an internet purchased ELM 327 bluetooth device that looks like the one below and it has always connected to my e46 328 BMW perfectly.
But on the Multipla Torque Pro says the elm is not reading the ECU
Has anyone had any luck with one of the cheap available bluetooth devices and the Multipla?
101-1003-1002_c.jpg
 
I have a similar experience but with an ELM 327 mini Bluetooth dongle.
Both Torque and Muliecuscan recognize the device but when they try to query the Multipla ecu, the time out and throw an error. The communications test in multiecuscan is all good.

The elm dongle works fine with my other car (Audi) so the little device does work.

Is suspect that my '99 petrol elx isn't perfectly obd compatible in that both multiecuscan and torque just don't understand what the multipla is spewing out.
 
Back
Top