DIY Tuning walk-through (TunerPro)
#31
Addict
Rennlist Member
Rennlist
Small Business Partner
Rennlist Member
Rennlist
Small Business Partner
Thread Starter
#32
Burning Brakes
Hey there Rogue,
Couple q's on the timing maps.
- on the part throttle map, the load axis goes up to about 52%. Can you provide a summary of any way to relate "load" to this axis? Understand the load value will be a function of the AFM input voltage but why does the axis only go to 52%? Does it kick to WOT at this point or is are the load % numbers assumed labels vs. actual labels from the map.
- on the part throttle map, the timing values are displayed in hex. The xdf editor shows a calculation being applied but the value displayed appears to the source table. I would expect to see calculated timing angles. Can you explain why there are hex values displayed and the purpose of the equation?
Jeff
Couple q's on the timing maps.
- on the part throttle map, the load axis goes up to about 52%. Can you provide a summary of any way to relate "load" to this axis? Understand the load value will be a function of the AFM input voltage but why does the axis only go to 52%? Does it kick to WOT at this point or is are the load % numbers assumed labels vs. actual labels from the map.
- on the part throttle map, the timing values are displayed in hex. The xdf editor shows a calculation being applied but the value displayed appears to the source table. I would expect to see calculated timing angles. Can you explain why there are hex values displayed and the purpose of the equation?
Jeff
#33
Addict
Rennlist Member
Rennlist
Small Business Partner
Rennlist Member
Rennlist
Small Business Partner
Thread Starter
- on the part throttle map, the load axis goes up to about 52%. Can you provide a summary of any way to relate "load" to this axis? Understand the load value will be a function of the AFM input voltage but why does the axis only go to 52%? Does it kick to WOT at this point or is are the load % numbers assumed labels vs. actual labels from the map.
Just talked to the author of TunerPro, the next version should be out soon, which will have cell-tracing. This will allow us to see exactly what cell is being used in real-time! That feature will make tuning much simpler
- on the part throttle map, the timing values are displayed in hex. The xdf editor shows a calculation being applied but the value displayed appears to the source table. I would expect to see calculated timing angles. Can you explain why there are hex values displayed and the purpose of the equation?
-Rogue
#34
Rennlist Member
I found the Item Comments window
Rogue you did a Fantastic job with this Thank You !!!!!!!!!!!
Brian
#36
Burning Brakes
Thanks Rogue. Yes, cell tracing will be huge. On my SMT-6, that's the key feature that really enables the tuning. Did Mark suggest an approximate date he was thinking for the next version?
#39
Addict
Rennlist Member
Rennlist
Small Business Partner
Rennlist Member
Rennlist
Small Business Partner
Thread Starter
#40
I have been trying to pull down the map I'm running with Maxtune (89 28 bit) out of the Ostrich 2.0 and into TunerPro, but I haven't had any luck, all the cells have the same value (7.28). Clearly I'm doing something wrong, perhaps wrong def file?
West
West
#43
Addict
Rennlist Member
Rennlist
Small Business Partner
Rennlist Member
Rennlist
Small Business Partner
Thread Starter
How does MaxTune save the .bin? If it is saved as a normal .bin then you should just be able to load it from the file...
-Rogue
-Rogue