Jump to content

Recommended Posts

Posted

Has anyone else had issues with using the Rough Country Speedometer Calibration module on a truck with Adaptive Cruise?  I just went to a larger tire and wanted to correct the speedometer reading. Driving at 30 it's off by 1 mph, at 40 its a bit more, at 60+ its closer to 3+ish or more.   The RC device (hypertech) does correct the calibration which is great, but when I turn on cruise things get weird.  If I'm truckin along at 65 on the highway and set cruise, the truck holds at 65 for few seconds and then accelerates to 69-71 and then pulls back and slows to 65.   Thats about the same amount the speedometer would have been off, + or - a mile or two.

 

RC support is was great and is looking into the issue, just curious if anyone else has had similar behavior especially if you have adaptive cruise.  The software has a specific entry for 2020 w/adaptive, which makes me think there is a difference in the programming.  

 

 

 

 

  • 2 weeks later...
Posted

Well it's been a week or more and no answers from Rough Country,  they've stopped replying to voicemails - disappointing.  I did try calling Hypertech who actually makes the module and they said RC had to provide support - but did give me a tip on changing settings by a fraction to "change up the math".  I was able to tweak settings to find a reasonable middle ground between speedometer calibration and cruise working, but what's the point if it's not 100% accurate -  so it's return/refund time.    I think this can probably work with the right update, but I'd recommend buying it from Hypertech vs RC, so you can skip the middleman and go directly to the manufacturer.

 

Posted

I had the same exact problem.  At first I thought it was my pedal commander interfering but when I took off the RC correction module the problem resolved.  I've not put it back on.  

Posted (edited)
5 hours ago, TNAT4 said:

I had the same exact problem.  At first I thought it was my pedal commander interfering but when I took off the RC correction module the problem resolved.  I've not put it back on.  

So I think I’ve cracked it.  I modified the tire size to .2” difference and I’ve got speedometer reading maybe 1/2 mph faster than gps and adaptive cruise working with no issues at the right speed including following, slowing and then accelerating again all on it’s own smoothly. 
 

the software could use some polishing but overall this works.  

Edited by romclean1
Posted
1 minute ago, romclean1 said:

So I think I’ve cracked it.  I modified the tire size to .2” difference and I’ve got speedometer reading maybe 1/2 mph faster than gps and adaptive cruise working with no issues at the right speed including following, slowing and then accelerating again all on it’s own smoothly. 
 

the software could use some polishing but overall this works.  

So did you just do trial and error on tire size until it worked?  

Posted
1 hour ago, TNAT4 said:

So did you just do trial and error on tire size until it worked?  

Yes, I only needed a fractional change in values to correct it.  I went from 275/60/R20 (32.9” in my particular case) to a larger 285/65/R20 (34.6” BFGs).  I changed that to 34.75” and I think it’s right on target.  (1.048 vs 1.054 or something like that) Speedometer is about 1/2 mph faster than actual speed, a tad over is better than a low reading in my book, cruise works as expected.  

Posted
Sounds good, I'll try again.  I had just given up on it.  

You can tell you hit the sweet spot when adaptive cruise is suddenly back to normal.


Sent from my iPhone using Tapatalk
Posted
12 hours ago, romclean1 said:


You can tell you hit the sweet spot when adaptive cruise is suddenly back to normal.


Sent from my iPhone using Tapatalk

I actually have 285/65/20 BFGs on my truck but I instead measured the tire size (they recommended that vs. entering the measurements).  We'll see how it goes

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

    • I went through again with a test light and everything checked out.    I suppose it could be the MAF itself but I've tried 3 different sensors, 2 of which were in running vehicles previously (the one in this truck, and the one in the donor truck), as well as a new one I picked up from NAPA. I would just be surprised if all 3 were bad.   EDIT/UPDATE: I swapped in the MAP sensor that was originally with the 2010 PCM, that made the code for map sensor voltage high Go away, and the map sensor seems to read normal with key on engine off (14psi or so), but it still doesn't run and does the same thing as before.
    • In addition to a cell or wifi connection, the infotainment needs to be enabled to download software updates. That's a toggle within the system settings.   But...if the truck was prevented from receiving updates in a past life, missing a bunch of updates may mean it won't go back and download all of those because they're not available or the system is too far out of date.   If a formal recall depends on a software update, the recall for that truck remains in an open status until it's applied. The dealer would need to apply the software update in that instance.   Most updates downloaded and applied via the infotainment aren't recalls/safety recalls, they're enhancements and usability fixes which aren't critical.
    • Recently I've been getting a message, "New Brake Pads Detected. Reset Brake Pad Life?", But I haven't had the pads replaced and the truck only has 28,000 miles. The Brake Pad Life shows Front 64% and Rear 79%. I select NO to resetting the brake pad life and the message goes away but comes back at the nest restart.   I stopped by the dealer and was told that it sounds like a software glitch that would require reprogramming. Even though I have the extended warranty, they tell me that reprogramming is not covered unless a module was actually bad and needed to be replaced. Simply reprogramming is not covered. So, they want $200.00 just to diagnose the problem. If it turns out no bad module, another charge on top of that to do the reprogramming. If the cause was an actual bad module, everything would be covered under the warranty.   Just wondering if anyone else has had this problem. Should this issue be covered under the warranty?   Thanks
    • NHT is diesel only, correct.     The GVWRs for NHT on 3/4 ton bring them to the same numbers as many of the 2WD 1 tons.  A crew 4x4 standard 3/4 with NHT is 11,750lbs, a 1 ton same cab/box/4x4 is 12,100lbs.     Hubs and hub bearings are the same for 11.5" and 12" axles.  Housing, diff carrier and ring/pinion are larger for the 12".   All gas use the 11.5" axle, 3/4, 1 ton and 1 ton DRW. 
    • Yes, I connected it to my home wifi.
  • GM-Trucks.com Clubs

  • Popular Contributors

×
×
  • Create New...