Jump to content

Footwell lights 2022 refresh Silverado

RedLT

By RedLT
in Modifications, Wheels & Tires

 Share

Recommended Posts

RedLT Enthusiast

RedLT

Posted
  • Author
Posted
11 hours ago, matt99199 said:

That 7.5V that you measured was probably a PWM signal from the BCM to the dome light directly. Would need an oscilloscope to confirm.

I'm trying to confirm for the refresh models now in my post here (for anyone interested):

I'll be able to figure it out soon as I have contacts inside GM and also at the dealership.

Thanks Matt! Keep us posted. LOL, I was going to link your thread over here as well.

  • 2 months later...
  • Replies 78
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

Minmax
Minmax

I have given up for the time being. Hoping someone comes up with a module or some sort of sure fire work around. I may install the set I have and install a separate switch somewhere to access them… bu

LowUfo
LowUfo

I'm still waiting for my new truck to show up!   It's been on order for almost 4.5 months and still not here.  I've been researching.   Check the above posts from paauto and see if pin 3 of X3 works. 

RedLT
RedLT

Thanks for your input, yes I have thought of a buck converter but think that would complicate the project and thoughts of heat issue would leave me restless. These new refresh models are so new I gues

Posted Images

paauto Enthusiast

paauto

Posted
Posted (edited)

I'm in the process of installing footwell lights.  On my 2017 I used the following relay, which allows for an adjustable "off time".  I initially used a standard relay, but it pulsated on and off due to the PWM feed off the BCM.  The Beular relay fixed this by holding the relay on for 5 seconds.  It only requires 8 volts to trigger.  Going to try this on my 2023 Sierra...

 

 

https://www.qualitymobilevideo.com/bu510td.html?gclid=CjwKCAiAzKqdBhAnEiwAePEjkqSzrm9emtUhz0gqI-MJDodizLSS_FPZAVijfTnmT94-Gocj82c8jRoCC-QQAvD_BwE

 

 

Edited by paauto
fixed typo
LowUfo Enthusiast

LowUfo

Posted
Posted (edited)
14 hours ago, paauto said:

I'm in the process of installing footwell lights.  On my 2017 is used the following relay, which allows for an adjustable "off time".  I initially used a standard relay, but it pulsated on and off due to the PWM feed off the BCM.  The Beular relay fixed this by holding the relay on for 5 seconds.  It only requires 8 volts to trigger.  Going to try this on my 2023 Sierra...

 

 

https://www.qualitymobilevideo.com/bu510td.html?gclid=CjwKCAiAzKqdBhAnEiwAePEjkqSzrm9emtUhz0gqI-MJDodizLSS_FPZAVijfTnmT94-Gocj82c8jRoCC-QQAvD_BwE

 

Would you use the BU510TD which is a Time Delay ON relay, or would you use the BU509TD which is a Time Delay OFF relay?  Where does the trigger wire connect to?

 

Edited by LowUfo
paauto Enthusiast

paauto

Posted
Posted

You'll want to use the "Delay-Off" version.

 

For my 2023, I am hooking the trigger up to Pin 23 on the first plug (X1) on the BCM.  This controls the "Dome Lights".  The wire color is gray.  In the 2023 up fitter manual, you can find it on page 6-308.  PM me if you want me to send you the manual.  I'm still in the process of installing.  I put the lights in today (for the back row, I put them at the bottom of the B pillar and for the front I put them at the top of the kick panel.  

 

On my 2017 I installed footwell lights and tapped into the equivalent pin as above.  At first I used a standard relay.  I learned, though, that the dome lights "fade" off.  The BCM uses PWM (pulse wave modulation) to accomplish this.  Essentially, it rapidly cycles the circuit on & off at varying frequency to dim the lights to the off state.  A standard relay will turn on & off as the PWM kicks in, essentially flashing the footwell lights on and off.

 

The Bueler delay off relay provides for a delay once the trigger power (i.e., the dome light PWM circuit) starts to fade to off.  Even a 5 second delay will "ignore" the PWM issue described above with a standard relay.

 

Hope this helps.  

  • Like 1
LowUfo Enthusiast

LowUfo

Posted
Posted
23 hours ago, paauto said:

You'll want to use the "Delay-Off" version.

 

For my 2023, I am hooking the trigger up to Pin 23 on the first plug (X1) on the BCM.  This controls the "Dome Lights".  The wire color is gray.  In the 2023 up fitter manual, you can find it on page 6-308.  PM me if you want me to send you the manual.  I'm still in the process of installing.  I put the lights in today (for the back row, I put them at the bottom of the B pillar and for the front I put them at the top of the kick panel.  

 

On my 2017 I installed footwell lights and tapped into the equivalent pin as above.  At first I used a standard relay.  I learned, though, that the dome lights "fade" off.  The BCM uses PWM (pulse wave modulation) to accomplish this.  Essentially, it rapidly cycles the circuit on & off at varying frequency to dim the lights to the off state.  A standard relay will turn on & off as the PWM kicks in, essentially flashing the footwell lights on and off.

 

