dear readers
i have done a full retrofit of oem bi-xenon with help from iichel.
everthing is wired and works oem like. that is very nice of course.
now, the last problem is the xenon range module. it is 6R0 907 357 module.
many error codes but the most important:
- module coded incorrectly
- no end of line programming
if the errors are cleared, headlights do a down-up so wiring is ok and headlights are ok.
the problem is that i cannot code it.
it simply rejects code with an error 22: conditions not met or request sequence error
current coding is for T5 and new code should be 01 8A 00 00 01 00 00 00:
- chassis polo 6R
- rain light sensor installed
- start/stop
- twist link axis
- info via sensor and not via CAN
but coding is not accepted.
it is a used module but i can still define workshop code etc. 12345 123 12345 or my garage codes both dont work
it is vcds 12.12.0
anyone any ideas on how to code it?
Bi-xenon retrofit: problem with xenon range module
- ciclo
- Bling Bling Diamond Member
- Posts: 8839
- Joined: Sun Feb 24, 2013 10:20 am
- Drives: 6R'13/G7.5'19
- Location: Earth ♥, Spain.
- Contact:
Re: Bi-xenon retrofit: problem with xenon range module
This is the most common coding in the Polo 6R, checked in many autoscan. Also WSC.
Address 55: Xenon Range (J431) Labels: 6R0-907-357.clb
Part No SW: 6R0 907 357 HW: 6R0 907 357
Component: LWR-ECU H02 0070
Revision: -------- Serial number: --------------
Coding: 0112000001000000
Shop #: WSC 00788 648 00255
ASAM Dataset: EV_HeadlRegulVWLWRPt 001004
ROD: EV_HeadlRegulVWLWRPt.rod
VCID: F7F7739C4E3305A6259-80A2
No fault code found.
BlueGT (with start-stop) LHD
-------------------------------------------------------------------------------
Address 55: Xenon Range (J431) Labels: None
Part No SW: 6R0 907 357 HW: 6R0 907 357
Component: LWR-ECU H02 0070
Revision: -------- Serial number: --------------
Coding: 0196000001000000
Shop #: WSC 00788 648 00255
ASAM Dataset: EV_HeadlRegulVWLWRPt 001004
ROD: EV_HeadlRegulVWLWRPt_VW25.rod
VCID: F7FDB51A4E7E89A0906
No fault code found.
Other BlueGT (st/stp) LHD
-------------------------------------------------------------------------------
Address 55: Xenon Range (J431) Labels: None
Part No SW: 6R0 907 357 HW: 6R0 907 357
Component: LWR-ECU H02 0070
Revision: -------- Serial number: --------------
Coding: 0192000001000000
Shop #: WSC 00788 648 00255
ASAM Dataset: EV_HeadlRegulVWLWRPt 001004
ROD: EV_HeadlRegulVWLWRPt_VW25.rod
VCID: F7F775054ED6E51
No fault code found.
Address 55: Xenon Range (J431) Labels: 6R0-907-357.clb
Part No SW: 6R0 907 357 HW: 6R0 907 357
Component: LWR-ECU H02 0070
Revision: -------- Serial number: --------------
Coding: 0112000001000000
Shop #: WSC 00788 648 00255
ASAM Dataset: EV_HeadlRegulVWLWRPt 001004
ROD: EV_HeadlRegulVWLWRPt.rod
VCID: F7F7739C4E3305A6259-80A2
No fault code found.
BlueGT (with start-stop) LHD
-------------------------------------------------------------------------------
Address 55: Xenon Range (J431) Labels: None
Part No SW: 6R0 907 357 HW: 6R0 907 357
Component: LWR-ECU H02 0070
Revision: -------- Serial number: --------------
Coding: 0196000001000000
Shop #: WSC 00788 648 00255
ASAM Dataset: EV_HeadlRegulVWLWRPt 001004
ROD: EV_HeadlRegulVWLWRPt_VW25.rod
VCID: F7FDB51A4E7E89A0906
No fault code found.
Other BlueGT (st/stp) LHD
-------------------------------------------------------------------------------
Address 55: Xenon Range (J431) Labels: None
Part No SW: 6R0 907 357 HW: 6R0 907 357
Component: LWR-ECU H02 0070
Revision: -------- Serial number: --------------
Coding: 0192000001000000
Shop #: WSC 00788 648 00255
ASAM Dataset: EV_HeadlRegulVWLWRPt 001004
ROD: EV_HeadlRegulVWLWRPt_VW25.rod
VCID: F7F775054ED6E51
No fault code found.
- iichel
- Bling Bling Diamond Member
- Posts: 6685
- Joined: Fri Nov 14, 2014 2:14 pm
- Drives: Polo 6R 2.0 TDI, Passat B8 2.0 TSI
- Location: http://mypassat.nl/
Re: Bi-xenon retrofit: problem with xenon range module
it's for a 1.6tdi so we'll try that one for the non-bluegt with start/stop! thanks ciclo!
what i understood is a no-end-of-line programming a 'bad' module that didn't receive a signature-like end-coding at vw so it could be 'unfixable'
what i understood is a no-end-of-line programming a 'bad' module that didn't receive a signature-like end-coding at vw so it could be 'unfixable'

