-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Cameron Goddard edited this page Nov 5, 2023
·
27 revisions
- Downlink period
- But should it really ??
- Change downlink period
- By making this a large value, this meets the requirement to stop downlinking completely
- No-op
- ChipSats shall not downlink at the same time. One ChipSat will have an initial delay to make the ChipSats offset.
- ChipSats shall stop downlinking if they have not received an uplink in over 24 hours. This requirement is met by using an alive time counter which is NOT stored in EEPROM. If alive time exceeds 24 hours, downlinking is disabled.
- Downlinks are always the same length. If a sensor fails, those sensor values are 0.
- downlink period only resets upon successful downlink
Two arduinos- one for uploading code, another for print statements.
File -> examples -> ArduinoISP -> pick ArduinoUno

- reset should go to pin 10
- Make sure "Tools > Programmer > Arduino as ISP" is checked
- Set the target board to Arduino Uno
- Load the program "Examples > 11.ArduinoISP > ArduinoISP"
- Upload this program to the Uno
- Set the target board to "MiniCore > ATmega328"
- Ensure the variant is "328P / 328PA"
- Burn the bootloader onto the ChipSat from "Tools > Burn Bootloader"
- Upload ChipSat code using "Sketch > Upload Using Programmer"
- Upload using the "program_via_ArduinoISP" environment
Use Arduino as ISP to Burn Bootloader on AVR Microcontrollers