I tried a few things tonight.
1st I reopened the bin and set altitude bias to back to the 9.8. Then I logged the data in ALDL SCAN Its a cool little program. The 23000 timing advance was back at times. 5 minutes or so of running would produce a crazy number every 30 seconds or so but only when the throttle was snapped. Here is a screen shot.
So I burned a fixed timing chip. Setting all cells to 9.8 degrees. The initial timing had also been set to 9.8 previously. So I should have fixed timing that never advances. While I was in there I did not turn off the scalar but instead I set the few cells in the altitude spark correction vs baro vs vacuum table to zero. Note most tables were already at zero by default. Something in the change really made the computer mad. It was stuck at the 23000 advance in tunerpro, no longer an intermittent problem. So that was awesome, I took the timing light and looked at what the true timing was. I looked at he timing limits on the bin and its limited to 9 degrees retard and 41 degrees advance so in theory it should not be able to put a 23000 number up. Its at the base timing setting at around 9. Not being crazy at all. Tunerpro sure didn't like it though. Here is the data log. I am thinking its a data interpretation problem that for some reason stops when certain changes are made to the chip rather than something that affects the timing.
Bookmarks