HPconfig project
HPconfig project
Okay, it seems like the interest is there, so I'm opening a new thread for my HPconfig project. It is intended to be a companion software to HPTuners. It will allow a user to read exported histos and trend/calculate/analyze across multiple tables. From my original post of this:
*****
I've roughed out the framework for a companion program for HPTuners that will read exported histos and allow tuning tables to be trended in various directions and limited in certain ways using calculations across multiple tables and give a snapshot of the expected result of the retune. The 'Load' button loads data into a spreadsheet. (working) The 'Show/Hide...' button allows the user to view and directly change loaded data. (working) 'Recalc' would reread the data from the spreadsheet and update the Snapshot in the main window. The power buttons would trend tables upward or downward. The % would represent the max move of data for any range that will allow a 100% move in data. (based on powerband) 'Commit...' would write changes to the histo files. 'Auto-limit' would prevent certain parameters from incrementing beyond a certain point. Obviously, there will be other things to add....

*****
It will take a while, but once I reach a successful beta, I'll edit this first post to include it. If this doesn't pan out, I won't be polluting other threads with discussion of it. Anyone interested can now come to this thread where I will put updates on my progress.
*****
I've roughed out the framework for a companion program for HPTuners that will read exported histos and allow tuning tables to be trended in various directions and limited in certain ways using calculations across multiple tables and give a snapshot of the expected result of the retune. The 'Load' button loads data into a spreadsheet. (working) The 'Show/Hide...' button allows the user to view and directly change loaded data. (working) 'Recalc' would reread the data from the spreadsheet and update the Snapshot in the main window. The power buttons would trend tables upward or downward. The % would represent the max move of data for any range that will allow a 100% move in data. (based on powerband) 'Commit...' would write changes to the histo files. 'Auto-limit' would prevent certain parameters from incrementing beyond a certain point. Obviously, there will be other things to add....

*****
It will take a while, but once I reach a successful beta, I'll edit this first post to include it. If this doesn't pan out, I won't be polluting other threads with discussion of it. Anyone interested can now come to this thread where I will put updates on my progress.
Last edited by Breadfan; May 24, 2012 at 01:24 AM. Reason: Update image
It did occur to me to include an automated section for MAF calibration. I can look over the histos for that and see if there is any value I can add to the process. Off the top of my head, maybe limiting the adjustments based on the number of hits in each cell might mitigate false adjustments based on inadequate sample size.
So far, I've got it to load the MALT, DAL, and WGDCC histos exported from the editor. Pushing the Show/Hide button yields:
So far, I've got it to load the MALT, DAL, and WGDCC histos exported from the editor. Pushing the Show/Hide button yields:
I just never seem to get the same trims on back to back scans while making no changes to the tune. But hey, if I ever get a weekend where I'm not heading north to GA to work on my Airstream, I might take you up on that Rob. Thanks!
Added the section to calculate requested boost based on DAL, MALT, & WGDCC tables. Does the result mean anything? Who knows. It displays not too badly. I'll need to go through and redo the algorithm for it. Updated the first post to show the new display.
Reworked the algorithm into a granular, per rpm calculation extrapolating for where table axis labels do not have the same increment. Updated the image in the first post. It is using the data from the stock tune. Added an auto-tune button. (not yet functional) The idea would be to push the tune around by the selected percentage until all the set limits are met. For example, for a 20psi tune with a 70% WG limit and a 100% torque limit, it would move DALs and MALT up while reducing WG toward a 70% peak. When WG is at 70% peak, and the estimated boost peak is 20psi, it would be done and would display the results of the modified tables.


