With a whopping total of 10 e-flights under my belt now, I can relate to your need to manage the logging buffer contents more easily. The feature that you want to ask them for is a circular buffer with time stamps at the start and end of a session, or at least with a unique session ID to discern what you have left in the buffer. A circular buffer simply wraps around when it becomes full and starts overwriting the oldest data, so you always have the most recent data that will fit the buffer memory that is available. A snake eating it's tail, if you will. The other handy thing would be an LED code/beep code to tell you that you're approaching, or are already into a wrap around condition, thus alerting you to grab the data from the controller before you lose the history that you may want.
Ed, I know that sometimes we complain too much, given the riches of information available as a built-in feature that used to be an expensive add-on not all that long ago.
More of a "Don't you wish they would also..." kind of musing. And while I'm musing about "Why don't they...?" kinds of things, it would also be nice if the Data Connect circuit (the one that lets you download ESC data logging without unplugging the ESC signal wire from the receiver) was also contained on the ESC circuit board instead of an add-on, in-line accessory which introduces more weight and another point of failure. I'm sure that's on CC's to-do list.
OK, so what model and electrical bits are you flying? Enquiring minds want to know!
