Laptop datalog freezing or disconnecting is usually due to interference. You can log with a 3.5 screen onto an SD card while you figure it out. On the newer software versions the datalogging rate is decent even on the SD card compared to the older software/firmware versions. Make sure none of the plug wires are running close to any sensors or sensor wiring. Have seen breakup issues due to a plug wire too close to the crank sensor, and have also seen various sensors cutout during a pull and all the other sensors on the same 5v and sensor ground circuit get skewed due to a sensor harness being too close to a plug wire. Not having the logging and breakup issue till you put CO2 on it points towards interference as well since more EMI will come from the plug wires as cylinder pressure goes up. In one case I dealt with a fuel pressure sensor would quit reading during a pull due to the MAP sensor wiring being too close to a plug wire, just to give you an example of the weird stuff that can happen.
I think we did figure it out and was a few different things. My laptop has been on the fritz so we used Jordan’s laptop, unplugged the dash and ran the usb right to the can splitter. That fixed the data log issue then breaking up when adding boost issue we had to do a custom timing setup because I realized i have the wrong cam gear in it. Dwell may have been to short with 1.5ms so changed that. I will have more update in next video but it has made a 700hp pull on 10psi
