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

i am trying to use a ms2 as a standalone ignition controller for an edis8 setup.

the ms2 is seeing the pip, i assume because the tach is functioning on the mega tune display. (btw i am using megatune right now because my tuning laptop wont connect to the internet to download TS.)

the only timing advance that i am getting is the default 10* from the edis unit.

as far as i can tell, i have done all the neccesary mods to the v3 main board to run edis.


what should i do?

thanks,
barry

It would be helpful to see your settings. Post your msq.

Ken

here is the msq. there may be some fuel settings out of whack because i am not running fuel right now, just ign.


also what would be a good way to verify the presence of a saw signal?



i am not an electrician or computer guy. i know just enough to get myself in trouble.
this is my second mega squirt project, first time with spark control.

You have jumper'd JS10 to IGN? And checked for continuity from JS10 to pin3 of EDIS?

I'd expect a decent DVM set to AC volts to show a reading of a few volts between pin 3 of EDIS and ground with the engine running, although you'd need a 'scope to see the signal properly.

Are you using a screened cable for SAW?

yes i jumpered js10 1nd ign. i have not checked continuity between js10 and edis pin 3 yet.

you say a screened cable for the saw. do you mean shielded?

the pip and saw wires are twisted together in the harness for about 3 feet. could the signal be getting muddied up by the pip?
the original edis harness had the pip and saw wires paired in a shielded loom.

Screened is the UK term for shielded. Twisting wires together is only a good idea for balanced signals (like telephones). Since they are separate signals, I prefer to use two individually screened cables, one for SAW and one for PIP. But I've not experimented to prove this is needed.

trakkies wrote:You have jumper'd JS10 to IGN? And checked for continuity from JS10 to pin3 of EDIS?

i have continuity between js10 and pin 3 of the edis.

i have also removed the saw wire from the twisted set with the pip. it is not shielded but it is routed as to not pick up or lose signal through induction.

i am also not reading any voltage ac or dc on the saw wire while running.

do i have the correct settings in my msq. file.

i am pulling my hair out with this thing.

You first need to be certain if there is a SAW signal or not. It's just possible your DVM won't read it. An LED with a 330 ohm series resistor should, if you don't have access to a 'scope.
If there is no signal, I'd try changing the software to direct coil control, to check the processor port is ok. Even temporarily go to extra code which has a coil test function.
In other words, to try and check whether the fault is with the MS output or EDIS unit input.

i switched the coil charging scheme from edis to standard charging and i get ac voltage at the saw wire. still nothing when edis is selected.

Just a thought - it might be worth going through all the MS settings and entering 'sensible' amounts - even although you're running ignition only. Just in case this is confusing the poor thing. For example, the engine capacity appears to be 20307ci. Or start afresh from the default MSQ.

i have since fixed all of those values. i had some glitches that was inputting those goofy numbers. i have attached the current msq with the coil charge scheme set to standard. that produced an ac voltage on the saw wire. all other settings the same with the edis charge shceme settings produce no saw signal.

Only thing I can now think of is to re-load the code.

we got it figured out.
after a few emails with matt cramer, we determined that the mask number and percentage were off. i set them to his recomendations and i now have a saw signal and full ignition control.

thank you for the trouble shooting assistance!


barry

How did you arrive at the settings in the MSQ you posted?

they were generated by mega tune. we changed the mask time to .1 ms and 10 %. megasquirt imediately started outputing a saw signal.

fastbarry wrote:they were generated by mega tune. we changed the mask time to .1 ms and 10 %. megasquirt imediately started outputing a saw signal.

Interesting - the defaults here are 0 ms and 50% - I've never altered them. I thought they would effect PIP, rather than SAW. Wonder if I should play with mine - EDIS 8?