Jump to content

Recommended Posts

Posted

Anyone else get repeated notifications to acknowledge agreements? Doesnt happen everytime i start the truck but often enough to be annoying.

20190923_122729.jpg

Posted

They probably update it and need an approval for each edition.

Sent from my SM-N975U using Tapatalk

Posted

I only got the acknowledge agreements screen the 1st time I set up my profile on my 2019 Silverado 1500.  I have gotten 3 software updates since and no additional acknowledgment was required.

Posted
43 minutes ago, MTU Alum said:

Does it come back after you accept the conditions during the next key cycle?

 

#iworkforGM 

Its intermittent, not every day/key cycle. Id guess every other day/4- 5 key cycles

Posted

I would recommend trying to see if your SD card is unlocked.  Power off vehicle, open and close drivers door, and let truck go to sleep (wait until green monster light is out).  Open center console, remove SD, look at SD card and there is a gray slider on left side of SD card, make sure that is in up position.  Reinstall SD and start the vehicle, accept all the messages and see if any return after a few key cycles.

 

#iworkforGM 

Posted

Mind of it's own, sometimes it's 5 or 6 starts in a row, sometimes it's good for 3 or 4. 

  • Like 1
Posted

All the freaking time!  It seems to only happen when at home, and I do have it connected to my home WiFi. Wondering if it’s updates or what not but geez it’s annoying. I was coming here to post about it as well. 

4B575505-17CF-4415-A618-C6A04E4973E6.jpeg

Posted
34 minutes ago, Chrisw253 said:

All the freaking time!  It seems to only happen when at home, and I do have it connected to my home WiFi. Wondering if it’s updates or what not but geez it’s annoying. I was coming here to post about it as well. 

4B575505-17CF-4415-A618-C6A04E4973E6.jpeg

That makes total sense now that I think about it.  It only happens when I am close enough to my house to be connected to it's Wi-Fi

Posted
On 9/23/2019 at 3:00 PM, DougFL said:

I only got the acknowledge agreements screen the 1st time I set up my profile on my 2019 Silverado 1500.  I have gotten 3 software updates since and no additional acknowledgment was required.

3 updates, jeez that's a lot in the short amount of time being out.  Any thing new in the updates that you have noticed?

Posted
20 minutes ago, Coolade said:

3 updates, jeez that's a lot in the short amount of time being out.  Any thing new in the updates that you have noticed?

Truck is a year old.  Two major over the air updates to 803.1 and then 805.1.  One Messenger App re-download and 6 Dealer installed software (recall) updates.  Most appeared to be bug fixes like "Climate Off" and reduced volume issues.  Noticed some additional info to the HUD's navigation screen but other than that no obvious big change.

Posted

That would drive me crazy.

Try blocking access on your router to see if it is indeed caused by hooking onto the Wi-Fi.

Posted

 

 

7 hours ago, MTU Alum said:

I would recommend trying to see if your SD card is unlocked.  Power off vehicle, open and close drivers door, and let truck go to sleep (wait until green monster light is out).  Open center console, remove SD, look at SD card and there is a gray slider on left side of SD card, make sure that is in up position.  Reinstall SD and start the vehicle, accept all the messages and see if any return after a few key cycles.

 

#iworkforGM 

I beleive this is the correct position. 

20190924_160541.jpg

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