The Bueler delay off relay provides for a delay once the trigger power (i.e., the dome light PWM circuit) starts to fade to off.  Even a 5 second delay will "ignore" the PWM issue described above with a standard relay.

 

Hope this helps.  

 I see Pin 23, X1 on BCM is "Interior Lamp Control" for the 2500HD/3500HD trucks.   I've looked at the manual for the 1500 series (2023).   I could not find "Interior Lamp Control", but did find "Done/Reading Lamp Enable Signal" on pin 3 of X3.  Can anyone confirm  if this pin will work for footwell lights?  Thanx

 

paauto Enthusiast

paauto

Posted
Posted

I think that should work.  That's circuit 4786.  Check out page 2-32 for the schematic.  

 

I looked thru all the BCM plugs and don't see anything more specific for the dome lights.

 

Let us know!

  • Like 1
  • 1 month later...
Geo9455 New Member

Geo9455

Posted
Posted

Hello, slightly confused and not sure if this was resolved. I have a refresh 22 Sierra and would like to add some footwell lighting and need a trigger source. 

  • Like 1
Minmax Enthusiast

Minmax

Posted
Posted

I have given up for the time being. Hoping someone comes up with a module or some sort of sure fire work around. I may install the set I have and install a separate switch somewhere to access them… but would rather they worked the way my old 2017 Canyon did, which was, they worked exactly how the ceiling lights worked, and they were fantastic. 

  • Like 1
  • Thanks 1
LowUfo Enthusiast

LowUfo

Posted
Posted
11 hours ago, Geo9455 said:

Hello, slightly confused and not sure if this was resolved. I have a refresh 22 Sierra and would like to add some footwell lighting and need a trigger source. 

I'm still waiting for my new truck to show up!   It's been on order for almost 4.5 months and still not here.  I've been researching.   Check the above posts from paauto and see if pin 3 of X3 works.  From his help, it looks like pin 3 of X3 seems to be the best trigger point.   I have already purchased the Bueler Time Delay OFF relay.   Paauto has an HD truck - it seems easy to connect footwell lights.    Once my truck arrives, and I get to try a few things out - I'll let everyone know and I'll take some photos as well.

  • Like 1
  • Thanks 1
Firetiger(MN) Enthusiast

Firetiger(MN)

Posted
Posted
On 2/11/2023 at 7:58 AM, LowUfo said:

I'm still waiting for my new truck to show up!   It's been on order for almost 4.5 months and still not here.  I've been researching.   Check the above posts from paauto and see if pin 3 of X3 works.  From his help, it looks like pin 3 of X3 seems to be the best trigger point.   I have already purchased the Bueler Time Delay OFF relay.   Paauto has an HD truck - it seems easy to connect footwell lights.    Once my truck arrives, and I get to try a few things out - I'll let everyone know and I'll take some photos as well.

The wiring on the "refresh" models appears to be different and I would suggest not copying what the OP did, as he has an older truck.

 

I looked over the schematics and it appears they are sending a data signal to the overhead module rather than switching the power on/off from the BCM under the dash like they did in the pre-refresh years. The module in the overhead then does the power switching to the dome lights.  Maybe I'm not interpreting the schematics correctly, but that's how I'm seeing it.

  • Like 1
LowUfo Enthusiast

LowUfo

Posted
Posted
24 minutes ago, Firetiger(MN) said:

The wiring on the "refresh" models appears to be different and I would suggest not copying what the OP did, as he has an older truck.

 

I looked over the schematics and it appears they are sending a data signal to the overhead module rather than switching the power on/off from the BCM under the dash like they did in the pre-refresh years. The module in the overhead then does the power switching to the dome lights.  Maybe I'm not interpreting the schematics correctly, but that's how I'm seeing it.

 It definitely is not as easy as on my 2016!   When the truck comes in, I'll try some things.  Worst case - I'll add a relay and switch

Razorback7 Enthusiast

Razorback7

Posted
Posted

So the illuminated door sills for the refreshed trucks use "cavity #1" on the X1 BCM connector to power the door sills. Would that work for footwell lighting as well? See pages 17-18.

 

 

 

2022-sill plate.pdf

Minmax Enthusiast

Minmax

Posted
Posted

I’m curious now. I’m sure it would work to at least power on floor lamps when the doors open, which is awesome, but I want them to come on with the “all domes” button as well. Not sure if it would come on in that instance. I suppose when I feel up to it I’ll have to get the old meter out there and try messing with it. 

LowUfo Enthusiast

LowUfo

Posted
Posted

When you look at Page 7-363 of 2023 Sierra 1500 Electrical Body Builder Manual, Pin 1 of K9 Body Control Module X1 - it shows "not occupied"

Jglew82 Enthusiast

Jglew82

Posted
Posted

I installed AMP Research steps on my 23 yesterday. When installing the OBD2 plug, there are 2 wires that connect to 2 different BCM plugs for the lights. These might just be door trigger inputs, but might be a step in the direction you’re looking for. I didn’t test them when installing for voltage. 
 

 

