Skip to content

O3 FL High Beam Assist - VCDS Autoscan

Featured Replies

Does anyone with an Octavia 3 Facelift MY18 vehicle have High Beam Assist specced from the factory? If so, and you've got or could get access to VCDS, would you be able to do an autoscan and adaptation channel map? I'm trying to enable HBA on my Scout, but the long coding is not editable as yet, it's just zeros.

  • Replies 72
  • Views 23.8k
  • Created
  • Last Reply

Top Posters In This Topic

Most Popular Posts

  • I took the car for a drive last night and can confirm that High Beam Assist can be programmed onto an MY18 Octavia 3 as follows:   Requirements: VCDS: 17.10 beta HEX-V2 or HEX-NET in ord

  • themanwithnoaim
    themanwithnoaim

    @Black_Sheep it seems it can be done, well done @wg100

  • Which HEX cable are you talking about?   HEX-USB+CAN - can't HEX-COM+CAN - can't HEX-V2 - can HEX-NET - can   Why? - because VW have made some of the very latest mod

Posted Images

@wg100, it might be worth posting an autoscan for your vehicle too :)

  • Author
2 minutes ago, langers2k said:

@wg100, it might be worth posting an autoscan for your vehicle too :)

 

I should have thought of that when I saw @andyvee this afternoon. Am thinking of getting VCDS for myself, so may be able to do so soon.

I had a look with VCDS and VCP and the long coding on 09 is just zero's apart from 1 byte.

 

Looks like they have 'masked' the coding

I don't think the coding is masked, instead it looks like VAG might be changing from lcode to adaption channels - at least based on this thread: http://forums.ross-tech.com/showthread.php?10616-Modules-reporting-zero-code-string

 

Andy, did you get an adaption map for 09? Might be worth posting it up on rosstechs forum as there are few people on there that might be able to help :)

No I didn't, the laptop battery wouldn't have lasted the half hour or so it takes to pull the adaptation map from 09!

 

Interesting though, this is the first FL O3 I have seen so haven't got anything to compare it with :(

 

I might try scanning my own Kodiaq and seeing how that is set up - I haven't had time!

I have an admap of my 1.5 SE L TSi DSG taken the day after delivery to me so it's fresh from the factory. I also  have autoscan which shows a couple of faults found.

 

Please PM me if you would like a copy.

Edited by YMe
Making sense.

  • Author
35 minutes ago, YMe said:

I have an admap of my 1.5 SE L TSi DSG taken the day after delivery to me so it's fresh from the factory. I also  have autoscan which shows a couple of faults found.

 

Please PM me if you would like a copy.

Did you have high beam assist from the factory?

Yes.

  • Author
2 hours ago, YMe said:

Yes.

Will get in touch when I'm back from a work trip in a couple of weeks.

These channels are interesting in YMe's map (with HBA):

ENG141650-MAS13782-Fernlicht_assistent-Will Beam assistant: responsivity adjustable via BAP    present
ENG141650-ENG141973-Fernlicht_assistent-Erweiterte_Fernlichtsteuerung    AFS: FLA: Fernlicht ueber AFS
ENG141650-ENG116639-Fernlicht_assistent-Fernlichtassistent Reset    active
ENG141650-ENG116637-Fernlicht_assistent-Menuesteuerung Fernlichtassistent    present
ENG141650-ENG116641-Fernlicht_assistent-Menuesteuerung Fernlichtassistent Werkseinstellung    present

 

This is from another O3 FL (probably with no HBA):

ENG141650-MAS13782-Fernlicht_assistent-Will Beam assistant: responsivity adjustable via BAP    present
ENG141650-ENG141973-Fernlicht_assistent-Erweiterte_Fernlichtsteuerung    AFS: Fernlicht ueber AFS
ENG141650-ENG116639-Fernlicht_assistent-Fernlichtassistent Reset    active
ENG141650-ENG116637-Fernlicht_assistent-Menuesteuerung Fernlichtassistent    Not Present
ENG141650-ENG116641-Fernlicht_assistent-Menuesteuerung Fernlichtassistent Werkseinstellung    Not Present

 

I would change the 3 red marked channels for a start. Probably the camera module still needs coding afterwards.

It seems that these are new channels in the FL.

Edited by aki78

On 11/11/2017 at 20:31, andyvee said:

I had a look with VCDS and VCP and the long coding on 09 is just zero's apart from 1 byte.

 

Looks like they have 'masked' the coding

Yep that seems to be the problem I'm having too

Dito :

 Address 09: Cent. Elect. (J519)       Labels:. 5Q0-937-08X-V2.clb
   Part No SW: 5Q0 937 084 CG    HW: 5Q0 937 084 CG
   Component: BCM MQBAB H   H34 0236  
   Serial number: 02001709503163
   Coding: 000000000000000000000000000000000000000000000000000000000000
   Shop #: WSC 73430 790 00000
   ASAM Dataset: EV_BCMMQB 017001
   ROD: EV_BCMBOSCH_017.rod
   VCID: 7F077CDAE63159D2C53-802A

Too many of us enabling chargeable options :blink:

 

4 minutes ago, Gti Jazz Blue said:

Too many of us enabling chargeable options :blink:

 

 

I think HBA is around £150 and cornering fogs around £300.

 

 

** Other chargable options and prices are available **

 

 

