Jump to content

2024 Silverado 1500 RST - Camera system fails constantly

Jacob Marshal
 Share

Recommended Posts

Jacob Marshal New Member

Jacob Marshal

Posted
Posted

I’ve been trying to get the dealer to fix this issue, but at least 75% of the time the back up camera system doesn’t work and displays a black screen with a red line through a camera image. Of course, every time I schedule an appointment and bring it in, it starts working again and they say they can’t diagnose an issue without seeing it. 
 

I’ve been told now there’s a service bulletin out, which is still listed under the title of an investigation, and there’s nothing they can do until they receive word from Chevrolet corporation.

 

Anyone else experiencing this issue or have resolved this with the dealer?

IMG_9018.png

IMG_9018.png

tjonesdfw Enthusiast

tjonesdfw

Posted
Posted

I hate to be the bearer of bad news, but there is thread after thread about issues with the camera systems on these trucks.  Mine is a 2021 with the surround view system, and has been through multiple camera module replacements, a rear wiring harness, multiple new tailgate cameras for faults and shorts, and a driver side mirror camera.  During one of the camera module replacements, they also did the rear window leak repair because they thought the modules were getting wet and causing them to fail.  To date, nothing has fully fixed the camera issues with our truck.  

Bikerjon Enthusiast

Bikerjon

Posted
Posted
15 hours ago, Jacob Marshal said:

I’ve seen a few threads on the topic, guess I was hoping after 3-5 years of the same incidents GM would have solved the issue. That is incredibly disappointing. 

I had my rear camera fail on a 2021 Trail Boss. I usually noticed the failure first thing in the morning when the truck was cold. I took it into the dealer and thoroughly described the problem. I dropped the truck off at the end of the day to be tested first thing in the morning. The camera failed for them first thing in the morning and they had to order a camera which pissed me off considering how many backup cameras were failing. But the moral of my story is you need to pay attention to when the camera fails so you can reproduce the failure at the dealer. If the dealer cant verify the complaint they will not repair anything.

Jacob Marshal New Member

Jacob Marshal

Posted
  • Author
Posted

Unfortunately in my case, there is no common method associated with these failures. I can’t predict or reproduce the symptoms. Mine has gone up to 5 days of not working, to working off and on throughout the day. 😕

tjonesdfw Enthusiast

tjonesdfw

Posted
Posted

I also recommend taking video with your phone of each incident if possible.  Time and date stamped videos with commentary like Bikerjon said of condition, and a description of what's going on is what finally got my dealer to start chasing it down despite not being able to replicate the issue during some of my service visits.  

GMCustomerService Senior Enthusiast

GMCustomerService

Posted
Posted
On 4/8/2025 at 9:52 AM, Jacob Marshal said:

I’ve been trying to get the dealer to fix this issue, but at least 75% of the time the back up camera system doesn’t work and displays a black screen with a red line through a camera image. Of course, every time I schedule an appointment and bring it in, it starts working again and they say they can’t diagnose an issue without seeing it. 
 

I’ve been told now there’s a service bulletin out, which is still listed under the title of an investigation, and there’s nothing they can do until they receive word from Chevrolet corporation.

 

Anyone else experiencing this issue or have resolved this with the dealer?

IMG_9018.png

IMG_9018.png

We know how upsetting your camera concerns must be, and we would like  to connect with your dealership directly to learn more. When you have a minute, please send us an email to [email protected] with your VIN, along with your dealerships name and address. Once we have this, we can determine the best next steps together.

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