Having a dumb issue I can't figure out.
My nb1/bp4w was running great, then developed a very inconsistent problem. Occasionally, under high boost, it will cut out for a split second. Sometimes for longer, almost like the key is rapidly being cycled on/off. I discovered that the RPM signal drops to, or near zero at these times. Attached is a very short log of it happening once.

I also have a composite log of it happening a separate time I will link to here: https://drive.google.com/drive/folders/1Qfua2N5VJoNFqzfRq9e7woXCTh69SOp3?usp=drive_link
I found a couple of brief instances where the cam pulses seemed to happen too far apart, while getting too many crank pulses-triggering the red sync error in MegaLogViewer. I'm new to reading that type of log.

Cam/crank sensors are both pretty new - Mitsubishi/Beck/Arnley, respectively. Tried a different cam sensor with the same result, and zip tied the connector to make sure it's not coming loose. Might try a different crank sensor, too, but don't want to go full parts cannon. I have extensively messed with trigger wheel gap. Brand new main relay, replaced because of a separate issue I had.

Really confused at just how sporadic and random it seems to be.
Seems to almost always happen in 4th, 5th, or 6th gear which makes no sense to me.

Running LS coils from FlowForce, they've been great other than having to replace plug wires recently.

 

Hey bud. My nb1 motor setup developed a misfire shortly after getting the swap running. It started only in boost and got worse. For whatever reason switching the main trigger setup from rising edge to falling edge (or vice versa, I can't remember) fixed it. Be sure to re set your base timing after you make this change since it will be slightly off after.

 

Hmm, interesting. I'll check that out. Just weird that it's run flawlessly for 1k miles until this started inconsistently happening. Thanks for the insight

 

Definitely losing sync. Looks like a cam sensor issue based on googling the error code (lost sync reason 31). If you google that error code you should find some threads about how to troubleshoot and debug.