Posted on

Jacob’s Status Report for 10/25/2025

This week, I finally got my computer connected to the Pi5 after adjusting my personal computer settings and adjusting my SSH configuration settings. From there, we set up the temperature sensor on the Pi5, and I wrote some code to test its basic functionality. This worked, allowing us to expand to multiple sensors.

I am still slightly behind schedule. I need to start making the live database and the alert system. But within the following weeks, I’m confident that I can keep making progress and a good pace and catch up.

Next week, I intend to configure each individual temperature sensor rather than only have the default sensor read. I’ll set up the alert system so that, given some input (an arbitrary one for now since we don’t have our algorithm running yet), the Pi5 sends a formalized alert to the user. I also plan on developing the framework for the database so that we can collect some inputs.

Posted on

Aidan’s Status Report for 10/25/2025

This week, I worked with the team to integrate the new Pi Pico workflow with the existing UART setup. This provided clarity for the Pico design and allowed me to move forward with further implementations in the control loop. I also assisted the team in inquiring about pricing for acrylic to aid in production of the testbench construction. This resulted in ordering precut parts for the testbench.

The schedule is currently on track and should allow us to move forward with further testbed construction next week after the precut acrylic is received.

Next week, I plan to continue integrating the Pico with higher voltage servos as we construct our test bed with external power supply. I also plan to finish fleshing out the design that communicates with the heaters, ensuring safe operation and fail-safe control loop functionality, while assisting further with testbed construction and misc integration.

Posted on

Team Status Report for 10/25/2025

Accomplishments

  • UART Communication: Completed and validated UART connection between the Pi5 and Pico
  • Hardware Assembly: Assembled fan and radiator subassembly, mounted SSRs and Pico to 3d printed mounts
  • Fabrication: Ordered custom cut parts for testbench
  • PWM Code: Started Pico control code for Servos
  • Sensor Code: Successfully connected and read from TMP117 and ADS1115 sensors through Pi5
    • Resolved I2C address conflicts

Significant Risks

  • Delay in Assembly: Waiting on delivery of custom-cut boards
  • Risk mitigation: Complete full assembly next week once boards arrive

Design Changes

  • No major design changes this week

Schedule Changes

  • Schedule remains the same
  • Slight delay due to fabrication lead time, but full assembly and loop testing expected to begin next week
Posted on

Kristina’s Status Report for 10/25/2025

UART Pi5 to Pico Communication Code

  • Successfully set up UART communication between Pi5 and Pico with wiring and code
  • Verified with test messages from Pi5 to Pico

Testbed Assembly

  • Assembled fan and radiator subassembly to prepare for full assembly next week
  • Mounted Pico and SSRs to 3d printed component mounts

Schedule & Progress

  • Slightly behind schedule for full system assembly since we are waiting on the custom cut boards expected to arrive Monday
  • Once they arrive, plan to finish assembling testbed early next week to catch up to schedule

Next Steps

  • Complete final assembly of testbed and water loop
  • Begin SSR testing with Pico
Posted on

Jacob’s Status Report for 10/18/2025

I made less progress than usual this week due to fall break. Towards the end of last week, I wanted to continue working on the Flask (Python framework for web apps) and Server-Sent Events (SSE) setup for real-time alerts for users. However, I faced a connectivity issue where my laptop isn’t correctly connecting to the Raspberry Pi, therefore, I can’t code on it. I did ping tests and checked SSH settings, but it still isn’t working.

Because of this, I’m running somewhat behind schedule. Next week, I’ll focus on repairing the Pi connection, either by resetting it or seeking assistance during lab. Once it’s operational again, I’ll return to configuring Flask and testing live data updates on the dashboard.

Posted on

Aidan’s Status Report for 10/18/2025

This week, I began developing code for the Raspberry Pi Pico and ran into some singificant issues debugging the workflow. This prompted substantial debugging and resulted in a pivot towards utilizing a different interface for developing Pico code. I began research on the new interface to ensure that the change would provide the same requirements needed by the sensors connected to the Pico and the communication to the Pi5 via UART.

The schedule is currently running slightly behind due to the pivot in code implementation, but this was mitigated by ensuring the new interface would provide the same funcationality required by our design.

Next week, I plan to begin integrating Pi5 to Pico UART with the new interface, while assisting with testbed setup and any potential Pi5 to Pico integration debugging.

Posted on

Team Status Report for 10/18/2025

Accomplishments

  • Design Report: Finalized and submitted the Design Report
  • Hardware Setup: Completed Pi5 SSH setup and connection to the on-campus network
  • UART Communication: Began developing and debugging UART communication between Pi5 and Pico
  • PWM & Sensor Code: Started implementing PWM control on the Pico and sensor code on the Pi5
  • All off-the-shelf components have arrived
    • Verified dimensions and adjusted CAD models accordingly

