Using version 2.1.12 and latest updates from HPT. Vehicle is a 2005 LS2 C6 Corvette A4 w/ an upgraded 3.42 differential from the original 2.73. Stock tires. All relative speeds have been compared against our calibrated chassis dyno rollers and most test speeds are 60, 70 and 80 MPH.
We have been in contact with HPT *MANY* times over this re-occuring issue and absolutely *NONE* of the "fixes" they have supplied/suggested are working...period! This is getting very expensive and time consuming trying to hunt around for an answer to this problem and it's getting ridiculous, as this isn't the first time we've had problems with this product..
We have performed every-single possible combination to get the DIC, the dash speedo and the HUD to have all the same values in speed, but nothing has worked 100% yet.. If we input the "3.42" ratio number in any one of the four(4) differential ratio data entry areas of this calibration, select "Commit" and so on, one of the three speed reference gauges are not accurate.
1. Input the "3.42" accurately in data entry areas and select "Commit" as instructed- Dash and HUD speedo are correct, but DIC and PC speedo are off by 50 MPH or so and do not climb with the same linear rate as the dash speedo. Obviously, the cruise control does not work either...
2. If we take that same file that was "Commited" to a 3.42 ratio, (to maintain shift patterns/strategies, as they are correct) but input "1.00" in all data entry areas, the dash and HUD speedo are 3 MPH slow and the DIC & PC screen are dead accurate- Cruise control works properly.
3. If *ANY* of the gear ratio data entry areas have the "3.42" input anywhere, there will be a problem somewhere with accuracy of the dash & HUD speedo, as well as, the PC speedo and the DIC. There has been no way around it..
As a test, we have altered the PPM up and down by huge margins to see if we get any sort of change at all- nothing... We do have the shift points set exactly to target and they are right where we want them for this application- this has never been the issue.
When we first broght this to HPT's attention, the latest version out at that time was 2.2.0 we believe. Now that we have the latest version and was told that the problem was corrected, we find differently and this is unacceptable.. We're chasing our tails here and since HPT won't provide a phone number for professional tuners to call to sort out the problem in a quick, efficient manner, we have to invest more time and hassle in tryping all of this out, while waiting for a reply that may or may not come. Time is money and HPT has burned up a lot of both around here thus far because of this very issue. We've still yet to hear from HPT on our last email sent yesterday.. We've always been supporters of HPT and have waded through the bug fixes patiently in hopes of a better product, but our patience is wearing *VERY* thin here with these re-occuring problems time & time again.
Anyone ran into this before or has some kind of solution? Thank you for your time.
Best Regards,
DTE