AFR display

[WFMCNALLY86]

I was experimenting with trying to make the esp32 respond to scanner requests on the can network to mimic the AEM 30311 because that seems to work with the MPVI in standalone and wouldn't require the prolink cable be attached also but was having difficulty making it connect and abandon the idea due to time. I believe the problem is caused by the hp tuners adapter cable as it is not just a simple wire to wire connection. Honestly for my application i haven't had any speed issues logging with analog. Even via can bus the Spartan 3 has a 10ms response time so at 8500 RPM you miss more than half the exhaust events anyway. I am just recreational riding and not trying to tune to the ragged edge but if i were racing I would definitely want every single edge possible.

[Swampdonkey]

Me too. Im just going to add a wheel and a cam and springs retainers, but I have the 230, so it has another 100 hp on the table. After that I am done until the car gets a blower��.

I just want to be able to reliably tune it and remove all of the stuff and let it live open loop (hopefully for a while).

Have you had any issues with voltage accuracy issues? I definitely dont want to be trying to tune off inaccurate afr values.

[WFMCNALLY86]

No it has been spot on with the dash. If you push the engine stop button after running it and compare the reading in the exhaust it will be very static and you can easily compare the dash (CAN value) to the analog value in HPT.

[Swampdonkey]

Thats a good point. My only fear is since the mpvi3 is grounded through the can plug (fuse/relay panel) and the spartan is grounded directly on battery negative, there may be a slight offset.

I did put 2-pin connectors on all of the i/o for spartan and prolink. Ill try to get some standalone logging, still havent used it since they fixed the spartan can issue.

What ide did you use for the esp32 and it looks like c or one of the derivatives.