Jump to content

Speed limitation deleted?


Recommended Posts

Posted

Not a good idea I know but I don't plan to hit that all the time. I do a lot of road trips, sometimes I need to pass a car or speed up for other reasons and the 98 miles speed limit is there.

Posted
3 minutes ago, newdude said:

It was so hard it sent the driveshaft through the bed floor and took the rear of the transfer case with it...

Wow

Posted

It’s fine to break 100. It’s limited due to tire speed rating. If you changed some things on the truck there’s no reason why it shouldn’t be allowed to go over 100 in a controlled environment. Ie: track. I don’t agree with it on public roads- don’t be that dick driver.

Posted

I can see where the OP is coming from. I usually drive at 85 mph out in the desert. There are times the highway would go downhill, allowing me to reach 100 mph with my steady foot, then when it levels off, the truck would go back to 85 mph. Likewise, going uphill with my steady foot, it would go down to around 70 mph. Anyhow, it is annoying when the computer refuses to allow it to hit 100 mph. I haven't hit that in my new truck, but my previous Ford F-150 was limited at 105 mph. I only hit it once by accident so I know.

Posted

Seeing how you can't do anything with the new body style 2019's computer, that is why you haven't seen a real answer on how to remove it.

 

If they ever do a work around, I'm sure it'll be just like the ZR1 and LP5 fixes where it'll cost you a few grand just to change a limiter lol.

Posted

Don't to faster then 100.  Absolutely no reason to.   Except maybe on a track or controller environment.

 

Ive driven very fast a lot ;)

 

Your biggest need when passing is acceleration, not top speed.  If you pass someone going 80 so you can go 85, you dont need to pass them at 105.  

 

Also,  most single lane highways top out at 55mph or 60mph....

 

Anyway I get your point,  Im sure your speedometer goes past 98mph right?  Its false advertising with a limiter...

 

Posted
1 hour ago, greatmizzou said:

Don't to faster then 100.  Absolutely no reason to.   Except maybe on a track or controller environment.

 

Ive driven very fast a lot ;)

 

Your biggest need when passing is acceleration, not top speed.  If you pass someone going 80 so you can go 85, you dont need to pass them at 105.  

 

Also,  most single lane highways top out at 55mph or 60mph....

 

Anyway I get your point,  Im sure your speedometer goes past 98mph right?  Its false advertising with a limiter...

 

Yeah totally false advertising.

Posted

I have hit the 98 MPH limiter passing someone that was doing ten under in the left hand lane here where our speed limits in some areas are 80 that being said... keep your eyes peeled... we'll likely have something you'll like very soon :)

Posted
1 hour ago, GTPprix said:

I have hit the 98 MPH limiter passing someone that was doing ten under in the left hand lane here where our speed limits in some areas are 80 that being said... keep your eyes peeled... we'll likely have something you'll like very soon :)

Hope first responders don't have to peel you out of the truck very soon.

Posted
9 minutes ago, mafd2 said:

Hope first responders don't have to peel you out of the truck very soon.

It was a clean pass; I promise :) But at the same time I do agree with you. Generally people around here are going a minimum of 85-90 on our expressways; its fast. 

Posted

Optimistic speedo is nothing new....

 

I always though it was a styling thing, and maybe to get the needle in the easily viewed area at speeds it could probably travel. 

 

With this one, if the needle is leaning to the right....you might be going faster than the factory installed bias ply tires should run (for very long)... 


Possibly a '68 pontiac.

 

 

Image result for 1968 camaro speedo

  • 5 weeks later...
Posted

Mine stops at 112. Yes, I tested it. No, it was not on a “track”... it was on some empty divided highway in rural Texas. 

 

Archived

This topic is now archived and is closed to further replies.

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