Jump to content

2016 SLT lights in 14/15 SLT/All Terrain almost done

zmnypit
 Share

Recommended Posts

BringTheRain403 Senior Enthusiast

BringTheRain403

Posted
Posted

BTW is the problem only there when the DRL is the only thing on or does it hair when the headlights are on as well?

 

Sent from my Nexus 6P using Tapatalk

  • Replies 910
  • Created
  • Last Reply

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

Popular Posts

zmnypit
zmnypit

Sorry I'm a little late, I've been in the Caribbean for a little over a week and just getting around to posting pictures. I know there was a lot of fuss of whether or not the SLT lights would so I bit

WSFD6107
WSFD6107

Well, I finally got around to installing my 16-17 LED headlights. A huge thanks goes out to @zmnypit for fabricating the adapter harnesses. 

zmnypit
zmnypit

One more night pic that should help.  

Posted Images

Payton34 Enthusiast

Payton34

Posted
Posted

BTW is the problem only there when the DRL is the only thing on or does it hair when the headlights are on as well?

Sent from my Nexus 6P using Tapatalk

Yes the drl only flickers when just the drls are on and the turn signal is used. Once truck warms up it works normal
Arth Enthusiast

Arth

Posted
Posted

Well huh.

 

Guess I will check mine tomorrow morning as well. One of those things you don't notice by yourself usually.

 

Might push me to look closer into getting that DRL to turn off with the turn signal like factory. It's just a small pain in the butt to get access to those wires all the time.

  • Like 1
zmnypit Enthusiast

zmnypit

Posted
  • Author
Posted (edited)

Only the bottom half of the drl turns off when the turn signal is on and only during the day in the new trucks

 

Sent from my Nexus 6P using Tapatalk

The whole DRL cuts off. This is why we've been trying to achieve it.

 

 

 

Yes the drl only flickers when just the drls are on and the turn signal is used. Once truck warms up it works normal

This sounds like interference but from how and where is anyone's guess.

Edited by zmnypit
Payton34 Enthusiast

Payton34

Posted
Posted

I actually prefer the look of DRL staying on. I was wondering if trucks with the 6.2 are only effected by the flickering drl until it warms up.

Arth Enthusiast

Arth

Posted
Posted

Well I have a 5.3 and I just checked mine this morning with no flicker. Little after 8 and about 70 degree out. Was the first start after about 5 days of sitting.

 

 

I actually prefer the look of DRL staying on. I was wondering if trucks with the 6.2 are only effected by the flickering drl until it warms up.

Payton34 Enthusiast

Payton34

Posted
Posted

Horacio and my truck are 6.2 and have flicker so maybe the electrical system has a more irregular voltage until they warm up

zmnypit Enthusiast

zmnypit

Posted
  • Author
Posted

Well I have a 5.3 and I just checked mine this morning with no flicker. Little after 8 and about 70 degree out. Was the first start after about 5 days of sitting.

 

 

Same here. Haven't driven my truck since thurs afternoon and no flicker. It's been a year or close to it and no issues. His is only one side also. Passenger side is fine. :dunno:

zmnypit Enthusiast

zmnypit

Posted
  • Author
Posted

It would be a non issue if the DRL cut out when the signal was on like it should, but I know that hasn't been ironed out yet.

Wait so your's flickers too? Payton34 has 6.2 and you have a 6.2. Hmmmmm

 

It will happen, just hang in there.

Payton34 Enthusiast

Payton34

Posted
Posted

I ordered a Gen5 harness and will have it today. I will see if there are 2 capacitors in the wiring.

zmnypit Enthusiast

zmnypit

Posted
  • Author
Posted (edited)

I ordered a Gen5 harness and will have it today. I will see if there are 2 capacitors in the wiring.

Fingers crossed! Maybe abominable Z71 will chime in on the 6.2L wiring. I see nothing but that isnt saying much.

Edited by zmnypit

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...