Jump to content

Recommended Posts

Posted

My park assist will not activate.  The message on the DIC just says "park assist off" every time that I toggle the switch (as well as when I start the truck). Anyone else have this issue?

 

- David

2019 Sierra  Denali, with ultimate package

Posted

Sounds like the system is being turned off while being told to be on creating the message. Did you

check the Park Assist setting in the menu to ensure it was not Off? You should not get the message with this option set.

Posted (edited)

Yes, I went into "settings" and made sure that park assist was enabled.  It was.  There is an issue with my system, that I am sure.  I am trying to figure out what that issue is.

WP_20181130_07_37_45_Pro.jpg

Edited by Bell040
  • 3 months later...
Posted

Welcome - mine does that  after a car wash in cold weather , I just spray it with window wash/ ripe it and it works .  good luck.

Posted
18 hours ago, slj2008 said:

Welcome - mine does that  after a car wash in cold weather , I just spray it with window wash/ ripe it and it works .  good luck.

 

Posted

Mine truck also does this. It started after an update. Before the update it would go off like crazy after the wash for 30 min or so. Alerting all directions back and forth. My wifes new Terrain also shuts off. Not sure how to tell when it is working again. 

  • 1 month later...
Posted

I’m having the same issue, if I go into setting and manually turn it off and then back on the LED light comes on for 3 seconds and then goes off. Please advise on how to fix!

Posted

Dealership fixed mine with a update I think. Took it in and explained what it was doing and it's now working..

  • 2 months later...
  • 2 months later...
Posted (edited)

new 2019 gmc sierra park assist not working, checked all settings, read manual, called dealer said need appt to check computer,

watched some videos on troubleshooting not much help, went out to truck with windex and papertowel, wiped all sensors and all cameras and presto park assist working just fine. had just driven down a wet dirt road 2 miles, sensors didn't look dirty but must be very sensitive. if you take your truck to dealer ,make appt and waste your time the dealer will say reset computer, or something, dealer gets paid for warr. call and tech gets his time, and all they will do is clean your sensors presto its fixed. hope this saves someone the trouble and time.

Edited by kmccarthy
added text
  • Thanks 1
  • 3 months later...
Posted

Washed my truck the day it got cold here. Got a warning park assist was off. Few minutes later it was back on but constantly going off on drivers side front. I wiped clean and saw no ice on the sensors. Really annoying in rush hour traffic. I was busy and unable to get to dealer, plus taking a few days thinking it may clear itself. A few days later the weather warmed up and it’s been fine since. 

I chalked it up to washing in the bitter cold. 

Posted
On 3/10/2019 at 2:53 PM, slj2008 said:

Welcome - mine does that  after a car wash in cold weather , I just spray it with window wash/ ripe it and it works .  good luck.

This goes back to the NNBS, I have the exact same thing on my 2008 right after a wash, then it goes back to working whenever it feels like, its just a known issue happens on the SUVs aswell, poor engineering. 

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

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