Supermiata 36-2 trigger wheel sync issue
 

Just took my recent VVT swap to a tuning shop and they are noticing frequent enough sync issues. We suspect and issue with crank sensor and the 36-2 trigger wheel. It is a brand new sensor from Mazda so I don't believe the sensor it the issue. I set the gap by using a credit card. My wiring job was not the best in that many of my wires were too long so I coiled them up and zipped tied them. They at least were going to cut the wires down to proper size and insulate them all a bit better to make sure there isn't an interference issue. I wanted to see if people on here had other ideas of fixes to try. ECU is the MSLabs MS3 basic. Power numbers are spot on even given the sync issue so that is the good news at least!

Are you using just the crank sensor (ie running batch fire injection and wasted spark ignition) or are you also using the stock cam sensor? Assuming NB1/NB2.

It is a VVT motor in a 94 chassis. I did the wiring talked about in vvt swap thread where you split the orginal NA sensor to the NB cam and crank sensors. I hope that answers your question.

Were you already running the stock 4T wheel before without issues?

Brand new engine and had the 36-2 installed on it during build. Previously car had the orginal engine in it.

I had an similar issue when my ignition input capture was on rising edge. Totally fixed it with the falling edge setting

Did you just change that setting to fix or more? I see a warning about this must match your tach input. Mine is also set to rising currently.

You need to get the sensor just about kissing the wheel, so make sure it's wicked close.

If your ECU was brand new and originally set for the 4G63 (ie NA CAS) mode, then you need to change your ignition input capture.

​​​​​​
​​​​​I already have spark mode set to Miata 36-2. Could you tell me what settings for rest of ignition options?

The ECU is one I bought direct from you a few years ago.

Other ignition settings I have are.
skip pulses - 3
Input capture - rising edge
Spark output - going high
Number of could - wasted spark
Spark hardware - ms3x spark
Cam input - js10

Also to clarify, it isn't constant sync issues. But enough to cause the ECU to fire a check engine.

Serial number of the ECU please.