Received mine today.
The blue one, Mini ELM327 V2.1 with the famous MAC address.
Tested 6 software on my Android, 4 aren't working at all (not detecting dongle, or after a few trys fail at connecting), EOBD Easy almost connects to dongle then fail, and OBD Car Doctor seems to have no problem.
I'd be interested in having some more proofs of the danger I am in using this thing in my car, because for now there's only 2 persons, 1 that had resolved problem by removing the dongle, and the other had a "check engine" signal on dashboard.
At around 5$ I guess that there are thousands of this thing all over the planet, and I'm not saying that all this post is BS, just that it would be more usefull with proofs that it's that bad.
For now I'm quite afraid so I don't think that I'll use it each time I take my car, so I'm making some more researches lol.
I have a ELM 327 2.1 with mac adress 00:18:56:AE:08. And i can't connect it with my Opel Corsa C 1,2. I was able to connect it once, but now it seems it is not working anymore. I used torque pro. Thank you.
Fake Bluetooth OBD2 - MAC 66:35:56:78:90:AB
Shows Pair OK with pairing code 1234, and no further BT connection.
MAC 66:35:56 does not belong to any registered vendor/manufacturer.
Just smash it and don't waste time on it.
I plugged in a ELM327 v1.5 bluetooth bought from ebay last week. seller is from uk, atcwave
On my 2003 peugeot 2.0i it seems to have caused major damage! It looks like my BSI module has been damaged. The dashboard has gone crazy, nothing functions anymore, the car does not start. All attempts to reset the BSI have been futile. Will have to go to dealer with this problem. Watch out with this cheap chinese crap!!
I'm using this bluetooth adapter:
http://www.amazon.co.uk/ gp/product/B00UR5BRZU?psc=1&redirect=true&ref_=oh_aui_detailpage_o02_s00
and it is working fine on a BMW 3 series 2010 model. The MAC address is AA:BB:CC:11:22:33. More expensive than some adapters but it had good reviews so worthwhile. It connects with no difficulty and all functions seem to work. I upgraded to OBD Car Doctor Pro which works very well.
I'm using this bluetooth adapter:
http://www.amazon.co.uk/ gp/product/B00UR5BRZU?psc=1&redirect=true&ref_=oh_aui_detailpage_o02_s00
and it is working fine on a BMW 3 series 2010 model. The MAC address is AA:BB:CC:11:22:33. More expensive than some adapters but it had good reviews so worthwhile. It connects with no difficulty and all functions seem to work. I upgraded to OBD InCarDoc Pro which works very well.
The pointed adapter marked as "V1.5" and this a good sign, while faked MAC address pointing to some "hidden factory" 😉
I bought 2. First one is here, not impressed. Connection to adapter, yes. To ECU, no. Adapter error count 0 other faults 1. Obviously it's not communicating from the EUC to phone. To be fair I tried 2 cars. I'll post back when the other one comes.
I bought 2 of the same adapter as the previous poster from ebay. Neither one works. Both show a MAC of 00:00:00:00:00:01
They connect to the program and say elm327 v2.1 then freeze. I opened one up and it has no elm327 chip. Instead it has a MCP chip, completely fake.
I bought 2. First one is here, not impressed. Connection to adapter, yes. To ECU, no. Adapter error count 0 other faults 1. Obviously it's not communicating from the EUC to phone. To be fair I tried 2 cars. I'll post back when the other one comes.
Second one came, same thing. Would not communicate to the ECU. Back to Aliexpress, look for another vendor with better feedback. Ordered 2 from there http://www.aliexpress.com/item/Universal-OBD-V2-1-ELM327-OBD2-Bluetooth-Auto-Scanner-OBDII-2-Car-ELM-327-Tester-Diagnostic/1578466645.html garbage. 0 for 4. On a different forum, nothing to do with this, asked if anyone was running torque pro and which adapter. http://www.bafxpro.com/ obdreader/ You can get them on Amazon for around $19. Ordered 2, paired right up, made sure settings were correct, BAM! Talking to the ECU. The seller of the counterfeit ones try to make you feel bad and stupid, but your not. The BAFX sells around $24 in general. https://www.scantool.net/scan-tools/smart-phone/obdlink-lx.html was also recommended, but has a price tag of $70.
Please note that issue could be not only with the adapter. The other possible reasons could be:
- car does not support OBD-II standard
- broken signal wire connection in socked
- engine not started
- issues with BT connection
- etc
You cold send us the log(s) with connection sessions, it might give at least some tips on the issue:
- switch off then on Bluetooth in phone
- plug off - on adapter
- turn on debug on page Menu-Configuration-Logging
- try to connect
then send log from the Menu-Configuration-Logging with issue and car details including year in letter.
Thanks
Sure, and I have swamp land to sell. I got off the notion of buying the adapter from China to get one promised to work. It did. $20 vs $5. I was 0 for 4. Now 2 for 2 with the BAFX. You'll help to confuse people with making excuses why the ECU doesn't connect because of blaa blaa blaa. The unit is pretty self explanatory.
Help, I purchased a bluetooth obd2 scanner for my 2000 Chevy C3500. http://www.amazon.com/gp/product/B011NSX27A?psc=1&redirect=true&ref_=oh_aui_detailpage_o00_s00
It connected fine and was reading the sensors and sending info, so I decided to put it in drive and see how the app "Torque Lite" responded. My truck went about ten feet, then all the electronics and engine died as it coasted to the side of the road. For a little while there was light indicating it was in park when the key was in ACC and a clicking sound coming from under the dash deep above and behind the brake pedal. I disconnected the battery to reset the computer but that changed nothing. What could this little obd2 scanner have done to completely shut down my truck?
Anyways I gave that thing a one star review, but I am sure they will just rebrand the same piece o crap. Any help on this would be greatly appreciated.
Well I figured out the clicking is coming from the buzzer, I guess it is not getting enough electricity to fully beep because the cab lights are looking pretty dim as well. Wondering if it is a bad ground or what, right now I am just like WTF is up with this truck. Battery measured at 12.45 V.
Please note that issue could be not only with the adapter. The other possible reasons could be:
- car does not support OBD-II standard
- broken signal wire connection in socked
- engine not started
- issues with BT connection
- etc
You cold send us the log(s) with connection sessions, it might give at least some tips on the issue:
- switch off then on Bluetooth in phone
- plug off - on adapter
- turn on debug on page Menu-Configuration-Logging
- try to connect
then send log from the Menu-Configuration-Logging with issue and car details including year in letter.
Thanks
Nope, cheap counterfeit. I ordered 2 BAFX http://www.bafxpro.com/ obdreader/ hooked up no problem. Paired to phone, communicated to the module, ECU reported back to the phone torque pro.
Hi Guys!
I've bought cheap ELM V2.1 from:
http://allegro.pl/interfejs-elm-327-bluetooth-v2-1-ulepszony-i5625431644.html
sorry, but page is in polish...
Anyway I was able to pair with my phone and I was able to read out some data from sensors, but I wasn't able to read out error codes. Any idea why? It could be caused by wrong address?
I can't read out address, because my car is in service now...
Thanks in advice!
