MSefi.com read only forum (Jan.15,2018)

Hi All,
Having what I think is some bad luck with EDIS4 modules. I have been bench testing an EDIS4 setup - 36/1 trigger wheel, stock VR sensor.

The issue I am having is no RPM output to MS from PIP, IE no tach signal. From what I gather from various sources, the PIP normally outputs a square wave waveform. At rest, it is a +12V signal, and with a drop to +5V while cranking/running.

What I am seeing is an output of +5.6V at rest, that drops to 2.2V with trigger wheel rotation. I get no RPM signal from 0-1500 RPM (max rpm of dummy motor), both on the MS2v3.0 and Microsquirt v3.0 I have been playing with. I have 2 modules laying around - the first seems to function OK, good spark output. The second does not seem to work at all. They are both from the junkyard.

The settings are as follows:
Trigger offset = 0
Ignition Input Capture - Rising Edge
Cranking Trigger - Calculated
Coil Charging Scheme - EDIS
Spark Output - Going High, inverted
Trigger Wheel Teeth - 0

I have the correct jumpers installed in the MS2, and the correct input connections on the Microsquirt (pin 12 + 30)
Both MS units run fine on the stim.
Also, all of the other sensor inputs (TPS, MAP, IAT, CLT) work 100% on the bench
VR sensor is correct polarity - as proven by #1 module outputting spark
Both EDIS and MS are receiving direct 12V power from battery, and grounds are good
One thing - I did not shield the PIP/SAW wires on the bench, but it should still pick up RPM signal even if poor quality?

I never want to be one to jump to conclusions, but I do indeed think that I actually have some bad EDIS modules. If anyone has some troubleshooting tips for diagnosing a bad EDIS module, that would be super helpful!

I take it the voltages you're measuring are DC? What do you see if you change the DVM to AC?

Yes, the voltages are DC. My understanding was that when not running, the PIP signal is not pulsed and it should read a constant DC voltage until it gets a signal from the VR sensor and starts to generate a square waveform. Hence why the reading drops to 5 V when measuring during cranking - it is then a pulsed (averaged) output that is being measured.

Regardless - I have 2 more modules, and will be attempting to run them as well tomorrow. I will measure AC and DC voltages from PIP.

Thanks for your input! If I get 4 bad modules in a row that may be a new record for the worst junkyard finds ever!

My guess is you'd be very unlucky to find an EDIS unit which produces a spark - but no PIP. It's most usually the power devices which fail first in anything.

Well, the results of testing are in. I did indeed have one bad EDIS module - it seemed to be completely non-functional both for spark and PIP output. However, the 2 other modules I have are functional. Both of the functional modules had the same PIP output at rest and cranking as was noted before ~5.6V at rest, 2.2V cranking, measured DC.

It turns out that the culprit for why I was not receiving an RPM signal was one of the defaults under the "dual/multispark options" ignition menu. It was set to "falling cam sync with tach or wheel." After resetting to "no dual or multispark," it picks up a stable RPM signal from 250 - 1500 RPM on the bench.

Also, I did some other experimentation while I was at it - the EDIS module seems capable of driving several different coils besides the stock one without issue, as long as the coil resistance is similar (~1.9-2.0 ohms). I tried out coil packs from a Neon and late model Focus in addition to the stock EDIS coil packs. The reason for this is that the stock coil packs have a rather inconvenient connector, versus the Neon packs which have a standard terminal post.

Thank you for all of your input, and I hope that this helps someone in the future.

How did you wire your edis in your ms2 ecu? Do you have pictures to show your board due to the fact that I am going through something similar.


Thank you
Carlos Lopez