Page 1 of 1

Megatune "config error" when selecting Wasted spark...

Posted: Sun Dec 14, 2008 5:42 pm
by E30_Driv3r
This with MS2e release 2.0.1

When i go to select wasted spark or COP option in the tacho/ignition settings section and burn/reboot all the display gauges "freeze" and i cannot change anything with the jimstim. When i go back and change the wasted spark setting back to single coil+burn/reboot everything works just fine. I AM going to run wasted spark (all the addition drivers and associated wiring to the board is done) so i have to deal with this issue.

Could it be a hardware issue or software issue or?

Thanks in advance.

Re: Megatune "config error" when selecting Wasted spark...

Posted: Sun Dec 14, 2008 6:12 pm
by jsmcortina
What are your other tach input settings and spare port settings.

You either have a tach input setup that cannot support wasted spark or you have a clash on the required output pins.

When you have the config error in place, open up Communications->MiniTerminal, then turn the Megasquirt off, then back on. You should see a message explaining what some of the problem is.

James

Re: Megatune "config error" when selecting Wasted spark...

Posted: Sun Dec 14, 2008 6:35 pm
by E30_Driv3r
The message i got from mini terminal was only 2 spark outputs allow on microsquirt?

Strange.

Im using the Tsel---->to VRout for a VR sensor

I do have a jumper wire installed in the JS10 spot to a spare DB9 connector i added for my wasted spark outputs which i was going to use to send a signal to my tachometer..when i set my tach output in megatune to JS10 it also "freezes" I just checked with the mini terminal and it says "confict with the output"..If i select the JS11 output its fine.

Im opening the case as we speak and im going to move the tach output since it may have something to do with why i cant select wasted spark. I will also go over my outputs.

Re: Megatune "config error" when selecting Wasted spark...

Posted: Mon Dec 15, 2008 3:05 am
by jsmcortina
So are you running a Microsquirt or not?
It sounds to me like you have loaded the Microsquirt version of the code onto an MS2 card.

In any case, be sure that SparkA output has D14 selected in Megatune and not JS10 (that would explain that conflict.)

James