When you click on links to various merchants on this site and make a purchase, this can result in this site earning a commission. Affiliate programs and affiliations include, but are not limited to, the eBay Partner Network.
Does your Techstream version work fine to access other modules? It looks like they are all yellow and unknown vs. white for ok communication. I can't recall how it looked on mine.
And those are the codes but my techstream can’t run the Afs or HL autoleveling
Hi Jeffe005, did you ever resolved the headlights always on after the triple beam swap? And did you get a U0182 error code “Lost communication with lighting control module (front)”?
Could this issue be with the wrong ECU is plugged in to the headlights?
Last edited by Gary350F; Oct 17, 2024 at 10:40 AM.
Hi Jeffe005, did you ever resolved the headlights always on after the triple beam swap? And did you get a U0182 error code “Lost communication with lighting control module (front)”?
Could this issue be with the wrong ECU is plugged in to the headlights?
Just an update to help everyone running with similar issue. I just performed triple beam headlight swapped on my 2018 GS350 F sport last week. It was straight forward and relatively easy. I run in to similar issue like Jeffe005, headlight is always on can't be turn off and no error code in the dash. Run Autel diagnostic scanner (instead of Tech Stream) and got U0182 error (ECU not communicating). Checked the fuse and headlight connections as recommended by other contributors but turned out OK. Looking at the back of the headlights, it turn out that the ECU (81016-30l20-driver side & 81056-30l20-passenger side) was installed to the wrong headlight and this is the root cause of the headlight not working (always on). After swapping the ECU to the correct headlight, I suddenly got an error on the dash "Headlight System Uninitialized, Visit Your Dealer" (This is a good indication that ECU is communicating) like BMGS mentioned. Even with this dash error or notification, the headlights can be turn on/off manually as normal, DRL and turn signal are working (except the annoying error dash bell error sound reminder). After clearing the old scan and re starting the initialization (using Autel programmer) of the ECU again, the dash error is gone and the headlight auto levelling works in initial start. Lesson learn for this 4th gen triple beam mod. is make sure buy the correct 2 ECUs for the headlight and check the ECU part number is paired correctly to the headlights! Hope this helps who will do the conversion!
Just an update to help everyone running with similar issue. I just performed triple beam headlight swapped on my 2018 GS350 F sport last week. It was straight forward and relatively easy. I run in to similar issue like Jeffe005, headlight is always on can't be turn off and no error code in the dash. Run Autel diagnostic scanner (instead of Tech Stream) and got U0182 error (ECU not communicating). Checked the fuse and headlight connections as recommended by other contributors but turned out OK. Looking at the back of the headlights, it turn out that the ECU (81016-30l20-driver side & 81056-30l20-passenger side) was installed to the wrong headlight and this is the root cause of the headlight not working (always on). After swapping the ECU to the correct headlight, I suddenly got an error on the dash "Headlight System Uninitialized, Visit Your Dealer" (This is a good indication that ECU is communicating) like BMGS mentioned. Even with this dash error or notification, the headlights can be turn on/off manually as normal, DRL and turn signal are working (except the annoying error dash bell error sound reminder). After clearing the old scan and re starting the initialization (using Autel programmer) of the ECU again, the dash error is gone and the headlight auto levelling works in initial start. Lesson learn for this 4th gen triple beam mod. is make sure buy the correct 2 ECUs for the headlight and check the ECU part number is paired correctly to the headlights! Hope this helps who will do the conversion!
thank you brother that was the issue with those modules thank you.
Now I can say that the problem was solved thank you
🙏🏻
