https://otter.ai/s/iemIzKOxRviN3cppbaXC-g
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
20-30m
- Wiki page that keeps track of Pyxidas, cameras, debuggers, antennas, etc
- where, with whom, condition of part, etc
- camera stuff: using fireflies, connecting to them with existing bbc
- putting on photodiodes to see if light is on or not on the cameras
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
...