This may be way wrong but if it was hardcoded then how was it possible to make a GMSC reflash and along the same lines how is it possible for us to reflash a 2k+ 1bar system to a 2 bar system using hpt. I call
FWIW I just read the HPT thread. Chris' (from HPT) answer makes sense based on what I know of GM code. In the OBDI systems the table size is defined in the table. The minimum and maximum range of the table are hard coded in, and the number of "steps" between max and min are determined by dividing the number of table rows or columns into the range needed. To re-scale the table you need to change the max value, the min value, the section of code which does the division, or all three. And in order to add more entries to the table you need to physically move all of the code which resides after the table. After this many of the instructions in the code will refer to information that's been moved, so all the instructions must be changed to point to the correct new locations. It can be not too hard, but it isn't something which should be done without some way to make sure everything is moved correctly.
If the table scaling is contained in the calibration section as variables then the code is already written to allow the table sizes to be redefined without moving code.
Is there a value called something like the "extended rpm slope?" That would determine your timing after the top line of the spark table is reached.
-->Slow
Wrench Monkey wrote:This may be way wrong but if it was hardcoded then how was it possible to make a GMSC reflash and along the same lines how is it possible for us to reflash a 2k+ 1bar system to a 2 bar system using hpt. I call
Because its a different OS, not just a different calibration...
4cyltuner.com - Information Source For 4 Cylinder Tuners
Buy stuff from CarCustoms Ebay! Won't be disappointed!
