Connection failed using Bluetooth ELM327 v2.1

[kipper]

Hi,

I have a 2013 Alfa Romeo Giulietta JTDM2 170 and receive the error Connection Failed when I try to connect to any modules.

When I pair the dongle to my Android mobile various ODB apps seem to work.
I have also installed AlfaODB and connected to an engine module, this module cannot be connected to using MES.

Multi Ecu Scan support came back with the following but haven't responded to any further emails:
"I checked the report and it seems that everything is ok with the configuration of the interface and the communication between Multiecuscan and the interface. The problem seems to be in the electrical connection. Please check if the interface is fully inserted into the OBD port (without any additional adapter cables) and make sure that the car key is switched to ON/MAR position."

I am using the following ELM327 Bluetooth adapter and the registered version of Multi Ecu Scan, v4.4 I think installed on Windows 10.
https://www.amazon.co.uk/TONWON-Scanner-Bluetooth-Reader-Android/dp/B06ZZZSH48/ref=sr_1_1?keywords=tonwon&qid=1553685911&s=gateway&sr=8-1


The interface settings are as follows:

Interface Type:

ELM 327 1.3/1.4/1.4b/2.1 (Bluetooth)

Serial port:

COM4 (Standard serial over bluetooth link)

115200



The interface tests look successful showing ok for all items:

First message displays the following, the second message is similar except ATI

Command: ATZ

RESPONSE: ATZELM327 v2.1

The last message displays the following "the interface is compatible with ELM327 1.4! should connect properly with all can modules”


ELM327 FG identifier gave the following results using com3 and a baud rate of 500000:

Supported commands:

1.0 : AT @1 --> OK
1.0 : AT AL --> OK
1.0 : AT BD --> OK
1.0 : AT CAF0 --> OK
1.0 : AT CAF1 --> OK
1.0 : AT CF 00 00 00 11 --> OK
1.0 : AT CF 111 --> OK
1.0 : AT CFC0 --> OK
1.0 : AT CFC1 --> OK
1.0 : AT CM 00 00 00 11 --> OK
1.0 : AT CM 111 --> OK
1.0 : AT CP 15 --> OK
1.0 : AT CS --> OK
1.0 : AT CV 1200 --> OK
1.0 : AT D --> OK
1.0 : AT DP --> OK
1.0 : AT DPN --> OK
1.0 : AT E0 --> OK
1.0 : AT E1 --> OK
1.0 : AT H0 --> OK
1.0 : AT H1 --> OK
1.0 : AT I --> OK
1.0 : AT IB 10 --> OK
1.0 : AT IB 96 --> OK
1.0 : AT L0 --> OK
1.0 : AT L1 --> OK
1.0 : AT M0 --> OK
1.0 : AT M1 --> OK
1.0 : AT NL --> OK
1.0 : AT PC --> OK
1.0 : AT R0 --> OK
1.0 : AT R1 --> OK
1.0 : AT RV --> OK
1.0 : AT SH 6A0 --> OK
1.0 : AT SH A595F2 --> OK
1.0 : AT SP 0 --> OK
1.0 : AT SP A0 --> OK
1.0 : AT SP0 --> OK
1.0 : AT ST 32 --> OK
1.0 : AT SW 92 --> OK
1.0 : AT TP 0 --> OK
1.0 : AT TP A0 --> OK
1.0 : AT WM C133F13E --> OK
1.0 : AT WM C133F13E00 --> OK
1.0 : AT WM C133F13E0000 --> OK
1.0 : AT WM FF --> OK
1.0 : AT WS --> OK
1.0 : AT Z --> OK
1.1 : AT FC SD 0430FF00 --> OK
1.1 : AT FC SH 000007B0 --> OK
1.1 : AT FC SH 7B0 --> OK
1.1 : AT PP 07 OFF --> OK
1.1 : AT PP 07 ON --> OK
1.1 : AT PP 07 SV 09 --> OK
1.1 : AT PPS --> OK
1.2 : AT AR --> OK
1.2 : AT AT0 --> OK
1.2 : AT AT1 --> OK
1.2 : AT AT2 --> OK
1.2 : AT BRT 0F --> OK
1.2 : AT IFR H --> OK
1.2 : AT IFR S --> OK
1.2 : AT IFR0 --> OK
1.2 : AT IFR1 --> OK
1.2 : AT IFR2 --> OK
1.2 : AT IIA 7A --> OK
1.2 : AT KW0 --> OK
1.2 : AT KW1 --> OK
1.2 : AT WM C133F13E --> OK
1.3: AT D1 --> OK
1.3: AT D0 --> OK
1.3: AT KW --> OK
1.3: AT AR --> OK
1.3: AT JS --> OK
1.3: AT S0 --> OK
1.3: AT RA 45 --> OK
1.3: AT S1 --> OK
1.3: AT JE --> OK
1.3: AT V1 --> OK
1.3: AT CRA 000007C0 --> OK
1.3: AT CRA 7C0 --> OK
1.3: AT V0 --> OK
1.3a: AT FE --> OK
1.4 : AT CEA --> OK
1.4 : AT CEA 04 --> OK
1.4 : AT CV 0000 --> OK
1.4 : AT FI --> OK
1.4 : AT IB 48 --> OK
1.4 : AT IGN --> OK
1.4 : AT RD --> OK
1.4 : AT SD FF --> OK
1.4 : AT SI --> OK
1.4 : AT SP3 --> OK
1.4 : AT SP5 --> OK
1.4 : AT SS --> OK
1.4b: AT CRA --> OK
1.4b: AT CSM0 --> OK
1.4b: AT CSM1 --> OK
1.4b: AT JHF0 --> OK
1.4b: AT JHF1 --> OK
1.4b: AT JTM1 --> OK
1.4b: AT JTM5 --> OK
2.0 : AT AMC --> OK
2.0 : AT AMT 20 --> OK
2.0 : AT SH 00 00 07 E0 --> OK
2.1 : AT CTM1 --> OK
2.1 : AT CTM5 --> OK

