Integration of remote pilot / graphlog / simulator / gpsview into a single windows program (rprog.exe). These were all previously separate programs, but integrating brought several benefits.
Allowing flightcontrol.c / flightcontrol.h to live in both the linux flight computer and rprog. These files are getting a little larger than I care for, but I manually transfer them around a lot with ftp, so I am inclined to leave them as single files. I do very minimal processing of the sensors in the flight computer sensor code files, leaving most of it for the portable flightcontrol.[ch] files, so I can simulate noise characteristics and observe responses. Forward and backward compatible log file format. I am constantly adding and removing fields from the telemetry packets, and this was causing problems with viewing older log files, so I now have a clean data format that lives with changes. Each telemetry packet dumps a tab-separated row of numbers, and the file is headed with a tab separated row of field names. Using tab separated text allows me to do useful manipulations directly in Excel, and the code tracks the known and unknown field names, so you can use the current version to view graphs of older log files, even if there are more telemetry fields available now. Rprog dumps every single telemetry packet it receives to an autolog file, even if it isn't in monitor telemetry mode. These files can get to be hundreds of megs if the lander is just sitting there for an hour, but on a couple occasions we had missed data we wanted when it required explicit dumping to a file. You never know when you are going to want to go back and look at, say, a slowly rising temperature trace. John Carmack _______________________________________________ ERPS-list mailing list [EMAIL PROTECTED] http://lists.erps.org/mailman/listinfo/erps-list
