AGreen

iTrader: (11)

MS2 v3. I switched from the firmware version 2.1.0d to 3.1.1, and now it will absolutely not start. I saved the .msq in both megatune and Tuner Studio, then uploaded it. I did the whole flash outside the car, so no coil packs were left plugged in or anything. I even loaded the .msq file out of the car with the Jim Stim. The weird thing is that last night with the JimStim plugged in, all 3 leds would light up on front of the ECU. Now, none of the 3 leds light up. I'm not really sure what that's supposed to mean though?

It seems to operate just fine when plugged in to the jimstim, but when plugged into the car harness, it just won't start it up. The fuel pump cycles 3 or 4 times just sitting too.... kind of weird.

I was using an old laptop with windows 98 and Megatune before, but since MSextra version 3.1.1 requires the use of tunerstudio and java, that old laptop wouldn't cut it. Now I'm using a laptop with windows 7, Tunerstudio, and a USB to DB9 adapter. At least the adapter cable's working and I can get it to communicate...

I'm also getting an error message when I open tuner studio. It says:

Controller Error. You have a configuration error!
This means there are conflicting settings and the controller does not know how to handle them. The controller message below should provide some guidance to the incorrect settings. Correct your settings then powercycle the Megasquirt. You do not need to reload the firmware to fix this problem.

Controller message:
Trigger offset must be zero in EDIS and trigger wheel mode.

Any suggestions?

Eagle7

Fix your configuration error?

AGreen

iTrader: (11)

I really wish I knew what that meant and then how to fix it.

I generally don't post new threads until I've thoroughly searched and honestly don't know what else to do.

Eagle7

Not sure where this is in your msq, but find the trigger offset and set it to zero. Post your msq if you need more help.

AGreen

iTrader: (11)

Hmm... ok. Weird. Under "tach input/ignition settings", I had the spark mode set to trigger wheel. Below it was "trigger angle/offset", which was not changeable, but it was set to 60.0. So I set spark mode to something else that allowed me to change the trigger angle back to 0. We'll see if this works, I haven't flashed it to the ECU yet.

Thanks eagle7

AGreen

iTrader: (11)

Cool. No more configuration error. However, it still won't start. It's now telling me that I have the wrong .ini file. I had Tuner Studio set to MSExtra serial310. I'm running MSextra 3.1.1. Off to search how the hell to get the correct file

Edit:
That was easy. I'm just not good with computers. I'm great with electronics and electrical stuff, but software isn't my forte. I read the README file and figured it out

AGreen

iTrader: (11)

Nevermind, I guess. I keep trying to get megasquirt-ii.ms2extra.ini to save under project properties, but it won't stay there. It keeps reverting back to MSExtra Serial310. Why!??

AGreen

iTrader: (11)

I followed this as well:
http://www.msextra.com/doc/ms2extra/upgrade.html
But I'm still not getting anything. When starting, I don't see a tach signal or anything. I'm about ready to upload the old 2.1.0d firmware and try again. I'm not sure what's gone wrong

Eagle7

You're much more likely to get prompt knowledgable help here http://www.msextra.com/forums/viewforum.php?f=101, especially since your issues don't seem to be related to rotary operation.

AGreen

iTrader: (11)

I just posted it there. I was considering posting it there before, but I have a 0 post count, since I've been a lurker on that forum, just searching and looking for answers without posting questions.

I really hope this is something simple. By the way, just out of curiosity which firmware do you use?

Eagle7

I'm running MS3 1.02 in a track-only NA FC.

AGreen

iTrader: (11)

I haven't gotten any help from the MSextra forum. I tried posting it, but it's up for a moderator's approval, and it's been sitting there for a day now. Anyways, I've tried searching for answers still, but can't find anything. The one thing I'm wondering about now is about the LEDs on the front of the MS. What are their purpose? When I had it connected and powered up with the JimStim before, all 3 LED's came on. After flashing it to 3.1.1, none of them come on. Again, I'm not sure what their purpose is, I'm just noting every little difference possible.

