MS pnp 5.0 weird flex fuel behavior

[BaldTurboFreak]

I just enabled Flex fuel on a customer's 5.0 stang, and it retards the timing about 45 degrees if there is anything other then 0 placed in the ignition compensation tables.
I understand that for some reason, it subtracts the adder (requiring negative numbers for advance) and with the data that is on the base map it just wont run.
If you change the ignition adder to a 0 it runs fine. So it would appear that the fueling side of things is correct, but the ignition code is all screwy?

Is this a known issue for the PNP's op system?

Also table switching, I cant seem to create a table switch routine based on flex % so I cant bypass the issue by running 2 discreet ignition maps for 0%/100%. It's hardware only? (boy MS3 has me spoiled).

[BaldTurboFreak]

This is the current tune. Without zeros in the flex ignition adder it wont run.

[jsmcortina]

I'm not sure why you think the timing addition is actually subtracted, it isn't.

Code: Select all

        lsum_ign += outpc.flex_advance;    // degx10

Negative additions actually triggers buggy behaviour, now fixed. http://www.msextra.com/forums/viewtopic ... 21#p501331

James

[BaldTurboFreak]

This is a screen shot from the base map provided on DIY autotunes site. This is probably the source of my confusion, it seemed like the PNP or ms2 version went about flex differently based on what was provided for a baasemap. ASSumption on my part.

[BaldTurboFreak]

DIY hosted basemap.