PID List:
FF12A5
FF12A6
FF1257
78
FF1282
73
FF12AB
44
3C
3E
10
66
43
34
FF1214
FF1240
24
FF1215
35
FF1241
25
0C
FF1202
04

File logging settings

Synchronous Logging : false
File logging interval : 0,5
Only when OBD connected : true
Automatically log gps : true
Automatically log G Sensors : true
Rotate logfiles : true
Format log values : true

Realtime web upload : not used

Trip Recording : used
Automatic trip recording : true
Update “Trip distance” only when connected to ECU : true
Discard trips < 0.5 miles : false Ignore short gaps between trips : true Log trip fule consumed : false Also log selected sensors : true Twitter : Not used Facebook : Not used

Confirmed this also happens if the ‘Only when connected to OBD’ option is ticked as well

So if either the following options are ticked, and you don’t connect to the vehicle ECU, you will get 0 byte files:

* Only when connected to OBD (doesn’t write to the file when there’s no OBD connection)
* Synchronous logging (which only writes to the file when connected to the ECU over OBD)

This will be why there are 0 byte files. I will implement a cleanup method to remove these files if no logging happens in the next update, which should relieve the annoyance of empty files

Quote from admin on January 18, 2022
Confirmed this also happens if the ‘Only when connected to OBD’ option is ticked as well

So if either the following options are ticked, and you don’t connect to the vehicle ECU, you will get 0 byte files:

* Only when connected to OBD (doesn’t write to the file when there’s no OBD connection)
* Synchronous logging (which only writes to the file when connected to the ECU over OBD)

This will be why there are 0 byte files. I will implement a cleanup method to remove these files if no logging happens in the next update, which should relieve the annoyance of empty files

————————————————————–

I’ve uploaded a CSV/TXT, with the PID’s selected (engine off) and all are present in the log.

https://www.uploadarchief.net/files/download/tracklog-2022-jan.-18_15-34-44.csv.txt

Hi!

Thankyou for the feedback – it is valuable as it means that the settings were not as clear as they could have been as to what was going to happen with some of the options

I’ve made changes to the wording in the settings to better reflect why you may not get any logfiles and this will be in the next beta release. I also added a ‘cleanup’ for those empty logfiles as well!

Hi!

You have told the app to log all the time, which is what it is now doing

You need to turn on the ‘only when connected to OBD’ option in the app settings, otherwise the app will log all the time even when not connected and can generate large logfiles.

Hi!

No problem – actually letting me know this happened helps me understand where things can go awry, I’ll try and add a warning or something like an ‘are you sure, this might produce large logfiles?’ kind of warning