SW: RevM Testing

[hedgecrw]

Peripheral Testing:

• [x] Battery
• [x] Bluetooth
• [x] Buzzer
• [x] IMU
• [x] LED
• [x] Logging
• [x] Power Off
• [x] Ranging Radio
• [x] RTC
• [x] Storage
• [x] System

Bluetooth Testing:

• [x] Visible via commercial BLE scanners
• [x] All characteristics enumerate and do not cause freezing
• [x] Only connectable from PC when charging
• [x] Advertising/scanning intervals are as expected
• [x] Maintenance mode functionality
• [x] Discovery range (>20 feet)
• [x] Doesn't crash with frequent ADV/SCAN updates

Ranging Testing:

• [x] Validate unobstructed ranges at known distances from 0-20 feet at intervals of 2 feet
• [x] Validate obstructed ranges at known distances from 0-20 feet at intervals of 2 feet
• [x] Determine maximum ranging distance for obstructed and unobstructed lines of sight
• [x] Validate ranging with 5+ networks on device

Full System Testing:

• [x] Network scheduling of TotTags
• [x] Correct sounds upon charging status changes
• [x] Power-down mode entered upon low battery detection
• [x] Power-down mode entered prior to scheduled experiment time
• [x] Power-down mode entered after scheduled experiment time
• [x] MCU wakes up upon charging status change
• [x] MCU wakes up upon scheduled experiment time
• [x] Ranging continues with frequent network changes (1000+ changes)
• [x] Ranging continues over extended time periods (1+ days)
• [x] Logged data is as expected

Power Testing:

• [x] Power consumption as expected when transitioning between BLE and ranging
• [x] Determine best voltage for CRITICAL shutoff of devices based on how long RTC clock holds value
• [x] Battery life when in power-down mode awaiting an experiment (seemingly weeks to months)
• [x] Battery life when ranging with 4 other devices
• [x] Battery life when BLE scanning for networks (seemingly days to weeks)