DNMakinson

iTrader: (3)

One more question, if I may. I set up a new project, then loaded my last good tune into it. (from the old project, not from the MS). However, I lost my customized dashboard (as did TZ above). Is there a means to keep the previous custom dashboard?

aidandj

iTrader: (5)

Save the dashboard before you update

DNMakinson

iTrader: (3)

And then copy the dashboard.dash file into the new project, in addition to loading the MSQ.

TorqueZombie

iTrader: (6)

^thats great. I had forgotten I could save the dashboard.

Adding to the odd stuff that changed. The launch control was cutting hte engine out. I went for a small drive yesterday and every time I wound up the motor and shifted it felt like the engine was dying when I let the clutch out. I turned off the launch control and bam it was okay again. I got home, curled under a man blanket on the couch and dug around. It seems the Vehicle Speed Sensor was turned of negating the speed cancel setting for launch. No a big deal. Just adding it to the oddities of updating for others to look for.

TorqueZombie

iTrader: (6)

Fun fact. When I did the test drive weeks ago the launch control kept activating at speed gong down the road. It made the car feel like it was bogging down between shifts. SO I turned the launch control off and went on my family trip. Now I'm back and messing around trying to find what could be the culprit. It seems the VSS speed sensor was turned off. Nope, didn't solve the problem going to lunch. Sitting and staring at various menus I see that the "wheel diameter" is in meters and set to 1.9. As in bigger than I am tall sized tires. So FYI when doing the firmware update check that as well. It was late last night when I saw it and it snowed here in TN so the roads are a big sketchy for Miata purposes. (mostly other people scare me)

I'll try to keep updating as I find more oddities.

"Wheel Diameter" is in Advanced Engine--> Speed and Gear Sensors--> Look left side and down a few lines in MS 1.4.1

yossi126

iTrader: (6)

Wished I have seen this thread before yesterday. Went from 1.3.4 to 1.4.1 but couldn't find a matching ini and tune was signature mismatched.
Had a bunch load of errors just like OP.
Reverted to 1.3.4. Somehow found a basic tune for a 1.4.0 and the ini from Trackspeed. Copied my tune manually going every single table and settings and the ECU would still do crazy ****. I did a "compare tune" and one click copied 12 pages of mismatch. Now the car runs fine on a 1.4.0.
Problem is the I/O is different from the other ms3 ini files I have seen and going about changing them manually is not something I am comfortable with.
I swear I wouldn't touch a firmware upgarde again after yesterday.

cabowabo

There's an ms3.ini in every firmware zip that you can use when creating a new project for that firmware, unless I'm doing it wrong.

DNMakinson

iTrader: (3)

You are correct.

yossi126

iTrader: (6)

So what dictates the I/O? Only the tune itself?

Savington

iTrader: (31)

IIRC, INI files have no impact on the tune. They're just definition files for TunerStudio. If you are upgrading to 1.4.1 and trying to load a 1.4.0 map, you're going to have a bad day. You should load 1.4.1, save a fresh 1.4.1 MSQ, and then copy your settings into it. Alternatively, ask your ECU manufacturer (DIY or MSLabs) for a basemap that has the I/Os already set up, and then load your fuel/spark/startup/WUE/etc maps into it.

DNMakinson

iTrader: (3)

My understanding is that it is standard procedure to load the previous FW's MSQ into the newer FW project, and then correct the errors. That seems easier, but your method seems safer.

@Braineack or @Reverant do you care to comment?

TorqueZombie

iTrader: (6)

Yeah now in confused.
- even with the wheel diameter fixed launch control still engages driving down the road.

I did nothing with the .ini file. I simply loaded the next level of firmware then and old tune from the firmware before it. Let it update the tune. Then stepped to the next level of firmware and the last tune.

My current problem is the launch control thing. More importantly it got cold here since I left and drove it last time. It really kicks back now at startup and oscillates bad until it's warmed to about 80ish. I blame the firmware update, but the car wasn't running much last winter so not sure should I just make a fresh tune in the new firmware and transfer evertthing?

I k ow im whining but why so hard.
​​​

Braineack

iTrader: (62)

I convert all my MSQs to the firmware I'm loading them into. If I start loading newer firmwares, I make sure the older MSQs I was using have been converted over and any new features/changes in the firmware have been addresses, and the MSQs are saved back out under the newer firmware before loading them on units.

DNMakinson

iTrader: (3)

By "converting" I understand that you:
1) Create the new Project
2) Load the old MSQ into it
3) Fix errors and address changes
4) Put the new project onto the MS.

Is that correct?

When you do this, how do you get the MS to hook up with TS? When my tune in MS has a different name from the tune in TS, they won't talk. So what I have done in the past is to rename the old project to "Miata_Old" or something, and rename the new one "Miata", which matches what is on the MS. Am I doing it wrong?

Also, If there is some concern that a MS tune is somehow corrupted, does one need to somehow erase flash and do a boot load or something? Or is loading a clean tune all that is needed.

It may seem that I'm being obtuse, but FW is not my area of expertise, at all. I really need a basic explanation in simplistic terms.

TorqueZombie, if you want me out of your thread, just say so.

Braineack

iTrader: (62)

By converting, I start a project (usually a temporary project) with the newer firmware. Then open to MSQ i want to load. I accept the errors, then go through and make sure everything is okay -- like every single page and parameter. Then I save the file back out -- the MSQ should now be able to into controllers/projects without any errors.


That's odd, if anything there should just be a differences report that comes up and it will say controller does not match the project.

When changing the FW on a unit, I almost always start a new project, and just click "detect" when creating it. But that was before the new feature in TS to upgrade firmware...

I fail to see the point in renaming the older project. Instead, name the new project something unique and with the firmware version in it.



MS3 typically doesn't need a boot jumper to load firmware, but if it gets corrupt and you cannot communicate with it at all, or flash firmware without one, then you'll need it.




I feel like you're making this more complicated that it is.

First thing you want to do is save out your tune as a separate file, not just a "currenttune.msq" file.

D/L the firmware.

Load the firmware on your MS.

Open TS and start a new project.

click detect with the MS powered on and connected.

disconnect/de-power MS.

open tune in offline mode. accept errors, go through entire file to make sure everything is good. save tune. reload tune and confirm no more errors.

connect to MS. load tune file from project when it prompts there's a difference.

TorqueZombie

iTrader: (6)

You're just fine. I'm curious how I screwed it up, or is it just colder than the car is used to and I'm in weird areas of temp I've never seen before. I think its the prior as the idle and launch control snafu is odd.

poormxdad

TZ,

Could you please post your final VSS settings. I have no idea what to even start with.

Thanks,

TorqueZombie

iTrader: (6)

Will do when I get home. Changing the settings so far does nothing. I even set it to turn off at 3mph. Still activated launch control driving down the road. I ran VEAL for a bit and it's doing weird stuff at low Map that it didn't do before. This firmware is cursed and Rev does the have base maps for this firmware so I can't just start from scratch and transfer everything. I even tried to turn it off and on again.

yossi126

iTrader: (6)

If you need a Rev 1.4.0 base tune let me know.

DNMakinson

iTrader: (3)

Great news! 1.5.0 was released today.