Well... I've never used a MAF on MS2 but I think it's about the same as MS3 which is what I'm using. But you must be using the newest release version of MS2/extra - version 3.1.0. Once you've gotten up and running on that version do the following:
First, rather than overwrite the one that comes with TS or the firmware, rename your "maffactor.inc" file to something else for example "MyMAF.inc".
Next you need to find where your TunerStudio project is located on disk. If you don't know its location, you can go into project properties in TS and on the "configuration" tab it's shown under "project directory". Open that folder.
Under the project folder there's a subfolder called "inc". You want to put your MAF inc file into that folder.
Now look for another subfolder in the project folder called "projectCfg" and open it.
In the projectCfg folder you'll see a file called "mainController.ini". You need to edit that file with a text editor.
In the editor, search for "ReferenceTables". You should find a section that looks like this:
Code: Select all
[ReferenceTables]
tableWriteCommand = "t" ;
referenceTable = mafTableBurner, "Calibrate MAF Table..."
;topicHelp = "http://www.megamanual.com/mt28.htm#??"
tableIdentifier = 003, "MAF Table"
adcCount = 1024 ; length of the table
bytesPerAdc = 2 ; using words
scale = 1 ; scale before sending to controller
;tableGenerator = Generator Type, Label, xUnits, yUnits, xLow, xHi, yLow, yHi ; lows and Hi's are just default values, they will be user editable
;tableGenerator = linearGenerator, "Custom Linear WB", "Volts","AFR", 1, 4, 9.7, 18.7
solutionsLabel = "MAF Sensor"
solution = "Ford V8", { table(adcValue, "maffactor.inc") }
; solution = "Ford V8", { table(adcValue, "maffactor.inc") }
See the two lines at the end (one is commented out with a ";" character) that say "solution =..."? Those are the lines that reference the include files for the MAF sensor. What you need to do is add a line that looks just like the one without the ";", but give it a name of your choosing and use the name you gave to the MAF include file earlier. So you might end up with something like this:
Code: Select all
[ReferenceTables]
tableWriteCommand = "t" ;
referenceTable = mafTableBurner, "Calibrate MAF Table..."
;topicHelp = "http://www.megamanual.com/mt28.htm#??"
tableIdentifier = 003, "MAF Table"
adcCount = 1024 ; length of the table
bytesPerAdc = 2 ; using words
scale = 1 ; scale before sending to controller
;tableGenerator = Generator Type, Label, xUnits, yUnits, xLow, xHi, yLow, yHi ; lows and Hi's are just default values, they will be user editable
;tableGenerator = linearGenerator, "Custom Linear WB", "Volts","AFR", 1, 4, 9.7, 18.7
solutionsLabel = "MAF Sensor"
solution = "Ford V8", { table(adcValue, "maffactor.inc") }
solution = "My MAF sensor", { table(adcValue, "MyMAF.inc") }
; solution = "Ford V8", { table(adcValue, "maffactor.inc") }
...if you want to fool around with different calibrations for your sensor, you can have as many .inc files as you want - just make sure they have unique names, drop them in the project "inc" folder, and create a line for each one in the mainController.ini file as shown above.
Now close the text editor, saving the mainController.ini file. One thing you should be aware of is that's a copy of the .ini file that comes with the MS2/Extra firmware... so if you ever upgrade your firmware in the future it could get overwritten. So you should make a backup copy of that file, so you can reinsert your changes later if necessary.
Next you need to go into TunerStudio and set up your MS for MAF sensor operation. Specifically, you need the following settings:
- Under "basic setup - basic/advanced user", "user level" must be set to "Advanced".
Under "basic setup - engine constants", "control algorithm" must be set to "MAF".
Under "basic setup - more engine constants", "secondary fuel load" should be set to "MAF" so you can make mixture adjustments by RPM and load
Under "basic setup - more engine constants", "secondary fuel" should be set to "multiplicative"
Under "basic setup - more engine constants", "multiply MAP" should be set to "don't multiply"
Under "basic setup - more engine constants", "incorporate AFRtarget", I suggest setting this to "include AFRtarget"
Under "basic setup - fuel VE table 1", make sure all the values are set to 100
Under "basic setup - fuel VE table 2", make sure all the values are set to 100 (to start with, this is the table you'll use for tuning)
Under "advanced - MAF settings", "MAF port" should be set to the port you have your MAF sensor connected to
Under "advanced - MAF settings", "engine size" should be set to the displacement of your engine
Under "advanced - MAF correction curve", make sure all the values are set to 100 unless you have a reason not to
There are a few other choices you need to make in the "basic setup - more engine constants" window. "Primary ignition load" can be set to "speed density" to have it based on MAP, or "MAFMAP" to have it based on the MAF sensor reading (there of course are other options too). Likewise, the AFR and EAE load can be set to MAF, MAFMAP (an estimation of MAP derived from MAF), or MAP.
And here are a couple of things that aren't strictly necessary to use a MAF sensor but are very helpful. First, in the project folder "projectCfg" subfolder, look for a file called "custom.ini". If it's not present create it, and edit it with a text editor. If it is present, just edit it. You want to make sure it has a "datalog" section with two values as shown here:
Code: Select all
[Datalog]
entry = maf, "MAF", float, "%.3f"
entry = mafmap, "MAFMAP", float, "%.3f"
Having that section and those values will cause TS to log MAF and MAFMAP, which can be very handy for troubleshooting.
And lastly if you want to use VEAL (VE analyze live) in Tunerstudio you need to change one more file. Find the folder you have TunerStudio installed in, and go to the "inc" subfolder of that folder. Find and open (in a text editor) a file called
"ms3VeAnalyzeMaps.ini"*. Look for some lines in the file that look like this:
Code: Select all
; Table 2
#if LAMBDA
veAnalyzeMap = veTable2Tbl, afrTable2Tbl, lambda2, egocor2, { ((dualTable ) || (algorithm2 != 0)) }
#else
veAnalyzeMap = veTable2Tbl, afrTable2Tbl, afr2, egocor2, { ((dualTable ) || (algorithm2 != 0)) }
#endif
...and change the second "veAnalyzeMap" line to replace "afr2" with "afr1" and "egocor2" with "egocor1" as follows**:
Code: Select all
; Table 2
#if LAMBDA
veAnalyzeMap = veTable2Tbl, afrTable2Tbl, lambda1, egocor2, { ((dualTable ) || (algorithm2 != 0)) }
#else
veAnalyzeMap = veTable2Tbl, afrTable2Tbl, [b]afr1, egocor1[/b], { ((dualTable ) || (algorithm2 != 0)) }
#endif
Well that's it, I hope I didn't forget anything!
* Edit 15-July-2011: The "ms3VeAnalyzeMaps.ini" file is if you're using Megasquirt *3*. If you're using MS2, I think you should edit "ms2VeAnalyzeMaps.ini" instead (note the 3 changed to a 2).
** Edit 15-July-2011: This originally did not include changing the "egocor" parameter but I'm now recommending changing that also based on input from nuvolarossa and Phil Tobin (author of Tunerstudio).
