Jump to content

Recommended Posts

Posted (edited)

That’s stupid. I feel like if you buy a vehicle with this option, that should be the only time you have to pay for it.

Edited by steelerdude15
  • Like 1
Posted

I don't think it's that stupid.. it requires constant updates, perfecting it, maybe enhancing it so that you could type in Starbucks and have it go and fetch you a cup of coffee. I sure as ****** would pay $25 for that.

  • Thanks 1
Posted

Yeah this is a reason most people won't use it I bet. Limited roads to use it on and a subscription service. Just like most people don't pay for Onstar after the trial period.

  • Like 1
Posted
On 1/7/2022 at 10:06 PM, Wiggums said:

I don't think it's that stupid.. it requires constant updates, perfecting it, maybe enhancing it so that you could type in Starbucks and have it go and fetch you a cup of coffee. I sure as ****** would pay $25 for that.

I would have had no issues paying it until dealing with this frustrating truck. I have no problem paying 25 a month for this, but they should really have considered legacy vehicles too. Heck, if I could get my adaptive cruise engaged, I would pay for updates now that make the braking less hesitant and better lka. 

  • Like 1
Posted
On 1/7/2022 at 8:51 PM, steelerdude15 said:

That’s stupid. I feel like if you buy a vehicle with this option, that should be the only time you have to pay for it.

 

On 1/7/2022 at 9:06 PM, Wiggums said:

I don't think it's that stupid.. it requires constant updates, perfecting it, maybe enhancing it so that you could type in Starbucks and have it go and fetch you a cup of coffee. I sure as ****** would pay $25 for that.

 

 

This is unfortunately the way of the future. Unless legislation steps in to do something about it.

But like Wiggums mentioned, it does ensure that you get consistent updates into the future. I'd rather pay the $25 and have continuing updates as opposed to not paying and having a product that never updates. Reminds me of the past when in-car Nav systems would only come pre-loaded with a certain map and it would be outdated after a few months/years when new development happened.

 

Just be thankful it's not Tesla who's charging something like $250/month for their FSD.

Posted

I don't much understand the interest in the automated driving anyways.  I would never use it.  When I drive somewhere, I like to do the driving.  Give me a decent audio system and that is all I need.

  • Like 3
Posted
6 hours ago, 453030 said:

I don't much understand the interest in the automated driving anyways.  I would never use it.  When I drive somewhere, I like to do the driving.  Give me a decent audio system and that is all I need.

To each their own. I for one, absolutely love autonomous driving systems.

I too love to drive, but that's what I have my manual vehicles for that I can take out on the weekends.

 

But when I'm doing an hour commute each way to work in stop and go traffic...I want to kill myself. And when I've had the pleasure of using a vehicle that has autonomous driving in those conditions, it improves my quality of life dramatically lol.

Posted (edited)
On 1/7/2022 at 7:06 PM, Wiggums said:

I don't think it's that stupid.. it requires constant updates, perfecting it, maybe enhancing it so that you could type in Starbucks and have it go and fetch you a cup of coffee. I sure as ****** would pay $25 for that.

Better hope it's better than Tesla's system so it doesn't run into a white semi trailer.  A few people have already been killed this way. 

 

Any idea of SuperCruise is programed to handle a flat tire?  Is the TPMS system going to work with it and pull over on a safe area so you can change it, or are you going to be forced to take control when something unexpected happens?

Edited by Transient
Posted

One of my favs " Remove all the warning labels from products and let things sort it's self out." 

Posted
On 1/18/2022 at 3:59 AM, diyer2 said:

One of my favs " Remove all the warning labels from products and let things sort it's self out." 

If this happened everybody would stop wishing for a giant earthquake to happen and sink California into the ocean.  Property values would plummet in that state, too.  I say this while in my home in California, too.

Posted

I thought I heard it was $25 a month on top of an OnStar subscription.  Can anybody confirm or deny that?

 

And I heard that GM gathers it's map data from user vehicles and then charges us to use it.  I think we should be able to charge GM to gather our vehicle's data if they're going to charge us to use it.

  • Like 1
Posted

I have an Ultimate held through GMC at my local dealership and my main draw back with the truck is Supercruise.  I don't want it but it's standard with the package.  I still have time to decide.  My other gripes are Carbon Pro Bed(cool but I don't need it), Vader Chrome Grill(love it but why doesn't the lower grill match it), and no Panoramic sunroof...like wtf?  I am searching for a Limited F150 to check out as well.  RAM limited is amazing but I cant bring myself to buy a RAM.

Posted
3 hours ago, 603Denali said:

I have an Ultimate held through GMC at my local dealership and my main draw back with the truck is Supercruise.  I don't want it but it's standard with the package.  I still have time to decide.  My other gripes are Carbon Pro Bed(cool but I don't need it), Vader Chrome Grill(love it but why doesn't the lower grill match it), and no Panoramic sunroof...like wtf?  I am searching for a Limited F150 to check out as well.  RAM limited is amazing but I cant bring myself to buy a RAM.

Don’t use it then? That’s the point of getting the Ultimate. You get all the options. Get an SLT or Denali if you don’t want all that stuff?

  • Like 1

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

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