Edited by Auric Goldfinger

Doh - just read the thread properly and checked out that Ross-Tech Forum Thread - that would explain why my coding is all Zeros. So time to do an Adaption Log to see what settings I have before playing.

On 11/11/2017 at 21:40, langers2k said:

I don't think the coding is masked, instead it looks like VAG might be changing from lcode to adaption channels - at least based on this thread: http://forums.ross-tech.com/showthread.php?10616-Modules-reporting-zero-code-string

 

Andy, did you get an adaption map for 09? Might be worth posting it up on rosstechs forum as there are few people on there that might be able to help :)

 

29 minutes ago, Gti Jazz Blue said:

Dito :

 Address 09: Cent. Elect. (J519)       Labels:. 5Q0-937-08X-V2.clb
   Part No SW: 5Q0 937 084 CG    HW: 5Q0 937 084 CG
   Component: BCM MQBAB H   H34 0236  
   Serial number: 02001709503163
   Coding: 000000000000000000000000000000000000000000000000000000000000
   Shop #: WSC 73430 790 00000
   ASAM Dataset: EV_BCMMQB 017001
   ROD: EV_BCMBOSCH_017.rod
   VCID: 7F077CDAE63159D2C53-802A

 

Oh joy - following the thread suggestion I sent an An Auto-Scan through for my May 2017 FL vRS and have just had this response back (with a thanks):

 

P.S. Your car has a few control modules (stuff like rear LED lighting modules) that are not able to communicate with your HEX+CAN interface so we would recommend trading it toward a HEX-NET using this page:

 

So it looks like it is upgrade time, the only thing that I don't like is the limited licence they introduced, I've help others out in the past and my cable has probably been through about 30 VINs, if I make the switch I'm going to have to be selfish and not assist anyone any more with a limit of 10 VINs - I'll need to keep them for myself / mates with Group Cars.

 

 

1 hour ago, Gti Jazz Blue said:

if I make the switch I'm going to have to be selfish and not assist anyone any more with a limit of 10 VINs - I'll need to keep them for myself / mates with Group Cars.

 

 

Alright bezzie Mate...........:hi:

2 minutes ago, Auric Goldfinger said:

 

Alright bezzie Mate...........:hi:

VCDS 3 VIN HEX-V2 cable ordered from Gendan, WiFi HEX is very nice but just more to go wrong at extra cost so I went for the USB version.

 

Went for an outright purchase so I can keep the current cable for unlimited use on older group cars - like my My Mum's Citygo and Daughters Altea.

Looks like you'll having all the FL 230 and the 245 boys wanting to lick your boots................

  • Author
53 minutes ago, Gti Jazz Blue said:

VCDS 3 VIN HEX-V2 cable ordered from Gendan, WiFi HEX is very nice but just more to go wrong at extra cost so I went for the USB version.

 

Went for an outright purchase so I can keep the current cable for unlimited use on older group cars - like my My Mum's Citygo and Daughters Altea.

Am planning to get the Hex-V2 cable  when I'm back from my work trip in a couple of weeks. I'd be interested in hearing how you get on.

  • 2 weeks later...
  • Author

Just got VCDS delivered this morning. Have done an autoscan and an admap of controller 09. What now...? Anyone able to shed light on next steps?

  • Author
On 12/11/2017 at 18:31, aki78 said:

These channels are interesting in YMe's map (with HBA):

ENG141650-MAS13782-Fernlicht_assistent-Will Beam assistant: responsivity adjustable via BAP    present
ENG141650-ENG141973-Fernlicht_assistent-Erweiterte_Fernlichtsteuerung    AFS: FLA: Fernlicht ueber AFS
ENG141650-ENG116639-Fernlicht_assistent-Fernlichtassistent Reset    active
ENG141650-ENG116637-Fernlicht_assistent-Menuesteuerung Fernlichtassistent    present
ENG141650-ENG116641-Fernlicht_assistent-Menuesteuerung Fernlichtassistent Werkseinstellung    present

 

This is from another O3 FL (probably with no HBA):

ENG141650-MAS13782-Fernlicht_assistent-Will Beam assistant: responsivity adjustable via BAP    present
ENG141650-ENG141973-Fernlicht_assistent-Erweiterte_Fernlichtsteuerung    AFS: Fernlicht ueber AFS
ENG141650-ENG116639-Fernlicht_assistent-Fernlichtassistent Reset    active
ENG141650-ENG116637-Fernlicht_assistent-Menuesteuerung Fernlichtassistent    Not Present
ENG141650-ENG116641-Fernlicht_assistent-Menuesteuerung Fernlichtassistent Werkseinstellung    Not Present

 

I would change the 3 red marked channels for a start. Probably the camera module still needs coding afterwards.

It seems that these are new channels in the FL.

 

Changing the highlighted channels has enable the light assist option in the light settings, however "fault: light assist" appears on the MFD when the high beam is engaged, so there is still some coding to be done.

I’m sure someone posted an elaborate sequence of ignition on/off which clears the error. I forget who or in which thread though. It assumes you’ve coded correctly of course. 

Have you reset the lights in HU after coding?

Create an account or sign in to comment

Recently Browsing 0

  • No registered users viewing this page.

Important Information

Welcome to BRISKODA. Please note the following important links Terms of Use. We have a comprehensive Privacy Policy. We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.

Account

Navigation

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.