Looking at the MSQ again, the problem is most likely because you are calling for +1% of ReqFuel, I doubt that is enough to show up. Try +20% and above.
Hello James, the 0 settings are from the tool tips and the manual, I think the 6000/6000 was in one of the manuals, its on page 65 of the setting up 1.3 manual under the heading
3.4.6.2 Time based accel,
the picture in the manual uses the exact settings that I was except I made my fuel pulse in the 1 to 4 percent range for the 100% tps trigger.
I have been using the same setting for a long time, its just now that the new intake manifold changed the engine characteristics, I think I am needing more AE and its just not working, it used to.
I will try a larger percent, but shouldn't it try to apply the given amounts when the trigger points are hit, with the throttle on some of the accel tests with tpsdots in the range of 1000 or higher, it should have tried to give 4 percent and registered no accel pulse. I am wondering if I might have corrupted the firmware with a glitch in the windows 10 updates, some of them have affected the communication settings, I recently had to use the communications menu in tuner studio to re-find a port and the megasquirt controller that has never given me any communication problems before....
Here is the current tune and a datalog,
James making the large end of the curve high seems to have corrected the issue, it triggered 6 times in a row... I am going to take it for a drive and then tune it better, but at least it activated each time the tpsdot was more than 150%
2017-08-16_21.45.57.msq
2017-08-18_18_modified.msl
Thank you for your help. I noticed something when I was changing the fuel percentages to increase the pulse, both of the axis for the graph in the tps dot Accel curve were set to Accel enrichment, so I changed the one axis back to tpsdot and left the other axis at Accel enrichment. I think I must have had a glitch while loading a tune or something, I also noticed that the only way to see what the graph axis settings were is when it is connected to the controller.
well so much for the ae working.... I took the car for a nice drive, did some Accel tests this is one of many Accel pulses in the datalog, the fuel pulse should have been close to 150% ..... but gave 102%..... the tspdot was about 1100%
I had tpsdots over 800% without a Accel pulse..... even though the dash indicator for tpsdot ae was activated during all of the Accel events... just no fuel pulse.
That certainly looks odd and I can't explain it. However, one of the motivations for writing the "accel-pump" AE strategy were oddities in the old time-based code.
James, Do you think I should try to reload the firmware 1.4.1 or possibly move to version 1.5.0?
I just don't understand the random application, the dash indicators say its triggering even when it shows no added fuel.... it always worked well in the past.... even with the low percentages it used to work great.
I just reloaded the 1.4.1 firmware and did some tests at idle, when the TPSdot was high enough to require added fuel it was applied. I still need to take the vehicle for a drive and get some data logging done then fine tune the TPSdot Accel enrichment curve...
2017-08-19_11_modified.msl
I am hopeful that this may have fixed the problem, but I wont know until after my test drive later today, the first try seems to be applying the requested fuel.
I believe that all the problems that I have had with the time based AE, were due to a corruption of the firmware because of a communications error (probably due to a windows 10 update) I reloaded the firmware and the test drives after the reloaded firmware have had fuel enrichment pulses commanded each time the minimum TPSdot value was reached.
I hope this is the last post on this topic. PROBLEM RESOLVED