Audidave69
Registered User
- Joined
- Oct 8, 2017
- Messages
- 453
- Reaction score
- 211
Works also on normal clusters.....already coded it a couple of times.Only works if you've a vc and I would thought the coding is the same as here https://www.audiworld.com/forums/a4...ctivate-vze-traffic-sign-recognition-2937059/
The pre loaded dongle codes all in one go and you can get them from a company called kufatec for £160 posted but from what I’ve been told you can use it on your car as many times as you want but not on any other car as it stores the VIN
Shut all doors, bonnet, switch on ignition, wait one minute, plug in dongle red light then when it goes green your done, just one thing while it’s coding it throws up lots of errors, I thought I’d killed my car until it went green and within twenty yards of driving my first road sign popped up.
@Audidave69 can you share the long coding for the speed warning in the MMI? Also did you get the HUD to work? I am struggling to get those to work... TSR works in the VC, but not getting the warning or in the HUD.I also coded the speed warning to show in MMI and you can set speed warning to work with every speed limit sign.
Did you flash the front camera?@Audidave69 can you share the long coding for the speed warning in the MMI? Also did you get the HUD to work? I am struggling to get those to work... TSR works in the VC, but not getting the warning or in the HUD.
Thanks,
Trickey
OBD 11... I think because I am in Australia camera parameterization was not required likely due to similar signs as Germany. The traffic signs load as I pass them. They show up in virtual cockpit but not on the HUD. One trick I found was I had to disable VZA (navigation based speed on the MMI) but I am going to play around with it later this week and see if I can get them both working. I think if both are enabled in the coding it will unlock the "fusion road sign" adaptation. But with VZA active VZE doesn't work... learned this after playing around with it a few times.Did you flash the front camera?
And what do you mean TSR works in VC? Do you have a pic?
What systems/cables do you use?
Verstuurd vanaf mijn SM-G925F met Tapatalk
Even in Germany you have to flash the camera. Thats why you don't have working TSR. You never have to disable VZA for TSR.OBD 11... I think because I am in Australia camera parameterization was not required likely due to similar signs as Germany. The traffic signs load as I pass them. They show up in virtual cockpit but not on the HUD. One trick I found was I had to disable VZA (navigation based speed on the MMI) but I am going to play around with it later this week and see if I can get them both working. I think if both are enabled in the coding it will unlock the "fusion road sign" adaptation. But with VZA active VZE doesn't work... learned this after playing around with it a few times.
Could you post a screenshot of your "Semi working" TSR?Strange... no flashing required. I think I tried byte 0 bit 0 with the long coding helper, but will try doing it the ones and zeros way to see if it works.
Any idea on how to get the MMi menu active to adjust speed warning thresholds?
Thanks.
Yes just enable VZAI used the pre loded dongle and gained traffic signs in virtual cockpit but lost them in MMI screen, is it possible to have both if I enable VZA?
Thanks will give it a goYes just enable VZA
Verstuurd vanaf mijn SM-G925F met Tapatalk
This disabled TSR for me... i think it requires enabling Fusion mode to have both active. (ie. my post above). Took me a few trial and errors to figure this out.
RJ-8V... what is your experience or background with VCP/ OBD-Eleven? Curious how much coding you have done? If so, i look forward to you sharing your logs.
I'm a software specialist for VAG
Daily work for me....i only use Odis, VCP and VCDS Hex-Net.
Verstuurd vanaf mijn SM-G925F met Tapatalk
Definitely didnt flash the camera, and i dont get annoying beepsThats right. In order to get VZE working as it should you have to flash the front camera. Only then you can have VZA +VZE with fusion mode enabled. As factory specced..
In some cars when you set the mode to Road Sign Detection (and VZA disabled) you get annoying beeps when it does not sees a road sign. This is because of the software in module 5F and front camera.
Codings between the models can be different. Yours is almost the same as "Q5, Q7 and B9"
Verstuurd vanaf mijn SM-G925F met Tapatalk
Adaptions:Definitely didnt flash the camera, and i dont get annoying beeps![]()
What code in module 5F enables the beeps? Also, any idea where i can activate the MMI menu to add TSR into DAP?
Possible if you add TSR.I have an aussie S5SB so hope you can get this working Trickey. What I really want is the speed limit in the HUD (from Nav or TSR, not fussed which). Have you managed to get display in the HUD?
Oh, I think Pre-FL and FL just refer to pre and post mid-cycle FaceLift of the S3 (which added the virtual cockpit).
RJ-8V, do you know if it's possible to get the Nav limit onto the HUD (I'm using OBDeleven)?
Cheers!
@RJ-8V I believe traffic_sign_display_BAP corresponds to byte5 bit2 mentioned earlier and traffic_sign_detection was the other one.
Tried disabling the latter hoping that was the issue, looks like it wasn’t judging by the commute today.
Other OBDEleven options I’ve noted is VZE (coded/not_coded) in A5 which I haven’t touched.
I’ll disable the ACC coding and see if that’s the issue when I get home.
Jup download the files from the filemanager, use flasher to load the parameters and that's it.Looks like A5: byte16 bit4 corresponds to VZE.
Interesting that older cameras (such as @Trickey) used byte1 bit0 to get it working, hence the confusion.
Did you have a B9 @Trickey?
After doing more research I’d say newer build dates (mine is 08/17) require parameterisation even if all the codings show up; the wiki was right in the end.
I’ll give VCP a go once the kit arrives. Does anyone have instructions specifically for patameterisation? I’m only familiar with VCDS and OBDEleven.
Looks like A5: byte16 bit4 corresponds to VZE.
Interesting that older cameras (such as @Trickey) used byte1 bit0 to get it working, hence the confusion.
Did you have a B9 @Trickey?
After doing more research I’d say newer build dates (mine is 08/17) require parameterisation even if all the codings show up; the wiki was right in the end.
I’ll give VCP a go once the kit arrives. Does anyone have instructions specifically for patameterisation? I’m only familiar with VCDS and OBDEleven.
I have a B9 but build date was mid to late 2016. I got an MMI update in late 2017 but they didn't do the VC. Attached is how it is displaying currently. If I scroll off this screen, I get a small icon in the bottom right next to Auto high beam. Still no HUD or fusion. Some of what RJ-8V is saying doesn't align with what I am experiencing or seeing in the coding. I really just need a dump of someone's code from obd11 who used a kufatec or has it factory specced. The missing links are MMI inclusion ( I don't have ACC so that could be why) and HUD working. I do have TSR in the mmi hud menu bit it doesn't physically show. I also have it as the steering wheel button option... but nothing to control speed or turn it on / off.
Yes just enable VZA
Verstuurd vanaf mijn SM-G925F met Tapatalk
5F - around byte 24 bit 6 something like thatCan’t for the life of me remember which control unit VZA was in?