OEM (The Real Deal) Ambient Lighting discussion

[Svtweb]

We have had success with acquisition of the last connector. 9U2Z-14S411-AHA. You have to make a slight modification with a razor blade to trim one of the alignment tabs off. After that it was a perfect fit.

For the reading impaired..... This brings total parts to $1025.

Now comes the fun of installing and coding everything.

 

[Wfo]

Any updates and pics ?

 

[Crash33]

Svtweb..."For the reading impaired..... This brings total parts to $1025."

Who has read the past 7 pages and could possibly be reading impaired???

 

[Svtweb]

Tied the small wiring pigtail to the factory console connector. Now if you need to remove the console you don't have any extra wires/connectors to deal with. The 20-Pin connector that was purchased for the HVAC module has 15 extra wire ends. They are the same ends that fit in the console connector.

Just for the ****-retentive value, I ran all the wiring through the factory anti-abrasion sleeve and even used the correct orange tape to secure the end of the harness. If you are going to do something, it doesn't take any more effort to do it right.

 

[13raptorcrew]

So what are you going to do with the as-built data? Do you plan on programming the platinum VIN in the HVAC module and then deal with the VIN mismatch DTC's that may occur when the other modules on the MS-CAN notice the discrepancy?

I think the way you are doing this to be completely stock appearing is the only way it should be done as it will look like it was supposed to be in there (in my opinion it should have been). I know ambient lighting is a small piece of the truck, but those of you (including me) with other Ford vehicles with it, get used to it being there and find it very useful when you drop something. Not to mention everyone that gets in, will likely comment on the lighting down by their feet, or in the cup holder.

My 2013 has no lighting in the center console and no lighting in the glove box, sigh....

 

[Svtweb]

So what are you going to do with the as-built data? Do you plan on programming the platinum VIN in the HVAC module and then deal with the VIN mismatch DTC's that may occur when the other modules on the MS-CAN notice the discrepancy?

I think the way you are doing this to be completely stock appearing is the only way it should be done as it will look like it was supposed to be in there (in my opinion it should have been). I know ambient lighting is a small piece of the truck, but those of you (including me) with other Ford vehicles with it, get used to it being there and find it very useful when you drop something. Not to mention everyone that gets in, will likely comment on the lighting down by their feet, or in the cup holder.

My 2013 has no lighting in the center console and no lighting in the glove box, sigh....

Thanks for the words of encouragement.

In a perfect world, I will reprogram the HVAC and APIM modules with the correct sequence to achieve the desired result. I have already acquired the as-built for my vehicle and for a 2014 Platinum that is only 700+ Vin numbers higher than my truck.

Looking closely at the As Builts, there is a pattern of changes on a couple modules. On the APIM there are only 9 hex changes that are different. What I will do is alter the coding one change at time and then read the vehicle for any errors.

Looking at several posts on many other boards, it appears that the coding of the modules is nothing more than a "Variable" file to set options on and off. Intermixed with the last several digits of the VIN. So using logic, if I make a single change, and then I get a VIN error, that tells me the specific octet that I changed was part of the VIN field.

While it will take a considerable amount of time and effort, the rewards will help those who decide to follow in my footsteps.

 

[DieselD]

you should be ok by just changing the individual build data codes to match a vehicle with the ambient lighting without getting a VIN mismatch DTC

I ended up changing 3 or 4 of mine in the BCM and APIM for my backup camera install. No issues with vin mismatching but it was on a 2011.

This is what bugs me with ford. Its entirely possible for these changes with simple programming. They could have it in the programmable parameters section to add or remove features like ambient lighting, backup cameras etc. Obviously you would need the required hard parts but other then that is just a matter of programing. Its not like your trying to install a jet engine in the thing! Just adding a feature that is already on another like model

 

[RAPTORSV]

@Svtweb, Great thread! Other guys on here have wondered if the front camera could ever be enabled without having to install NavTV, which IMO isn't that great of an option. I would believe if anyone could answer this question, you could? Thanks.

 

[Svtweb]

@Svtweb, Great thread! Other guys on here have wondered if the front camera could ever be enabled without having to install NavTV, which IMO isn't that great of an option. I would believe if anyone could answer this question, you could? Thanks.

I really can't provide a qualified answer on that one. Seeing as the Raptor is the only vehicle that I know of that has a front-mounted camera, I would guess that programming options for its operation would be extremely limited.

I do not know of the inner workings of NavTV, but I am guessing that they interrupt the speed signal that blanks the TV Screen for the video inputs and pumps the front camera video signal into the AUX connections.

 

[BAJASVT]

I believe the "speed signal" for the front camera is based on GPS and VSS just like the OEM navigation (Map based - GPS assisted). That's why it's difficult to "hack" without NavTV.