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.

Posted on

Team Status Report for 10/04/2025

Accomplishments

  • Parts Procurement: Ordered all major off the shelf components from the BOM
    • Waiting for deliveries before starting fabrication of laser cut plates
  • Raspberry Pi Setup: Began setting up the Raspberry Pi 5 for UART communication with the Pi Pico and sensor data collection
    • Resolved hardware and network setup issues and completed initial Pi OS configuration
  • Design Report and Research: Continued progress on the Design Report, refining use case and design requirements and supporting them with relevant sources

Significant Risks

  • Dependency on off the shelf parts for fabrication: Same as last week, cannot finalize or fabricate custom mounting plates until we have real parts to verify mounting hole dimensions
    • Plan to begin fabrication immediately upon receiving parts to stay on track

Design Changes

  • No major design changes this week. Block diagram and CAD assembly finalized last week

Schedule Changes

  • Schedule remains on track at this point but may need adjustment next week depending on actual part arrival times
Posted on

Kristina’s Status Report for 10/04/2025

Raspberry Pi Setup

  • Set up Raspberry Pi 5 for future UART communication with Pi Pico code development
  • Troubleshot several setup issues:
    • Broken mini-HDMI cable causing monitor display issues
    • Missing microSD reader, preventing Pi OS installation through the Pi Imager
    • SSH connection issues due to the wired ethernet network being different from CMU Secure wireless
  • Successfully imaged Pi OS onto the microSD card and completed initial configuration at home before bringing the Pi back to campus, which resolved network issues

Parts Procurement

  • Ordered off the shelf components listed in the BOM
  • Currently waiting for parts to arrive before verifying part dimensions and fabricating laser cut mounting plates

Design Report and Research

  • Worked on Design Report sections covering use case and requirement justifications
  • Found IEEE Xplore papers related to anomaly detection to reference for style and technical wording in the Design Report

Schedule & Progress

  • Currently slightly behind schedule due to:
    • Waiting for hardware parts to arrive before starting laser cut fabrication
    • Delays in Pi 5 setup and network access during initial configuration

Next Steps

  • Begin laser cut fabrication once parts (specifically the pump) arrive
  • Continue 3D printing remaining brackets and verify fits
  • Start Pi 5 to Pico UART code development
  • Finish Design Report as soon as possible to get feedback