Jump to content

Recommended Posts

Posted
On 4/21/2021 at 5:57 AM, Transient said:

HID LED vs LED. Turn signals are also LED.

Sent from my SM-N960U using Tapatalk
 

I purchased the Boostauto and will be adjusting my headlights when I replace my front bumper face due to a hot water heater in the fast lane just north of the GW bridge heading north to visit family. Oh well ****** happens but the fog lights do help out big time 

Posted
On 4/21/2021 at 4:57 AM, Transient said:

HID LED vs LED. Turn signals are also LED.

Sent from my SM-N960U using Tapatalk
 

I see that "HID LED" in the High Country, and in the Midnight Edition package for the  LT Trail Boss, but what is it, exactly?  The wider DRL light is easy to differentiate from the other thin DRLs as part of that light option group, but the HID LED headlights look like the LTZ lights.  What am I missing?  Are they actually brighter, or different at the reflectors, or both, or neither?

Posted
I purchased the Boostauto and will be adjusting my headlights when I replace my front bumper face due to a hot water heater in the fast lane just north of the GW bridge heading north to visit family. Oh well ****** happens but the fog lights do help out big time 
I've driven that bridge before. Anything like that happens and you have no choice but to hit it. Trucks can be repaired. Are you okay?

Sent from my SM-N960U using Tapatalk

  • Thanks 1
Posted
I see that "HID LED" in the High Country, and in the Midnight Edition package for the  LT Trail Boss, but what is it, exactly?  The wider DRL light is easy to differentiate from the other thin DRLs as part of that light option group, but the HID LED headlights look like the LTZ lights.  What am I missing?  Are they actually brighter, or different at the reflectors, or both, or neither?
I have no idea. Sounds like you know more than me.

Sent from my SM-N960U using Tapatalk

Posted
14 minutes ago, Transient said:

I've driven that bridge before. Anything like that happens and you have no choice but to hit it. Trucks can be repaired. Are you okay?

Sent from my SM-N960U using Tapatalk
 

Thank you for asking we are all fine my wife in the passenger seat and daughter in back. It happens so very fast. Thank god Ed’s the truck is high enough that it just pushed the large cylindrical item out of the way and I drove around/through it. The truck is a beast and aside from the small dent no issue. I just purchased a painted replacement front bumper face off EBay awesome company came painted to match for $700 not too shabby. But back to the lights. I do believe I have the same as the high country and Midnight edition. It is the TB. LT with LED and dark bezels. Can anyone tell me exactly what I have? 

Posted
Thank you for asking we are all fine my wife in the passenger seat and daughter in back. It happens so very fast. Thank god Ed’s the truck is high enough that it just pushed the large cylindrical item out of the way and I drove around/through it. The truck is a beast and aside from the small dent no issue. I just purchased a painted replacement front bumper face off EBay awesome company came painted to match for $700 not too shabby. But back to the lights. I do believe I have the same as the high country and Midnight edition. It is the TB. LT with LED and dark bezels. Can anyone tell me exactly what I have? 
If you have a TB LT without the midnight appearance package, then your in the same boat as me -- no HID with your LED.

Sent from my SM-N960U using Tapatalk

Posted

Got it just LED NO HID for the TB LT that is some stupid ******. GM ought to be ashamed of itself. Thank you for letting me know. I will not be buying High Country lights I will live with what I have till my Tesla pick up arrives, lol. 

  • 2 weeks later...
Posted
On 4/22/2021 at 7:43 PM, bwoodsmn said:

I see that "HID LED" in the High Country, and in the Midnight Edition package for the  LT Trail Boss, but what is it, exactly?  The wider DRL light is easy to differentiate from the other thin DRLs as part of that light option group, but the HID LED headlights look like the LTZ lights.  What am I missing?  Are they actually brighter, or different at the reflectors, or both, or neither?

The High Intensity LEDs are in a projector whereas the normal LED lights are in a reflector housing. 

 

That is why the higher trims with the High Intensity lights put out a wide beam with even lighting and a defined cutoff. 

  • 3 weeks later...
Posted
On 3/13/2021 at 11:06 AM, boneill said:

Added HID LED High Country lights to mine . She’s bright .  Next fog lights and then it’s all finished up 

217F2ED1-8C6D-4AB9-AF13-FDC12C51D743.jpeg

The High Country headlights were plug and play? No extra harnesses needed? Im about to pull the trigger, these led's in my LT are trash

  • Like 1
  • 2 months later...
Posted

Having trouble finding any info for improving 2021 RST headlights. Absolutely HORRIBLE for our mountain driving with suicidal deer.  Drove truck for first time in dark last night and even with high beams the reach is so poor. Dealer adjusted levels after Bilstein's installed. Any suggestions where to search greatly appreciated.

Posted
10 hours ago, DVR said:

Having trouble finding any info for improving 2021 RST headlights. Absolutely HORRIBLE for our mountain driving with suicidal deer.  Drove truck for first time in dark last night and even with high beams the reach is so poor. Dealer adjusted levels after Bilstein's installed. Any suggestions where to search greatly appreciated.

I saw your other post.  Almost copy and paste in the other thread.  With that said, I completely disagree with what you said.  I've had my truck for a year, and do plenty of mountain driving at night.  I'm not talking hills like the Appalachians.  I'm talking the Intermountain Rockies.  I have absolutely nothing but good things to say about the led headlights, and my previous vehicle had protector HIDs.

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

  • Latest Articles

  • Posts

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