MS II - Tuner Studio Settings
 

I switched over from Megatune to Tuner Studio (v2.0.8).

I'm using MS2Extra Serial324 for my firmware on my MSII board.

BASICALLY, IT WONT START.

I have fuel only, no ignition.

It ran and started just fine on the old Megatune settings but when I "converted" to Tunerstudio, I had some settings I wasn't sure how to convert.

Here are some screen shots:

Some basic settings questions were: (Especially dealing with start up)

Do I pick ODD or EVEN fire?

The Priming PW settings. Megatune was 2-point.

Secondary load Parameters? Speed density?

Cranking PW %?













http://forums.pelicanparts.com/uploa...1369889700.jpg
http://forums.pelicanparts.com/uploa...1369889714.jpg
http://forums.pelicanparts.com/uploa...1369889724.jpg
http://forums.pelicanparts.com/uploa...1369889736.jpg
http://forums.pelicanparts.com/uploa...1369889752.jpg

Needs to be even fire for sure.

Fuel and ignition load depend on how it was set up and tuned. If you dont have a tps sensor than it would have to be speed density.

You should be able to open your old .msq file in tunerstudio and have all the old settings move over.

TunerStudio (TS) just interprets your tune file. If you chose "use TS Settings" when you first opened the program you have just over written your previous tune file.

Just open your latest .msq tune file in TS, burn to the controller and you should be fine.

If you want to start from scratch (not needed) then open Megatune (MT) and TS and then set each dialog box the same in each program. Make sure you save the tune in TS as a new file.

Thanks guys.

First: I did make the file from scratch by moving over all the settings from the file. I have it on 2 different laptops. Megatune on one and Tuner Studio on the other.

I had version 2.891 (this is the firmware burned on the MSII ECU version).

I did do an import directly into Tuner Studio and it originally said I had mismatched versions. 2.892 vs 2.890. TS said my msq file was 2.892 and TS only had a version of 2.890 available to match it with (?).

Anyway, I burned the ECU with the latest firmware DIYAutotune had available. This is what got me here right now.


SPEED DENSITY is correct.
EVENFIRE was default.

Everything else I copied over by hand.


There was only one thing different. The Crank PW page. Megatune had it as Temp and PW msec but TS has it as Temp and PW%. I'm using the default PW% that was on TS.

Otherwise I've triple checked all my settings and everything is the same.

I'll give it a few more attempts but if I don't get it by Sunday night I'll burn the old Firmware back on to it and start over. I have a DE event next Friday I'm attending.

Thanks for the help.

It sounds like you updated your firmware, not just updated the tune file (.msq)

You would certainly have issues if your code in the first post is an MSExtra 3.2 variant and your code in your latest post is a 2.981 (B&G Code). These have very different fuel calculation algorithms.

usually, the autodetect function of TS will work well. There should not be a problem between the include file definition of 2.890 vs 2.892 despite the error. you can always download the include file (should be in your firmware package folder). Just navigate TS to look for the file in the correct location and it will update the definitions.


It sounds like you updated your firmware, not just updated the tune file (.msq).

Years ago when I first converted to the MSExtra codes I had problems starting the car. It was not getting enough fuel. I slowly scaled up the req_fuel value until the car started and then fine-tune adjusted from there based on AFR. Once started, I retuned the car for the new firmware. This assumes that your base settings are correct.

Thanks Jamie,

I got it started.

I actually went back to your first advice of just letting TS do the conversion of my Megatune .msq file.

So what happened was, when I originally did the TS switch I DID load the .msq file but got the firmware/template mismatch. I guess it spooked me and I went ahead and updated the firmware. TS was saying something about "minimum firmware version.." it needed to work. In hindsight I think it was referring to the 'Extra' code.

I ended up keeping the current firmware (MSII Extra 3.2.4) and took my Megatune .msq file and let TS do the "conversion". This time TS did a pretty good job of telling me what my errors were and converted my .msq over.

The last thing I had to power through was an ignition setting, which I don't even use. But the car wasn't starting with this error. It said the "toothed-wheel" setting wasn't correct. I looked for a "none" setting but it didn't have anything so I set it to EDIS.

Car fired up after I power cycled the MSII.

Thanks for the help, guys!



BTW, The TS auto-tune feature is awesome! Much better then Megatunes version.

Glad you got it figured out. Yes, MS2E requires an ignition setting even if the outputs are turned off.