| Commit message (Collapse) | Author | Age |
|
|
|
|
|
|
| |
This lets us tell if the altimeter supports 32-bit GPS altitudes in
the eeprom log.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
Uses the GPS data and/or previous kalman data to compute the upper 16
bits of the truncated telemetry altitude value.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
Detect when the wider data is present and handle it correctly
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
Scan entire flight to figure out which columns to include before
outputing header or data. Limit data output to values which are valid.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
|
| |
Parse out hdop/pdop/vdop from telem and eeprom. Deal with legacy
eeprom files that have dop/100 instead of dop/10 values.
Clear state DOP values to MISSING at startup
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
Altos now supports 2400 and 9600 baud in addition to the classic 38400
baud rate. Add support to altoslib for these as well
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
| |
When the transmitter serial or flight number changes, we re-init the
state information, but we want to preserve the receiver serial number
so that the log file has that in the name
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
|
|
| |
We're seeing some log files created without a suitable -via- number
included. My hypothesis is that incoming telemetry is getting
interleaved with the configuration data containing the serial
number. This change simply disables telemetry while retrieving the
configuration data to try and keep that from happening.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
Prepare for future release by bumping java versions now
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
This will let us move them into the Mac OS X menu bar, as well as
making them look a bit nicer.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
Use MISSING instead of bogus values so that displayers can tell what
to do.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
Makes display of these values consistent across all instances
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
It wasn't getting cloned
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
Provide a common presentation for voltage values
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
If we don't remove the telemetry monitor, the telemetry device will
still be sending telemetry, which isn't good.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
If we ever get around to supporting multiple simultaneous remote
devices, we'll need to notice that the serial changed right away
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
| |
Long idle periods with TeleGPS can easily overflow 16 bits of tick
count. Using the GPS seconds provides an additional sort which will
span the tick wrap-around.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
| |
This lets TeleGPS report height/speed values without needing to
customize every AltosState user to pull out GPS values when the other
sensors aren't present.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
| |
This lets TeleGPS just show the battery voltage values without also
adding enable lines for the other flight computer ADC values like
ignitor voltages.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
TeleGPS has no flight state, so add a new 'stateless' state for code
to handle this case differently than any of the existing states
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
This doubles the amount of space available to log position information
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
| |
TeleGPS had configurable boost-detect values; those have been replaced
with a configurable stop-tracking motion limit and logging/telemetry
interval value.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
* Use new log-space value provided by firmware when available.
* Divide that up into 1-8 flights and offer those sizes as options to
the user instead of a fixed set of sizes.
* Show how many flights each selection will store
* This also checks values provided by the user
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
| |
This reverts commit d69547796caf74405f8304d23d4ae318315bbd7b.
|
|
|
|
|
|
|
|
| |
TeleGPS stuffs battery voltage in the apogee_delay slot of the
configuration packet. Pull it out from there and stick it into the
current state.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
I suspect the 15 and 27 values are a 'close approximation' for integer
work on the cc1111 devices
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
TeleGPS adds 0x80 to the state value to signify that this otherwise
unused byte contains the current state value
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
Provide a way to elide the usual flight data from a graph for TeleGPS
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
| |
Instead of listing products with the 'l' command, just exclude
products that don't have logging from using the 'l' command to collect
the number of stored flights.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
|
|
|
|
| |
Build an exception handling chain to get numeric parse errors
propagated all the way back to the original 'save' command and up into
a dialog window, including the pyro channel, field and value that were
in error.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
Moved the altosui graph files to altosuilib and fixed things up.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
Move a couple of files from altosui to altosuilib, hook up the info
table after changing it to implement the AltosFlightDisplay interface
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
This contains a summary of the tracking info, including position,
speed and course.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
log-format was added for 1.0; earlier log files don't include that,
but do say which product they're from.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
API has changed for these libraries, time to bump the file versions
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
|
|
|
|
| |
memory
Prepare to share with TeleGPS application.
This also has the changes to the site map tile which cache only a few
images and regenerate the flight path on the fly, saving piles of memory
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
It's sharable, so share it
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
GPS fields past 'day' were not getting parsed. Ground values for the
IMU were not getting parsed, but a false 'temperature' value was being read.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
calibration
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
| |
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
|
| |
TeleMega records whether each pyro has been fired in the eeprom file;
track that in the AltosState record.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
|
|
|
| |
Just cleaning up the source code.
Signed-off-by: Keith Packard <keithp@keithp.com>
|