I'm going to post my .msq file just for *****/grins. Maybe there's something in it that's a smoking gun. I wouldn't think that the wrong .ini file on Tuner Studio would cause the ECU to not let the car start. Rather, it would just not connect to the MS properly. I don't know. Let's see where this gets me.

I really hope a mod approves my thread soon.

-Terrence

AGreen

iTrader: (11)

That's a blank file. WTF...

Here it is.

Eagle7

The LEDs are your ignition signals - one fires the leading coil, one selects which trailing coil will be fired, and one fires the selected trailing coil. The coil charges when the LED is off, so the correct power-up state is all three LEDs lit. If that's not the case with your setup, something's wrong - either the hardware or the firmware or the msq. Your msq looks OK to me. You said the LEDs are on when using the stim, but off when installed in the car. That points to a wire harness issue. It would probably be a good idea to restate what your current status is - it's hard to follow what's changed since the original post.

BTW, using the LEDs for ignition control requires a modification to the baseboard - pullup resistors must be installed. If that hasn't been done on your baseboard then it won't work in your car. However that wouldn't keep the LEDs from lighting. And just so you know, when the LEDs are continually off it can burn up your coils.

I would not install the MS into your car until it operates correctly on the stim, and TunerStudio communicates properly with it.

AGreen

iTrader: (11)

Actually, they're off when connected to the stim and I really don't know what they're doing installed. It's under the carped in the stock location

AGreen

iTrader: (11)

And I doubt it's a wiring issue. I started it up with it flashed to 2.1.0d, then took it out to flash it to 3.1.1. Reloaded the tune, installed it, then went to start it and nothing

I am using the pullup resistors on the MS2 v3.0 board, and an unmodified CAS with Ken's Zeal daughterboard for the 2nd VR conditioner.

muythaibxr

Send your 3.x msq.

Ken

AGreen

iTrader: (11)

Post 13

AGreen

iTrader: (11)

I just got the chance to check the LED's. Key on, they're all lit.

Now I'm not getting any firmware mismatch errors, it's just plain out not starting. I don't get a tach signal, the LED's aren't blinking, just nothing.

AGreen

iTrader: (11)

I'm also seeing a lot of threads on the MSextra forum about being "synced". Well, at the bottom right corner of TS, it's telling me "not synced" in red. Not sure that's supposed to mean, but I think I'm at least on the right track now. I ruled out wiring as an issue. I traced everything with my ohmmeter, paying special attention to the CAS wiring. Everything's still in tact.... just as I thought. I couldn't see how one day the wiring would work, then with the car sitting in the garage, the wiring go bad the next morning, but stranger things have happened.

AGreen

iTrader: (11)

Was I supposed to install the boot jumper? The way I understood it, if I was running a version of MSExtra, I didn't need to install the boot jumper when upgrading the firmware. Maybe that's my issue?

I'm going to try and re-install the firmware with the bootload jumper this time to see what happens.

AGreen

iTrader: (11)

Alright, I know I'm posting alot of stuff here, but I'm sort of doing this as a log so I can remember what all I've already done.

So new update, I flashed it BACK to 2.1.0d and it runs. This time, I installed the boot load jumper and told the download.bat program that I was updating from NON-MSextra firmware. So now I'm going to try flashing it over to 3.1.1 again, this time using the bootload jumper. We'll see if this makes any difference

AGreen

iTrader: (11)

Went back to 3.1.1, this time with the bootload jumper. I guess that was the key, since it starts right up. And it idles so much better than with 2.1.0. It even holds an idle with closed loop idle control! YAY!

Eagle7

Edit: post removed, comment was not applicable to this thread.

AGreen

iTrader: (11)

By the way, thanks Marty! You really tipped me off here:
I figured the .msq was fine, since it ran on the last firmware. The hardware HAD to be fine, since it literally JUST ran, and I didn't flash firmware with coils attached. I couldn't see any reason why the ECU would burn out during an ECU flash. It had to be the firmware.

Not sure why I had to have the bootload jumper installed, but lesson learned I guess.

Thanks again
-Terrence