0BEAE2FC-C648-4E35-9DCB-6E310A0B4AF1.jpeg

  • Like 1

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share
Go to topic listing

  • Latest Articles

  • Posts

    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Did have to make 1 modification because of the WeatherTech rear mud flaps and that was needing 3 longer screws than what came with the install package. 😄
    • SFC Retired
      2023 DRW Wheel Liners

      By SFC Retired · Posted

      Picked up the liners yesterday. Installed passenger side WITHOUT any modifications. All mounting holes lined up perfectly. Rain is interfering today with drivers side. Very Happy! Will add pics when finished
    • KARNUT
      OCI, not when but why?

      By KARNUT · Posted

      As a matter of amusement I’ll leave this conversation with this. Do you beat the government average fuel estimate? Statistics are a guide to me. Not a rule. Someone once said I have to have the last word. If true and possible may be. I’ll blame that on working in a family business.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That is a fair point, and I agree that trying to log “everything in the truck” would be the wrong direction.   There are a lot of modules and a lot of traffic. If the product became a full-truck datalogger, the amount of data would get huge very quickly, and most owners would never use it.   I think the first useful version would need to be narrow: - powertrain-side event evidence - selected high-value parameters - communication / voltage / reset events - pre/post event window - short report first, raw log only as backup   One distinction I should make is between active OBD/PID polling and passive bus capture. If you are polling PIDs through OBD, then yes: the more parameters you request, the lower the effective sample rate becomes, and you are adding diagnostic traffic to a vehicle that is already busy running itself. With passive CAN capture, the recorder is not asking all the modules for data. It is listening to traffic that is already on the bus. So it does not consume vehicle bus bandwidth in the same way that a scan tool polling hundreds of PIDs would. But your point still applies in a different way.   Even if passive capture does not add bus traffic, the recorder still has limits: - processing rate - storage rate - timestamp accuracy - decoder workload - event filtering - report size - user attention span   So the answer cannot be “log everything and let the user figure it out.” The product would need to store enough raw evidence to be useful, but only decode, graph, and present the important parts around the event.   A practical report should probably show: - what triggered the capture - how much pre/post data was preserved - which selected parameters changed - how those values compared to baseline - whether the same pattern happened before - whether any voltage, reset, bus-off, lost-message, or communication fault occurred - selected graphs around the event - raw data only as supporting evidence   So I agree with you. More data is not automatically better. The real product is the reduction from raw data into a useful event report.
    • bluev8
      Intermittent no-code issues on 2022.5+ V8 trucks — what did the shop fail to capture?

      By bluev8 · Posted

      That makes sense, and I agree with most of that.   I think the product would need both: 1. a default powertrain template, so it is useful out of the box; 2. user-selected priority parameters, so the owner or shop can choose what they want to see first.   Different users are going to care about different things. One owner may care about oil pressure and voltage. Another may care about misfire trend, AFM/DFM behavior, or U-codes. A shop may want communication events and repeatability first. Your baseline point is probably the most important one. Raw data is not very useful unless the report can show what normal looked like for that vehicle under similar conditions.   The way I would think about it is: - start with a basic known-good baseline - learn normal behavior for that specific vehicle over time - allow the event to be overlaid against baseline - show whether the event was a one-time spike or a repeatable pattern - provide a simple severity level, but with clear limits on what that severity means   For example, early severity could be something like: - Info: event captured, no obvious abnormal pattern - Watch: value moved outside baseline, but not repeated - Warning: repeatable abnormal pattern under similar conditions - Critical: communication loss, voltage drop, bus-off, reset, or severe repeated event   I would not want the first version to say “replace this part.” That would be overclaiming unless there is repair-confirmed data behind it. It would be more honest to say “this pattern deserves inspection.”   On the OBD port question, I think OBD absolutely has a role. OBD is probably the right place for: - DTCs - freeze frame - VIN - calibration information - normal scan-tool parameters - Mode 6 / enhanced diagnostic data if available The reason I am still looking at an ECM-side recorder is that the failure may happen before anyone connects a scan tool. If the owner plugs in a scanner after the event, the pre-event evidence may already be gone unless the ECU happened to save it. So I do not see this as “OBD versus ECM-side.” I see it more like: - ECM-side recorder: always armed, rolling buffer, event evidence - OBD/DLC companion: DTCs, freeze frame, VIN, calibration, normal scan data - phone/cloud: status, notes, upload, report generation, notifications   I agree that phone connection and push notifications would be useful. I just would not want the phone or cloud connection to be required for capture. The recorder should save the event locally even if the phone is not connected. The phone should help with event marking, download, notes, upload, alerts, and report viewing.   For a default GM V8 event report, would this list make sense? - RPM - calculated load / MAP - throttle position - vehicle speed - gear / torque converter state if available - coolant temperature - oil pressure - oil temperature if available - battery voltage - commanded AFM/DFM state if available - actual AFM/DFM state if available - misfire counters / roughness by cylinder if available - fuel trims - relevant U-codes / communication events - bus-off / lost periodic message / module reset / voltage drop events Which of those would you remove, and what would you add?

  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...