Jump to content

Recommended Posts

Posted

So last night I hoped in the truck after shopping at a store and happene to turn the wheel. Well. There was a vehicle parked in front if me and I noticed the lights dimmed while turning the wheel from side to side. Do these new trucks have a auto dim feature that dims the lights while turning so that they aren't so bright to oncommers in a turn? This was the first time I noticed it and haven't read anything about the subject so I thought I'd ask.

Posted

The lights were probably just dimming a bit due to the electric power steering working harder as you turned. Never heard of headlights dimming to turn...seems unnecessary to me.

Posted

Yep, like Dan said. The steering is now electric power assist, instead of hydraulic. So that's normal.

Posted

Fair enough and I had thought about that but didn't think it would really dim the headlights as much as it did.

Thanks guys

Posted

I have always wondered about the moron engineer that says..."hey, lets add another high amperage thing to the already over taxed electrical system". LOL

Posted

Not the engineers fault. You have our over-reaching, nanny govt. to thank for this type of thing. They put out CAFE standard mandates and the auto industry has to meet them by law. So expect lighter, flimsier everything on your trucks for as long as they can continue to build them. Full size truck days are numbered if we continue this way.

Posted

While we are talking about headlamps. I'm not sure I like the way the low beams work on my GMC. Out on the interstate its ok, but if you get on some hilly county roads I don't like the way the shutter cuts off the light. Like drawing a line across, completely dark above. Haven't drove it much at night yet, maybe I'm just not use to it. Anyone else notice what I mean?

Posted
While we are talking about headlamps. I'm not sure I like the way the low beams work on my GMC. Out on the interstate its ok, but if you get on some hilly county roads I don't like the way the shutter cuts off the light. Like drawing a line across, completely dark above. Haven't drove it much at night yet, maybe I'm just not use to it. Anyone else notice what I mean?

 

 

All projectors seem to be like that. Even the Subaru I had before my current 2011 had a very sharp cutoff and there was no shutter- the low beam was projector and the high beam a normal reflector.

Posted (edited)

All off the alternator...

 

Sent from my SCH-I535

 

Why is it still belt driven then? So all these fancy components and it does not make it's own power?

 

"The belt-driven electric power steering system features an integrated

electromechanical power steering unit, containing the power steering

control module, its sensors, the power steering motor, a belt drive and a

ball nut mechanism."

 

Source... http://sandyblogs.com/techlink/?p=2147

Edited by Blue Sierra Owner
  • 11 months later...
Posted (edited)

FYI: I have upgraded the ground wire from the frame to the battery from the original 8AWG to 2 AWG OFC as part of an audio build (of course, then I decided just to ground straight to the battery, haha). After this, reduced if not eliminated headlight dimming and my transmission seems to shift with less clunkification, although that could just be my brain making that part up, but I'll take it. My 2011 Silverado's headlights dimmed when I first turned on the signals... no other car I have ever had did this. My 2014, same thing. Baffles me that this was not engineered out - stupid and embarrassing.

 

Later I I also added a 2AWG wire from the engine block to the battery and added another OEM grounding strap to the OEM location. This did nothing but cost me time.

 

I believe the lights at least if not the steering and tranny ground to the frame so their ground would be going through the 2AWG to get to the battery (in theory).

Edited by sirbOOm
  • Like 1
Posted

This is insane...so if the belt snaps.....then what???

You lose power assist. There is still a mechanical connection to the rack from the steering wheel.

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
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Forum Statistics

    250.4k
    Total Topics
    2.7m
    Total Posts
  • Member Statistics

    342,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   5 Members, 0 Anonymous, 2,134 Guests (See full list)

  • Latest Articles

  • Posts

    • Paid $2.72 for E85 today.
    • Welcome back! No, it definitely doesn't pass the sniff test. Even "ceasefire" needs an alternative definition these days.    $5.29 at Kroger today
    • That makes sense, and I think you are describing the real product problem. Capturing data is the easy part. If the owner or technician has to manually dig through five minutes of millisecond-level logs, the product has already failed. The device would be at the ECM harness, not at the OBD port, so I agree that data retrieval and event marking need to be thought through carefully. The way I am thinking about the architecture is: The recorder itself should not depend on a phone, app, Bluetooth, Wi-Fi, or cloud connection to capture the event. It should always keep a local rolling buffer and lock the event locally. A button, phone app, or small cabin device would only act as an event marker. If the driver feels a stumble and presses the button 10–30 seconds later, the pre-buffer has to already contain the useful data. For data retrieval, the practical options would be a sealed service USB lead, Wi-Fi download, or a phone/cabin companion device. I would not expect the owner to remove the ECM-side module or work with raw files directly. The cloud or AI side would be for interpretation, not for capturing the event. The truck may have no connection when the issue happens, so the evidence has to be saved locally first. After that, cloud processing could help decode the data, compare it against baselines, and generate a readable report. For the first version, I would keep the automatic triggers conservative and objective: driver event marker bus-off error passive voltage drop / brownout device reset FIFO or queue overflow a normally periodic message disappearing side-to-side communication mismatch, if the topology supports that For “learning normal,” I agree with your point, but I would not want to overclaim it as automatic root-cause diagnosis at first. A realistic first step would be learned baseline comparison for that specific vehicle and operating condition. For example, a value would only be compared against similar conditions: RPM range load / MAP throttle position gear / vehicle speed coolant and oil temperature battery voltage AFM/DFM state, if decoded and validated Then the report could flag things like: this periodic message disappeared compared with its normal timing this value deviated from this vehicle’s normal range under similar conditions the same abnormal pattern repeated after the same type of event the anomaly occurred together with voltage, oil-pressure, misfire, or communication changes But I would still call that “abnormal pattern detected,” not “replace this part,” unless there is enough validated repair data behind it. So the intended product would not be “here is a huge log.” It would need to be an event package: what triggered the capture how much pre/post data was preserved what changed before and after the event whether the device itself reset, overflowed, or saw a bus error selected graphs around the event raw data only as supporting evidence From your perspective, what would make this kind of report useful instead of just another datalog? For example: What are the top 5 parameters or events you would want highlighted first? Would you trust a learned baseline for that specific vehicle, or would you prefer fixed thresholds? How much false-positive flagging would be acceptable before you stopped looking at the reports? What would a one-page report need to show for an independent shop to take it seriously? For misfire, AFM/DFM, oil pressure, or U-code complaints, what would you want the tool to flag automatically?
    • 2024 Silverado 2500 HD LTZ grille no camera Parts list   84603331 84913656 84913657 84913654 84913655 84911567 84911568 85646092 85646093 85797921 85797922   11570637  x10-15   grille/bumper bolts 11546500  x10      grille clips 11571006  x10      push/retainer clips 11546454  x6       nut retainers 11611609  x6       M5 bolts 11610700  x6       molding/trim retainers
    • And use RA's 5% discount code if you buy from them.  google for the code, one is always available.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...