BAWC Forums

Next let me scale back my statement a little. The ECU I'm using now is an Enginelab https://enginelab.net/products/

This is the same as the AEM infinity (my hardware if AEM, I just run the enginelab version firware/software). The enginelab version (which is what AEM starts with) gives you a toolset to setup a functioning ECU, but there is no "model" or control logic in it, you need to write that using the tools they provide:

https://enginelab.net/documentation/

I absolutely LOVE this thing. You can set it up to do most anything you can dream up...but you have to youknow, actually set it up.

I added a model that gives me the % error TB to tb to make sync easy and also use the info to trim the cylinders in between TB syncs

Hardware IO Interface: The user should describe the harness interface requirement to the engine position sensors. There are several harness pins that can be used for engine position sensors where the signal conditioning circuitry ranges from variable reluctance, hall effect and optically isolated inputs. The engine position sensors for the timing setup require the following:

Harness pin: This is the harness pin that the user will interface to the sensor.
Number of teeth: This specifies the number of teeth on the reluctor wheel.
Edge control: The user can have the timing trigger on the rising egde, falling edge or both edges.
Noise cancellation: This value indicates the number of 3.2 microsecond increments that must be present for the hardware to trigger the edge. A value of 10 (32 microseconds) is generally a good choice for this setting. Noisy crankshaft and camshaft sensors can be resolved with adjustment to this field.