| Commit message (Collapse) | Author | Age |
|
|
|
|
|
| |
None of these appear likely to have caused actual problems.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
The satellite info wasn't being correctly converted from telemetry
files to the data log structure, so ao-postflight was not seeing it.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
GPS date/time information was already being stored in the log, it just
wasn't getting displayed by ao-postflight.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
| |
With the switch to the skytraq GPS unit, we don't have the same level
of detail in the GPS stream, so stop reporting that in the telemetry
stream, in the UI and writing it to eeprom.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
Realloc'ing the wrong data, and failing to set the realloc'ed size was
causing ao-postflight to crash while reading long logs.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
|
|
| |
Telem files have multiple entries of the same state, and sometimes
long gaps between recordings. Deal with this as best as possible.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
This tool reads either an eeprom or telem log file and displays some
rudimentary data (max accel/alt for each flight stage).
Signed-off-by: Keith Packard <keithp@keithp.com>
|