I’ve been following this thread since its origin, thanking my lucky stars that I’ve not suffered from this problem that so many of you have. Well, I ran out of lucky stars. After data logging mass airflow transfer tables, I made my first series of corrections to the calibrations in the tune and flashed the changes. When data logging to examine the results of those changes the scanner gave me an error message that I needed at least one PID to scan. When checking the Table, nothing had changed. All the standard PID’s and three custom PID’s where there.
I contacted HPT support, whose response was to “download the current version.” Did that and set up a new config file that included the three Custom PID’s I’ve been using for years. While connected and scanning, all the PID’s, including custom PID’s were reporting data in the Table. When checking a histogram (that has worked for years) reported "This histogram is not supported with the current loaded parameters." When going back to the table, suddenly half the PID’s reported that they were not supported.
When presenting this latest problem, supports response was, “Unfortunately we do not perform any in house tuning or calibration work nor we give advice on how to create custom histograms. For free tuning advice please visit our user help forum.” What a cop out!
So, I uninstalled version 2,24.1168, cleaned the registry, made sure there were no programs remnants, rebooted and reinstalled. I opened the application and half the PID’s in the stock table were greyed out reporting unsupported. Still waiting for a response from support.
It is clearly becoming recognizable that HPTuners is in serious turmoil. The glitch that this thread follows, best practices should have patched it in less than a month, nonetheless, still unresolved. Their systematic method for managing the provisions of services to their customers and product management dealing with the product planning is imaginary.
Originally Posted by Ranger6202
