Jump to content

Recommended Posts

Posted

Hello all, I am wondering if anyone here can help with a fix for my issue. I have spent some time googling over the last year or so as this has been an issue on and off, it seems this issue happens across any type of GM Vehicle.

 

my lines have gone which tell me where I’m going when I park. The screen displays the camera just fine, but there is a blue egg time in the top left corner and the button on the bottom right that toggles the lines view on and off is greyed out. 
 

this has been happening for more or less the whole time since I got this refreshed 2022 in 2022 however recently the lines went and never came back, usually it fixes itself.

 

took it to a dealer and they didn’t help, simple answer was to blame it on my lift kit. They ignored the fact that it has been working for 90% of the time, It would just glitch once in a while, not often… but this time it’s not fixed itself

 

I have a GM Case open too, but it’s just hard work… 

 

Any guidance would be greatly appreciated.

image0.jpeg

Posted

With the GM case, AND the dealership, be respectful and keep asking for 'help'. If they want to push back on the lift kit, and they likely will, ask if they can share any details as to how/why it would interfere. Explain that you want to know the details so you can discuss with the kit manufacturer to get their help as well.

 

Dealerships like to throw blame around but don't like to have to provide the details to justify their statements. The entire reason they don't want to cover it under warranty is because they want to charge YOU for the work (GM doesn't want to pay if they don't have to, and the dealership makes more profit on non-warranty work).

 

Just don't argue with them or let things get emotional. Stick to facts, remain calm, and keep expressing things in terms of "I need your help here".

Posted

Thank you for the reply! Attached here is the summary from the dealer. Basically I read this as, because I had the park assist retro fitted (chip shortage when I ordered the truck) they then had to recalibrate everything, which is why the lines don’t work.

 

the point which is being ignored is 1) this lines issue first happened 2 years ago, the park assist was installed in  November 2023. The lines have continued to work 90% of the time until last week. This is why I think they are wrong, and it’s also noting to do with the lift.

 

they mention a hard error in the system preventing the lines from displaying, which ‘cannot’ be cleared…

 

doesn’t add up to me! I’m wondering if they could just refresh? Recalibrate? Reboot the modules or something … they seemed unwilling to try, and told me I was lucky the camera even works with the truck this high up…

 

 

IMG_7686.jpeg

IMG_7687.jpeg

Posted

Ugh... Messy.

 

- Do you have any work orders for the lines disappearing PRIOR to Park Assist being added?

- PRIOR to the lift being installed?

 

Anything you can provide that shows that the problem occurred before anyone touched anything would possibly help you here.

 

They told you there's an error but the work order shown implies it's a "setting." Terminology matters... settings have configurable options, errors indicate problems / failures. Which is it? 

 

It seems that the tech is acknowledging that installing the lift made no actual changes to the camera system. Once the Park Assist was installed, however, they had to re-calibrate the camera to account for the changed height of the truck. Why would raising the truck and adjusting the camera angle turn that feature off? And, can you PROVE that it worked after the Park Assist was installed at any point?

 

Dealership Service Writers are useless for discussing this stuff - they spew all kinds of bullshit that I swear they make up on the spot and clearly have absolutely no clue what they're talking about. The Service Manager is likely just as useless (the one at the dealership where I bought my truck tried arguing specific repair items with me claiming that GM was "never" going to address them yet I not only had them addressed, but had them addressed at -that- dealership).

 

Speaking to the Shop Foreman may get you some details, and the actual Tech as well. You could request through GM Customer Assistance to speak with either the Field Tech (or any field tech) or the District Manager that covers that dealership to better understand the details and the options. Anything that a Field Tech offers up is very likely backed by documented details that they could provide to you.

Posted

Unfortunately I never had any previous work orders for this - it was never something that could be recreated! It would happen one day, then seconds later go back into reverse and it would be fine again for months.

 

all of the explanation about the park assist was kinda pointless because, it happened on and off before, and on and off after, just for now, it seems to be off and not back on!  
 

the fact it’s all over other forums makes me wonder what the issue really is! 
 

it even says on the attached Cadillac bulletin ‘may be caused by a software anomaly’

 

just needs a ctrl+alt+delete and a reboot!! 

IMG_7663.png

IMG_7665.png

IMG_7666.jpeg

IMG_7668.png

IMG_7667.png

Posted

