Post by sdmatt on Jan 14, 2018 20:45:23 GMT
I received my device yesterday. I watched many youtube videos, read online forums ahead of time to properly do some modifications to my car using OBDeleven. Needless to say, I think I killed my car or least perhaps I have done some serious damage. Here's what I did that has lead to my MK7 being completely inoperable.
I plugged the OBDeleven into the port, fired up the app on my phone, created the user account, etc. I then turned on the car, just the ignition, I didn't start the engine. The app connected and prompted me to select my vehicle type/model. I first ran a scan of everything. A few minor errors came up mostly because the engine wasn't running and it couldn't check some things. I then went into the OBDEleven Apps and selected to turn on the remote window feature. It accepted and I saw the feature available on the Infotainment screen and I turned it on to all windows. AWESOME!
Then, while looking at other Apps, I decided being able to turn off DRL's would be nice. I went into the app to change it and held down the apply green checkbox and got an error "battery voltage is low Ensure battery charger is connected and try again." Odd, I had been connected with the car switched on for maybe 10-15 minutes at most. While Googling to figure out what this error meant, the car started to go absolutely BONKERS haywire. Ton's of warnings and chimes, basically EVERYTHING had an error, message Brakes, Airbag, Driver side door sensor, etc. Then all dash gage lights and screens were flickering on and off. I immediately turned off the car, logged out of the app and unplugged the OBDEleven. I then tried to start the car and I immediately noticed the brake pedal felt very firm and I couldn't really depress it much. I went ahead and pressed the start button with my foot on the brake, there was a bunch of clicking from under the hood and a ton of errors coming up, along with lots of chimes and warning beeps. And the engine did not start!!
The only thing I later saw that I thought may have caused incorrect coding to kill my car is that the OBDeleven app may have coded itself to be a 2015 Golf GTI Sportwagon instead of a 2015 Golf. Not sure if the coding is that drastically different between various models to cause such a mess.
I'm planning to have my car towed to VW first thing tomorrow morning to have them take a look at it. How big of a chance is there that I've caused $$$$ in damage? Anyone else screw up their Golf doing coding to the point it was "bricked"? Fingers crossed the dealer service dept. can recode everything and it won't cost me an arm and leg replacing the computer, sensors, etc.
Thanks!
I plugged the OBDeleven into the port, fired up the app on my phone, created the user account, etc. I then turned on the car, just the ignition, I didn't start the engine. The app connected and prompted me to select my vehicle type/model. I first ran a scan of everything. A few minor errors came up mostly because the engine wasn't running and it couldn't check some things. I then went into the OBDEleven Apps and selected to turn on the remote window feature. It accepted and I saw the feature available on the Infotainment screen and I turned it on to all windows. AWESOME!
Then, while looking at other Apps, I decided being able to turn off DRL's would be nice. I went into the app to change it and held down the apply green checkbox and got an error "battery voltage is low Ensure battery charger is connected and try again." Odd, I had been connected with the car switched on for maybe 10-15 minutes at most. While Googling to figure out what this error meant, the car started to go absolutely BONKERS haywire. Ton's of warnings and chimes, basically EVERYTHING had an error, message Brakes, Airbag, Driver side door sensor, etc. Then all dash gage lights and screens were flickering on and off. I immediately turned off the car, logged out of the app and unplugged the OBDEleven. I then tried to start the car and I immediately noticed the brake pedal felt very firm and I couldn't really depress it much. I went ahead and pressed the start button with my foot on the brake, there was a bunch of clicking from under the hood and a ton of errors coming up, along with lots of chimes and warning beeps. And the engine did not start!!
The only thing I later saw that I thought may have caused incorrect coding to kill my car is that the OBDeleven app may have coded itself to be a 2015 Golf GTI Sportwagon instead of a 2015 Golf. Not sure if the coding is that drastically different between various models to cause such a mess.
I'm planning to have my car towed to VW first thing tomorrow morning to have them take a look at it. How big of a chance is there that I've caused $$$$ in damage? Anyone else screw up their Golf doing coding to the point it was "bricked"? Fingers crossed the dealer service dept. can recode everything and it won't cost me an arm and leg replacing the computer, sensors, etc.
Thanks!