Corrado Govea’s Status Report for March 23rd

This week’s accomplishments

  • This week I made some major modifications to the power management PCB.
    • Initially, I had designed a special circuit to do zero-crossing detection for the triac. This would require having a separate Arduino code to handle the zero-crossing detection and actuate the triac gate.
      • After some research, I found a newer version of the triac driver that I had selected, which has zero-crossing detection incorporated. This allowed me to remove the entire detection circuit.
    • I also re-did the layout with much thicker traces for the HV side of the board, and changed some components that were not rated for 120VAC.
    • Lastly, I compressed the layout in size to reduce the PCB cost from >$60 to just $2 for qty 5.
  • I also submitted the purchase forms for both the PCB and the components (smd for pcb and through-hole for prototyping).

Next Week’s Deliverables

  • Write Arduino code to control the kettle and pump.
  • Test prototype circuit when components arrive.
  • Reflow one board and test.

Status Report: On schedule

Elijah Knupp’s status report for March 23rd

This week’s accomplishments

  • Attended mandatory labs
  • Finished the team’s ethical assignment
    • Personally answered 2 of the 5 ethical questions required for the written portion
    • attended the ethics-based lectures
  • Finished altering the digital scale to allow its integration 
    • Will need to finish testing the signals from the scale. Whilst attempting to tare and orient the scale, received some rogue and incorrect signals. Will need to troubleshoot and possibly replace the AD/C component if errors continue. Next, will need to ensure the rpi properly receives the signal (as I’ve been doing the testing on my PC).

Next weeks plan

  • Finish integrating the scale into the project. 
    • Troubleshoot the system. More than likely due to a bad AD/C converter. Once the errors are ironed out, will ensure the signals are properly read by the rpi.
  • Continue designing and creating custom movement patterns on the 3-D printer for the pour patterns. 
    • was unable to work much on this aspect this past week due to errors related to the scale
  • Plan out cable management for the added components (including the wires coming from the scale). Will be important to ensure the safe operation of the machine (so that no boiling water comes in contact with wires or exposed components).

Status Report: On schedule

Rio Pacheco’s status report for March 23rd

This week’s accomplishments

  • Continued work on Django app(8hrs)
    • https://github.com/Quarks-1/pour-over-and-over
    • Data model definitions refined and tested
    • Home + brew + profile creation page skeletons created
  • Attended mandatory lab (4hrs)

Next weeks plan

  • Design and print water bottle + raspberry pi mount
  • Continue work on web app

Status Report: On schedule

Elijah Knupp’s status report for March 16th

This week’s accomplishments

  • Attended mandatory lab
  • Finished the ethical assignment
    • Both the individual and team components
  • Began integrating the scale into the project
    • Deconstructed the scale, and cut the wires to directly wire into the AD/C, which will then be routed to the Arduino. From there, the signal will be sent to the rpi. This week, soldered the wires from the scale to the AD/C. 
  • Established connection between the 3-D printer and octoprint (on the team’s rpi), tested to ensure full control. 

Next weeks plan

  • Finish integrating the scale into the project. 
    • Create and route the jumpers from the AD/C to the Arduino and then from the Arduino to the rpi.
      • Cable management will be important to ensure all wires and components are safe from the gimbal’s movement and any hot water the machine will be producing
  • Begin designing and creating custom movement patterns on the 3-D printer for the pour patterns. 

Status Report: On schedule

Corrado Govea’s Status Report for March 16th

This week’s accomplishments

  • This week I finished the schematic for the power management circuitry.
    • This includes the new Triac circuit for controlling the PID on the kettle.
    • This also includes adding a transistor to control PWM DC voltage regulation for the DC pump.
  • Selected all components from Mouser and created a BOM to order the components.
    • This includes both SMD and Through-hole for prototyping.
  • Completed the ethics assignment and thought of ways to make better decisions on our project’s design.

Next Week’s Deliverables

  • Place Mouser order for all components of PCB.
  • Place PCB order.
  • Meet with the team for ethics assignment and discussion.
  • Start working on arduino code for controlling the new circuits on the PCB.

Status Report: On schedule

Team Status Report for March 16th

This week the team focused on continuing work on the physical hardware of the system as well as finalizing our circuit design for all of our electrical systems that we are hardware hacking.  A final product for the water pump mount was printed in HTPLA and checked to make sure it fits with the gantry system.  Work was also started on the software side of things, with the GitHub repo and initial web app structure being developed. Integration of the scale into the project has begun as well.

Our biggest challenge coming up is ensuring our PCB will have good integration with the off-the-shelf components that we have.  According to our design spec and theoretical testing, it should work fine, but we will have to wait for real-world testing to ensure that.  We are currently waiting for the PCB to arrive so that we can do this.

We are currently on track.

Rio Pacheco’s status report for March 16th

