|
i log everything in that list as well as commanded afr, throttle position, fuel system status, injection mode, coolant temp, oil temp, intake air temp, and a few other less important things.
intake air temp and coolant temp are mostly used for filtering the data before processing. being able to filter on fuel system status and injection mode are also crucial to cutting through the 'noise' and getting the data to return something useful.
one thing missing is flkc. this isn't something you log in the traditional sense, it is not a steady stream of data thrown into a column. you read it from memory and (at least with brzedit) it attaches a text file to the log with the contents of the flkc table. i would consider this to be pretty crucial, as it's a full 1/3 of the knock-control strategy you can't see otherwise. i also noticed fbkc is missing as well, that is important.
the key thing i've learned about tuning from logs is that you need lots of data, you need to filter the data to eliminate noise, and you need to be able to process the data intelligently afterwards. looking at a csv file is mind-numbing, making graphs slightly less so. i use excel or apple's numbers to quickly generate scatter plots and what not as i go to help visualize things and see where the data really is.
|