Woolich tuning MT09SP Pt4 - Dealing with poor extracts. Fuel cut outcome. Decoding their log file

There are multiple parts squished into one video.
I set out to test the disable fuel cut setting and determine why their csv had TPS and not ETV thinking that TPS was actually ETV.
Spoiler...
Disabling the fuel cut really smoothed out the harsh engine braking as well as removing the transition at 3000rpm.
But more surprisingly I was shocked to discover that the CSV extract was outputting TPS and not ETV which makes the CSV extract completely useless for any practical purpose.
So do I give up/give in? F##K NO!!
For those who care to stick around I then go into detail about how I decoded the woolich log file. Amazingly I decode a make my own csv converter to extract lot more than woolich expose anywhere including identifying that they have some bugs in their own processing of the log file for the MT09
There will be more on that in a later video but basically the ETV calculation error puts Autotune AFR readings in the wrong ETV/TPS cell so every single Woolich autotuned MT09 (gen3 for sure) on the planet is wrongly tuned. oops.
The next thing I do is a rambling discussion of a lot of potential changes while I unintentionally demonstrate some of the usability issues in the UI. LOL
As for the delays in the videos... Well the rabbit hole gets a lot deeper.

[@stephengale8601]

Ive got to watch the rest of your videos.. Injector Duration should be in milliseconds..

[@KHIJAPAN]

I asked Woolich to give me those data you decoded, and they refuse by saying they were very busy. Is there a way I can get that converter to excel file and format it to my ECU data?
Well done!