ELM 327 OBDII troubles
I was wondering if anyone had any experience with OBD II and the torque app for android. I received an ELM327 as a stocking stuffer so I thought I would test it out. I have had a cracked emission line so I thought I would repair the line and then clear the codes out with the ELM.
So I plugged the ELM in and found the emission codes, swapped out the correct hose and started the D back up. I used the clear codes command and nothing happened with the check engine light though the torque app no longer showed any codes pending. I thought maybe I needed to restart the D so I turned it off and then went to start it up again.
Nothing. The engine cranked but would not start. As dread started to creep in, I thought maybe I had bricked my Durango like some cell phone hack. It would crank away but would not catch. Slowly I could smell gas and checked the exhaust which had black oil specks on the pavement.
So I tried a computer reset by pulling the negative cable. After doing that, and another round of cranking, the engine barely started and sounded horrible for about 30 seconds and then like magic ran like normal.
What gives? This is my first time playing with a OBDII but it doesn't seem like a consumer device like this should allow me the mess up the truck so badly. Could I have some other issue with my bus that is causing the problem?
So I plugged the ELM in and found the emission codes, swapped out the correct hose and started the D back up. I used the clear codes command and nothing happened with the check engine light though the torque app no longer showed any codes pending. I thought maybe I needed to restart the D so I turned it off and then went to start it up again.
Nothing. The engine cranked but would not start. As dread started to creep in, I thought maybe I had bricked my Durango like some cell phone hack. It would crank away but would not catch. Slowly I could smell gas and checked the exhaust which had black oil specks on the pavement.
So I tried a computer reset by pulling the negative cable. After doing that, and another round of cranking, the engine barely started and sounded horrible for about 30 seconds and then like magic ran like normal.
What gives? This is my first time playing with a OBDII but it doesn't seem like a consumer device like this should allow me the mess up the truck so badly. Could I have some other issue with my bus that is causing the problem?
I use the torque app and have some $20 bluetooth obd II adapter from ebay (not sure of the model) and haven't had any issues with it. I'm not positive, but I think I remember that the codes would only clear while the engine is off, but the key is turned to run.
if you cleared the codes w/ the engine running i am willing to bet that is your problem, you are supposed to clear the codes with the key on and the engine OFF, not doing so can cause problems w/ the engine controller and all sorts of issues, give it another try following the proper procedre and see if it happens again .
if you cleared the codes w/ the engine running i am willing oldto bet that is your problem, you are supposed to clear the codes with the key on and the engine OFF, not doing so can cause problems w/ the engine controller and all sorts of issues, give it another try following the proper procedre and see if it happens again .









