Just a note that the change affects also odometer reading, and thus your fuel consumption readings - improving them, as seemingly you are doing more miles. At speedo reading 50 your real speed is 51. The correction by +7.8% would make your speedo very optimistic – showing about 53 when actually doing only 50.Ĭurrently with your bigger wheels I think that your speedo under reads about 2%. Speedo reading would be about 2% more than actual speed – at speedo 51 when real speed is 50. So for you the setting +4.0% definitely would be better match – taking away some of the EU tolerance. They have been reading 103 when real speed is 100 with factory wheels. I have observed about 3% error in T6 vans. I think EU regulations has forced speedos read over a little. Īs “” tells that speedo error is -5.18% your wheels are significantly bigger than factory wheels (also revealed by your avatar) – so the correction choices (if table 2 applies to your van) at first glance would be +4.0% or +7.8%. Thus giving actually a couple of choices for bigger wheels.įor smaller wheels – use "-" values of table, unfortunately not much to do. So changing (table 2) coding from factory setting “4” to “3” will just make my speedo read more – at certain speed at factory setting "4" speedo would read 100 units and after coding to “3” speedo would read 104 units at the same speed.Īnyways, the bottom line is that for bigger wheels you need to make speedo read more, that is “+” values in the table. In the tables above my simplified approach was to look only how coding change affects speedo reading. Yes, the challenge is not to get confused with speedo reading, correction, speedo error with new wheels, etc. Of course the coding change can be done with other tools, too. And the most important part: Post the values from (2), (3), (4), (5) here please.If not happy with the result % try different coding = go back to (4).Verify achieved correction factor by calculating the change% by dividing value from (5) by value from (3).Read and record measurement value IDE00845 again.Change the coding (initial guess would be from the tables above).Read and record corresponding factory measurement value IDE00845 (Wheel circum.).Check and record the factory coding of your van (in the tables above leftmost column, value in range of 1-7).There the VCDS comes to help being capable of verifying the result from coding change right there. As soon as required correction is known the VCDS can do the job.Īnyways, a slight pitfall being that the T6’s seem to come with different factory codings and different corresponding wheel circumference tables behind as the tables above show. Last version of VCDS Mobile is 0.Thanks, yes, exactly as you said.
VCDS ON ANDROID APK
Versions of VCDS Mobile apk available on our site: 0.018.
VCDS ON ANDROID ANDROID
You could also download apk of VCDS Mobile and run it on android emulators like bluestacks or koplayer. If any of materials on this site violates your rights, report us You could also download apk of Google and run it using android emulators such as big nox app player, bluestacks and koplayer. VCDS Mobile can be installed on android devices with 2.3(Gingerbread)+. You can visit their website or send to them. Estimated number of downloads range between 100,000+ in google play store VCDS Mobile located in category Tools, with tags and has been developed by Ross-Tech, LLC. This app has been rated like bad by 118 number of users. Total number of five star reviews received 137. This is cumulative rating, most best apps on google play store have rating 8 from 10. In general apk file VCDS Mobile has rating is 6.3 from 10.
0 kommentar(er)
