Issue with ECU field definitions on MS3 Batch Injection

[sdezego]

Running 3.06

I am Logging MS3 and am NOT running sequential injection currently. When set to Auto detect, I get errors on instantMPG as well as other calcs because ML appears to be assuming I am running sequential injection. Tried manually setting field ECu definitions to Megasquirt, but that throws and GEGO error when trying to load VE analyze (I am assuming because they are not MS3 defs). Thoughts?

Also, The instant MPG calcs do not appear to be taking into consideration Fuel Cut. I guess I could add a range limit. Thoughts? I can post a log if necessary.

Thanks,
Shawn

[sdezego]

Using Batch Alternating, not full Batch.

[jsmcortina]

Autodetect what?

James

[LT401Vette]

Autodetect what?

James

Auto detect Field Mappings I assume..
As the Log Field naming changes between firmwares and what not, MegaLogViewer 3.0 by default looks at the header names in each log at open and maps it to a field map so that all the calculated fields work.

sdezego,
Can you post a short data log just to be sure I am working with the same fields as you.

[sdezego]

Sure, here is a log.

[sdezego]

Let me know if there is anything else I can provide or help in any way.

Regards,
Shawn

[LT401Vette]

Nope, that did it...

I created a new Field map for non sequential MS3 1.1+. So it will be in the next release.

That formula seems Ok currently if you switch from Manual to MegaSquirt, but then ego_corr is wrong.

[sdezego]

Ok, thanks!