MSefi.com read only forum (Jan.15,2018)

Hi,

I am trying to improve my system by adding a MAF sensor. It is a Ford sensor connected to JS5(baro pin). I have a MS-II V3.0 and I am running Microsquirt code 2.89. My problem is that even if I use configurator to change fueling from Speed density to MAF megatune (2.25P3) always show AFR table in MAP format(kPa in left row) Should it change to AFM volts?



Tero

In the code version you have, if you have a MAP as well as a MAF sensor, the ecu will use MAP for the VE, AFR and spark table indices. If you only have MAF, it will calculate a Map(pressure) value from the MAF, rpm and cylinder volume.

If you want to switch to 2.905 code you can use the best SAE standard for load with a MAF sensor, called SAE PID 43. This bases it on the Maf sensor reading scaled by your cylinder size and rpm and comes out as a % value.

The code and ini file for this are attached, but you will have to use Tuner Studio as MT won't work with this ini.

Do you know if the problem with MegaTune is simply a code update vs. Tuner-Studio, or is it a more serious problem why MT won't use the new version?

Hi,

Does this new version have other new features? I am looking for closed loop idle control. And am considering switching to Extra code.



Tero

AFAIK CL idle is only available in Extra code............

Ken

gfolsom wrote:Do you know if the problem with MegaTune is simply a code update vs. Tuner-Studio, or is it a more serious problem why MT won't use the new version?

The 2.9 code has improved features for downloading a MAF table (the 1024 point one that can be auto-generated with the MAF Analyzer) and CAN messages. Part of this is built into the ini file, and part in TS. MT doesn't recognize the piece that is in the ini file so it quits. There may be other reasons, but that is the main one. There is a block in the ini file with mafTableBurner
and right after it a block with canOutmsgBurner. If you remove both of those blocks you might get it to work, no guarantees.