question about the lagstuning page?

[nismoautoxr]

I dont know if this is normal operation or not but I decided to kill a littletime this afternoon so I connected to the car and dropped the map lag factor from 50-40 but this did not light up the burn button . I had to change from single to dual table to get the burn button to light up and then change that back to single ...then the burn button stayed lit then I was able to burn the lag factor change but simply changing the lag factor by itself ...I get no burn button that way.

[93white3400z]

This is indeed a bug. Just getting the field out of focus should be enough to enable the "Burn" button but that won't be a problem anymore as I just fixed this for the next version.

You've been a great help so far, thank you!

[nismoautoxr]

This is indeed a bug. Just getting the field out of focus should be enough to enable the "Burn" button but that won't be a problem anymore as I just fixed this for the next version.

You've been a great help so far, thank you!

Glad to help if I can ...Additionally...I thought since the burn button stayed lit that it would be tricked into burning the new map lag factor in but it did not change it in the tune. The car was idling at the time I burned it and the idle did burp and revert to cranking IAC counts as it usually does when I burn but the setting was not changed . The reason I know that the new value of 40 was not burned is because when I got home I needed to analyze some logs with MLV so I hooked my tuning laptop up so the the current tune on my laptop reflected the changes that I made with the tab earlier today and the lag factor for map was still at 50 on the controller .

The tune did reflect the changes I made to the AFR table but the map lag factor remained at 50 even though I _thought_ I changed it earlier with the "trick" . Hope that helps explain it .

[93white3400z]

I'm not 100% sure but I think that it could be related to the same bug. It's possible the app lost track that you modified the lag factor (because the burn button wasn't enabled when you changed that) and just burned your "single" to "dual" and "dual" to "single" setting instead (which is nothing since you just put the value back to where it was).

Anyway, I will have to double check that to be sure when I'm not brain dead

EDIT: Ok, fixed your second bug too... and now its 1h10AM, d*** it!

[nismoautoxr]

You guys are making great strides with this app. I have not had a lot of opportunity to test it because my tune is fairly established at this point and most of my changes lately are strictly tweaking the VE table and AFR table. Keep up the good work!