|
|
Post by tonsic0011 on Dec 14, 2019 17:48:18 GMT
Does enione know were to find in obd to change wheel circumsize ...my speed isnt good acording to gps and Im now rooling on 18 inch wheels and I guess that it is 16 or 17 inch wheels in my car computer..thanks
|
|
|
|
Post by dv52 (Australia) on Dec 14, 2019 18:45:59 GMT
^^^^ yep - go to dashboard module @ address hex17 - select the text version of coding and scroll-down until you see wheel circ - select the version/variant number to suit your car (see 2nd option down on screenshot below)
Of if you want to use the tick-box version of coding it's byte 3, bit 0-3. The settings are like this: version 1= hex0, version 2 = hex1....................version 9=hex8 - then variant 1 =hex A, variant 2 =hex B .......... variant G = hexF.
I don't know how the version/variant numbers relate to actual circumference size - so trial and error (alas)
Don  |
|
|
|
Post by tonsic0011 on Dec 14, 2019 19:57:48 GMT
I ll try but I saw somevere and now I cant find it, I had somethin like wheel size and it was writen 1970mm cca and I need to write in 2000mm but Ill try this find
|
|
|
|
Post by tonsic0011 on Dec 14, 2019 21:12:47 GMT
Found it in control board-adaption-wheel circ...it was set to 0 and now its set 2002mm...hope thats it
|
|
|
|
Post by steve1 on Dec 15, 2019 16:26:44 GMT
Found it in control board-adaption-wheel circ...it was set to 0 and now its set 2002mm...hope thats it Can you be more specific? Was in in Control Units > Dash Board > Adaption? |
|
|
|
Post by crafter2020 on May 9, 2021 21:52:36 GMT
I have a 2020 crafter and have manage to change wheel circumference 2 times, but now i Just get fault 22 marginal conditions not met, what to do, the speedo is not good😅 tnx in advance😁
|
|
|
|
Post by dv52 (Australia) on May 21, 2021 21:54:56 GMT
try using a different Diagnostic session - it's an option on the main screen for the control module
|
|
|
|
Post by dv52 (Australia) on May 22, 2021 22:13:43 GMT
try entering the security code first- maybe?
nextgen OBD11 does have an EEPROM option, but I've not managed to get it to work - besides, you don't know the correct memory locations that hold the wheel circumference values !!
Don
|
|
|
|
Post by dv52 (Australia) on May 23, 2021 21:31:41 GMT
If your mk7 is before MY16, the security code is 20103
Don
|
|
|
|
Post by dv52 (Australia) on May 24, 2021 11:43:44 GMT
hmm....... this is the Battery monitoring module (it's called "J367"):  ) (ignore the yellow gunk- it's an anti-frosting spray)
J367 communicates directly to the CAN gateway module (@ address hex19) via the 2 x wires shown - it is not related in any way with the wheel circ tweak which concerns the dashboard module (@ address hex17)
Please check the integrity of the connector shown in my picture and the state of the 2 x wires.
Don
PS: Yes, the wheel circ tweak doesn't need a security code - my suggestion was only given as a possible fix for your problem about reverting to the factory value. I have no issue if you don't use a security code
|
|
ldm82
New Member
Posts: 1
|
Post by ldm82 on Jun 27, 2021 13:38:43 GMT
Did you manage to find the issue with this? I have the same problem after changing to version 8, can't get it to go back now and getting the same error....
|
|
|
|
Post by ratulovsky on May 28, 2022 15:34:06 GMT
You sorted this problem, I have some problem.
|
|
|
|
Post by j0rmu6andr on Jun 26, 2022 10:30:49 GMT
So having a issuse here with speedo calibration. So mine was default set to 3 I changed it to 1 but I'm still a little off on the speedo. Tried to switch it to 5 but say functions now available. Anybody have an answer for that.
|
|
|
|
Post by j0rmu6andr on Jun 26, 2022 21:13:57 GMT
Still trying to fix this issue. I've tryed clearing data/cache, uninstalling, and going into developer mode and trying again. To no avale I e gotten no where. I'm hoping some one might have a work around.
|
|
|
|
Post by dv52 (Australia) on Jun 26, 2022 23:28:03 GMT
j0rmu6andr : Hi I had a discussion with a colleague on the VCDS forum about this very matter recently (read HERE - a VW "Transporter" is built on the same MQB platform as a Golf mk7). For reasons beyond my understanding, it appears that:
Byte 3, Bit 0-3 changes to the Dashboard module are only allowable - in one direction (at least this seems to be the case in later versions of the hex17 module)!! Clearly the problem applies across diagnostic devices - so the restriction is obviously in the factory firmware for the hex17 module, itself.
I have absolutely no idea why - maybe someone else can suggest a reason?
My only thought on the matter is that perhaps the restriction is related in some way to the prohibition on changing the odometer reading on this module (unless the car is new) - but this is a wild guess!! Don
|
|
|
|
Post by j0rmu6andr on Jun 27, 2022 1:32:53 GMT
Thank you Don for your input on the topic. I guess I could understand the restriction to the module give the facts of what it controls. Still thought it's pretty limiting seeing as how modifiable this vehicle is. So I guess short of changing the firmware which I am in no way capable of I'm stuck. Well I got close I guess only off by 2mph. Guess I'll get slightly smaller tires next time around. Thanks again Don.
|
|
|
|
Post by Malyk38 on Oct 25, 2022 23:26:34 GMT
Hi everyone.
I know this is an old thread but I just came across it tonight and it has worked for me perfectly! I have a UK Passat B8 (2018) 2TDI 150 Man.
For various boring reasons I was out a few nights ago with a GPS to see how much my speedometer was off by. My friend swears by the 10% rule but I wanted to investigate. It turns out that as standard my car reads approximately 3MPH under the indicated speed. For example on the dashboard 40=37, 50=47 etc. This means a true 70MPH is about 73MPH indicated. It’s only a small margin and more than acceptable but I wanted to try and make it spot on. I drive HGVs which have calibrated tachographs and I think it’s important to know what your true speed is.
Following the advice on this thread I went into the relevant module and changed my wheel circumference to setting 6. My tire size is 215/55/17. I was skeptical but I followed all the steps and then went back out to test.
It really works! My car speedo is now 99.999% accurate with a GPS. When I sit at an indicated speed it now shows as the GPS speed and not 3MPH less.
I’m more than happy with the results.
I just have one question for anyone who may know;
If I were to change the physical tyre size on my car, does changing the wheel circumference setting also change the odometer calibration? Basically, could I change tyre size and not have to suffer with a dodgy odometer reading?
Thanks to everyone who posted on this thread.
|
|
|
|
Post by dv52 (Australia) on Oct 26, 2022 19:55:47 GMT
@malyk38: Hi (nice pic!).
My suggestion (based on logic and the laws of science) is that the answer to your excellent question is most definitely YES- changing wheel size would necessarily change the odometer reading.
The physical mechanism for measuring car speed is counting pulses from the toothed ring that's located on each of the wheel hubs (the speed sensors are actually part of the Brake module @ address hex03). When you made the coding changes that you describe, you altered the factory setting for the distance traveled for each pulse from the ring sensors. Regardless of wheel size, the number of pulses from these toothed rings for one revolution of the wheel is the same. However, the distance traveled between each of these pulses is dependent on wheel size and since velocity is defined as the distance traveled in a fixed period (hour) - it necessarily follows that changing wheel size MUST alter the odometer reading - QED! Don |
|
|
|
Post by vwjap on Oct 26, 2022 20:30:19 GMT
New tyres will give a different speed from old tyres also
|
|
|
|
Post by MartiniB on Apr 18, 2023 13:37:27 GMT
i'm feeling like won a lottery  after done few changes i started to search what exactly do change of `Wheel circ.` and `Wheel circumference 2` - clear answer haven't found  but found comments about this section can be changed just once -> forum.obdeleven.com/post/66470/thread-> forums.ross-tech.com/index.php?threads/35033/#post-295025luckily my MY23 Superb weren't locked - changed values few times, ~two weeks between different codings Control unit: 17 Dashboard
System description: KOMBI
Software number: 3V0920790H
Software version: 6220
Hardware number: 3V0920790H
Hardware version: 526
ODX name: EV_DashBoardVDDMQBA0
Wheel circumference 117 Dashboard Long coding orig -> 05A5001AFF8C000A0188734B0001000800600000 new -> 05A500 19FF8C000A0188734B0001000800600000 or --> Wheel circ.: orig -> Version 3 new -> Version 2 Wheel circumference 2
17 Dashboard Long coding orig -> 05A5001AFF8C00080188634B1001000800600000 new -> 05A5001AFF8C000A0188634B10010008006000 01
or --> Wheel circumference 2: orig -> Version 1 new -> Version 2 result:  |
|
|
|
Post by ascotvan on May 1, 2023 2:05:20 GMT
I'm interested in understanding what effect Wheel circumference 2 (Byte19, bit 0-4) has on the mm wheel circumference values?
Is it perhaps a fine value modifier on Wheel circumference 1 (Byte 3, bit 0-2) or a replacement for it?
How do they interact?
Thanks for any insights.
|
|
