ASE not staying on long enough?

[jamies]

Hi guys
Just seen an issue with MS3 both on older firmware and 1.4.0.
Where ASE when either set to 0.1 second interval, or engine cycles, does not seem to stay on more than a couple sec
some logs attached, I even tried setting it to 700 engine cycles which makes it stay on only the same amount of time....
can someone either try replicate, or confirm an issue

[slow_hemi6]

That log seems to match up with the msq. About 5 seconds of ASE on log and MSQ has a taper of about 54 (x 0.1s) for 47 degrees.

[jamies]

Ok,
i have reflashed again, and set ASE to 10 seconds and seems to be holding on for 10 seconds

However look into the attached log, there are 3 resets where the engine was turned off and restarted
Look at 5-6 seconds after the restart and note the sudden drop in pulsewidth which causes the engine speed to dip....

any ideas on what could be causing this?
msq same as above

[jsmcortina]

msq same as above

Which has ASE set to 5 seconds??
Please post the EXACT tune you used with that datalog.

James

[jamies]

here is teh one with ase at 10

[jsmcortina]

The two places in that log where there is ASE are different.

On the first one, the ASE lasts for 9.5 seconds, ok, that's not exactly 10.0, but it is close enough.

On the second one, there engine had been running for 4 seconds before TunerStudio started logging, so we can't tell.

James

[jamies]

james yeah it appears ase is a little inconsistsant, i'll try get more datalogs.
I know when i set it to 700 cycles, it only stayed on 3-4 sec..

also what about this PW drop - copied from above:

"However look into the attached log, there are 3 resets where the engine was turned off and restarted
Look at 5-6 seconds after the restart and note the sudden drop in pulsewidth which causes the engine speed to dip....
any ideas on what could be causing this?"

[jsmcortina]

Look at 5-6 seconds after the restart and note the sudden drop in pulsewidth which causes the engine speed to dip....
any ideas on what could be causing this?

It is related to the "batch fire during cranking" setting, but doesn't appear to be working as expected. Investigating.

James

[jsmcortina]

OK... so here's what's happening.

You have:
Batch fire during cranking = On
Cranking fuel pulse rate = Alternate
Squirts = 1
Injector Staging = Simultaneous

During cranking inj A,B,C fire as a group and D,E,F fire as a group, these alternate. This is from the "Batch fire during cranking" and "Cranking fuel pulse rate" settings.

When you move above the cranking RPM and the engine is in "Run" mode, initially it remains in the cranking batch mode until the engine is confirmed as fully running to avoid switching back and forth. At this point the 1 squirt/simultaneous setting is also applied, so all injectors fire at the same time - once per 720 degrees.

After 5 seconds of "run" mode, the batch-fire cranking is disabled and the code switches to normal operation. In this case (semi) sequential operation of the six injector outputs - this is when the pulsewidth changes as the injectors now fire once per 360 degrees.

To smooth out that middle phase, try setting 4sq/alt or 2sq/sim.

James

[jamies]

thanks for looking into it and clarifying that james,
I'll make some changes to the settings and see how it behaves
thanks