The more are two reasons CAN logging doesn’t work very well, I’ve tried.
One: The ECU update rate through the OBD connector is very slow, very very slow, I’m talking about 2 or 3 data point as you sweep through second gear. So to work with the data you have to extrapolate the missing data via interpolation, not the best method.
Two: No wideband sensor, so basically no good data. Even with a setup that adds a wideband into the data log like I was using, see problem number one.
The only good way to datalog I’ve found on an R3 is with PC-V, AT-200, POD-300 and use the MAP sensor as an optional (raw) input recording map values into the POD-300 logs.
Even doing it the last way, you miss out on an log of cells in the table that you can easily tune on a dyno but not so easily on the street. Doing sweeps through 20,25,30,40,50,60,70,78,100 percent throttle is a lot of time datalogging on the street. It’s also needs to be open road and preferably up hill so you spend longer in each cell of the table.
It can be done, but it takes quite a long time to do right. My street tune was close but I still picked up 6hp having it on a dyno in early 2017. The more power you have the harder it is to street tune as the bike shoots straight through cells in the table so quickly, once your over about 200hp it’s nearly impossible, trust me, I’ve tried (with some limited success). I’ve been street tuning vehicles for 14 years now and I’m still challenged on the R3, just avoid the headache and do it right