This document briefly outlines the procedures for operating the Recovery Trigger Board.
Procedures presented :
| Part Name/ID | Type of Part | Version ID |
|---|---|---|
| RE Board | Hardware | VF |
| RE Board | Software | Latest |
| Equipment | Qty | Packed in | Sign-off | Done |
|---|---|---|---|---|
| Screwdriver (electronics flathead) | 1 | Malette RE | ......... | |
| Buzzer directory | 1 | Drive | ......... |
Quantities are given for a single board.
| Part | Qty | Packed in | Sign-off | Done |
|---|---|---|---|---|
| Trigger Board | 1 | Malette RE | ......... | |
| SD-Card | 1 | Malette RE | ......... | |
| E-Match | 1-2 | Malette RE | ......... | |
| Battery Plug | 1 | Malette RE | ......... | |
| Custom Parachute Plug | 1 | Malette RE | ......... | |
| 18650 LI-ion Battery Cell | 1 | Malette RE | ......... |
Insert the SD-Card into its holder before starting any procedure (the code will throw an error if it doesn't detect the card on startup)
\setcounter{rownumbers}
| Step | Task | Time | Sign-off | Done |
|---|---|---|---|---|
| \rownumber | Battery Inserted (or not) | - | ......... | |
| \rownumber | If Battery is inserted: insert battery plug (while holding user button if previous code was uploaded) | - | ......... | |
| \rownumber | While holding Seeed BOOT button ('B' silkscreen), insert USB-C cable | - | ......... | |
| \rownumber | Insert other end of the cable in a PC running Arduino IDE | - | ......... | |
| \rownumber | Fetch latest code from Github | - | ......... | |
| \rownumber | Upload the code from Arduino IDE | - | ......... | |
| \rownumber | When code upload finishes, either the code starts running immediatly (8 rapid beeps) or nothing happens (in that case unplug and plug back the USB-C cable) | - | ......... | |
| \rownumber | If running hold the user button during the 8 beeps, 3 more short beeps should be heard and the Seeed's yellow LED should be off -> unplug the USB-C cable | - | ......... |
If you were too slow to hold the user button on step you will have heard either three long beeps or one long beep
If three long beeps were heard something is amiss with the board or code investigate and then resume from step #0
If one long beep was heard (followed by other beeps or not) unplug and the USB-C cable while holding the user button and plug it back in. Resume from step #7
The code is now uploaded and the board is ready for the startup procedure software wise.
We assume that the code was succesfully uploaded and only a reset of the Eeprom and more generally of the code is needed.
First we explore the situation where the board is running (battery inserted, battery plug out, status blue LED on, Seeed yellow LED blinking rapidly)
\setcounter{rownumbers}
| Step | Task | Time | Sign-off | Done |
|---|---|---|---|---|
| \rownumber | Insert battery plug while holding user button | - | ......... | |
| \rownumber | Remove battery plug, 8 rapid beeps should be heard | - | ......... | |
| \rownumber | During the beeping, hold the user button, 3 additional shorts beeps are heard and the Seeed's yellow LED is off | - | ......... | |
| \rownumber | Insert the battery plug | - | ......... |
Now we explore the case where the board is off but code has been ran on it before and a reset is needed.
\setcounter{rownumbers}
| Step | Task | Time | Sign-off | Done |
|---|---|---|---|---|
| \rownumber | Insert battery plug | - | ......... | |
| \rownumber | Insert Battery | - | ......... | |
| \rownumber | Remove battery plug, 8 rapid beeps should be heard | - | ......... | |
| \rownumber | During the beeping, hold the user button, 3 additional shorts beeps are heard and the Seeed's yellow LED is off | - | ......... | |
| \rownumber | Insert the battery plug | - | ......... |
Board has been reset and is ready to follow the Board Startup Procedure again.
We assume that the code has been succesfully uploaded or reset. This means that the last thing that happened to the board is either the Code Upload Procedure's last step or the Code Reset Procedure's last step.
Furthermore, we assume that the SD-Card is in its holder and that the battery plug is inserted.
\setcounter{rownumbers}
| Step | Task | Time | Sign-off | Done |
|---|---|---|---|---|
| \rownumber | Insert Battery | - | ......... | |
| \rownumber | Insert custom parachute plug | - | ......... | |
| \rownumber | Insert the E-Match in a screw terminal using the screwdriver | - | ......... | |
| \rownumber | Pull the battery plug, the blue user LED should be on, and 8 rapid beeps followed by a long beep (and the battery status beeps) should be heard | - | ......... |
The board is now started, armed and waiting for takeoff. You can check on battery health by listening to the intermittent beeping and cross checking with the buzzer directory.
The board is armed with black powder so operators should send the least amount of people to perform this procedure as a security measure.
It is assumed that this is taking place after the Board Startup Procedure.
\setcounter{rownumbers}
| Step | Task | Time | Sign-off | Done |
|---|---|---|---|---|
| \rownumber | Insert the battery plug while holding the user button | - | ......... |
The board is now off but the E-match should be removed if further manipulation is needed as a safety precaution (operators must be careful of short circuits that could blow the E-match).
Depending on the situation a Code Reset Procedure may be needed before doing the Board Startup Procedure again.
We assume that the board has blown the E-match already. More than one operator can be present in case pictures need to be taken if at touchdown for example etc...
\setcounter{rownumbers}
| Step | Task | Time | Sign-off | Done |
|---|---|---|---|---|
| \rownumber | Insert the battery plug while holding the user button | - | ......... |
The board is now off and safe to operate.