Better datalogging using the stock ECU

[prj]

Yup, it will work.
As will every gauge with 0-5V output.

But is it needed?

[4WheelDrifter]

Just to give you an idea, how detailed this is.
This is cranking and starting the engine, 1.5 seconds:

That is impressive.

[prj]

Ok, so I added some more stuff to the datalogging.
Mainly to calculate target AFR in the ECU and compare target with actual to be able to tune big MAF cars better...

After doing that, data slowed to 33hz on the bench. So it was clear I was hitting the limit of what the 9600 baud rate (about 1 kb/sec) had to offer.
So, I tested the next available baud rate. This is 187500 baud (about 23 kb/sec) on this processor.
My eBay interface seems to support it, and I am now getting a sample rate of 100hz. Compare that with 4hz in VAG-COM, ha!

Though I am thinking that 100hz is overkill. Besides, it will go down with revs, as the ECU is more busy calculating other things, so I am thinking of sticking a time based limiter on it. Or even putting it back to 9600 baud, because 33hz, which becomes around 25hz at revs should be good enough.

[prj]

The culmination of my hard work, as well as a show of how the knock control works in the stock ecu per cylinder.
Knock retard step, phase in speed, thresholds, activation thresholds, maximum retard etc is all configurable in software...

Screenshot showing the goodies:



Turbo is HX40 Super with KKD manifold.

[Sonic]

[Thuppu]

Just readed the thread again. Was there some problems with the wideband AFR input? Do it work properly with the data logging? Or do it need some different signal than 0-5V? Or maybe I havn't understand anything..? which isn't a suprice though.