Multiecuscan

pardon me, i know this has been posted so many times ..tried searched, but more i read, more confused i am getting

try all the procedures ..

COMMAND: ATZ
RESPONSE: ?

>

COMMAND: ATI
RESPONSE: ?

>

COMMAND: ATE0
RESPONSE:

ELM327 v1.5

>

COMMAND: ATL0
RESPONSE: ATL0

OK

>

COMMAND: ATH0
RESPONSE: ATH0

OK

>

COMMAND: ATSPC
RESPONSE: ATSPC

OK

>

COMMAND: ATS0
RESPONSE: ATS0

OK

>

COMMAND: ATCAF0
RESPONSE: ATCAF0

OK

>

COMMAND: ATCFC0
RESPONSE: ATCFC0

OK

>

COMMAND: ATCRA 7B0
RESPONSE: ATCRA 7B0

OK

>

COMMAND: ATSH 7B0
RESPONSE: ATSH 7B0

OK

>

COMMAND: ATAT1
RESPONSE: ATAT1

OK

>

COMMAND: ATST41
RESPONSE: ATST41

OK

>

COMMAND: ATBI
RESPONSE: ATBI

OK

>

WARNING: This interface is not compatible with ELM 327 1.3! Will not connect to any CAN module.
a

can someone comment if this is indeed the mini Bluetooth's issue?
but why i saw some members saying 1.5 should work as well ..

there is a suitable driver for the "bluetooth serial port"?? CDW driver is not compatible .. it's USB to console ..XD

Hello

Yes this has been written many times

The few v1.5 work with MES has to do with it
Some vendors have a version between v1.4 to v1.5 on the chip
In the interface. And this was the beginning with MES
Following v1.5 versions.

Once again for all who read this here

As soon as the interface shows the test

"WARNING: This interface is not compatible with ELM 327 1.3! Will not connect to any CAN module."

There is no way to make any modification of resistors to make this ELM compatible with MES.

And you have to buy a different interface.

Greeting Eddy