Hardware trouble? Timing won't advance from 10 BTDC.

Colin Doyle · Post by **Colin Doyle** » Mon Jun 26, 2006 6:47 am

I'm using MSnS-E on a V2.2 PCB. I've changed the .ini file for Megatune to use -Extra. I'm attempting to use EDIS.

On the PCB, I've removed D9 and soldered a 1K resistor exactly as shown here:

I've connected pin 30 on the DB37 to pin 3 (SAW) on my EDIS module. I've got continuity between pin 30 and pin 3 on the EDIS module. In Megatune, the little timing gauge will display like it's advancing when I rev the engine, but I can see the timing stay rock-solid at 10 BTDC when viewed with a timing light.

Did I miss some steps in the hardware mods? Before I found this site I had been corresponding via email with a guy, who mentioned connecting the fifth pin of JP1 to pin 3 on the EDIS module. Another website mentioned jumpering XG1 and XG2 with a 1K resistor. I had tried both of these (in conjunction), and it would not advance spark.

Any insight would be greatly appreciated - I'm getting a little frustrated... been reading various websites over and over for hours and they all say the same thing, but it's not working for me.

Thanks,
Colin

Minami Kotaro · Post by **Minami Kotaro** » Mon Jun 26, 2006 7:30 am

Do you have the PIP wire attached?

Did you jumper the fidle relay as shown?

In codebase and output functions, did you turn off MSns and turn on MSnEDIS and set fidle to spark output?

Colin Doyle · Post by **Colin Doyle** » Mon Jun 26, 2006 8:15 am

PIP is attached.

I don't have a FIDLE relay (no relay board.)

I did not set FIDLE to spark output. D'oh!

Thanks,
Colin

Minami Kotaro · Post by **Minami Kotaro** » Mon Jun 26, 2006 12:26 pm

Colin Doyle wrote:PIP is attached.

I don't have a FIDLE relay (no relay board.)

I did not set FIDLE to spark output. D'oh!

Thanks,
Colin

Haha.

Hope that fixes it. I had a few days' trouble getting my EDIS to work but, when it did, it was the "magic bullet".

Colin Doyle · Post by **Colin Doyle** » Mon Jun 26, 2006 8:46 pm

Changed that, still not working. When I go into the config file, I can change it to MSnEDIS, but Megatune will not open. If I leave it at MSnS-Extra Megatune will open and run just fine, and I can open and adjust the "codebase and output" settings.

I'm a Mac guy through and through, so this screwing around with Windows is a learning curve...

Colin

Minami Kotaro · Post by **Minami Kotaro** » Mon Jun 26, 2006 11:44 pm

Hmm. You've got me stumped. I'm not a computer person so I have no idea, unless maybe I was there and could see what's going on.

I hope someone else can help.

Colin Doyle · Post by **Colin Doyle** » Tue Jun 27, 2006 11:19 pm

Yeah, I'm kinda hoping so, too.

I'll probably have to enlist the help of my buddy Nick, who's running a 95 Ranger 2.3T with MSnTFI... although I'm pretty sure the board mods are different, he seems to be better with computers than I. Maybe he can help sort out this mess.

Colin

EstateAgent · Post by **EstateAgent** » Wed Jun 28, 2006 12:47 am

MSnS-Extra is the one you want. MSnEDIS is a very early version - its all tied in Extra now.

If you done the EDIS mod - did you put the resistor on the LED and run the wire across?

If so, go into MegaTune, click:
Basic settings,
Codebase and output settings,
Set EDIS: to EDIS
Set FIDLE back to Idle control*
Set LED17(D14) function to Spark Output A

And there you have it

EDIT: Just re-read your post, realised you done option 'A' (I did Option B). So you may keep with the FIDLE set to Spark Output.

Have you done part 2 on that list yet?

Minami Kotaro · Post by **Minami Kotaro** » Wed Jun 28, 2006 4:08 am

EstateAgent wrote:If so, go into MegaTune, click:
Basic settings,
Codebase and output settings,
Set EDIS: to EDIS

Thanks for clearing that up. That's what I was trying to tell him to do. Just now noticed he edited the config file instead.

Colin Doyle · Post by **Colin Doyle** » Sat Jul 01, 2006 1:15 pm

EstateAgent wrote:If so, go into MegaTune, click:
Basic settings,
Codebase and output settings,
Set EDIS: to EDIS

That's exactly what I did, then I changed the output from FIDLE to spark out. MS thinks it's advancing the timing - the on-screen gauge tells me it's advancing, but it's not actually advancing. I've got continuity between pin 30 (FIDLE) and SAW on the EDIS module, like I said.

Bad module?

Colin

Minami Kotaro · Post by **Minami Kotaro** » Sat Jul 01, 2006 1:46 pm

Try doing the LED 17 mod instead of fidle. From what I've read, it's the more reliable method. That's cheaper than buying a new module, lol. If it still doesn't work, and you are sure your wiring and board mods are good otherwise, you can try replacing the module.

Can you post your .msq?

Colin Doyle · Post by **Colin Doyle** » Sat Jul 01, 2006 8:31 pm

I can try to post a .msq... we'll see how that turns out with the journey across the great divide (to my Powerbook.

)

I'm going to tackle the LED17 method after work tomorrow... seems like the smarter way to do it, anyway.

Colin