Probably a noob question, but I wanted to verify before I possibly do something dumb. I have a MS3 basic from Rev and I have a new 949 36-2 trigger wheel to install. it appears my firmware doesn't have the option in the menu and I need to update the firmware. I am assuming I can use the one in attached picture. Never done it before and are there any tips on process? Supply power to all, good USB connection, plug and chug?

Thanks for any help and I apologize for noobness. I just didn't want to assume wrong

 

Yes. to all of your questions.

It should be very simple. It will ask you if you have an ms3pro or just ms3. You want just ms3.

I like to save a copy of my tune outside the normal folder in case something goes awry.

 

Check with Rev before doing anything. He sometimes uses custom firmware.

 

Not on MS3-Basic. Standard FW. The above was his advice to me, standard FW. (I'm running 1.4.1).
I'm not sure about the enhanced and extreme, however.

And, the latest T/S lets you update FW while connected, not needing the separate procedure. (Update / Install Firmware)

 

So it seems project cursed strikes again. I updates the firmware and now it won't sync. It will fire the car and run with throttle. It doesn't like it, but I got a composite log. I did backup the project and tried reloading the old tune file. I got about 84 errors and it says it fixed.

 

Composite log. It seems that it gets the sensors, but the little red light on TunerStudio say no sync.
https://drive.google.com/open?id=0B8...3BMMkp5OHk3SlE



Hopefully that will share the file.

 

Post tune

 

There is a bunch of garbage in the crank signal. Check your air gap.

Stock wheel? Or 36-2?

 

949 harmonic damper and 4 tooth wheel. I'll double check air gap. What makes you say air gap. Not doubting you, but trying to learn to diagnose some myself.

 

Stuff like this in the composite log.



But it didn't lose sync which is the weird part.

Post the old tunes and new tunes.

 

You went from what to 1.4.1?
Do you have a MSLabs CAN EGO box? I ask because I went from 1.3.x to 1.4.1 and the box and had sync loss problems. I took the box out and went back to analog O2 input to fix problem, but stayed with 1.4.1.

That issue is where Rev suggested 1.4.0, but I confess I did not try that.

 

New composite log after making the crank sensor gap 0.020 and giving the connections a once over.
https://drive.google.com/open?id=0B8...l9pNnNkeUhVUHM

I drove it home last night and other than the firmware update nothing was touched on the car. My brain says it was a firmware update that did it in. Which is great because this is currently my daily. Apologies for being a Debby downer. I'm a bit sick today and figured I could handle this update since "what could possibly go wrong?"

 

No can box. Nothing changed pre or post (well set air gap) the firmware update. I learned my lesson not to change very much each time I try stuff. Nothing sucks like chasing down what new thing went wrong out of 15.

Old tune just before the update I saved a couple days ago.
https://drive.google.com/open?id=0B8...zk2ZmZiSzR5U3M


"new" tune
https://drive.google.com/open?id=0B8...EdYRUVYd3R0TU0

I will add it seems to really want to fight starting up. I get some kick back I didn't have before. Few back fires and all this starting and failing to run has the garage a little fumey.

 

I may not know how to correctly open other people's tunes, but I don't see any material difference between the two.

What was the old FW revision?

Quite interested in the resolution to this.

 

Yep, mine did that kind of thing. Changing the Crank Sensor changed nothing. Changing the Cam Sensor changed nothing.

 

I was on 1.2.3 firmware. Now 1.4.1. Not sure what happened. The compare tune shows zero changes. I noticed the "garbage" in the crank sensor a few minutes ago trying to see wtf. I did, repeat did/affirmative/positive disconnect the ignition coils during the firmware update. Curious if somehow the crank sensor got spazed? I have a spare around here somewhere. Maybe a quick swap in the morning to see.

Why does this thing hate me?

 

What tells the ecu what is a go/no go for the sensor inputs. I know there has to be a setting somewhere for the ecu to decide what is a 1 and what is a 0. The more I look at the logs the more it seems like a small calibration went weird. All the setting are the same, but what changed in the firmware?

Where do I find the sensor threshold section? The has to be a way. The sensor is analog and has a middle point, but the ecu only shows binary in the log. On (peak) or off (at the bottom). Where do I tell it at what value to ignore and make a 0 and what is enough to be a 1? I'm obviously not a computer wizard, just spit balling ideas cause I can't find any changes.

Or does the MS3 have the potentiometer aka "trim pots" cause that will suck. I remember when I had cam sensor issues reading about so trim pot to adjust, VR conditioner, or something like that.

 

Ms3/ms3x has trim pots. No idea about mslabs

 

I'm curious if somehow the code for the updated firmware messed with it. It appears the trim pots are before the ecu gets any information, so I'd assume the firmware has no decision with the trim, but weirder stuff happens. I wish I wasn't sick otherwise I could get frisky and see.

 

The ECU has no trims pots. Download and try 1.4.0 instead.