Jump to content

Recommended Posts

Posted

Love that we can now keep Camera on for monitoring stuff, even though you can't change much while moving, but hate that it no longer remembers Intellibeams On setting. I always have to turn it on now. 

Posted

What is different with the camera function?

Posted
On 3/22/2023 at 11:22 PM, MrLeadFoot said:

Love that we can now keep Camera on for monitoring stuff, even though you can't change much while moving, but hate that it no longer remembers Intellibeams On setting. I always have to turn it on now. 

Do you have the firmware info? Is this for the new trucks or the 19-22.5? (yours says 22, but i don't know if that is pre/after refresh.)

Posted
On 3/22/2023 at 11:22 PM, MrLeadFoot said:

Love that we can now keep Camera on for monitoring stuff, even though you can't change much while moving, but hate that it no longer remembers Intellibeams On setting. I always have to turn it on now. 

 I hate that it doesn't remember intellibeams!

Posted

Yes I just realized the Intellibeams are shutting off when the ignition goes off. SO not sure why they did this.

 

Maybe so we use them less I guess because I forget to turn them on now.

Posted

I looked for a place to submit 'bugs' and/or feature requests and couldn't find anything other than calling or snail mail. I tried the call them route and that was a waste of time. Anybody know how to submit things like this to them?

Posted

I updated Wednesday morning. Everything seemed to go well. I see people talking about the Intellibeams , I tested mine tonight and it seems to stay active after a restart. The best part of the update is it fixed my finicky wireless phone charger. I've had this truck for 2 weeks and that damn charger was driving me nuts . Constantly cutting out. There was one sweet spot where it would work. After the update as long as the top of the phone is down it charges no matter where it sits in the charger. This is with the case on the Pixel 7 pro.

Posted
On 3/27/2023 at 6:43 AM, smit303 said:

What is different with the camera function?

Used to turn off 8 seconds after you start moving. Now, it stays on while driving, presumably so you can monitor stuff in the bed. Once moving, it limits view option changes, but retains last setting even if you had selected forward view. 

Posted
On 3/27/2023 at 10:39 AM, 1454 said:

Do you have the firmware info? Is this for the new trucks or the 19-22.5? (yours says 22, but i don't know if that is pre/after refresh.)

Sorry, mine is a refresh. I will update my profile to reflect that. 

  • Like 1
Posted
On 3/31/2023 at 3:36 PM, Louie Foster said:

I looked for a place to submit 'bugs' and/or feature requests and couldn't find anything other than calling or snail mail. I tried the call them route and that was a waste of time. Anybody know how to submit things like this to them?

I think they only "listen to" repair orders at the service department. Too bad because it might save them a lot of wasted time having us tie up time in the service department just to get a bug noticed while someone who really needs something fixed has to wait. 

Posted

Is this a OTA software/firmware update? I just installed the update that allows me to continue receiving updates, on my 2023 Sierra, is this a newer version?

Posted (edited)

I'm not actually not sure because not too long ago dealer performed a recall update pertaining to daytime running lights not turning off at night, as well. Shortly afterward I noticed 3 changes that supposedly were not part of the recall. In fact, my inner tailgate not locking out was something no dealership could fix, and GM was "aware of it, but had no fix". Then, suddenly the tailgate issue was fixed, so I'm thinking it was an OTA.

 

Since yours is 2023, maybe you didn't need the update. Does your inner tailgate lockout using the "hold for 3 seconds" instructions? Does your camera stay on while driving? 

Edited by MrLeadFoot

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,758
    Total Members
    8,960
    Most Online
    Randy Ginoza
    Newest Member
    Randy Ginoza
    Joined
  • Who's Online   4 Members, 0 Anonymous, 2,189 Guests (See full list)

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