Jump to content

Recommended Posts

Posted

I have a couple of questions about the bank of switches in the 2020 AT4, located right under the temp controls.

 

1. Has anyone taken that part of the dash apart? If so, any suggestions or pics?

 

2. Are the two “empty” switches on each end purely for decoration or are they potentially ready to be wired?

 

These are the ones I’m referring to:

 

 

e99a82611170beaf40c6c59ef979af13.jpg

 

 

 

Thanks!

 

 

 

Sent from my iPhone using Tapatalk Pro

Posted
Far left is for the Lane Keeping on/off. Far right is for the power running board.

Thank you. I don’t have either option so now I just need to disassemble that part of the dash...wonder if anyone has done that yet.


Sent from my iPhone using Tapatalk Pro
Posted

i was wondering the same thing and im interested in you're results

wanting to add a switch for the grill lights and that spot would be perfect

 

Posted

Huh... My 2020 has one large hill decent control... Could that be replaced with a power running board switch?3fc627fb8ff937d1733a17b608fb7b80.jpg

Sent from my Pixel 4 XL using Tapatalk

Posted

I decided to use one of extra switches in the switch cluster. I want to save those for future adds (power boards and maybe a winch). Instead, I ran an illuminated toggle directly below the parking brake button. Easy to reach, out of the way, and low enough that the switch illumination does not affect interior cab lighting at all, night or day.

c625483145a8a1b9994ce287556e6197.jpg848d318b321f20a38dee8257480ff2a8.jpg


Sent from my iPad using Tapatalk Pro

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

    • 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.
    • Just don't turn the steering wheel as much?
    • Rockauto bud. I pass local stores for parts.   Findya something online. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...