Traffic sign recognition nearly coded

[M1tchy]

Andy,
The only differences between ours were on the instrument coding.

Yours was:
Address 17: Instruments (J285) Labels: 4H0-920-xxx-17.clb
Coding: 338F00020F572600010100

Mine was:
Address 17: Instruments (J285) Labels: 4H0-920-xxx-17.clb
Coding: 338F01020F532600010100

I changed it to your coding and now it all works perfectly so many thanks for posting that up.

I had a look at my coding this afternoon following strange fuel consumption readings and it seems that where I had the coding 1 (5th digit in) dictates what fuel tank you have. It shows 00 is A6 01 is A7 and 02 is A8 so changed it back to 01 and will see what happens. (Hope I don't run out of fuel!!)

[Hellodave.]

Just a word of warning for anyone who is thinking of buying a Kufatec dongle, not all Image Processing modules are compatible with traffic sign recognition. I bought a dongle, did all the coding and it still didn't work - turns out I needed a software update to the image processing module. This means sending your module back to Germany for an update, costing about €50 inc shipping (but the car might not be driveable in the meantime because removing the module breaks the FlexRay bus) or buying a new module for €363 inc shipping and returning the old one for "approx" €300 credit. The dongle can't be returned for a refund once it's been used so (with little choice) I chose the second option and the new image processing module seems to work fine once coded with VCDS - speed limits are now shown in the DIS and HUD. I haven't sent my old module back yet so don't know exactly how much credit I'll get.

The image processing module is a bit fiddly to change because it's hidden under the carpet in the passenger footwell. You can get to it by removing the sill trim but it's awkward. I copied my coding from the old module to the new one using VCDS and so far it seems OK - fortunately the Lane Assist camera calibration is stored in the camera module behind the rear view mirror, not the image processing unit so no recalibration is required.

I don't know exactly which image processing modules are and aren't compatible with traffic sign recognition but my old module was part no 4G0 907 107 D and the new one is marked 4G0 907 107 E (the D is crossed out)! I found a VCDS scan from someone else in this thread and their image processing module was also a revision E so that (or later revisions) should be OK. Revision D or earlier won't work without an update.

For reference, you can find the part number of your image processing module (8E) using VCDS. This was a scan of my old one - notice the SW version:

Address 8E: Image Processing (J851) Labels: 4G0-907-107.clb
Part No SW: 4G0 907 107 D HW: 4H0 907 107

[M1tchy]

Wow, that's a whole lot of pain! If I remember rightly it does state that it won't work with software version D or below on the listing.


Sent from my iPhone using Tapatalk

[Hellodave.]

Wow, that's a whole lot of pain! If I remember rightly it does state that it won't work with software version D or below on the listing.

It states:

At faulty recognition of the traffic signs, the control unit for image processing need to be updated. (up to index D)

Which is a bit vague! I read it as "if your control unit doesn't work, we'll update it to index D" - as my unit was rev D I thought it would be fine. As you say, it actually means you need index E or above.

[M1tchy]

Ah my bad, yes that's far more vague than I remember! Glad you got it sorted anyway.


Sent from my iPhone using Tapatalk

[Uberman]

Did anyone ever find out what the Kufatec Dongle actually changes? Or is it a case of buy the dongle and then still have to fiddle around bit to get it to work fully?

[smassart]

It seems that the problem come from the navigation system. Even if you have an old 8E module, you can have traffic sign recognitions working by disabling the navigation datas (select a database of another country in the mmi green menu). Of course this is not an ideal solution because you cannot have at the same time speed limits recognition and navigation working.

[darkyuk]

I had a look at my coding this afternoon following strange fuel consumption readings and it seems that where I had the coding 1 (5th digit in) dictates what fuel tank you have. It shows 00 is A6 01 is A7 and 02 is A8 so changed it back to 01 and will see what happens. (Hope I don't run out of fuel!!)

Hi Mitch,

You have the larger fuel tank on your A7 don't you as mine is set to the A6 setting.....

Andy

[M1tchy]

I do yes. I changed to 02 and it was back to normal and getting 650+ miles from a tank again with no problems so really happy with the retrofit!


Sent from my iPhone using Tapatalk

[949BFN]

Hi Guys
I’m new to the forum, but have been following this thread for some time and eventually ordered this unit (the Euro version) from Kufatec for my 2015 S8: Kodier Interface Verkehrszeichenerkennung VZE-40225_M (I provided Kufatec with my VIN and they suggested this unit)
My S8 has just about every option available (including ACC, which seems to be the essential option to get this to work), apart from Lane Change Assist.
Although the manual for this unit is not available in English (only German), I managed to do most of the coding and changes with the help of this thread and Google Translate. In short, I managed to everything, apart from the very first step, i.e. - 17 Instruments, Long Coding, Byte 05, Bit 2 on. Even the option to show the Traffic Sign in the Heads Up Display is available in the MMI setup menu.
On my car, Address 17, Byte 5, Bit 1 relates to rear spoiler according to long code helper and there is no Bit 2 to change.
Should I be using a different method to code Byte 2?
The rest of the coding worked fine and going into MMI > Driver Assist, I have the Speed limit display option, but it is greyed out and if I go into it, it tells me “The selected system is currently not available”.
I have not connected the Kufatec Module yet, because it warns in its Installation Instructions that the Module should not be plugged in until all.coding has been done correctly. Unfortunately, being a weekend, Kufatec support is closed
Thanks
2015-09-12_10-52-22.jpg


EDIT / UPDATE:
I went for a drive after doing the above and all of a sudden Speed Limit sign popped up in the Heads Up Display (probably after passing a Speed Limit sign). I passed a few other speed limit signs and low and behold, the speed limit sign in the Heads Up Display changes to the correct speed each time I passed a speed limit sign. This is working without having plugged in the Kufatec module yet!
2015-09-12_14-15-27.jpg


However, I do not get any indication in the instrument panel of the posted speed, only this:
2015-09-12_14-16-22.jpg

Could it be that that is the purpose of the Kufatec Module, i.e. to get the Traffic sign to show in the instrument panel, or do I not get the speed displayed because of the issue I have to code Address 17?
What do you guys see for Bit 2 when going to Address 17, Byte 05?

Current coding of Address 17: 338F0802BF410008010100

(The Speed Limit Display option in the MMI setup is no longer greyed out and if I click on it, I get some or other option about trailer speed limit signs.)

Doing a scan of the Instrument Controller (Address 17), shows the following errors:
2 Faults Found:


13636608 - Control Module Incorrectly Coded
U1014 00 [009] - -
Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 117
Mileage: 12573 km
Date: 2015.09.12
Time: 09:39:07


16776979 - Function Restricted due to Missing Message(s)
U1111 00 [008] - -
Intermittent - Confirmed - Tested Since Memory Clear
Freeze Frame:
Fault Status: 00000001
Fault Priority: 6
Fault Frequency: 1
Reset counter: 157
Mileage: 12573 km
Date: 2015.09.12
Time: 09:46:24