Originally Posted by breakers28 (Post 7574632)

I'm certainly not an expert and not sure I can help but I'll share my thoughts anyway....
1. I don't understand this comment: but when it comes to programming the addresses and values as his instruction states FORScan will accept the specific changes necessary BUT it will also change values that should not be changed on its own and are far different from the as-built values. Be aware that the last 2 digits of each line in a module are calculated values and FORScan will calculate these values (it is actually the HEX of all the previous values in that line). If that is what you are talking about, then that should be expected. If not, please explain more or provide examples. I also assume you are changing the AsBuilt file and manually changing the values as needed.
Example of what FORScan calculates on each line item: 726-01-01 0001 0101 0133 ==> the 33 is the hex sum of 726-01-01 0001 0101 01 and FORScan will calculate the value. If you change any of those values, the 33 will be different but FORScan will calculate the correct value based on the values in that line.
2. Per your description, it appears you have an issue with Daytime Running Lights (DRL) on the left side (driver's side). As I recall, the daytime running lights operate at a lower intensity than the regular nighttime lights. Without having another LED headlight to test with, you might consider changing your configuration to use the FOGs as DRL (instead of the low beam). Or you might consider checking voltage at the headlight connector for the DRL light in the daytime (would require getting the pin layout and testing to ensure voltage for DRLs) Your guess of a bad ballast or LED light could be correct. I just don't know.... However, changing to FOGs would tell you if the BCM is handling the DRL request successfully. Just my thoughts....
3. I also upgraded my US built 2016 jXLT 302A from Halogen to factory LED headlights. My configuration had (and has) the FOG and PARKING lights set as DRL, not the low beam. I'll share the changes I made to my BCM module for the LED headlight upgrade. Hopefully it will help you review or diagnose your issue. Here are the lines and values I had and what was changed with the LED upgrade (again, I had FOG and PARKING set for DRL before the LED upgrade)
Line Number: Value B4 LED upgrade Value after LED upgrade
726-24-01 0000 0000 00xx ===> 0000 00FF 0Fxx
726-26-02 0100 0001 00xx ===> 0100 0000 00xx
726-27-01 0100 0001 00xx ===> 0001 0001 00xx
726-29-01 0000 0000 01xx ===> 0000 0000 00xx
726-45-01 0A00 7F01 00xx ===> 0A00 7F01 00xx (this line needs the 7F in order to allow all DRL configurations)
726-50-01 04xx ===> 04xx (04 in this line enables FOGs as DRL)
I hope that is helpful and gives you something to go on... Good luck!

Originally Posted by Ryan B (Post 7577078)

It sounds like you have a programming issue. Did you use the as-built format or the easy format? Used headlights could also be contributing.

Originally Posted by UnwaryFunguy302 (Post 7582345)

I have a feeling it may also be a programming error as well, but I'm not exactly sure as to where. Everything I did has been changed in the as-built screen. My issue lies in the AutoLight settings where only the passenger low beam bulb lights up in the daytime. On AutoLight nighttime, and all other settings, I have no other problems.

Would having halogen tail lights contribute to the issue? Or could it just be as simple (and expensive) as a bad driver's side headlight? I'm tempted to ask you if you'd be willing to look into my current as-built and see if you notice anything.