Adding timestamps will be easy to do. I'll add that soon.

The current rate, I think, is 10 updates a second but I intend to redo this and make it more real time.

I think you have other uses in mind than I do. If you do a WOT pull with that sample rate, you'll have one log entry idling and the next log line you'll be going 150 km/h already. That would be of no use for analysing O2 levels versus map and such things. At redline, my bike ignites each cylinder at 70 Hz.

After one single WOT pull to redline, I can produce something similar to a dyno graph if I have the timeline and good enough sample rate. Near redline, 10 Hz resolution is low, but for most purposes it will do. The LC-1 sensor only outputs 12 Hz anyway.

BTW, look at the beatyful map I made with Innovate Logworks at 10 Hz: http://www.v11lemans.com/forums/index.php?showtopic=13803&view=findpost&p=164170

I'm delighted you asked cause I'm very proud of my plugin 

It passes ALL available info from MyECU as well as some more info that is derived from the raw data. It's overkill of course, but after I had solved all mysteries involved in parsing the raw data and passing it to LogWorks, it was a piece of cake to add everything I got.

Before this plugin, I wrote a generic GPS (NMEA) plugin as an excercise. Using both, you even get stuff like ground speed and MSL altitude if you want to 

Finally, LogWorks is a powerful beast, so it can use all this data in sensible ways, like filtering out all crusing parts from a huge log file or calculating actual horsepower from WOT pulls, given you can input cw values and other stuff. Or give you a complete new map ready to use, with sensible changes! All in all, it's very cool toys but I haven't used them yet this year. It's too easy forgetting to just RIDE the freight train!