May 22

I got the firmware running with the actual trigger pulses picked from the car.

I also noticed that the negative side of the cam pulse was shorted to -0.6V. This is not the case for the pulse generated by the .wav amp. The output impedance for the sensor is quite high: 600 Ohm and there should remain on the genboard some diode set from the 2nd trigger Hall input.

I only have a notebook from the 90's (256kB!!) and was only able to run MegaTune. Here after part of the log file:

||285.862||0||11||

||285.948||10||11||

||286.089||226||11||

||286.210||265||11||

||286.314||388||11||

||286.418||527||13||

||286.560||671||141||

||286.701||570||141||

||286.823||591||141||

||286.945||578||141||

||287.031||652||141||

||287.153||703||141||

||287.312||696||141||

||287.455||759||141||

||287.616||849||141||

I did not find from the Megatune doc what the engine code 141 means. 11 is for cranking, !? 13 is for running +warmup+TPSAccelEnrichment !? ...

Anyway we can see that genboard starts to run while the engine is still cranking, which is a good point.

I feared that because genboard firmware 1.1.90 has to find out the smaller side between the 2 triggers to sync, - which means at least a full cycle of cranking, the genboard start would take too long. This is not the case.