VCDS Scanning - Headlight Range Module

[dArK5HaD0w]

i was hoping some could help, and/or tell me why, when i do a VCDS (v18.9) Autoscan, it doesn't show Address 55 Headlight Range?

i even tried scanning with car engine running and the lights on AUTO.
no luck.

i'm using a Hex-Can cable.

there are no issues scanning the other bits.
Scan: 01 02 03 05 08 09 10 13 14 15 16 17 19 2B 36 3C 42 44 47 4B 52 5F 6C 6D A5

i need to be able to change the Coding value of the Subsystems within Headlight range.
however i don't understand why the vcds scan is not picking this up.

any ideas?

my car is MY17 Superb 220. its factory fitted with Xenons.
i've successfully got HBA coded via VCDS.

below is an example of Address 55...



Address 55: Headlight Range (J745) Labels: 7P6-907-357.clb
Part No SW: 7P6 907 357 D HW: 7P6 907 357 A
Component: AFS-ECU H07 0090
Revision: -------- Serial number: --------------
Coding: 06D602007F010000
Shop #: WSC 33361 790 00063
ASAM Dataset: EV_HeadlRegulVWAFSMQB 001120
ROD: EV_HeadlRegulVWAFS_SE26.rod
VCID: 4084F5F7DBD5DA3E1D-8014

Subsystem 1 - Part No SW: 4H0 941 329 HW: 4H0 941 329 Labels: 3D0-941-329.CLB
Component: LeiMo links H02 0013
Coding: B30000

Subsystem 2 - Part No SW: 4H0 941 329 HW: 4H0 941 329 Labels: 3D0-941-329.CLB
Component: LeiMo rechts H02 0013
Coding: B30000

No fault code found.

[kamold]

There is no more 55.
It's 4b now in newer mqb cars, with d6 and d7.
Needs a vcds V2 cable to address them.

[dArK5HaD0w]

yes, after doing more research, i need either a HEX-NET or HEX-V2 cable to access the headlight range control module.
i was using a HEX-CAN cable.

i believe its still at address 55, not 4B. the above scan i showed is from another MY17 Superb.
my 4B is "Multifunc. Module"

nonetheless, i need a newer cable.
*sigh*

[kamold]

Older cars still had 55.
My18 most definitely does not.
4b is a gateway to the led headlight controllers.
Then liemo attached to them.

[dArK5HaD0w]

Do u know if it can it b accessed and coded via ObdEleven?
I've got the coding values I need.

[kamold]

Pretty sure obd11 can see and code them.

[dArK5HaD0w]

Seems to be the case.

However I'm not sure if it will let me code the subsystem specifically.

In the example above, they are coded as "B30000"
I'll b looking to recode my replacement LED controllers to become "B30000", like above.

[kamold]

Are you looking at an led headlight retrofit from xenon? What is the aim here?

[dArK5HaD0w]

not an LED from Xenon upgrade, but rather more bells & whistles to the existing xenons.

i'm looking to retrofit Smart-Light Assist headlights to my Superb.
its got factory fit bi-xenons, however i'm looking to upgrade its existing capabilities. the best it can currently do is HBA (high beam assist), which i enabled via VCDS last year.
this upgrade will allow it to do the fancy high beam masking/shadowing, and enable the "whiskers" as DRLs


using Erwin, the difference between the SLA capable headlights and normal xenon headlights is:-
1. the headlight unit itself (3V294101xB). these are not LED, but still xenon. it just has additional motors and mirrors.
and
2. the AFS LED Controller Module (4H0 941 329), for both left and right sides.

the non-SLA headlights (3V294101xA) use AFS control modules with the part number 8U0 941 329.

i've acquired a set of RHD second-hand SLA capable headlights from overseas, and a set of AFS controllers.
hence i need to recode the afs controllers, so its Superb friendly.

i've got the coding from someone who has a Superb with factory fitted SLA headlights, and the subsystem/controller is coded as "B30000".
its in my first post above.

i'm looking to recode these second-hand controllers to be the same, i.e. "B30000"

be it under Address 55, or Address 4B.

[kamold]

They may also need a suitable parameter set, depending what car they came from.
Vcds V2 is best for coding. For parameter set you'd need VCP or ODIS with online access, a vas5055a cable and trick the servers into loading for a different vin.