I've been in Wichita for the last week, and probably won't get home until sometime on the coming weekend. Hopefully this will be my last trip down here until at least March.

I've been flying a lot, but have managed to find a few hours to work on the EIS flight test data program. I now have a working prototype that grabs records at a specified interval, decodes them, adds a timestamp, and writes them to a text file. I want to make it more user friendly, and add a watchdog program that will restart it just in case it ever hangs up. I have never seen a hang up yet, but I want to cover that failure case to ensure I don't land and find I haven't got much data. I'll also move the list of parametres to be recorded, and any special parametre scaling, to a config file, to make it easier for other people to modify for their aircraft.