Posted on

Hiroko’s Status Report for 4/3

This week, I connected the water pumps to the relay system that I assembled last week, and measured the flow rate of the water pump. Kanon and I met up and calibrated the soil moisture sensors in order to figure out when and how long to turn the water pumps on for. I planted the pea shoot plants earlier this week, so we used the soil to test the soil moisture sensors and water pumps. We also tested communications between ESP32 and AWS by sending sensor data to AWS, using the data and user inputs from the website to determine when to turn the greenhouse components on/off, and sending the on/off commands from AWS to ESP32.

Overall, I think I am on schedule. Next week, I plan on adjusting the watering tube to distribute water more evenly to the plant, and figure out where to physically place and connect the components in the greenhouse. I will need to adjust the wire length of all of the components connected to the ESP32 and determine the specific layout of the electrical components so that I can order a case with the right dimensions to enclose the electrical components in.

Posted on

Kanon’s Status Report for 4/3

This week, I continued working on sending data from website to ESP32 that I was doing since last week, and also worked with Hiroko to calibrate sensor values.

Our website can now send data to ESP32 once the user changes the parameters (i.e. temperature, soil moisture) on the user page. The algorithm is pretty simple. If the user sets the temperature or soil moisture rate higher than the current value from the greenhouse, the website backend will send a binary signal to ESP32, and ESP32 will turn on the corresponding components such as heater or water pump. The LED light can be turned on and off in a similar manner.

The following is the data that we receive from ESP32 and is stored within AWS DynamoDB. As you can see, the soil_1 and soil_2 moisture sensors have values that are around 3000 or 2000. Hiroko and I had to calibrate this value so that the user can see them as a percentage.

This week, my actual schedule was to deploy the website to EC2, however, we had to work on calibration and had to play around with how we send data to ESP32, which can be done more easily when we work locally. Therefore, I decided to deploy the website next week, and I am off schedule for a week.

Next week, since initial schedule was dedicated for UI testing which is not a lot of work, I am aiming to deploy the website and also conduct UI testing at the same time.