Been doing a bit of searching and just can't find the info I need to sort this thing out.

Just wondered if you could give me any pointers on what mods you guys have made to get your MS2's running as we've been told to follow the mega manual to set up the MS2 and now we're being told to pick bits from the MS2 extra site and use their firmware instead.
Thoroughly confused and in need of help as I can't seem to get the spark running as per the MS2extra manual (just locks the ecu up when switching to the 4G63 mode) and really don't know where to turn on this one now!

Any help would be a godsend!!

Cheers,

Rich

 

Pointer: Post every bit of info about your setup. Like...

Car info
Engine info
Engine mods
MS version, firmware
Any mods done to MS2
What's tested, what works

And you might wanna look over some of the other MS2 threads in this forum for help.

What sensor are you using for a RPM input? The factory CAS?

 

Just to chime in on this as I've been working with Richard trying to get this working...

The car is a 1990 Jap spec turbo.
Standard 1600 engine running 320cc injectors.
MS2 extra 201 firmware on the ECU with mods as per MS2Extra manual.
Using stock factory CAS for RPM inputs.

Already searched through all the MS2 threads but they all seem to be either 99-00 cars (different triggering) or running as parallel installs which we just don't want to get into (why have a powerful ECU then only use half of it??).

Has anyone actually got an MS2 running on an early 1600 at all or are we just wasting our time and should have gone for an MS1 instead??

 

arga on the forum runs MS2E on a 1.6 miata. But he, like I, uses EDIS4 for his ignition input, which makes for a simple setup after mounting a 36-1 trigger wheel and sensor. MS1 code supports the factory CAS. Odds are, MS2 code does, but I don't know. So I really couldn't tell ya.

 

Here's everything you need for the CAS inputs and the spark outputs: MS2-Extra Miata 4g63 Manual

You'll need to set up the primary trigger as per the first drawing (V3.0 Internal Wiring) do the spark output mods as per the second (Output Mods for V3.0 PCB) and build the circuit described in Second Trigger Input (2 slot Sensor on CAS. Configure Megatune as described in MegaTune Settings, though you'll have to experiment to find the trigger angle. I expect it'll be in the 60s or 70s.

You need to do the TIP12x based mod described here for idle: MS2-Extra Hardware Manual

The 1.6 Miata's fuel pump circuit is a bit odd. To drive it with the MS's built-in fuel pump relay driver, you need to tap the light green wire at the fuel pump relay (aka the Circuit Opening Relay) which is under the dash near the steering column. Wire that to the MS's FP output.

You should ideally be running MS2Extra 2.0.x. Grab the release package here: http://www.msextra.com/ms2extra/file..._Installer.exe

What else?

 

Thanks guys.

All of the hardware mods are done so I'm hoping the firmware update will sort it!

I'll let you know.

Rich

 

No joy with the software - it appears that the problem is with the tach input signal when I change to 4G63 from EDIS. Any clues anyone????

Rich

 

Sure, don't use EDIS. It's an overly complex system that adds no benefit to an MS.

 

I think he's having issues with is ECU crashing/failling to respond when EDIS is deselected as an input option in MegaTune. Rather than whether using EDIS or not is an option

IMO you either have a bad install on your PC, OR you have a short somewhere...

 

I got my users mixed up when Pat said "But he, like I, uses EDIS4 for his ignition input, which makes for a simple setup after mounting a 36-1 trigger wheel and sensor." I'm running a 36-1 wheel too, and I don't use EDIS. I just have the VR sensor connected directly to the MS, and configured as a 36-1 wheel.

My mistake.

A16BBR, is the MS really is locking up, then I'd start by re-flashing the firmware into the unit (which will, as a byproduct, erase all your settings) and also re-load MT onto the PC.

Failing that, as richyvrlimited says, it is not impossible that something is mis-wired in the spark outputs mod. If the transistors are accidentally shorting +5 to GND, that'd definitely halt the CPU.

 

I wouldn't say no benefits. I have spark control to 4/32 of a degree accuracy or some ****. Better than a CAS. And since the EDIS module controls the coils, I don't have to setup anything for the ignition system to work like dwell, fancy inputs circuits, etc. Just do the mod for EDIS on the MS board that's very simple and well documented. And I don't have to unplug coils when burning firmware as it's impossible to burn the coils us since MS doesn't directly control the coils. And the MS/ignition system interface consist of TWO wires. That's it. EDIS tells MS RPM, MS tells EDIS how much to advance. Pretty damn simple to hook up. Hook those two wires up and switch the ignition module on/off with +12V and I have dead-reliable spark. I wouldn't say it's overly complex.

But it does suck that I can't have launch control by spark cut...

 

Granted, EDIS-based systems are inherently more accurate than CAS-based systems, however using a VR sensor directly into the MS buys you exactly the same degree of precision without the external hardware. EDIS is just a layer of extra complexity that happens to rob you of adjustable dwell control in the process.

 

Thanks for the support guys but it seems that I'm not the only one with this problem - MJ71 has exactly the same issue.

Is there a problem with the MS2 Extra board or firmware?

Rich