Action Items
- Work on Final Report - All
- Finalize website content - David
––––––––––––––––––––––––––––––––––– Demo Day –––––––––––––––––––––––––––––––––
- Set up table and poster with demo
- Purchase supplies for demo day - David
- Make edits based on Schafer suggestions - all
- Build new daughter boards - Richard
- Continue to refine UI - Mike
- Put new heater in - Richard
- Make separate demo showing the TOF boards - All
- 3D print UI holder - Richard
- 3D print spacer to fill in hole at the top - David
- Continue fine tuning code - Eric and Richard
- Work on making the UI look nicer - Mike
––––––––––––––––––––––––––––––––––––– DR4 ––––––––––––––––––––––––––––––––––––
- Assemble edited boards for demo day - All
- Test overall integrated system with main board/coffee maker - All
- Solder/Attach Pre-crimped wires for JST connector cables for board interfaces - Mike
- Put together boards with mechanical housing for DR4 - Mike and David
- Order edited daughter boards from OshPark/Elecrow, whatever will get here in time for Demo day (the earlier the better) - Mike and Richard
- Figure out way to mount transistors onto old boards for the demo for DR4 - Mike
- Put together second daughter board and test functionality of the two boards daisy chained together - Mike
- Adjust integrated code as needed for full operation for DR4 - Eric
- Integrate new TOF-testing code with overall operating code - Mike and Eric
- Figure out how the demo for DR4 will go down since we need to take current boards out and put new boards in - All
- Verify with Schafer necessities for board access after demo day - All
- Make and order poster for Demo Day - David
- Begin Final Report - all
- Create DR4 agenda - Richard
- Reattach wires that were cut when making the physical housing - Mike and David
- Work on daisy chained TOF boards - Mike
- Get requirements list ready - David
- Create website - David
- Continue working on code - Eric
- Work on initial poster design - David
- Get a finalized mechanical housing - David
- Assemble another TOF board - Richard and Mike
- Debug and fix code - Mike
- Figure out the issue with the TOF board and fix it - Richard and Mike
- Test and debug boards - all
- Build boards - all
- Start crimping for connectors - Mike
- Make update meeting agenda - Eric
- Order 3D printed parts and revised versions - David
- Continue to refine code - Eric
- Finalize how to mount boards inside Keurig - all
- Order boards and parts - all
––––––––––––––––––––––––––––––––––––– DR3 ––––––––––––––––––––––––––––––––––––
- Work on Board Revisions
- Work on DR3 agenda - all
- Develop plan for DR4 - All
- 3D model the reservoir extension - David
- 3D model the housing extension - David
- Work on board scheme - Richard and Eric
- Establish control over the brew and power button with code/ESP32 - Richard and Mike
- Work on board routing - all
- Gain control over the reservoir flow - Mike
- Add UI and rotary encoder to board
- Develop the Integrated Hardware/Breadboard Demonstration - all
- Make a decision on MOSFETS versus just a direct connect to IO - Mike and Richard
- Work on extended reservoir - David
- Re-configure new coffee maker to get it where it was - Mike and Richard
- Work on code - Eric
- Work on modifying the Keurig housing - David
––––––––––––––––––––––––––––––––––––– DR2 ––––––––––––––––––––––––––––––––––––
- Develop a plan for DR3 - All
- Work on DR2 agenda - Richard
- Work on sensing demonstration - Eric
- Work on Coffee pour demonstration - Richard and Mike
- Develop preliminary board designs - All
- Create daughter board schematic - All
- Create main board schematic - All
- Continue to figure out their finite state machine for making coffee - Mike and Richard
- Purchase new sensor type to try for the liquid cup detection - David
- Purchase another Keurig - David
- Look into these sensors
- Sensor 1 - Too expensive
- Sensor 2
- Sensor 3
- Sensor 4
- Sensor 5 - Inaccurate Ranging
- Sensor 6
- Sensor 7 - Range too short
- Look for new sensors for liquid height - Eric and David
- Determine Mux to combine the sensor inputs
––––––––––––––––––––––––––––––––––––– DR1 ––––––––––––––––––––––––––––––––––––
- Create DR1 agenda - Mike
- Determine regulator needed - Mike
- Figure out power requirements are needed for the pump, heater, and valve - Mike and Richard
- Determine what microcontroller to use S3 or C3 - all
- Research and make a decision on the UI and its communication protocol - David
- Test the Ultrasonic Sensors - Eric
- Make a final determination of a more detailed subsystem design with regard to the cup sensing and the pour tracking - Eric
- Think about how are we going to heat - Mike and Richard
- Attempt to control pump using 12 V power supply - Mike and Richard
- Use multimeter to analyze components brew cycle - Mike and Richard
- Disassemble second Keurig mini - Mike and Richard
- Test pump control with DC power supply - Mike and Richard
- Assess internal construction - Mike and Richard
- Test ultrasonic and TOF sensors for liquid height - Eric
- Order Ultrasonic sensors - David
- Test liquid height with Lidar sensor - Eric
- Acquire new Keurigs - All
- Begin testing with TOFs for cup height detection - Eric and David
- Purchase height detection sensors (TOF/Ultrasonic) - David
- Purchase liquid detection sensor (Ultrasonic) - David
- Have Eric ship his stuff from home - Eric
- Create cardboard mockup of cup and liquid height sensing - David
––––––––––––––––––––––––––––––––––––– DR0 ––––––––––––––––––––––––––––––––––––
- Create DR0 Agenda – David
- Determine the work done over break – Eric
- Create the system block diagram (retrofit from the HLD) – Eric
- Create the plan for DR1 – all
- Create plan for DR2 – David
- Develop list of requirements - all
- Write out our plan for complete subsystem design - Mike