GOLFMK8
GOLFMK7
GOLFMK6
GOLFMKV

OBDELEVEN

vulticGTI

Go Kart Newbie
Location
PNW
eh, I got an RCA tablet from walmart for $35. It is certainly more convenient to use your phone verse having another tablet IMO

I would agree with that but not sure if I want to wait for iOS and the version is more expensive anyways. Wondering if my kindle fire works as android tablet hmmmm.
 

7.5

Passed Driver's Ed
Location
FL
Car(s)
2018 GTI SE, Audi S5
I’ve run into an issue with my rear parking/backup sensor. I installed a shop fan on the wall that comes on automatically when the garage door opens. So when I’m backing in I’d sometimes get the rear traffic alert because the fan was in view. Last three times it applied the brakes for me which is a big no no.

Is there a way to keep the alert from the sensors for cross traffic but disable it’s ability to apply the brakes?
 

eXult

Ready to race!
Location
Online
Car(s)
'17 GTI SE 6MT
Anyone have any idea why I would see these long coding changes in my history when I am 100% sure I have never done them myself?

---------------------------------------------------------------
Long coding
Control unit: 2B Steering Column Locking
Old value:
0101000830085900FB00002B080F00000001070000000000000000000000
New value:
5500000000000000
Mileage: 5258 km
Date: 2018-11-26 17:27

---------------------------------------------------------------
Long coding
Control unit: 29 Light Control Left
Old value:
0BAD0912A988CF0502886B095000000080000000
New value:

Mileage: 5258 km
Date: 2018-11-26 17:27

---------------------------------------------------------------
Long coding
Control unit: 17 Dash Board
Old value:
5500000000000000
New value:
0BAD0912A988CF0502886B095000000080000000
Mileage: 5258 km
Date: 2018-11-26 17:27

---------------------------------------------------------------
Long coding
Control unit: 13 Adaptive Cruise Control
Old value:
0BAD0912A988CF0502886B095000000080000000
New value:
2D00008101FFC728949C810500401600000000000000000000
Mileage: 5258 km
Date: 2018-11-26 17:27

---------------------------------------------------------------
Long coding
Control unit: 09 Central Electrics
Old value:
0400
New value:

Mileage: 5258 km
Date: 2018-11-26 17:26

---------------------------------------------------------------
Long coding
Control unit: 03 Brakes
Old value:
2D00008101FFC728949C810500401600000000000000000000
New value:
01FA6BA154280972407C020660C96880D62A90024006163610435051C089430B00000012121212B835351919323200
Mileage: 5258 km
Date: 2018-11-26 17:26

---------------------------------------------------------------
Long coding
Control unit: 2B Steering Column Locking
Old value:
5500000000000000
New value:
0101000830085900FB00002B080F00000001070000000000000000000000
Mileage: 5258 km
Date: 2018-11-26 17:25

---------------------------------------------------------------
Long coding
Control unit: 17 Dash Board
Old value:
8CCCFC00000000005000001AC24800000065
New value:
5500000000000000
Mileage: 5258 km
Date: 2018-11-26 17:25

---------------------------------------------------------------
Long coding
Control unit: 16 Steering Column Electronics
Old value:
2D00008101FFC728949C810500401600000000000000000000
New value:

Mileage: 5258 km
Date: 2018-11-26 17:24

---------------------------------------------------------------
Long coding
Control unit: 17 Dash Board
Old value:
0BAD0912A988CF0502886B095000000080000000
New value:
8CCCFC00000000005000001AC24800000065
Mileage: 5258 km
Date: 2018-11-26 17:24

---------------------------------------------------------------
Long coding
Control unit: 13 Adaptive Cruise Control
Old value:
00020004200110000000000000000006
New value:
0BAD0912A988CF0502886B095000000080000000
Mileage: 5258 km
Date: 2018-11-26 17:24

---------------------------------------------------------------
Long coding
Control unit: 16 Steering Column Electronics
Old value:
0400
New value:
2D00008101FFC728949C810500401600000000000000000000
Mileage: 5258 km
Date: 2018-11-26 17:23

---------------------------------------------------------------
Long coding
Control unit: 15 Airbag
Old value:
8CCCFC00000000005000001AC24800000065
New value:

Mileage: 5258 km
Date: 2018-11-26 17:23

---------------------------------------------------------------
Long coding
Control unit: 08 Air Conditioning
Old value:
091900122424002F1000
New value:
00020004200110000000000000000006
Mileage: 5258 km
Date: 2018-11-26 17:22

---------------------------------------------------------------
Long coding
Control unit: 13 Adaptive Cruise Control
Old value:
2D00008101FFC728949C810500401600000000000000000000
New value:
00020004200110000000000000000006
Mileage: 5258 km
Date: 2018-11-26 17:22

---------------------------------------------------------------
Long coding
Control unit: 03 Brakes
Old value:
01FA6BA154280972407C020660C96880D62A90024006163610435051C089430B00000012121212B835351919323200
New value:
2D00008101FFC728949C810500401600000000000000000000
Mileage: 5258 km
Date: 2018-11-26 17:22

---------------------------------------------------------------
Long coding
Control unit: 01 Engine
Old value:
091900122424002F1000
New value:

Mileage: 5258 km
Date: 2018-11-26 17:22

---------------------------------------------------------------
Long coding
Control unit: 08 Air Conditioning
Old value:
00020004200110000000000000000006
New value:
091900122424002F1000
Mileage: 5258 km
Date: 2018-11-26 17:22