This week’s accomplishments

  • Finished editing and printed final (hopefully) version of single pump mount (6 hrs)
    • Began printing prototypes at home over break, printed with HTPLA in techspark after break ended
    • Needed to make 2 revision prints due to printing tolerances
  • Began work on Django web application (2hrs)
    • https://github.com/Quarks-1/pour-over-and-over
    • Initial directory + structure setup done
  • Attended mandatory lab (4hrs)

Next weeks plan

  • Design and print water bottle + raspberry pi mount
  • Continue work on web app
    • Make home page + skeleton code for interfacing with hardware
  • Make rough draft for double pump mount

Status Report: On schedule

Team Status Report for March 9th

This week, the team traveled to their respective homes to visit with their families over spring break. This status report is intended to be combined with the status report from March 1st. 

While work was limited due to traveling and rest, we focused on preparing our machine for the next step: integration. This included taking measurements and designing the custom frames and mounts for the components that will need to be mounted to the frame of the 3-D printer.

 

Part A: Written by Corrado Govea

The outcome of our project has users who are not tech-savvy in mind. While being a complicated system to produce the best quality coffee possible, we aim for anyone to be able to actuate the machine without having any prior experience with computer systems. An example of this would be our design requirement to have 5 loaded presets that users can easily actuate without having to program much. By having this goal in mind, we are greatly increasing the size of our user group and ensuring that we’ve removed one of the biggest barriers of entry to lots of “tech-centered” solutions nowadays. It is very unfortunate that lots of these great products are completely inaccessible to non-tech-savvy people, so we are ensuring that this will not be the case with our project.

Part B: Written by Elijah Knupp

When we first began considering creating a machine that would deliver delicious and convenient pour-over coffee, we were really only focused on creating the machine for individuals who did not have the time or desire to learn a new, detail-oriented brewing option. However, as we spoke to others and read several Reddit posts, we realized that this machine could also potentially benefit those who struggle with fine motor controls.  Per the Reddit posts, the individuals who struggled with this spoke about how difficult (or impossible) it was for them to pour boiling water over coffee grounds in a controlled manner for extended periods (a task required for pour-over coffee).  When they asked for suggestions on how to overcome this, most of the replies suggested that they find a new brewing method. However, we did not care for this answer. We fully believe that our pour-over coffee machine will solve many of the issues that these individuals are facing, even though there may be a cultural belief that they should “find a different brewing method.” We believe that this pattern of thinking  (“let’s figure out a way” and not “try something else”) could increase the connectivity between different groups of people and bring joy to those formally excluded in some cultural activities.

Part C: Written by Rio Pacheco

Due to the wasteful nature of pod-based machines, we aim to provide similar ease of use without the need to buy coffee pods. The user will only need to use materials already used for pour-over coffee, which are paper filters and brewing devices.  Paper filters are compostable and the brewing devices are reusable, thus making pour-over a much more sustainable option compared to pod-based coffee machines.  Also, by giving people the ability to use any ground coffee they have, they can support local cafes and buy sustainably sourced coffee rather than being forced to purchase coffee in pods that were likely sourced from underpaid workers. Overall, our solution gives people a more sustainable and eco-friendly option to brewing coffee without compromising on ease of use.

… with consideration of environmental factors. Environmental factors are concerned with the environment as it relates to living organisms and natural resources.

Schedule is currently on track.

Elijah Knupp’s status report for March 1st

This week’s accomplishments

  • Wrote, edited, and formatted the design report. Specifically, these were my responsibilities on the report:
    • hardware architecture
    • Introduction
    • gantry subsystem implementation
    • water heating and distribution subsystem implementation
    • scale subsystem implementation
    • risk mitigation
    • BOM
    • Formated, edited, and submitted the final report
  • Attended mandatory lab
  • Pump flow and current testing
    • will need to test further to fully understand the relation between current and flow rate.

Next week’s plan (spring break)

  • Will be traveling, so I have limited time to work hands-on with the project
  • However, will be looking to successfully run OctoPrint on my personal Rpi to communicate with the 3-D printer
  • Experiment with different flow rates (and how much current each rate requires)

Status Report: On schedule

Team Status Report for March 1st

This week, the team focused on finalizing the design report document (attached to this post). This also drove us to polish some of our designs and plans for the next few weeks.

A byproduct of this work is that we finalized our testing strategy by writing down a step-by-step spec for each test that we plan to conduct.

Additionally, we received the majority of our project’s order for parts, and we started assembling/inspecting internals for some parts. This includes the 3D printer gantry (which is being assembled), the water kettle (which we took apart in order to modify the circuit for custom controls), the water pump (which we tested with a DC power supply), and others. We noted that varying the amount of current supplied to the pump proportionately affected the flow rate. We will have to do further testing to determine exact relation between the two.

The biggest challenge possibly coming up is with integration of off-the-shelf components. From what we’ve looked at so far, there are no major indicators that anything wouldn’t work, but we will not be sure of this until we’ve reached full system integration. To mitigate this risk, we plan on doing as much assembly work as possible this coming week such that, if anything doesn’t work, we can order replacements.

Schedule is currently on track.

Design report: Team_A1_Knupp_Govea_Pacheco_proposal