Weekly Activity Update: Flood Detection System Development Week 1 (Settimana 1)

Week 1 Overview

For our project, we are designing a flood detection system, aimed at enhancing safety during extreme weather events. The system will utilize various sensors to detect water levels, soil moisture, and potential hazards, activating warning mechanisms such as LEDs and buzzers to alert users. Inspired by the increasing need for accessible flood detection solutions, we aim to develop a compact, efficient, and reliable prototype.

In the first week of the project, we focused on laying a solid foundation. Our activities revolved around coding for the microcontroller, planning the project objectives and timeline, preparing the components for assembly, and visualizing the prototype layout. We also encountered several challenges, including delays in component delivery and limitations in simulation tools. Despite this, our team worked collaboratively to maintain momentum and make progress.

We also faced limitations in our component availability, which slowed down testing. To address this, we sought help from one of the demonstrators, Will, who assisted us with a few missing components that had not been ordered by the lab technicians. This support allowed us to proceed with testing some aspects of the code, ensuring we stayed on track despite the delays.

Figure 1: Two team members setting up the initial project layout in Fritzing, arranging components and wiring virtually before physical integration.

1. Coding for Microcontroller

We started drafting the initial code structure to handle sensor inputs and trigger alerts such as the buzzer and LEDs. This foundational code will act as the backbone of the system, enabling real-time flood detection. We ensured modularity in the code to facilitate future integration of additional features, such as data logging and threshold adjustments.

The code has been designed in a modular format to allow for easy expansion and debugging. The key components include:

• Sensor Data Acquisition Module

  • Reads values from the soil moisture sensors (SEN0308, SEN0245) and ultrasonic sensor (HC-SR04).
  • Processes real-time input and converts raw data into meaningful values (e.g., water level in cm, soil moisture percentage).

• Threshold Detection & Alert System

  • Compares sensor readings with predefined thresholds to determine if flood conditions exist.
  • If conditions exceed safe limits, it activates the buzzer (ABT-414-RC) and LED (RS PRO RGB 5mm LED) to alert users.

• Logging & Data Handling (Planned for Next Week)

  • Future implementation includes logging sensor data for analysis.
  • This will allow us to track trends over time and fine-tune our detection system.

Current Stage & Status

• Basic input-output functions (sensor reading & LED/buzzer triggering) have been implemented successfully.
• Initial calibration of threshold values is ongoing to ensure accurate flood detection.
• The logging module is yet to be developed, but the structure is in place for future integration.

Figure 2: Initial coding during Tinker CAD simulation

 

The basic input-output structure has been implemented (sensor reading & alert triggering).

Threshold calibration is ongoing—initial testing showed inconsistencies in sensor readings due to environmental factors.

A logging system is yet to be implemented, but the structure has been outlined.

Limited access to some components delayed full testing, but we adapted by simulating certain sensor behaviours and getting assistance from Will for missing components.

Conclusion: The initial code draft is functional but requires further refinement. The group agreed to improve sensor calibration and optimise power consumption.

2. Project Planning & Component Selection

This week, we outlined the project’s objectives and created a detailed timeline to align tasks with deadlines. We also finalized the components necessary for the system:

• DFRobot Development Board (DFR0478)

• Soil Moisture Sensor (SEN0308)

• SEN0245

• Ultrasonic Sensor (HC-SR04)

• 800mAh LiPo Battery (3.7V) (BT06808)

• ABT-414-RC Buzzer

• RS PRO RGB LED 5 mm Through Hole

• Oktapad Single Height 3U Extended Double-Sided Eurocard Prototyping Board

Here is a primary digital layout of our project

Figure 3: Digital initial layout of the project 

Conclusion: The group agreed that these components best fit our project needs. However, we need to evaluate battery efficiency once physical testing begins. The delayed components are a major concern.

3. Prototype Layout Discussion

To visualise the arrangement of the components, we used Tinker CAD and Fritzing for simulation. These tools helped us design a rough layout for the flood detection system, but certain limitations arose due to the unavailability of exact sensor models in the simulation tools. We explored alternatives to approximate real-world functionality and prepared for the integration of the actual components.

Additionally, we created a primary hand-drawn design of our product to assist in visualisation next week. We concluded that the current digital layout provides a solid starting point, but adjustments will be necessary once the real components are assembled.

Figure 4: Primary initial simulation of CAD design in Tinker CAD

Figure 5: Initial hand-drawn design of product 

Conclusion: The team concluded that the current layout is effective for initial planning. We need to review spacing and wiring constraints once physical integration begins.

4. Problems, Issues, and Concerns

• Delayed Components: The parts ordered on December 13, 2024, have not yet arrived, delaying real-world testing.
• Simulation Limitations: While useful, Tinker CAD and Fritzing lack accurate equivalents for some sensors, making real-world behaviour hard to simulate.

Despite these setbacks, we remain optimistic and continue working on areas within our control.

Conclusion: The team agreed to escalate the component delay issue by sending multiple emails to follow through with updates after every 2 days. Meanwhile, coding and simulation will continue using alternative tools.

Both ultrasonic and infrared sensors are used for distance measurement, but they operate on different principles and have distinct advantages:

• Ultrasonic Sensor (HC-SR04): Utilises sound waves to measure distance by calculating the time taken for an echo to return. It is highly effective for detecting water levels as sound waves can reflect off liquid surfaces.

• Infrared Sensor: Uses infrared light to detect obstacles and measure distances. While it can be useful in some applications, it is less effective in detecting water surfaces as infrared light can be absorbed or scattered by water.

Conclusion: The ultrasonic sensor was chosen for flood detection due to its reliability in measuring water levels. Infrared sensors may still be used for detecting solid obstacles in future iterations.

6. Responsibility Matrix

To ensure accountability and streamline workflow, we have updated the responsibility matrix with assigned tasks for each team member:

Task	Responsible member	Status
Coding microcontroller	Sayem	Initial stage
Component selection	Sayem & Sayed	Completed
Prototype layout design	Sayem	Initial design ready
Simulation setup	Cian	Completed
Blog documentation	Sayed	In progress
Comp. delivery follow up	Sayed	In progress
Sensor research & testing	Cian,Sayem,Sayed	In progress

7. Tasks for Next Week

• Follow-Up on Component Delivery: Sayed will contact the lab technician for updates on the delayed parts.

• Refine Simulation Setup: Cian will identify and document substitutes in simulation tools to approximate sensor behaviour.

• Outline Test Procedures: Sayem and Cian will create a checklist to verify each component's functionality upon arrival.

• Continue Coding: Sayem will refine the threshold detection system, integrate a logging function, and optimise sensor calibration.

• Update Blog Documentation: Sayed will summarise the progress made and include new findings in next week's update.