lost sync 31 & 32
 

Reverant built MS2

Getting lost sync randomly although mostly happens at cruise. Found a post with the codes and apparently my cam sensor vanishes? wtf

31 = Miata 99-00 - 2 cams not seen
32 = Miata 99-00 - 0 cams seen

When it happens there is a miss, RPMs drop on the tach and AFR spikes. What could be causing this and how do I fix?

Forums wouldn't let me up load so get the log from here

check sensor positioning? loose wire?

I would think it almost has to be a bad/loose connection somewhere. How often is it happening? Is it just random or at fixed intervals? Maybe it's a stupid question, but have you tried jiggling the connection on the sensor to see if it clears up?

Its a firmware issue. I need to send you a new firmware to load. PM me your email address.

PM'd. Glad it's an easy fix, I was going to swap the stock ECU back in to confirm wiring/sensor issues.

I'm starting to understand why the MS is so popular here. This thing is awesome!

Check your email!

That's what I call service! Reverant upgraded the firmware for me, and then I took a drive to The Gun Shop to test things out. Idles much better than the stock ECU ever did, but I'm not making ---- for power until ~5500rpm. Lots of tuning and learning to be done. Never done anything like this before and I gotta say the whole process has me impressed, Reverant did a great job with the ECU and TunerStudio is just awesome. Totally worth the $70.

I'm glad I could help, and double-happy that it has been so easy for you.

Bump from the holy grave!

Starting about 4 days ago I have run into this same sync loss issue.

MS3x running 2001 engine in 93 chassis.
I logged two individual sync error 32 events. Was this just a reverant based firmware issue? Or is there another potential cause of this issue?

Nothing tune wise has changed in over two weeks.

I did move the wires at idle in attempt to cause a stumble or miss to no avail.

Thoughts? :makeout:

I get the same ones, but only revving up to 7,000rpm or so. Never happens below 6500. MS3X in my case. Pots set up as per Frank's (WestfieldMX5) instructions, using a DVM.

I never played with the pots, left them where scott set them back when he built it. WOT I have yet to have a miss, only under cruise.

My issue was fixed 100% with a firmware upgrade.

It's usually either the ms3x grounds or the sensor/placement.

This. How did you wire the MS grounds and your sensor grounds?

Sensor grounds and remaining grounds were wired into the factory ground wiring, just as the ms1 wiring was prior. (which has been the configuration since 2009 with no issues)

This engine has been running fine the way I have had it set up for 4 months, I dont believe it is a grounding issue tbh due to that fact. I did move the wiring harness around at the connector to try and recreate this momentary signal loss to no avail, but I did find that the problem left for a while after moving the harness. So now im thinking its either the connector, or the wiring within the harness is having a bit of an issue... :facepalm: