NB miata (bp4w) cam sync issue after V3 migration

Since the switch to V3 i will get crank no starts, it pops from the intake like the ignition is 180 degrees out of time. I have to bump the starter a few times before it will start, then it will usually start again a few times until it sits with the key in the off position for a while or the battery is unhooked. This was not an issue before the update. Once in a while i will notice T-error flashing. I’m attaching a trigger log, this was right after the car was running. I haven’t had a chance to do a trigger log right after connecting the battery. can someone tell me why the trigger pulses are very close together in the beginning then spread out evenly after a few cranks? is it pre and post synchronization I’m seeing?

it actually says i cant post a log

If you can’t upload files yet, use a file sharing service like WeTransfer and paste the link in your post.

I will once I get home, thank you.

https://we.tl/t-COIC1YLSxw here is the log. i also tried falling edge for cam sync, ive seen other posts where this helped but did not help my case. switching to batch fire allows the car to start

do you have any input?

I’m having the exact same issue here. Mazda roadster NB 1999 (JDM model). Using the OEM trigger wheel / cam sensor.

Noticed it already when setting up base timing, where the timing marks sometimes ‘dissapeared’ as if they were 180 degrees out.

Here’s what I’ve seen:

  • Base timing using timing light: crank markings show 50% of the time.
    • Seems 180 degrees out of phase randomly.
  • Cranking: car does not start 50% of the time
    • I did a LOT of tuning with fuel/ignition, to no avail.
    • Went back to base map fuel/ignition for cranking, also got inconsistent results.
  • I currently have to crank it either 1, 2 or even 3 times for it to start.
    • The first times it seems 180 degrees out of phase
    • The car sounds like it’s backfiring a bit / unburt fuel smell
    • Once it finally picks up the right angle, it PERFECTLY starts each time.

A possible fix seems to be using a 36-2 trigger wheel?

Please post your trigger settings and scope from cranking. I will advice

Here are my trigger settings (cam2 is not used):

I’ll make some logs once I get to the car and upload them here ASAP.

The scope is the most crucial thing right now. I will simulate it on the bench.

Here’s two scope logs, first a ‘no start’ that caused it to flood, then a normal ‘start’ (after flooding but started just fine).

no_start.emubscp3 (529 Bytes)

start.emubscp3 (561 Bytes)

Please publish your firing order and coils seetings.

Also please make a scope with multitooth as a primary trigger. Make sure the fuel pump is disabled for this scope.

Also please change the primary trigger edge to falling.

Here are my firing/coil settings. Car is now running on Toyota 1zz coils (note that this did not influence the starting issue at all)

Once I get to my car I’ll make scope with multitooth+falling edge settings.

Could you advice what I should enter for ‘num teeth’ in the trigger settings? It defaults to 60, the mazda trigger wheel has 4 teeth, not sure which ones are missing

It is internally changed to 2. Looking at your config I would suspect wasted spark as an issue (it is not suitable for this trigger).

However the scopes looks suspicious. I will simulate it and let you know.

Strange, because the OEM setup is also wasted spark. Nothing was changed in this regards going in the EMU black setup.

Will provide any scope data you need once I get to my car!

Option Wasted spark means that the EMU will start without camsync as well it will pair the ign. oututs according firing order. In your case you use double fire coils and your primmary trigger doesnt allows to start in wasted spark (without cam sync)

I’ve made tests on the simulator and everything seems to work correctly.

On your two scope the position of the CAM vs crank is different.

No start - the distant from sync tooth to the crank tooth is quite big

Start - the crank tooth is next to sync tooth.

Is there vvti ?

Could you please make a scope with parameter Primary trigger / Take skipped edges on scope.

mazdanb_risingedge_0.emubscp3 (538 Bytes)

mazdanb_risingedge_1.emubscp3 (558 Bytes)

multitooth_fallingedge_2.emubscp3 (530 Bytes)

multitooth_fallingedge_1.emubscp3 (532 Bytes)

multitooth_fallingedge_0.emubscp3 (530 Bytes)

Here are some logs - with the mazda NB setting + take skipped edges this time. And multitooth with 2 tooth with falling edge setting.

I also checked it out and it seems like multitooth with num teeth=2 isn’t correct, from what I interpret it would fire the engine twice as fast as required. Not entirely sure what I’m looking at though.

There is no VVTi in this engine.

Let me know if you need any more specific scope data!