Feature request: Additional fields in the TS log file.
Posted: Wed Dec 10, 2014 12:26 am
Hi,
I've been running the car and logging my runs for later analysis. Specifically so I can write a program to crunch that data to provide tweaks to the map. If and when I finish this it will be GPL'd along with the rest of the project. I'm missing some critical values in the log to do these things, though. Here is a header of an TS log (MSL format). This log was produced by revision 5733.
Issues:
- Fuelload is always 0. Probably because I'm using MAF based fueling This should make sense in SD fueling?
- Missing ignition information, maybe ignition advance. This one is really necesary when we start hunting for more power.
- It would be nice if we could break down from the data in the log how much did the base pulse and the enrichment contribute to the final injPulse. This would require at least the enrichments to be added to the log.
Fix:
Not sure how TS works yet, but some of these values are probably already broken out. I looked in firmware/tunerstudio/rusefi.ini and found that there is a DataLog section. Maybe these values can be added here.
I've been running the car and logging my runs for later analysis. Specifically so I can write a program to crunch that data to provide tweaks to the map. If and when I finish this it will be GPL'd along with the rest of the project. I'm missing some critical values in the log to do these things, though. Here is a header of an TS log (MSL format). This log was produced by revision 5733.
Code: Select all
"MShift v0.01: Bowling & Grippo MS1 Base Code MShift v0.01"
"Capture Date: Tue Dec 09 19:36:10 AST 2014"
Time RPM CLT IAT TPS MAF MAP AFR vBatt Fuelload injPulse
RPM <B0>C <B0>C % V MAP AFR V % ms
172.018 1200 70.0 30.0 0 0.02 8 21.12 7.81 0 1.616
- Fuelload is always 0. Probably because I'm using MAF based fueling This should make sense in SD fueling?
- Missing ignition information, maybe ignition advance. This one is really necesary when we start hunting for more power.
- It would be nice if we could break down from the data in the log how much did the base pulse and the enrichment contribute to the final injPulse. This would require at least the enrichments to be added to the log.
Fix:
Not sure how TS works yet, but some of these values are probably already broken out. I looked in firmware/tunerstudio/rusefi.ini and found that there is a DataLog section. Maybe these values can be added here.