---------------------------------------------------------------
 

Jose_Gti

Autocross Newbie
Location
Philadelphia
Did you buy your obd11 new or used?
All the coding has been done the same day of November.
 

nype

Drag Racing Champion
Location
Vancouver, B.C.
Wouldn’t Obdeleven still track changes this way, even if you used apps instead of long coding?
 

eXult

Ready to race!
Location
Online
Car(s)
'17 GTI SE 6MT
Did you buy your obd11 new or used?
All the coding has been done the same day of November.

New.

Wouldn’t Obdeleven still track changes this way, even if you used apps instead of long coding?

I've never used the apps myself. Always did the changes via Adaptations. I did make changes that same day, however I've made other modifications since and the long coding has not displayed for every one of them.

Anyone willing to grab their values for those modules and tell me so I can compare?
 

DV52

Drag Racing Champion
Location
Australia
here's a copy of my reply to your same question on the OBD11 forum:

"^^^ Please don't take offense - but I seriously doubt that those code-string changes could be made to your car and the car still works!!

Even if there were genuine attempts to make these amendments, most of the changes are impossible because the amended values impose a very different Byte count on the modules.

While I'm sure that the crazy, zany software guys/gals @ VOLTAS IT do their best to ensure that these history reports are accurate - the veracity of the information is really dependent on when the snap-shot of values is taken. For example, for VCDS, the data for the equivalent reports is locked-in just before the user presses the "Doit!" button - which is the same as the green tick in OBD11. This means that the history reports in VCDS show what the user asked the module to change - the reports don't show what actually changed! I don't know when OBD11 takes the data snap-shot for these reports - it could be the same as VCDS - perhaps if anyone from VOLTAS IT is reading this. they might respond?

What were you doing to the car @ about 1722 hours on 2018-11-26 (i.e. about 6 months ago)?

I suggest that you make a scan report of the car. Then perhaps check the code-string values on the modules in the scan report with those in the history report.

Don

Read more: http://forum.obdeleven.com/thread/6070/history-long-coding-changes-make?page=1#ixzz5pGzZo0Jx
 

eXult

Ready to race!
Location
Online
Car(s)
'17 GTI SE 6MT
here's a copy of my reply to your same question on the OBD11 forum:

"^^^ Please don't take offense - but I seriously doubt that those code-string changes could be made to your car and the car still works!!

Even if there were genuine attempts to make these amendments, most of the changes are impossible because the amended values impose a very different Byte count on the modules.

While I'm sure that the crazy, zany software guys/gals @ VOLTAS IT do their best to ensure that these history reports are accurate - the veracity of the information is really dependent on when the snap-shot of values is taken. For example, for VCDS, the data for the equivalent reports is locked-in just before the user presses the "Doit!" button - which is the same as the green tick in OBD11. This means that the history reports in VCDS show what the user asked the module to change - the reports don't show what actually changed! I don't know when OBD11 takes the data snap-shot for these reports - it could be the same as VCDS - perhaps if anyone from VOLTAS IT is reading this. they might respond?

What were you doing to the car @ about 1722 hours on 2018-11-26 (i.e. about 6 months ago)?

I suggest that you make a scan report of the car. Then perhaps check the code-string values on the modules in the scan report with those in the history report.

Don

Read more: http://forum.obdeleven.com/thread/6070/history-long-coding-changes-make?page=1#ixzz5pGzZo0Jx

Hey Don,

I appreciate your input. I'll reply to both forums so people have the info. I thought the same thing...that likely the history was reporting wrong info. Today I looked at the individual history of each module, and the long coding changes are not shown there (actually I think the individual histories do not show all changes there to begin with).

As for what I did that day...I made the following change 4 minutes after those supposed Long Coding changes, nothing before that:

Adaptation
Control unit: 44 Steering Assistance
Name: Driving profile switchover
Values:
Old value: Incremental, controlled over time
New value: Direct, controlled over threshold value
Mileage: 5258 km
Date: 2018-11-26 17:31

I guess its possible either the application crashed mid scan, or I had issues with my phone, but besides that, nothing else was done that day.

I may be overthinking this, but can you elaborate on what you mean by "I suggest that you make a scan report of the car."?
 

codypka

Go Kart Champion
Location
New Jersey
I know the info for this is probably somewhere in this thread, but the search feature on this website is completely useless, so I'm forced to create a new post

Yesterday my car had all the symptoms of a battery going bad. So I replaced the battery myself. After driving 30+ miles all the error codes I was getting came back on (TPMS, Airbag, ACC, Front collision etc etc). I would have thought they would have cleared out by now.

Is there some sort of OBD11 coding to do to reset the car for new battery that I should have done?
 

imthanick_a

Autocross Champion
Location
Ohio
I know the info for this is probably somewhere in this thread, but the search feature on this website is completely useless, so I'm forced to create a new post

Yesterday my car had all the symptoms of a battery going bad. So I replaced the battery myself. After driving 30+ miles all the error codes I was getting came back on (TPMS, Airbag, ACC, Front collision etc etc). I would have thought they would have cleared out by now.

Is there some sort of OBD11 coding to do to reset the car for new battery that I should have done?


https://www.google.com/search?q=sit...69i57j69i58.9668j0j9&sourceid=chrome&ie=UTF-8
 

imthanick_a

Autocross Champion
Location
Ohio
Thanks man. 4th link down had the answer. Will give it a shot when I get out of work

You got it. Google searching using the site filter is much more effective than the forums search function
 
Top