0-10m
- Wherever there is an error state, set and print flags
- We want to put the flags into both the flash
- Assuming the flash and the radio aren’t one of the flags
- We should assume that we have a radio
- Radio link a good idea
- Priority should be confirming that the flash works and that we get back data
- Probably should halt work on HOOTL and other side projects
10-20m
- No test flights
- Pick a lockdown date for code
- Discuss Error State (Flag all errors that happen in prelaunch)
- Get someone to keep track of what's going on with hardware
- Create wiki page that has chart of all Pyxida versions we know of.
- Record date, version, etc. that we know of
30-40m
- Camera tasks:
- Hardware part:
- Building and attaching circuits to firefly and through to spare GPIO on pyxida
- 'Potting'?
- Taking test results from the cameras to confirm what operating mode they're in
- Epoxy light circuit and USB
- For camera - "Picture will be broken out from the ribbon cable via veroboard"
- Software part:
- Reading from GPIO the stage
- Stage will be "high or low - detect a waveform from a digital can"
- Make a function you can call for initializing camera that "sends on signal wait to see what comes back, send the signal again and wait again, repeat for a certain number of times before it gives up
- Luka: "READ ASANA POSTS AND LIKE THEM" and be more active on asana in general
70-80m
Create better hardware script (see requirements)
Test equipment budget $100
- Set aside $800 budget for pyxida hardware (450 spent so far)
80-90m
need three fully assembled boards; rest for testing
$50 each plus parts -- $350
$800 budget for hardware
groundstation temps - $500?
extra spending for away team on mountains
2 dipoles -- $40-50 each
reduced the budget by $700
more batteries
oxidation problem with pyxida 6
cover and launch procedures
flight computer requirements
away team procedures
more programmers/debugger - upload firmware
90-100m
- Currently able to flag the firmware to upload to the flash, but worried that we cannot do that with the debugger for the first time
- The debugger generates a hex file and uses ozone & Jlink
- Even if it doesn’t work the first time, we can use programmer to flash all the boards for the first time and then use the debugger
- Have 5 devices that can program on pyxida
- Next time, talk about better handling of launches for firmware, more detailed specification on how we configure boards, how we read the flash
- Also, clean Github issues
- Want to be able to inspect stuff through CLI, so that when you connect USB, you can control stuff, read out flash/config
- Currently, pyxida check during startup if USB is connected, if so, then it goes into a state where you can issue some commands (not well-defined though and needs to be fixed)
- Tasks for firmware:
- Downloading flask through ground station
- Configuring from ground station (in any state we’re at)
- Some way to read out configuration values and modify them/update them to pyxida, also need to have default config values
- Need the ram values for configuration to be updated
- All of this needs to be relayed back to ground station in messages, letting us know when something has been modified/updated
100-110m
- Work on ground station needs to happen.
- We need someone working on ground station.
- Need to implement configuring through ground station. There's a firmware task here too.
- Connect to pyxida and read/write config values.
- Pyxida will need some way to restart after this
- There is no official way to get data from Pyxida
- There might exist a script that might help us read from flash.
- We still need to figure out how to merge all of the features
- moving to the next hardware iteration?
- We need to figure out if current code is compatible with new hardware