| Commit message (Collapse) | Author | Age |
|---|
| |
|
|
|
|
|
| |
The hardware is software-compatible with v1.1, but it's nice to have
the right version number in all of the files.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
| |
The flash part on v0.1 boards is only 128kB.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
|
|
|
|
|
| |
Record separate internal vs external monitoring state, allowing
both to happen at the same time, and when either is turned off, the
other keeps working.
This also adds disable/enable so that other radio users can
temporarily take over the radio; monitoring will resume when the other
radio user is finished.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
| |
Make all monitoring programs define whether they want all of the old
telemetry formats too.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
v1.0 boards have noisy accelerometer data caused by interactions
between RF transmission and the accelerometer measurements; this noise
generates a negative bias in the accelerometer readings. The net
effect is that the estimated speed is lower than the actual speed,
causing early an apogee estimate.
By increasing the sigma value for accelerometer data, the kalman
filter 'trusts' the acceleration data less, putting more weight on the
barometer data. This causes the estimated time of apogee to be closer
to the correct value.
This reduces the response to changes in acceleration.
This new value is applied solely to TeleMetrum v1.0 boards. v1.1
boards correct for this error, and hence can use the correct sigma
value for the accelerometer.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
| |
Report continuity values from remote altimeter
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
| |
Telebt uses one LED for bluetooth connection and the other for telem
packet reception leaving none for RSSI.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
| |
so that ao_launch gets them too
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
|
|
|
| |
This just has simple command-line based packet transfers for testing.
This also adds special ao_telelaunch bits where the launch control
code will live.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
| |
We probably don't want this raw radio interface, but it's a start.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
| |
|
|
|
|
| |
Looks a lot like TM, but without the flight code.
Signed-off-by: Keith Packard <keithp@keithp.com>
|
|
|
More arch-indepdency bits.
GCC stdio is different from SDCC, so create suitable code in
avr/ao_avr_stdio.c
Create macros to initialize the task stack frame and save the task
context.
Add GCC/SDCC type definition compatibility macros
Signed-off-by: Keith Packard <keithp@keithp.com>
|
