Jump to content

Recommended Posts

Posted

So I was thinking about calibrating my speedometer but then this happened. I went from stock TB tires 275/65/18 to 295/70/18. When I was on stock, my speedometer always matched the speed that displayed on my Waze Apple CarPlay. Then when I got my new tires, I noticed that the speed was off 3-4 MPH at higher speeds, slower on speedometer than Waze, which was expected. This happened for about a week. Then suddenly, my speedometer speed is now matching with my Waze speed. Waze has never given me any issues before and it estimates speed based off of GPS tracking. Also, it feels like I’m going 75 MPH when the speedometer says it too but I don’t trust that. Does anyone know if the newer trucks calibrate on their own or am I crazy? I almost want to have someone drive next to me and tell me their speed to compare to mine.

 

 

Sent from my iPhone using Tapatalk

Posted
You could also try a separate speedometer app to verify...


Sent from my iPhone using Tapatalk Pro

Any recommendations on an APP that has worked well?


Sent from my iPhone using Tapatalk
Posted

The new trucks do not have the ability to synchronize their speedometer if you switch tire sizes. It has no idea what size tire you put on there. Both Rough Country and Hypertech sell speedometer calibrators. I’ve had better results with Hypertech

Posted
Do you have an apple watch? We put my wifes on the bicycle app and it matched waze for me.

Yeah I’ll give that a try as well thanks


Sent from my iPhone using Tapatalk
Posted
The new trucks do not have the ability to synchronize their speedometer if you switch tire sizes. It has no idea what size tire you put on there. Both Rough Country and Hypertech sell speedometer calibrators. I’ve had better results with Hypertech

That’s what I was thinking too but just can’t explain why Waze was accurate for the 7 months I’ve used it then the day I changed my tires it was inaccurate for a week afterwards but now back to matching my speedometer. I was planning on using Hypertech but wanted to test a few things out before I spend $200+


Sent from my iPhone using Tapatalk
Posted
1 minute ago, RadoPhan said:


That’s what I was thinking too but just can’t explain why Waze was accurate for the 7 months I’ve used it then the day I changed my tires it was inaccurate for a week afterwards but now back to matching my speedometer. I was planning on using Hypertech but wanted to test a few things out before I spend $200+


Sent from my iPhone using Tapatalk

I mean even if the speedometer can somehow calibrate itself (which I find incredibly unlikely) you still need a calibrator to get your shift points correct and get your ESC set to a larger tire

Posted

Just a note, but read through your warranty, as I believe you'll find at least part of your warranty is void if the odometer isn't calibrated properly.

  • 1 year later...
Posted

If you have a Global B truck it has the ability to recalibrate for different size tires using the OnStar GPS signal, wheel speed sensors, and other sensors. I can't remember if it is ignition cycles and or distance but it's probably a hundred miles in a few ignition cycles before it implements the new Cal.

Posted
11 hours ago, justanengineer said:

If you have a Global B truck it has the ability to recalibrate for different size tires using the OnStar GPS signal, wheel speed sensors, and other sensors. I can't remember if it is ignition cycles and or distance but it's probably a hundred miles in a few ignition cycles before it implements the new Cal.

 

Rough or smooth surface inside intake runners?

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

    • 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.
    • Just don't turn the steering wheel as much?
    • Rockauto bud. I pass local stores for parts.   Findya something online. 
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...