Dragonfruit Team Meeting - April 17th, 2017
Attended: Kevin, Gordon, Tyler, Kaeo
Updates
- Tryston is setting up a meeting with Garmire who will take us to the roof to put up our board
- need to make sure board works and have a battery ready
- 3.3 Voltage Regulator was thought to be faulty on board 5
- Regulator still didn't output anything when part was replaced
- Tested other pins, and found out the enable pin was also zero
- XBee Vreg takes XBEE_EN from MCU as the enable value
- Sensor 5V Vreg takes SENS_EN from MCU, and is working find
- We conclude that the reason for this problem is most likely because MCU is not coded correctly, and is not set to enable the XBee voltage regulator
- Updated bill of materials for version 2
- Waiting on key to use roof for testing
Problems
- Late to get the key to roof
Tasks
- Set up all reference pins to observe changes in data on roof
- Charging chip debug LED tests
- 1 - 5bit number to voltage tests
- this is used to make sure that the charging chip follows tryston's charging chip behaviors
- to be completed for adafruit charging chip and dragon fruit charging chip
- 5bits = 31 in decimal
- 00000 = 0 = 3V
- 01001 = 9 = 3.9V
- 01101 = 13 = 4.3V
- 10100 = 20 = 5V
- 2 - Use 3 debug LEDs to visually indicate when switching between solar panel and battery
- LED 1 : Vload = Solar Panel
- LED 2 : 4.3 < Vload < 4.5 (around the voltage that Vload switches from Panel to Battery power)
- LED 3 : Vload = battery mV
- If all are off, then the load voltage is between 4.3V and battery voltage
- Need to connect Vload to MCU
- 3 - Use LEDs to flag Ghost voltage, low XBee voltage, and dropped transmission
- LED 1 : Ghost voltage is 4V (this is much too high for XBee power)
- LED 2 : XBee voltage at less than 2.7V (full range is 2.7 - 3.6V)
- LED 3 : flag for transmission (we do not know how to do it yet)
- Need to connect XBee power to MCU
Authors
Contributing authors:
Created by tyamauchi on 2017/04/18 07:21.