HPTuners Histogram Data erasing after saving.. (SOLVED)
04-28-2019, 09:11 PM
#1
HPTuners Histogram Data erasing after saving.. (SOLVED) I upgraded to a 3 BAR MAP
While I drive and log, HPTuners scanner shows data being populated in the histogram for my VE Error. Once I stop the scan, the data is still in the histogram, but the moment I save the log, all the data in the histogram disappears. I have other histograms for 2 bar and 1 bar MAP, those show data (single line data, since I wasn't logging those PIDs).
What gives? Is this some weird 3 Bar MAP issue? Like how you can't log a 3 bar map w/ key on engine off?
Very annoying.. I've wasted two drives gathering really good data, all for it to be erased the moment I save it
While I drive and log, HPTuners scanner shows data being populated in the histogram for my VE Error. Once I stop the scan, the data is still in the histogram, but the moment I save the log, all the data in the histogram disappears. I have other histograms for 2 bar and 1 bar MAP, those show data (single line data, since I wasn't logging those PIDs).
What gives? Is this some weird 3 Bar MAP issue? Like how you can't log a 3 bar map w/ key on engine off?
Very annoying.. I've wasted two drives gathering really good data, all for it to be erased the moment I save it
Last edited by TXjeepTJ; 05-03-2019 at 09:16 AM.
04-30-2019, 08:09 AM
#2
Found the issue
Apparently, for some reason, the histogram values shown changed from "Average" to "Low". I changed it back to "Average" and the data showed up lol also, for some reason the histogram switched to "zoom data" too. Not sure why these two options were changed, I never changed them
Hopefully this will help someone in the future that overlooks this simple, self imposed (maybe?), problem
Apparently, for some reason, the histogram values shown changed from "Average" to "Low". I changed it back to "Average" and the data showed up lol also, for some reason the histogram switched to "zoom data" too. Not sure why these two options were changed, I never changed them
Hopefully this will help someone in the future that overlooks this simple, self imposed (maybe?), problem