Unsupported commands:

1.0 : --> KO
2.2 : AT CER F1 --> KO
2.2 : AT IB 12 --> KO
2.2 : AT IB 15 --> KO
2.2 : AT IFR4 --> KO
2.2 : AT IFR5 --> KO
2.2 : AT IFR6 --> KO

Device Manager on the pc shows two com ports being used:
Com3:
Incoming
Android-Vlink
Com4:
Outgoing
Android V-link 'SPP Dev'

Hopefully someone can help shed some light on this, do I just send the Dongle back and try another, if so are there any reasonably priced bluetooth ODB adapters that are know to work?

Thanks,
Kip

[sam7376]

I'm sorry to hear that your connection failed. I will say this though, I had a similar issue with my ELM327 connection. Doing this fixed the issue. I scanned for interfaces before connecting, and once the interface scan was performed and one was found I was ok to proceed with a connection. It was a successful connection. I hope this helps.

[kipper]

Hey Sam,

Thanks for your reply.

Following trying about 4 Bluetooth adapters including ones sold as working with MES from UK sellers I actually gave up and purchased a set of cables which worked.
The only problem I had with the cables was one set of instructions said to use the yellow cable and another said to use green, all good now though:)

[s130]

Personally I've not used Bluetooth to connect to any vehicle and would shy away from doing so if making changes like Proxi, Key Programming, etc. For such functions you need a reliable, stable and repeatable connection and for me direct cable connection is the only way to go.

An exception to this would be if I was using expensive diagnostic kit from the likes of Snap-On, Fiat WiiTech, etc. where one is spending £550 to £1000+ and hopefully the manufacturer has thoroughly ensured that their diagnostic unit and bluetooth modules are bullet proof.

Another exception would be if I just want to monitor certain parameters whilst driving around where any loss of data or error is not of importance.