FAULTY ELM 327 INTERFACES DE-MYSTIFIED (READ HERE)
Re: FAULTY ELM 327 INTERFACES DE-MYSTIFIED (READ HERE)
Hi Tony
I've marked the resistor of prevented the CAN bus protocol with MES with a red frame.
But this interface is also back at least 15 times described here.
Greeting Eddy
I've marked the resistor of prevented the CAN bus protocol with MES with a red frame.
But this interface is also back at least 15 times described here.
Greeting Eddy
Re: FAULTY ELM 327 INTERFACES DE-MYSTIFIED (READ HERE)
So just remove the resistance and work ?
Re: FAULTY ELM 327 INTERFACES DE-MYSTIFIED (READ HERE)
Yes , you must remove an Resistor not Resistance
Greetings Eddy
Greetings Eddy
Re: FAULTY ELM 327 INTERFACES DE-MYSTIFIED (READ HERE)
it worked perfectly .
Thanks so much Eddy
But it would be better to create an index with all the pictures of the cards and the changes to be made ?
because they find the information in 156 pages is very difficult
Thanks so much Eddy
But it would be better to create an index with all the pictures of the cards and the changes to be made ?
because they find the information in 156 pages is very difficult
Re: FAULTY ELM 327 INTERFACES DE-MYSTIFIED (READ HERE)
Tony Evo wrote:it worked perfectly .
Thanks so much Eddy
But it would be better to create an index with all the pictures of the cards and the changes to be made ?
because they find the information in 156 pages is very difficult
Hi Tony
For that reason I give this help yes
Gruß Eddy
Re: FAULTY ELM 327 INTERFACES DE-MYSTIFIED (READ HERE)
Hi guys,
watching all the others PCBs posted I realized that the resistor to be removed is always the one jumping the pin 6 and pin 7 of the 8-pin-micro (i don't get to see the serial). So, I removed the resistor R27 (I don't if that was the one to be removed), but the device is doing the same.
I plug the Bluetooth Elm327 device to the diagnosis outlet, all the leds blink for a second and after that, the red led stays on. The phone or the PC pairs with the ELM really fast. The thing is that it doesn't get to communicate with the ECU. When the sofwares/apps attempt to connect to ECU the green and yellow leds start to blink, but nothing happens. With some apps like Torque, the green and yellow leds blink (when attemping to connect to ECU) until I close de app, then these leds go off and the red one stays on. With other softwares/apps the green and yellow leds blink for a while and then they get static (like the device stops working), so I have to unplug it and plug it back again.
I've used 15 apps for android and not even one connect to ECU. All the apps and softwares connect with the device but not one connect to ECU. I've used 5 softwares with my PC and only the Scanmaster get to "connect". It says "Connected: Protocol not known" and it doesn't work properly. I get strange codes like ERROR B10E2.
I would like to get some extra information based on your experience with these devices. Maybe I should stop trying or maybe I'm doing something wrong.
I don't know if I should let the device just like it is right now or if I should weld the resistor back.
Anyway guys, hope you can help me.
Thanks for your time and help!
Cheers!
PD: Forgot to mention that my car is a 2002 Daewoo Tacuma or Daewoo Rezzo (I know the information on this forum is for Fiat, VW, Alfa R...etc, but I'm kind of desperated).
watching all the others PCBs posted I realized that the resistor to be removed is always the one jumping the pin 6 and pin 7 of the 8-pin-micro (i don't get to see the serial). So, I removed the resistor R27 (I don't if that was the one to be removed), but the device is doing the same.
I plug the Bluetooth Elm327 device to the diagnosis outlet, all the leds blink for a second and after that, the red led stays on. The phone or the PC pairs with the ELM really fast. The thing is that it doesn't get to communicate with the ECU. When the sofwares/apps attempt to connect to ECU the green and yellow leds start to blink, but nothing happens. With some apps like Torque, the green and yellow leds blink (when attemping to connect to ECU) until I close de app, then these leds go off and the red one stays on. With other softwares/apps the green and yellow leds blink for a while and then they get static (like the device stops working), so I have to unplug it and plug it back again.
I've used 15 apps for android and not even one connect to ECU. All the apps and softwares connect with the device but not one connect to ECU. I've used 5 softwares with my PC and only the Scanmaster get to "connect". It says "Connected: Protocol not known" and it doesn't work properly. I get strange codes like ERROR B10E2.
I would like to get some extra information based on your experience with these devices. Maybe I should stop trying or maybe I'm doing something wrong.
I don't know if I should let the device just like it is right now or if I should weld the resistor back.
Anyway guys, hope you can help me.
Thanks for your time and help!
Cheers!
PD: Forgot to mention that my car is a 2002 Daewoo Tacuma or Daewoo Rezzo (I know the information on this forum is for Fiat, VW, Alfa R...etc, but I'm kind of desperated).
Re: FAULTY ELM 327 INTERFACES DE-MYSTIFIED (READ HERE)
wasuky wrote:Hi guys,
watching all the others PCBs posted I realized that the resistor to be removed is always the one jumping the pin 6 and pin 7 of the 8-pin-micro (i don't get to see the serial). So, I removed the resistor R27 (I don't if that was the one to be removed), but the device is doing the same.
I plug the Bluetooth Elm327 device to the diagnosis outlet, all the leds blink for a second and after that, the red led stays on. The phone or the PC pairs with the ELM really fast. The thing is that it doesn't get to communicate with the ECU. When the sofwares/apps attempt to connect to ECU the green and yellow leds start to blink, but nothing happens. With some apps like Torque, the green and yellow leds blink (when attemping to connect to ECU) until I close de app, then these leds go off and the red one stays on. With other softwares/apps the green and yellow leds blink for a while and then they get static (like the device stops working), so I have to unplug it and plug it back again.
I've used 15 apps for android and not even one connect to ECU. All the apps and softwares connect with the device but not one connect to ECU. I've used 5 softwares with my PC and only the Scanmaster get to "connect". It says "Connected: Protocol not known" and it doesn't work properly. I get strange codes like ERROR B10E2.
I would like to get some extra information based on your experience with these devices. Maybe I should stop trying or maybe I'm doing something wrong.
I don't know if I should let the device just like it is right now or if I should weld the resistor back.
Anyway guys, hope you can help me.
Thanks for your time and help!
Cheers!
PD: Forgot to mention that my car is a 2002 Daewoo Tacuma or Daewoo Rezzo (I know the information on this forum is for Fiat, VW, Alfa R...etc, but I'm kind of desperated).
Hello Wasuky
As you have correctly identified it is not about daewoo cars
Also not a VW or so
But the diagnostic software Multiecuscan
Any attempts to remove your a resistor use all nothing
Because with MES do not you come to the engine control unit of your daewoo
Greeting Eddy
Re: FAULTY ELM 327 INTERFACES DE-MYSTIFIED (READ HERE)
hi
I have a problem with ELM 327 Bluetooth which i've bought via Aliexpress. Interface can connect and works with Torque apk on Android, but it can't connect with AlfaOBD Demo. Interface is visible in application, but there is no way to connect with any ECU in my car (Stilo m-JTD 120 HP). All i can see is information - "setting environment, please wait...", but after few minutes nothing happens.
I try the same with Multiecuscan 2.2 Free on my notebook. Bluetooth dongle device recognize the interface OBDII. so i open MES and in "Options" section i try to scan for interface but i found nothing. My interface looks like below:
Can anybody help me?
I have a problem with ELM 327 Bluetooth which i've bought via Aliexpress. Interface can connect and works with Torque apk on Android, but it can't connect with AlfaOBD Demo. Interface is visible in application, but there is no way to connect with any ECU in my car (Stilo m-JTD 120 HP). All i can see is information - "setting environment, please wait...", but after few minutes nothing happens.
I try the same with Multiecuscan 2.2 Free on my notebook. Bluetooth dongle device recognize the interface OBDII. so i open MES and in "Options" section i try to scan for interface but i found nothing. My interface looks like below:
Can anybody help me?
Re: FAULTY ELM 327 INTERFACES DE-MYSTIFIED (READ HERE)
Hello Boch
Go to page 146 since the interface is described.
EddyDj has the same interface as you and has the
Resistors removed.
Greeting Eddy
Go to page 146 since the interface is described.
EddyDj has the same interface as you and has the
Resistors removed.
Greeting Eddy
Re: FAULTY ELM 327 INTERFACES DE-MYSTIFIED (READ HERE)
Thanks Alfaeddy I saw this thread before, but... there is important differance between me and EddyDJ. EddyDj had no problems with connecting to engine controller via non modyfied ELM 327 interface. He had a problem with connecting to other modules (CAN network i think). in my case there is a general problem - i can't even connect to engine ECU. as i sad before, Torque works fine.