Significant Risks

  • Need to get custom-cut parts fabricated after Fall Break before full assembly can begin
  • UART communication and PWM development are behind schedule due to debugging and setup time for the Pico and Pi5
  • Risk mitigation: Continue code testing with partial assembly and move forward on database and sensor code setup in parallel

Design Changes

  • Flask + SSE alert system changed to a simplified alert system running locally on the Pi 5 terminal, as Flask integration is not necessary

Schedule Changes

  • Schedule remains the same
  • Team generally on track for post-break sprint code development and assembly

Global Factors

Aidan

Part A: Our system considers global factors by addressing a need to improve hardware reliability and longevity as demand for liquid cooled PCs increases worldwide. By focusing our product on providing data-driven solutions, it aims to support a diverse array of technology through a global push towards sustainability. Given the function of our product is geared towards reducing hardware replacements and decreasing energy waste caused by inefficient cooling, the end solution aligns with broader environmental goals by enhancing global initiatives towards sustainable electronics.

Cultural Factors

Jacob

Part B: The product design carefully considers the diverse interactions between the world, PCs, and human-computer interaction. This is executed by utiizing user-friendly interfaces for interacting with our product and providing transparent and functional configuration. Through training the ML model at multiple CPU loads, the end product aims to provide adaptability, respecting the global culture of PC customization and performance tuning, given the endless unique pre-existing setups. Designing a system to perform reliably under varying usage supports user freedom to tailor their machines to their own specific use cases, while maintaining the same level of protection and oversight by our product.

Environmental Factors

Kristina

Part C: One environmental consideration of our system is reducing both energy and water waste in liquid-cooled computing systems. By detecting cooling inefficiencies early, the system prevents pumps and fans from running at unnecessarily high speeds and helps maintain proper coolant flow, lowering overall power consumption.

Early fault detection also prevents thermal stress over time that can cause leaks or excess coolant evaporation in water-cooled loops. This conserves water and reduces the need for maintenance refills. In large data centers, improving cooling efficiency in this way can reduce energy usage and water waste, making the system more sustainable overall.

Posted on

Kristina’s Status Report for 10/18/2025

UART Pi5 to Pico Communication Code

  • Began writing code for UART communication between Pi5 and Pico

Design Report and Research

  • Focused on finishing the Design Report and polishing all sections for submission
  • Strengthened justifications for system and model design tradeoffs

Schedule & Progress

  • On schedule:
    • All off-the-shelf parts have arrived
    • Custom part dimensions verified and adjusted to match real measurements
    • Plan to send out custom cut parts after Fall Break
  • Behind schedule:
    • UART Pi5-Pico communication delayed due to debugging
    • Minor delays from Pi5 setup and network configuration issues

Next Steps

  • Begin setup and partial assembly of testbed
  • Continue debugging UART communication
  • Assist with sensor integration and PWM control code
Posted on

Jacob’s Status Report for 10/4/2025

I presented my slides to the class this week. I displayed our updated system design and highlighted how each component integrates to meet our design requirements. I focused on the role of the database and dashboard and how our planned anomaly detection model fits into the system. The presentation went smoothly, and the feedback received will help refine both our architecture and testing approach moving forward.

Also, I began exploring Flask and Server-Sent Events (SSE). These will be used to implement real-time alerts in our user interface. Flask will handle communication between the Raspberry Pi 5 and the dashboard. SSE will allow the server to push live alerts, like anomaly detections, to the user without needing manual refreshes. I plan to set up a basic Flask environment and start researching how to structure the SSE endpoint for continuous data streaming.

Next week, I plan to continue developing the alert system prototype and test real-time communication between the backend and dashboard to ensure smooth integration with the rest of the system.

Posted on

Aidan’s Status Report for 10/4/2025

This week, I setup the toolchain for the Raspberry Pi Pico and began learning how to flash the Pico to allow for iterative design and debugging. This involved debugging mulitple toolchain source dependencies, which were resolved and ended in a successful uf2 file for flashing. Next, I utilized partial part datasheet research to intialize the code skeleton for the Pico control loop. This will be further developed after we acquire the parts and the manuals and datasheets are fully accessible. Lastly, I finalized our laser cutting strategy by sourcing acrylic and aluminum cost and researching and confirming strategies to mititage labor cost.

The schedule is currently running slightly behind due to a delay in part acquisition, but this was mitigated by ensuring the toolchain and workflow will be completly ready for SW dev immediately upon receiving the parts and comprehensive datasheets.

Next week, I plan to begin integrating Pi5 to Pico UART interface to ensure design coherence and robustness. Additionally, we plan to finish the design report to ensure we have time for iterations and feedback as needed.