Power Commander POD-300: accessory display for Dynojet devices

[northern]

Want to share my experience with device I recently purchase.

There is manufacture information: http://www.powercommander.com/powercommander/products/pod300/powercommander-pod-300.aspx

Also video description:

mknaP_6zASM


And there is shown, what kind of data it could collect for later analyzing (startind from 2:30 of video 1iSJ4Z-EAVQ?t=151):

[northern]

Connection is very easy - one cable connecting to PCV main unit.
There I post my way of mounting display on handlebar: http://gsx1400owners.org/forum/index.php?topic=420.msg44959#msg44959 , but I already do not like this mounting and will think how to put it on different way. Anyway - I consider this device as a tool, and do not think it will be always on my bike. Just for logging and tuning purposes.

After it was installed, I did ~2 day ~300 km ride, while I was collection some logs.
Have to admit - fist time it was not the best and I make few mistakes (also it wasn't test runs, but ride with a purpose, with additional testing), and those test are just first steps to understand, how it all work. I find out, device hive only 4 memory slots to collect logs. Meaning, I can save up to 4 files inside device, and then I have to delete them to collect more. I do not know the size of those memory slots, but I assume the less channels I use for logging, and with smaller data rate (readings per second) is used, the more longer logs can be saved. For my firs logs I record engine RPM, AFR and Throttle position, with rate 1 data collection per 1 second.

Later at home, I export those logs to my computer, and using Dynojet Power Core software, convert those logs to more visually acceptable view (attached pictures).
Don't know, why I have those peek's on AFT chart, but I remember display was showing unrealistic AFR numbers from time to time. May be lambda sensor is getting fresh air somewhere (even PAIR is blocked).
Chart view is showing average AFR in much more understandable form, and having this data, I can modify fuel map myself... BTW, autotune is doing the same 

To be honest, usability of this method is questionable. I see it this way - take a laptop, and go to drag strip, where after collecting logs on some runs, analyse them and correct the fuel map. And then same thing again...

Is it worth it? Can't answer to you, but for me - another toy to play whit