Jump to content

Recommended Posts

Posted

front center parking sensors act up sometimes.

ill be stooped and it will just start going off.

doesn't happen consistently.

 

no its not blocked by something.

no its not wet.

 

 

is it as simple as a bad sensor?

Posted

On my ‘16 I got the message in my DIC to check my sensors and (if I recall correctly) neither the fronts not backs worked.  

 

Took it it to the dealer.   One in front bumper was bad.   Swapped and I rolled.   All good.  Warranty.   

Posted

I had one bad sensor on my 2017. Every time I would wash it or drive in the rain I would have issues for a day or so. I took it to the dealer and they couldn't find anything wrong, Went back to the car wash and got the same problem. I took it back and showed them the pics of the messages I was getting and told them to wash the truck. They ended up changing one sensor and all has been fine since.

Posted

Same thing was happening on my 16. Dealer found a TSB and reprogrammed. It stopped the issue, but I noticed that it no longer beeps with every increase of the "sonar" waves on the DIC. It only beeps when I'm in the final/"red" zone. Don't really like how it operates now.

  • 1 year later...
Posted

well i finally figured it out

 

i swapped the inside sensors to the outside and outside to the inside. and now the right sensor is randomly going off. 

so i ordered a replacement from advance auto for $30 shipped to my door. $43 regular with 25% off and a $5 coupon.

 

oem one is like $140 so ill give the aftermarket one a shot.

Posted

So the one from advance is identical to oem both are bosch one just has a GM logo and part number. 

So no reason to buy the GM one for 4 times the price at advance Auto.

IMG_20190820_164631147.jpg

  • 1 year later...
Posted

Don't paint over paint like you have. If ill form a solid connection to the side of the sensor. Try scratching the paint off in a ring around the sensor head to fix it. Also water in the housing area is known to cause problems. Try taking the sensor out cleaning the housing , sensor and silicone ring and puting it back together.

Posted
15 hours ago, JJS77 said:

Don't paint over paint like you have. If ill form a solid connection to the side of the sensor. Try scratching the paint off in a ring around the sensor head to fix it. Also water in the housing area is known to cause problems. Try taking the sensor out cleaning the housing , sensor and silicone ring and puting it back together.

i fixed it awhile ago. it was a faulty sensor. i panted the new one to match been working perfectly for 2 years now.

  • Like 2
  • 7 months later...
Posted
On 6/9/2018 at 7:21 AM, Boardmember said:

On my ‘16 I got the message in my DIC to check my sensors and (if I recall correctly) neither the fronts not backs worked.  

 

Took it it to the dealer.   One in front bumper was bad.   Swapped and I rolled.   All good.  Warranty.   

Do you happen to have the part number they used? I'm having the same issue but am getting different part numbers!

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