Jump to content

Recommended Posts

Posted

Been searching the forum to see what it will take to do this upgrade. I have found a lot about replacing the third brake light with the camera, but I have an additional question. Hopefully someone may have some insight. My truck already has the bed-view camera in the brake light. Would I still need to take the whole headliner down to run the wires to the mirror, or might the wires be in there and just need to be connected to the new mirror?

 

I'm really hesitant to start taking the truck apart. I want to do a speaker replacement too. 

 

Thanks in advance!

Posted
1 hour ago, nards444 said:

there was a thread on this.  I just upgraded the speakers in my 21  2500 last night.  Was really easy and did improve the sound.

Don't mean to hijack the thread.  Did you remove the Bose speakers?  If so, what speakers did you install?

Posted
1 hour ago, HiggySTL said:

Don't mean to hijack the thread.  Did you remove the Bose speakers?  If so, what speakers did you install?

 

 

no non bose system with 8in screen.  JBL in the doors and memphis for the dash.  Took me about 90mins,  if I did it again probably take me less than an hour

 

Got everything from crutchfield

 

 

Posted
1 hour ago, nards444 said:

 

 

no non bose system with 8in screen.  JBL in the doors and memphis for the dash.  Took me about 90mins,  if I did it again probably take me less than an hour

 

Got everything from crutchfield

 

 

Sounds like a nice combo!

Posted
1 hour ago, HiggySTL said:

Sounds like a nice combo!

stock speakers are a joke for non bose.  honestly they looked something out of an 80s chevette.  Ive heard guys complaining that the BOSE system wasnt worth the upgrade.

 

If you go to the crutchfield site an search for vehicle it all comes up,  just pick the ones that say compatible or whatever.  Door panels come off in like 2 mins.  Door speakers were plug and play,  dash has to be spliced.  Just make sure you order all the suggest parts with each one,  yeah you can splice and figure it all out without it,  but this way it was all there, built for it and it was an extra 10 bucks adding a few things

Posted
18 hours ago, onetactical said:

Been searching the forum to see what it will take to do this upgrade. I have found a lot about replacing the third brake light with the camera, but I have an additional question. Hopefully someone may have some insight. My truck already has the bed-view camera in the brake light. Would I still need to take the whole headliner down to run the wires to the mirror, or might the wires be in there and just need to be connected to the new mirror?

 

I'm really hesitant to start taking the truck apart. I want to do a speaker replacement too. 

 

Thanks in advance!

The bed view camera is only for bedview and that camera is connected to the VPM(Video Processing Module) directly. The Rearview camera Mirror is independent from the BCM(Body Control Module) and independent from the VPM. The mirror itself does all the processing, so yes the headliner will have to be pulled down and the CHMSL( Center High Mount Stop Lamp) will need to be replaced for the one with both cameras.

 

The first thing you should check to see is if your headliner harness has the rearview mirror plug. In my case I did not have an auto dimming mirror so the plug was glued up inside the headliner just not used. The same plug provides power for the auto dimming mirror and the rearview camera mirror.

 

I've done this mod but I don't have the bedview camera.

 

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

    • Monday looks like a good day for the dealer to test an ac issue. Hopefully it all turns out good.
    • 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
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...