vesi
IDEATION
Before vesi was created, we generated over 100 different ideas for products, even if they initially seemed unachievable. After conferring with our peers, we ultimately narrowed down our selection to three ideas and sketched them, preparing for peer review. By the end of the week, we gathered more constructive and insightful comments than we ever believed possible. Once we analyzed our feedback and researched if there was a need for this product, we made the decision to create vesi, with the input of our peers. When we announced the launch of vesi, we were overwelled with support, as family members and agriculture enthusiasts were intrigued by our idea, and we hoped that we would be able to use it to solve our problem at school.
Model Version 8
Model Version 7
Model Version 2
Model Version 8
Model Version 6
Model Version 5
Model Version 1
Model Version 6
PROTOTYPING
With our experience running the school garden, The vesi Team began brainstorming a plethora of solution to tackle water and other gardening problems. Our vesi soil module, solenoid valve, and app emerged as an exciting innovation, tackling a major problem for gardeners and farmers, and a technically possible and affordable solution. We developed the three parts of vesi by working together to design and build prototypes, and to create a pitch in order to convey our business plan to investors. The final product was not a success first try. After many iterations of our coding, wiring, and design, vesi is now a reliable product and is now ready for the market. Check out our ideation process of our modules to see how our models have progressed throughout the year.
REFLECTION
During the development process for vesi, we struggled with various technical issues. For example, when we were coding the radio transmitter and receiver that connects the soil sensor to the solenoid valve. The components did not work and delayed our progress for several weeks. When we replaced the components with a different make and debugged our code, it began functioning properly.
For a few months, we struggled with the solenoid valve, unable to work out how to provide it with enough power for it to operate. After extensive research and consultations with members of our neighboring STEAM communities, we were able figure out the charge it needed. In completing our project, we have had to deal with the fact that we are working remotely.
We also struggled in building our pitch, because of our lack of experience, meaning that we had to learn what was relevant and effective through the pitches we practiced and delivered in class.
TIMELINE
September
Design Thinking Skills and Activities
In September, before we were even paired in teams, we learned about design thinking, and began formulating a list of over 100 ideas for possible products. In doing this, we also learned how to conduct a Naturalistic Observation, where you look around in any public space (park, store, etc.) to see if there is a need that needs to be addressed.
October
Brainstorming and Initial Research
In October, we were put into our teams and continued to brainstorm ideas for products to create, but this time, it was with our teams. We created a list of 100 product ideas and narrowed it down, with the help of feedback from our peers, to the best idea we had - vesi.
November
Design & Prototyping
In November, we worked on sketching out designs and prototyping our modules using cardboard and basic CAD software. In addition, we worked on coding and wiring the AdaFruit Stemma Soil Sensor We also began desigining our logo that we believed would represent vesi as a team.
December
Soil Sensor & Power
In December, we worked on many iterations of wiring and coding the solenoid valve as well as wiring and coding the AdaFruit Stemma Soil Sensor. Trying to derive enough power for the soil module was a struggle that we faced, but after learning about other innovative solutions in our school’s greenhouse, we realized that the vesi water valve would be housed indoors, allowing us to power the Arduino directly from an outlet. During the second half of the month, we conducted a series of tests with the soil sensor, in order to conclude what values were considered most optimal. Working with the intake pH, moisture, soil moisture values, we iterated our code to only open the valve when the soil is not moist any when it is not too warm, in order for us to save as much water as possible, without any of it evaporating, therefor not being absorbed by the plants
January
Reiterating Design & Solar Panel Efficiency
In January, we worked on many different iterations of wirings for the solar panel trying different power boosters and lipo batteries, in order to maximize the intake voltage per square inch. After conducting a series of tests, exposing our design to a different setup, recording our data through a digital multimeter, we arrived at our final design.
February
Wireless Communication & Redesigning The Enclosure
In February, we worked on finding solutions in order to allow two Arduinos to communicate wirelessly through long distances. After attempting to using radio transmitters, Bluetooth, and wifi modules, we worked together as a team, receiving guidance from upperclassmen in order to have a functioning prototype of our design. We also together began making an enclosure for both the vesi soil module and the vesi solenoid valve.
March
Combining Components & Software Efficiency
In March, we worked on redesigning our model in more detail, focusing on making the model functional, detailed, and to scale. Secondly, we worked on assembling all of our different components. One challenge that we faced was trying to tweak and combine our code and wiring in order to make them compatible with each other.
April
vesi App & Adapting To New Circumstances
In April, we were initially planning on coding our app and making it compatible with our module, but since we did not have physical access to our models, were not able to complete this goal, although we do have a working interface.