feregetmy.blogg.se

Scanmaster elm unable to connect error 43
Scanmaster elm unable to connect error 43












scanmaster elm unable to connect error 43
  1. Scanmaster elm unable to connect error 43 driver#
  2. Scanmaster elm unable to connect error 43 full#
  3. Scanmaster elm unable to connect error 43 android#
  4. Scanmaster elm unable to connect error 43 code#
  5. Scanmaster elm unable to connect error 43 Bluetooth#

I have come across the GM single wire issue while researching. The other busses allow for simple discrete transceivers, but the CAN uses an MCP2551 etc type chip for the interface between obd port and elm327 chip.

Scanmaster elm unable to connect error 43 Bluetooth#

There seems to be a potential here that the CAN problems on these bluetooth devices stems from incomplete implementation on the 3rd bus. The chip deals with all the obd protocols via 3 physical and isolated busses: I've just been looking over some datasheets on the el327p IC (genuine Elm Devices) and example application. " If you can, try manually select a can protocol (11bit or 29bit) and see how you go." - Oh god how many times and variations I tried already. This might prove something or at least give me a chance to. The seller is sending a new identical unit for me to try. Thanks Tazzi, all your efforts are much appreciated.

scanmaster elm unable to connect error 43

I also recommend getting a USB version :beer chug:

Scanmaster elm unable to connect error 43 full#

Hope that sort of helped! Your best bet is to just try a whole bunch of "trial" paid software and see which one works for you before full purchase. I know the above from personally developing my own obd2 software for monitoring the bus, and a few that tried it with CAN protocol came up with that error until I made appropriate changes! If I had enough support/testers, I could get a CAN compliant app for the VZ's off the ground alot faster!

scanmaster elm unable to connect error 43

although generally only smart developers implement this. This error can be switched off with the correct commands to the elm. The ELM devices will throw a "DATA ERROR" fault as the CAN frames are structured differently thus alot of softwares fail when seeing the error. If you can, try manually select a can protocol (11bit or 29bit) and see how you go.Īlso, good old GM made the CAN communication a little unordinary. By the sounds of it, the apps are trying to use the *auto detect* feature and they are getting nothing back. They can *auto detect* the protocol most of the time, but sometimes they fail or choose the wrong one. But as you said, all systems speak over ALDL except for the PCM (ecu). In saying that, your VZ commodore will speak over CAN protocol and ALDL. These places are making deals with scantool providers like so that they can both profit significantly instead of the little asian sales man. But I told you so!.Īlot of softwares are starting to "prevent" these cheap cables fro working. Anyone have a clue?Ĭlick to expand.*sigh*. I understand that most of the systems are still ALDL in the VZ but not the ECU. Why does the unit work flawlessly on the Astra but not the VZ? Why? The dumbay seller says the commo is not obd2 compliant, I tried to explain otherwise, but whatever. The unit works perfectly on a 2003 Holden Astra using any of the apps.

Scanmaster elm unable to connect error 43 code#

The torque app is different, it just keeps asking for the pairing code and then fails. When an app is launched and asked to connect, it does and then starts an auto process of testing all the obd2 protocols but ends up saying things like "Cannot connect to ECU" etc. The adaptor is found and paired easily on either of the droids.

Scanmaster elm unable to connect error 43 android#

I tried it with Torque, Car doctor, scanmaster and a couple of other apps on two different android units. I thought the unit may be faulty, but it turns out it isn't. but there were enough good luck stories around to persuade me to take a punt on one of these cheapies. I know, I know I should have listened etc. Update, I just catched that moment when is connecting to the service mode the after 2 secs then jumping back to the main menu ( RAA wroted ( viewtopic.OK, so I bought a mini bluetooth elm327 on feebay. I tried on Fiat Doblo Family 1.9JTD Multijet type 223. Or maybe this cable is a cheap clone and this is why its wont running in service? The seller should change it, but maybe will be the same. but i tried without key, key is on, with engine running. What i did wrong? Cable connect to car connector, then to laptop`s usb, multiecuscan start, key is on without engine running. But the service menu is important for me and its not connecting, i uploaded a video about this: įrom the hundreds try maybe once or twice its connected to the service then after 2 secs its jumped back to the main menu. I know need different cable for the airbags, but i wont touch that at the moment.

Scanmaster elm unable to connect error 43 driver#

1497.l2649), it says ver 1.4, cable test, interface, driver looks ok, engine connection ok, but nothing else, i just did an oil change what is worked, so I can reach and connect to engine only. I just bought a licensed multiecuscan and one elm 327 usb cable from ebay (. Hello guys, im newby here, million thanks for yani & for everybody who support this site/program/share the info etc.














Scanmaster elm unable to connect error 43