-
Notifications
You must be signed in to change notification settings - Fork 5
Power Budget
There are 3 different possibilities when the RockBLOCK downlink period has been reached.
In the first case, the RockBLOCK gets a high enough signal to attempt to downlink. However, the downlink fails for some reason. This is considered a "hard fault". This branch includes a test script that puts the RockBLOCK in sleep mode, attempts a downlink ignoring signal strength, and then puts the RockBLOCK back in sleep mode. This is the worst case scenario in terms of power budget. A hard fault resets the downlink period. The following graph shows RockBLOCK current consumption during this scenario.
In the second case, the RockBLOCK gets a high enough signal to attempt to downlink and successfully downlinks. This is the optimal behavior. A successful downlink resets the downlink period.
In the third case, the RockBLOCK never gets a high enough signal to attempt a downlink. After attempting this for a certain number of minutes, the downlink period is reset. This is considered a "soft fault".