Stormfinder

Hey Everyone, as you may have read in a previous thread, i have recently acquired a MSlabs MS2 Enhanced. it was built for a 90-97 miata, according to the case.

my issue is that i have no sync at all. it appears like i have no cam signal input to it. i do see crank input though. Falling/rising edge made no difference.

I have it set up as 4g63 and believe i have everything setup correctly. but nothing shows up..

i can hook up my speeduino and have sync from it, and i even borrowed a good friends mspnppro and i have sync with it without any loss over multiple hundreds of miles from each ecu

so im guessing i have a hardware problem with the ms2Enhanced.

i am attaching my cranking logs, tune files, and .inis from both the ms2e and my speeduino, just to show the difference.

Kinda getting the feeling that i have a fancy paperweight here.

Stormfinder

Ok so trying to check the wiring for the cam signal and I am more confused then ever.

The crank signal is coming in on db37 pin 24, goes to tachselect, then to xg1, where I lose it after there. But it works as far as I can tell, from the datalog above.

The cam signal comes in on db37 pin 25, goes to IAC1A, then to r52 both top and middle holes, then to the middle pin of u7 on the side closest to the cpu. I lose it after there.

Stormfinder

Anyone have any ideas? Or am I gonna be stuck doing a 36-1 to get batch fire only?

Reverant

iTrader: (10)

Start by making sure no one has flashed a Microsquirt/Microsquirt Module firmware on it, as this will happen if you flash the wrong firmware type. It needs to have the correct firmware type on it.

Stormfinder

Hey rev,
Someone did previously flash a newer firmware to it, however I have flashed the 332b5 firmware back to it. Still not working. Wondering if there is anything I can do to check the circuitry further?

Stormfinder

It just sucks that i'm still stuck at the same place I was when I emailed you back in October. I'm hoping that you can point me in a direction to look and find out what has gone wrong so I can fix it.

Thanks

Reverant

iTrader: (10)

It's a V3 mainboard so you can get the schematics for it and trace the cam routing. It's been 8 years since we've stopped building these so I can't really help. The signal goes to one of the two white optoisolators on the board, and from there to the CPU.

Servaas Schutte

Please post pictures of top and bottom of PCB along with your tune so we can help you troubleshoot. I build custom thru hole MS ecu's on the side (Lexington SC 29073) so I would also be willing to look at it if you want to go that route.

Stormfinder

I can get the pics once I get home today. But that wouldn't be a bad idea to have you look at it. Lexington is only a couple hours from me

Stormfinder

here are the first 3 pictures

Stormfinder

And here are the other pics, I tried putting them into one post but it wouldn't let me. If a mod could merge these two that would be great.

Reverant

iTrader: (10)

The two pink wires on the bottom are the cam signal (in from the sensor, VRout from the 4n25 optoisolator to the CPU). The 4N25 on the top that has the capacitor soldered directly on it is for the cam circuit, which consists of this 4N25, the cap on it and the two resistors directly above it (one 470R which acts as a 5V feed and current limiting for the light emitter in the 4N25 and one 4.7K which acts as a pullup for the open collector output of the 4N25). Both resistors are connected together on one end, this is the 5V for them, so the other end of each resistor is the sensor (470) and the CPU output (4.7K).

Stormfinder

So, I tried remelting the solder at all the connections, just to see if it made any difference. It did not.
I can't help but be found Trying to tinker around on the holidays.

Stormfinder

UPDATE!! Thanks to Servaas, i was able to find that it was the daughterboard that was dead on my hardware, js10 was stuck high at all times, even on different hardware, . with a test ms2 daughterboard it worked great, so i have ordered a new one from diy.

Wanted to post the update and put an end to the story if anyone wondered.

Reverant

iTrader: (10)

Weird, I've never had a CPU failure like that before, however this one is like 10 years old now so anything is possible.