@linni I have a new question. 

 

If the car has ACC ( I guess yours have that). Could you please provide me with some information.

 

In control module 13 (Adaptive Cruise Control) what are your settings in long coding: 

 

Is Byte 01, Bit 0 (Traffic Sign Detection) activated or not ?

 

I have found no information on this elsewhere. 

Edited 8 March, 20206 yr by linni

Hi @linni thank you so much, for your quick reply. It’s also off on mine. I wonder what it does, as traffic sign assist works fine without it ticked.
 

I some times I get an ACC error, and it stops working. This error goes away after ignition shutdown, and 30 seconds wait before turning back on. Thought that this might be the reason, and needed to be activated, but I guess not.

 

Byte 03, 04 and 24 differs from mine, would you be so kind, to screenshot these also. That would be so helpfull. I think it is because you have park assist and maybe also a trailerhook 

 

My default HEX is:

32 04 67 51 5C FF 87 28 74 9C 81 45 30 40 87 00 00 00 00 00 00 00 00 00 04

Edited 8 March, 20206 yr by snowatom

Set Front Assist to more mild condition - average or normal or smth similar.

 

Traffic sign detection is there because in the near future Audi is planning to add the feature to ACC - car slows itself down when regonizes speed restriction and speeds up after that.

OK, how do i change front assist to more mild conditions ?

Infotainment - car menu - Front Assist - Advance warning. I have set it to Late if I remember correctly.

Do you have Amundsen or Columbus?

Columbus.

But it shouldn`t matter. Car settings are identical despite the headunit you have.

It`s under Driver assists submenu.

 

Edited 8 March, 20206 yr by linni

Wonder if fusion mode is still correct with Amundsen

Amundsen, Columbus - doesn`t matter.

They are just infotainment units.

All the codings are performed in modules under the bonnet.

Ok. Just looking to see if sign assist could cause acc to cause errors.

Snow, sleet, mud - they can block radar and disable ACC.

Sign recognition is not involved in ACC performance.

@linni sorry to bother you once again. But I get some errors in my log, and I think i might have found the reason.
 

In unit 5F Adaptations.

Would you please check what your defaults are at :

traffic_sign_recognition_0x21_msg_bus 

 

Is it: Database extended or Databus Infotainment ???

 

Mine is the first, but I suspect that on a car with sign recognition the Databus Infotainment setting might be the correct one.

No bother at all.

Will check tomorrow morning.

 

@snowatom

 

It`s Databus) extended.

 

@linni Thank you for checking. Mine is also set at that, was hoping I had found some differences. 

 

I still suspect the ACC error (acc deactivates and stops working until engine shutdown) to be due to activating the Sign Assist. After it has been at the repairshop, they defaulted every control-unit with my VIN number. So my sign assist was of cause gone afterwards. Since then I haven’t driven so much with the acc on, to verify if the error has gone. But I am a bit causes enabling sign assist again, just to see my acc error coming back. 

Sign recontition uses windshield camera.

ACC uses radar.

 

I doubt the problem lies there.

@linni OK, I have activated sign assist once again, and it works perfectly. Gonna see if my acc error comes back. 

 

My obdeleven keeps a history log of the changes I’ve made. And I went to look, to verify, and something strange came up. I have never been in this control unit, so I know it is not me. The obd history log says that in Unit 19 (gateway) it has activated Byte 03, Bit 4 and Bit 5. I have no idea what they are, besides to be something regarding battery, I think. 

 

Think you’re getting a bit tired of me asking, but would you tell me, what your defaults are in unit 19, Byte 03, Bit 4 and 5 ? 

 

 

@snowatom

 

Don`t worry, I do not get bored.

Well, maybe my wife sometimes, but...

 

Strange thing is, that Byte 3 does not have bit 5.

Orinary version (blue background) of coding gives only two bits under byte 3.

This yellow experimental is more complex.

 

 

I also have OBD11 Pro, if you want to verify some codings.

Did you use app to activate road sign recon? People say do not use apps with OBD11 ever This thing screws up oher things.

And I would recommend not to use OBD11 for any sohpisticated codings. Too many complaints all over the web. That`s why I bought also VCDS.

@linni Thank you so much for taking your time to help me. 

 

Firstly, let me assure you, that I never use obdeleven's apps. Only manual adaptations and long coding, which then should be more or less the same, following the same guides from VCDS. 

 

But now it gets a bit more weird. Cause as our image shows, your current settings (hex value is 0B010034), is exactly the same as mine, but what obdeleven history says, it has changed it to. I know I have never changed anything in unit 19. And your EM Battery Architecture seems to be 3 (in regards to your hex value). So maybe mine has also always been 3, but for some reason obdeleven chose to make a wrong history log. - OR obdeleven is correct, and my EM Battery Architecture was actually 0, and now 3. I'll think I'll leave at 3, seeing your setting is that, and also, I have no idea what EM Battery Architecture is ;o)

 

Please see my obdeleven images for reference.

@snowatom

 

Checked the history, I have a list 2 kilometers long there. Added, removed, again added, again removed (ACC for example) etc etc. Complete rubbish. Granny, give me some bullets.

 

Checked for faults - found some in couple of modules. At the same time VCDS found zero faults.

 

I think we can (or must) stick this obd11 as deep as we can.

 

P.S. I have the same EM Battery Architecture nr 3.

 

Just in case my long coding. There are some differences but I guess it?s due to older version of the hardware/software.

Edited 15 March, 20206 yr by linni

Hi @linni

 

Strange that Obdeleven finds faults and vcds does not. But yes, I have some newer versions, I do however think the difference in HEX is due to you having the RS model, and I do not. Most likely we paid the same, but in my country (Denmark), car taxes are insane. My basic car is 71.000USD, and the top spec RS model is 101.000USD, so way out my league ;o)

 

Just for kicks, I'll post the different hex'es to compare, If you'll also post yours ;o)

 

 

I found the easiest way to turn Traffic Sign Recognition on in my MkII Octavia was to buy a Honda!

@snowatom

 

I have an opinion on why OBD11 has different readings. But this is strongly my personal opinion.

If you look at the adaptions, that OBD11 provides, they are identical to the ones VCDS provides. But VCDS is always two steps ahead.

As I can see the things, obd11 is pretty much just copying the adaptions and not doing the research themselves. This ezplains why things get screwed with modules. Not knowing the exact architecuture.

 

Your version of OBD11 seems slightly different, but here it comes:

9 minutes ago, FirstAndLastSkoda said:

I found the easiest way to turn Traffic Sign Recognition on in my MkII Octavia was to buy a Honda!

 

Honda is a good car, if it`s a Legend.