ELM327 Problem - Please turn ignition on

[helloSunshine]

This problem seems to be Bluetooth chip related (not ELM itselfs), and yes it appears much often exactly on new Mazda. We believe Mazda CAN network may have slightly other timings (than Ford).

I sent the log and debug trace files to your contact mail address. My impression is that this could really be an issue with Forscan for Android and the new Mazda models. I'm also participating in a Mazda community and so far I could not find anyone (!) who brought the Android version of Forscan with Bluetooth connection to work. Again, the Android version is working fine with Wifi or USB connection.

Who could recommend a - recently bought - ELM327 adapter with BT connection which works with Forscan for Android using Bluetooth and a new Mazda CX-5 or Mazda 6?

[FORScan]

sent the log and debug trace files to your contact mail address. My impression is that this could really be an issue with Forscan for Android and the new Mazda models. I'm also participating in a Mazda community and so

2 sessions in logs, on first session adapter got frozen on the first request that returned multiple data from PCM. Torque and others doesn't send such requests, FORScan uses them to identify vehicle, so we have to send them,

In the 2nd session FORScan was able to successfully identify vehile but the adapter got frozen when FORScan started to read TCM configuration.

far I could not find anyone (!) who brought the Android version of Forscan with Bluetooth connection to work. Again, the Android version is working fine with Wifi or USB connection.

We have beta testers with new Mazsa and Android+BT, with successful experience.

Who could recommend a - recently bought - ELM327 adapter with BT connection which works with Forscan for Android using Bluetooth and a new Mazda CX-5 or Mazda 6?

White-label solutions (not clone): OBDLInk MX (recomendation is available on the application page of Google Play Market)
Clones: iCar v1, iCarv2 (no serious complaints yet).

[helloSunshine]

Thanks for looking into this so quickly!

I try to get logs from the same VGATE adapter connected to a Ford car to see if it's working there.

In the meantime I also check out the iCar adapter you mentioned.

[helloSunshine]

White-label solutions (not clone): OBDLInk MX (recomendation is available on the application page of Google Play Market)
Clones: iCar v1, iCar v2 (no serious complaints yet).

I can confirm that the VGATE iCar 2 BT adapter is working fine with Forscan on Android and Mazda CX-5.

Test of the other adapter with Ford Focus is still pending.

[tompol74]

I have first device from this topic: http://forscan.org/forum/viewtopic.php?f=4&t=1091

I also have problem mentioned in the topic title. I have Ford S-Max '10. Torque and ScanMaster work fine on Android but Forescan refuse to work with that adapter. There is another Android application called Piston which also can't connect to the car.

I'll try to send you log file but not sure if I manage to do that today.

[tompol74]

Log files sent on your contact e-mail.

[tompol74]

I've checked my adapter using terminal program according to Forscan suggestion in his answere to my e-mail and my adapter is faulty. Newest version of ELM327 1.5 clone used in it doesn't support half of commands of original ELM327 as described in section #3 of following post: http://forscan.org/forum/viewtopic.php?f=4&t=1575

I will try iCar.

[martin123]

Couple of questions
1. Why test this and run with obdlink mx? It's £70!
Of all the elm327 surely there were cheaper ones.
Also, you mentioned rs232 etc.
What chip should a working adapter have if it's to work with this?