The dealership has claimed that there's an error that "can't be cleared" and that would mean it will never work. So, all you need now is for it to work... Once... When you can get video of it working on your phone. Be sure to add commentary as to the time and date, and capture the mileage on your truck in the video. This would all potentially negate the "it will never work again" claim of the dealership.

 

As an aside... There's been a MASSIVE problem with GM's OTA updates for their trucks. I bought my truck in late October, there was an OTA update, and shortly after I started having weird error codes showing up and setting the Check Engine Light. The dealership dismissed it as "no code" (and they don't know how to troubleshoot without a code or a TSB that explicitly calls out the exact issue) and gave the truck back. On the way home, it "blew up" my dash with every error code known to mankind, reduced power, etc. They had to get TAC involved for very detailed troubleshooting (I took the truck back to them -immediately-) and determined that the Gateway Communication module had a corruption and needed to be re-flashed.

  • Thanks 1
  • 7 months later...
Posted

@2022LiftedRST Did you get any resolution to this? The dealer installed my leveling kit today and I noticed the same thing - no guidelines, disabled button for them, and the hourglass. Going to call tomorrow and see if they messed with any calibration, I can’t imagine that it can detect that it’s sitting a few inches higher. It’s a pickup, loading the bed or towing could just as easily affect its angle!

Posted (edited)

Or the setting got changed. 

The are several selections available.

One of the options that can be selected is 'no guidance lines' 

 

I don't know which one is the default.

 

Edited by redwngr
Posted

This button on the far right that’s now disabled? Or is there some other system setting I haven’t found yet? 🤔

IMG_0875.jpeg

Posted (edited)

Hello!

 

I do indeed have an update!

 

a few weeks ago I had the front of the truck lowered back down a bit to stop a vibration I had, and the camera lines came back and have worked as normal for 95% of the time since

 

looks like the dealer was right! The truck was too high. I was about 12” lift on the front. I switched to adjustable struts and the shop I go to recons they lowered it back down 2-3 inches or so.

 

sometimes my lines disappear for a day or so, but I’m guessing that’s due to the fact I’m still around a 10” lift on 37s so that must be close to the limit for the camera knowing where it is. 
 

 

Edited by 2022LiftedRST
Posted

For example I parked last night with my lines. Woke up this morning they had vanished for the first time in a while.. home again now and the lines are back

 

give your lines a few days to see what they want to do 🙂 

 

I got used to life with no lines, would rather have a bigger truck than the lines 😂

Posted

I only went up ~3.5" (including tires) and kept a little rake, nowhere near 10" and 37s. I haven't unloaded the old tires from the bed yet, hopefully that makes it happy. 

 

1 hour ago, 2022LiftedRST said:

I got used to life with no lines, would rather have a bigger truck than the lines 😂

 

Lol same, I wouldn't want to go back, but damn...I really like that feature. Stupid computers. 🤷🏻‍♂️

Posted
On 11/21/2024 at 3:37 AM, 2022LiftedRST said:

Hello!

 

I do indeed have an update!

 

a few weeks ago I had the front of the truck lowered back down a bit to stop a vibration I had, and the camera lines came back and have worked as normal for 95% of the time since

 

looks like the dealer was right! The truck was too high. I was about 12” lift on the front. I switched to adjustable struts and the shop I go to recons they lowered it back down 2-3 inches or so.

 

sometimes my lines disappear for a day or so, but I’m guessing that’s due to the fact I’m still around a 10” lift on 37s so that must be close to the limit for the camera knowing where it is. 
 

 

Same is happening to me no guidelines since vehicle got lifted front 1.5inch and rear 1inch so my truck is almost leveled, i will try to replicate that solution by lowering air pressure in front tires and increase in the rear. I'm wondering if it has to be something with vehicle level or just a raised front.

  • 2 weeks later...
Posted

I purchased a 2025 Silverado 1500 LTZ. Most often the grid lines for the backup camera are not visible. I also noticed an hourglass at the top left corner of the camera display. The button to enable grid lines is grayed out. Now, on a rare occasion the system loads, the hour glass is gone and the grid lines are visible as it should be. I took it to the dealership and they didn’t know what to do about it and said “give it some time”, so I waited a month and as expected no change. I called the dealership again and they said to call GM Customer Support. GM Customer Support said to take it to the dealership so they could open a case. I now have another appointment, but I have zero faith that anybody has a clue what to do.

 

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,759
    Total Members
    8,960
    Most Online
    DM22
    Newest Member
    DM22
    Joined
  • Who's Online   3 Members, 0 Anonymous, 1,615 Guests (See full list)


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