Hi, new 2019 Octavia MkIII combi Scout owner here. Any VCDS owners in Barcelona/Girona/Catalunya who'd like to help me try to enable traffic sign recognition on my Scout? (It has lane assist, adaptive cruise control, blind spot assist, ...) possibly based on the information in: 

thanks :-)

-Jay

 

t

Jay,

 

Lets do this....but your instructions on how to do for a Superb won't work on an Octavia (wouldn't it be nice).

 

If you go to the top of this forum, it should show you the necessary details for a non-FL Octavia but there will he tweaks necessary (for MIB2 and MIB2.5 settings for FL models).

 

Will revisit when Im done outside later on today.

Thanks as ever @varaderoguy.

I'd found this set of instructions, which are for a MkIII (unsure about whether FaceLift - looks like daveface's MkIII might be the model year before the FaceLift), which is what I plan to try - when I received my OBDeleven, which will be in a few weeks.

So, no hurry, as I can't do anything until the OBDeleven arrives.

warm regards,

-Jay

By: daveface

Briskodian

Location: Gloucestershire

Model: Skoda Octavia MK3 vRS

Posted 9 February, 2018 (edited)

I have just enabled TSR on my 2016 vRS using ODBEleven, originally I attempted to use the "App" however this simply popped up a notification stating that it wasn't supported. I did look at the guide on here at the "Tried and Tested" but I found translating them to be used with ODBEleven a little tricky (or maybe I'm just dim!) However on the ODBEleven forums I found the following guide/steps which I followed and seems to have worked nicely and on my initial drive around the block I haven't received any error messages. These were the steps I followed:

 

Traffic Sign Assist Activation:

1. Control Unit 5F - Information


·         Adaptation


    o    Car_Function_List_BAP_Gen2

        §  traffic_sign_recognition_0x21 = Activated, then Green tick


    o    Car_Function_Adaptions_Gen2

        §  menu_display_road_sign_identification = Activated, then Green tick


        §  menu_display_road_sign_identification_over_threshold_high = Activated, then Green tick


8. Control unit A5 (front / advance camera)


·         Security access - 20103

·         Control unit Long Coding 


        o    Byte 1
Bit 0 Activate - "01 Traffic Sign Recognition (FTE) active", then Green tick


13. Control unit 17 (Dashboard)


·         Control unit Long Coding 


        o    Byte 5


        o    Bit 2 Activate, then Green tick

18. Control unit A5 (front / advance camera)


·         Adaptation

        o    Display end of speed limit symbol

        o    Importance to activate: Display valid additional signs 


        o    View Channel Valid suffix


        o    Corresponding value: 00100111. (default was 100111)

Remember to select the green tick at each stage of the adaption, otherwise the changes you've made won't stick.

 

I have tried to make them a little more readable.

 

Original Source - http://obdeleven.proboards.com/thread/2106/high-beam-assist-traffic-recognition

The TSR enablement should be pretty much identical for any MQB car. However, it's important to find instructions for the right age of car as the modules change depending on model year.

 

More importantly, is the OP aware that TSR needs an Amundsen to Columbus to work properly? It uses the satnav data as a basis and uses the camera to supplement it when their are temporary limits, changes etc.

 

It can be made to work if you also change:

Address A5
    channel IDE04733-Road sign detection fusion mode to Road Sign Detection

 

But I think you'll have a warning on the cluster every time the car is started

Many thanks @langers2k. Yeah, I'm aware that I might have an issue with the lack of a nav system in my car. (I've never met an in-car nav system that I liked better than Google Maps. That said, Google Maps Navigation through Android Auto kind of sucks, but we had no choice in the model and features of the car anyway). I think I had seen discussions of the issue of a warning message due to no nav database on which to fall back, and maybe some suggestions on working around it. And in the end if it's a 30 seconds harmless warning that goes away I could live with it.

Thanks so much for the recommendation of the A5 channel IDE04733!

-Jay

The coding you've posted looks to be for a 3Q0 camera but I expect you'll have a 3QD or even 2Q0 camera.

- If you have a 3QD camera, it'll be a different byte/bit

- If you have a 2Q0 camera, it's not possible with VCDS/OBDeleven to enable TSR as it needs an extra FeC applying :(

Hi @langers2k, I'm unfamiliar with the camera model option codes that you mention, and I found nothing in searching for them. (I found some VW group option codes documents, and the website http://vag-codes.info/, on which these codes don't seem to relate to camera models).

My Scout has Adaptive Cruise Control, Lane Assist, front and rear parking assist, rear camera ..

Where may I find details about the option codes/ camera types that you list, and what exact cameras my car has?

thanks,

-Jay

 

It's not a pr code, it's the first part of the camera part number 😉

 

When you scan the car, you'll find out which and therefore which coding is correct 🙂

TSR will give you a warning bong as you don’t have a navigation system every time you get in the car and it’ll only use the camera to pick up signs. If no new signs are picked up, the sign will go off the dash after a certain amount of time. The coding for a 3Q0 A5 camera is usually Byte 16 Bit 4 and this is what I expect you will have. Otherwise coding for 5F and 17 is similar.

You all rock - thanks!  I'll let you know how it goes once my OBDeleven arrives in a few weeks.

(The offer of InfoSec assistance stands. :-) ).

Hi everyone. After a ridiculously long customs delay (on an item that in theory shouldn't even have had to have gone through customs, being shipped by OBD Eleven from Lithuania to me here in Spain), and then further delayed by me being away over the holidays (I put 3400km on my Scout; MAAAAAN this car makes long drives easy and comfortable), I finally got the OBDeleven device and did some adjusting today...

Traffic Sign Recognition is enabled and works.

I only got the "limited" warning once, though I fully turned the car off and back on again I think three times after finishing the coding. Anyway, I can certainly live with that.

 

The current OBDeleven app has the long coding bits already text-labeled for the Adaptation in the Multimedia Control Unit under Car_Function_List_BAP_Gen2 (which I had to find in German, I think 😅) 'traffic_sign_recognition_0x21', and 'menu_display_road_sign_identification', as well as Dashboard Control Unit long coding text 'Road sign detection'. (Though, now that I think of it, I'm not sure that I have seen any new options appear in the head unit under Car -> Settings). Anyway, traffic sign recognition works.

 

Thanks!