drolsen / dro-matic Goto Github PK

Fully Automated Hydroponic OS for DIY DRO-Matic cabinets - Nutrient dosing, irrigation, topoffs, timers, EC & pH drift fixing.

Arduino 6.41% C 7.78% C++ 85.77% Makefile 0.04%

hydroponics automation regimen irrigation plants plant-watering

dro-matic's Introduction

DROMatic OS

The DRO-Matic OS has been built to automate nearly every aspect of hydroponic farming for you! From nutrient dosing to pH / EC drift fixing, feeding types to draining, top-offs and even timers; we have quantified everything you need to automate successful crops.

Users create, configure and share what are called "crops" by interfacing with an LCD screen and external MicroSD card. A single DRO-Matic crop disk size (SD card) can vary, but in very extreme crop configurations (10 channels, 100 weeks of dosing sessions per channel) were found to be just under 5MB. The OS has also been built to scale to nearly any size farm; so, have no fear if you are considering using this for a large-scale farm or a small personal garden.

Why do we need this?

Before diving into the OS configuration, let's ask ourselves why this even exists? It's undoubtedly true across all cultures that agriculture and food growth is not just a necessity, but is also very expensive. Agriculture is not only expensive in amount of land used, but also time spent to get a harvest and even energy burned to obtain consistent quality. While humans can expect another 9 billion people over the next 30 years; we need to seriously address the fact that as of today 90% of all farmable land is currently being used at its max capacity.

The technology to solve feeding 9 billion people is available and also removes the costly impacts of large soil based farms, it’s called vertical hydroponic farming. Vertical farms save vital land usage by summing farms up into much smaller (stackable) areas. Vertical gardens save time/money at food production because it's quicker to achieve a consistent crop quality ALL YEAR LONG.

(this video explains the problem and pros of vertical farming in further detail)

However, the down side to vertical farming (or hydroponics in general) is you do have to learn A LOT about nutrients, dosing regimens, regimen drifting, EC/PPM and PH testing etc etc. Because of the large learning curve, we still don't see a lot of traditional farmers make the jump to this more cost-effective solution. So, to answer the question of "Why DRO-Matic"; it all comes down to farmers need a way to simplify the process of hydroponic farming and what better way to do this than to go fully automated.

The DRO-Matic OS is here to take care of all the heavy lifting our of your hydroponic farming needs. The goal is curve all time spent learning and maintaining hydroponic farms by automating nearly every aspect and ultimately bring a much more efficient way of food production option to the world. Please note that this OS is only the OS part of this solution; without the actual DRO-Matic dosing cabinet (not commercially available, must DIY build), this OS makes no sense for you yet. For detailed instructions on how to DIY build your own DRO-Matic cabinet, please visit our hardware requirements page videos.

OS Overview

Th DRO-Matic OS has the ability to fully automate the follow process for you:

Regimen dosing (full feedings and top off feedings with drifting amounts)
pH adjusting (both plant and reservoir water sources)
EC adjusting (plant water source top-offs)
Irrigation (feeding, draining and topping off)
Timers (4 120v/10amp power receptacles that can be timed)

Because of the sheer flexibility of the DRO-Matic OS, there is a lot of a screens to configure a single crop. Below is a overview of the available OS features.

Home Screen

Displays current date / time, and plant water's current PPM/EC levels and current pH level

System Settings

Date/Time = Allows you to set the date and time of the DROMatic OS
EC Calibration = 3 point calibration (Dry, Low, High) for both EC probes.
pH Calibration = 3 point calibration (Low, Mid, High) for both pH probes.
Pump Calibration = Calibrate how many milliliters per minute your peristaltic can pumps.
Pump Delay = Calibrate how long of a delay each dosing pump should take between dosing each solution (allows time to fully mix each solution).

Crop Settings

New Crop = Start a brand new crop project on your SD card
Load Crop = Load an existing crop project on your SD card
Delete Crop = Delete the available listed crops on SD card (except for currently loaded crop)
Reset Crop = Resets crop back to first configured regimen and timer day/week. Does NOT reset crop back to factory settings!!
EC Range = Sets the desired range of EC you would like your DRO-Matic to maintain for this crop for a given regimen.
pH Range = Sets the desired range of pH you would like your DRO-Matic to maintain for this crop for a given regimen.
Number of Regimens = Sets desired number of regimen doses you expect your plant's life cycle to take.

Pump Settings (after choosing a pump)

Prime = Primes a pump line to remove any excess air during first setup.
Amount = Configure how many milliliters a pump will dose for a given regimen. No need to calculate reservoir volume, OS will do this already.
Delay = Configure how long of a delay between each pump to prevent nutrient lockout.

Irrigation Settings

Reservoir Volume = Configure the volume of water your reservoir / plants will be using throughout the life of plants.
Top-Off Concentrate = Configure the fraction amount of dosing amount top-off water gets.
Drain Time = Configure how long of a plant water drain time you will need. You can may want to over estimate this.
Flow Calibration = Configure pulse count per second IN and OUT flow meters are manufactured to send. These numbers are different for per size/manufacturers of flow meters.
Manual Flush = Utility that allows you to flow either IN and OUT irrigation valvels to do any manual flushing during setup / testing.

Timer Settings (after choosing a timer)

Start End Times = Configure start and end times over a given day of the week, for an infinite amount of configurable weeks.

dro-matic's People

Contributors

Stargazers

Watchers

Forkers

bazbalz austrocoin chinbaap mdingman bjrush fsjo ejambo garurumoon jeffindia foggyfarm byrmahmet donj51 joshvette001 uberjoejitsu ethernalvoid per1234 rjlabs shaolingardener poppat cqnguyen80 brentenebros ochui udhayamgit roniap marshall2056 aferust dennis-gif azzziel danyp77 tahaali1 berry825 m-santh mariusl waqashassan98 ltsharks dragonxu skoroglyad scottaandy bue-twitter imle berten-ernie420 lgv2018 hi2aks theosedirwa alekcey1123 xbos777 mr-mbello adsl865 rafatahmed kodemannen haxor1991 shanglor skbugshan edwardmgoldberg ved-22 aerobota jonnylewis iotiq thyratron75 dheerajjadhav andyn8484 jjuri-socialmining ignhans amsomeboys dazcoles paliwalshivam tiagommfx jyleo bryanchou akuan333 xiongdg gleke javaqiang mbrues lovechang1986 ziziwu2020 thelastsupper666 easthj yuwenfu smartjoy-tech jackiea hunseto xiaofengxyz ywjb shadingfish iwwork skylark3409 umratt yuanxiaoming8899 susumu-ura yuanzhongqiao eric0326 yamachan0922

dro-matic's Issues

Is this dead?

Has development moved somewhere else? Is there a good alternative? I came across this when I was thinking about making something similar myself, but would much rather find something existing

Add Crop Reset Sessions

Add a "reset crop sessions" option under System Settings that will loop over all channels and their session and set their expired prop to false and reset set any repeat values. While resetting each session, it will be important to update each sessions year start time to current year, however we can't shift month, day, hour or min.

Goal of this is to allow users to share a crop configuration online with others. Sharing user or downloading user can open crop and reset it's sessions and finish configuring it as needed.

General Project Cleanup

Within the .ino file, relocate all save portion of loop() to individual files such as channels and sessions.
Within the .ino file, clean up if/else mess and consider using switch case statements.
Make better naming conventions for functions across OS that resembles an actual API.

Progression?

I've been digging into this project big time lately as I look to automate my setup. I have some items...

Do you have a diagram of how your setup is with everything you've listed on this project? Two PH probes, two EC probes, fill and drain valves, and items like that. It'd be helpful to see how you've envisioned and utilized these in order to plan my setup better.
If I want to add ORP or another atlas scientific sensor, how do I go about that?
Any updates to include web management or anything of the like? With your portfolio, that seems well within reach.

Thanks again for everything you've done and I look forward to the responses.
boasist

8 dosing pump for nutrient

Dear Devin

I am a beginner using Arduino
and I was searching for dosing controller for my hydroponic
I have found your project, which I am looking for.
But I have a question,
your project has 10 dosing pumps
8 for nutrient and 2 for PH.

What I do not understand, why 8 dosing pumps for nutrient?

We use A and B nutrient solution, so we need only 2 nutrient dosing pumps
in this case, if I want to use your project,
Is there a way to modify the code? To operate 4 pumps, 2 for PH, and 2 for A & B nutrient ?
If this is possible, is there anyway to edit?

Thanks and Regards

Top-off correction need to be both time and volume based.

Right now, EC correction does two steps:

drains plant water by configured amount (gallons) converted into time (seconds) based on out flow meter
feeds top-off water from reservoir to plants by (gallons) converted into time (seconds) based on out flow meter

However the problem here is that water pressure / flow rate from reservoir changes as reservoir gets lower in water volume. Because of this, plant water levels can get too low during top-off cycles leaving roots exposed.

Instead of feeding of top-off water based on time, we should use out flow meter and measure exact gallon volume. This will keep water levels for plants more constant over the life of a regimen.

The expected behavior is that the feeding step of EC correction will get longer and longer as water volume gets lower in reservoir, but exact gallon amount will still be fed. First step in EC correction will remain time based and constant no matter the volume of reservoir size as plant water volume should now remain constant.

Build TopOff Amount Screen

After much testing and diagnostics, confirmed that moving into next regimen must happen within topoffs not flow rate checking. In light of this, no longer is it appropriate to make EC correction or rather topping off time based, but instead amount based.

We need to build out a topoff amount screen to allow users to set how many gallons of topoff should be used during EC correction and topping off plants.

Regimens use zero based index

For consistency, move regimen file system to stop using 0 based indexing. It makes it harder when configuring crop from file system and it adds to code by having to increment index number manually.

Temperature Sensor Integration with EC Probe

Great work on this! Have you integrated a Temperature Sensor for the pH and EC readings?

Repeating Regimens

Issue

Due to plants taking up nutrients / water faster as they get bigger, OS needs to accommodate by
allowing to repeat regimens.

Repeating regimen feature should repeat the entire regimen, and not just the topoff portion of a regimen. The plants do not respond well if only repeating topoffs after about the the third topoff as I've discovered.

Solution

Within the Regimens (ml) Configuration menu, as you get to set your ml amount we should allow users to specify a repeating amount. However screen limitation might make this a problem so a new "Regimen Repeat Configuration" menu might be necessary.

Developer Notes

Do not forget to include the resetting of these repeating regimen numbers when user uses "Crop Reset" feature of OS.

Peristaltic Pump Setup

I'd love to build this setup and document my whole experience on rollitup.org, where you'll get a lot of interested minds in the project - but the syringe pump method is a big barrier for me.. do you plan on releasing a peristaltic pump guide?

Thanks for your hard work on this, can't wait to see it when it's finished.

Finish building out new, open and delete crop logic.

Finish building & testing out the screens for:

New crop creation
Open another crop
Delete a crop (other than currently open crop)

Won't Compile on newest 1.8.7 Arduino IDE due to StandardCplusplus

Project won't compile if using the newest Adruino IDE 1.8.7 due to some breaking changes made in Arduino 1.8.6 - avr-gcc 4.9.2 to avr-gcc 5.4.0 it causes StandardCplusplus not to work anymore and throw errors regarding (class std::basic_istream) and ostream.

The easiest fix I have found currently without digging into this further is to simply install the 1.8.5 IDE which still uses avr-gcc-4.9.2

No Wire.endTransmission() needed after Wire.requestFrom()

Hi, do you use a special Wire library ? I noticed odd usage of the Wire library.

After a Wire.requestFrom() you use Wire.endTransmission(). That is not needed. The Wire.requestFrom() is a complete I2C transaction on its own. The Wire.endTransmission() is only used when writing data.

I suggest to keep the "Wire.beginTransmission - Wire.write - Wire.endTransmission" close together. You have the Wire.beginTransmission() in a seperate function, which is unusual. In the Arduino Wire library, the I2C bus transaction is fully done with Wire.endTransmission(). The other two functions set variables and write to a buffer.

You request 48 bytes with Wire.requestFrom(), but the Arduino Wire library has a maximum of 32 bytes.

Regimen Dosing Screen Updates

While performing regimen dosing to reservoir water under both full feedings and topoff feedings the screen should be updated as follows:

DOSING REGIMEN
RSVR EC: XXXX
or
DOSING TOPOFF
RSVR EC: XXXX

This gives the end user the ability to visually see what the current EC level is for reservoir water between each nutrient solution being dosed / delayed for mixing.

Remove Delay Screens / Config

There is no need for this feature as you can do it in the session date/time configure if you need it.

Help is here

This has been left for dead. After a few hours of working this, I finally got it working. If anyone needs help, email me at [email protected]

Drainage/Top Off System

The goal is to allow DRO-Matic to top off plants with it's dosed reservoir water X times between full water flushing of plants once every 7 - 14 days. This also allows the DRO-Matic to do full flushing/draining of plant water and refill with dosed reservoir for you.

To Do:
Built out optional drainage/top off system that allows you to configure up to 6 Electrical Solenoid Valve (0 PSI requirement and default closed) that can be scheduled to open for X amount of seconds/minutes and can be configured to repeated hourly, daily, weekly, monthly and yearly per valve.

First screen will ask user if they would like to turn on or off drain/top off system (off by default).
If on, next screen will be number of valves (6 max as we are limited)

If on, back out on main menu you will now have:

System Settings
Channels Settings
Drainage Settings

Like channels settings, once under the new Drainage settings you will be presented with a list of available values we configured above. Under a single valve menu we have DateTime Config and Repeat Config that allows you to configure when/interval length and how long a single value will be opened for.

Alternate Probes

Mr. Olsen this project is fantastic and want to look at building this for my Hydroponics garden outside, but the Atlas probes and boards are pretty expensive. What would it take to have the OS compatible with other EC/PH probes (couple examples below)? Do you have an active forum for this project?
PH Probe:
[EC Probe:] (https://www.dfrobot.com/product-1123.html?gclid=Cj0KCQiA-qDTBRD-ARIsAJ_10yKWDGon203htZ6dMRXqX6cp960XcQ1lZjxinw7uSXDezrHRrVK_bPEaApgbEALw_wcB)

Crop status updates

Description

When setting a crop status to paused, the screen should ask if you would like to pause pH adjustments as well. Currently the entire system becomes paused including pH adjustments and this might not be what the end user wants.

Requirements

This requires a new property in the crop's setting for pHstatus and to flag for it within the .ino.

Goal

The goal behind this is to allow a user to put crops automation into full pause or partial pause. This basically turns the OS into a full manual system or a partial manual system with automated pH adjustments.

Clean up Core.cpp/h

Core was used as a middle man while converting system from being time based to event based and new classes we being build. Now however some functions in core do not belong in core, but instead in said newly created classes.

We need to clean up core and relocate some functions to their now, more logical locations.

General Project Questions/Feedback

First of all let me start by saying a big heartfelt thanks for starting this project. This project is going to help not only hobby cannabis growers, but patients that can't truly can't afford their medication anymore. This could be built out to support the hobby agriculturist, or anyone that simply can't afford a vastly overpriced commercial dosing system.YOU'RE DOING GOD'S WORK, SON.

I hope to see you build a lot of functionality out of this! It would be awesome to see this take off.

Questions:

Do you know of any other detailed guides I can follow for the dosing mechanism, that will interface perfectly with your project? I do not have the time or craftsmanship to do a huge array of syringes. I think this is the most important because it's the largest barrier towards general public adoption to your project.
Could I make a a water solenoid valve work in a gravity fed solution, instead of the peristaltic pump alternative?
Would this cheapo autodosing pump work in your system?
Will you add "real time" nutrient dosing/PH adjustment? From a farmer's perspective, I would argue this is easily the most important feature to implement into this project. You could have the probes constantly polling PH and PPM data and then dosing based on when those levels vary out of range over a set period of time (with a delay after dosing before retesting we can avoid the false positive of having the system dose PH/PPM to adjust and then immediately re-detecting a PH/PPM spike which we just administered).
Does the project do this or do you intend to add this functionality? I think it's mission critical.

I'll send you a picture of the monsters I grow if you can add this functionality.

Build OS Configure Web Interface

Approaching the finish of being able to configure all OS settings from LCD shield, it is now time to consider building a quick web interface tool that allows you to configure a crop via interfacing with calendar and events as sessions.

Tool can be hosted on jsfiddle and embedded and linked to with revisions available for later on and requiring no hosting. Here are the found resources for this app thus far:

jQuery latest (calendar plugin requirement)
FullCalendar http://fullcalendar.io/
JSZip https://stuk.github.io/jszip/

User Experience Outline:

No login required
Fills out crop name
Fills out channel number
Gets presented with entire interface
Interface is essentially a large month to month calendar with options above it.
User can switch what channel and what session they are under and use calendar to configure session times.
User can add and remove sessions while under any of the channels they configured in the beginning.
User can also alter number of channels at any point by max is 10 min is 1.
All repeat, amount, and start time for sessions are set in the events of the calendar.
Once done, user can hit generate button and a zip file / download will be given to them with crop fully configured. User can take contents of zip and put on SD card and plug into Arduino/OS and load crop up.

Thank you Devin...

Hi devin, how are you? This project is awesome. I just edited the library folder names and uploaded it. Thank you very much. Now it's time to set up the system. i hope i can install it. If only the wiring diagram was improved. I think if I can do that, I can give a boost from here.Greetings from TURKEY.

Please help this crop error

Hi, i got the code to compile and upload successfully with few warnings, but the lcd sheild is at Crop name and it does not let me input alphabet, only the forward button works and the back button has become the top bottom. other buttons dont work. using dfrobot lcd sheild 2.0

these are the errors would be great help if anyone can help me through this

using arduino ide 1.8.5 and same libraries as drolsen.

warnings as follows -

sketch\Crops.cpp:507:14: warning: character constant too long for its type

if (type == 'low'){

sketch\Crops.cpp:511:14: warning: character constant too long for its type

if (type == 'mid'){

sketch\Crops.cpp:515:14: warning: character constant too long for its type

if (type == 'high'){

sketch\Crops.cpp:524:14: warning: character constant too long for its type

if (type == 'dry'){

sketch\Crops.cpp:528:14: warning: character constant too long for its type

if (type == 'low'){

sketch\Crops.cpp:532:14: warning: character constant too long for its type

if (type == 'high'){

sketch\Crops.cpp: In function 'void setCropData(ArduinoJson::JsonObject&, bool)':

sketch\Crops.cpp:83:55: warning: default argument given for parameter 2 of 'void setCropData(ArduinoJson::JsonObject&, bool)' [-fpermissive]

void setCropData(JsonObject& d, bool returnHome = true){

sketch\Crops.cpp:24:13: note: previous specification in 'void setCropData(ArduinoJson::JsonObject&, bool)' here

extern void setCropData(JsonObject& d, bool returnHome = true);

sketch\Crops.cpp: In function 'void cropRename(int)':

sketch\Crops.cpp:147:13: warning: NULL used in arithmetic [-Wpointer-arith]

if (dir != NULL){

sketch\Crops.cpp: In function 'void printStatus(int)':

sketch\Crops.cpp:540:29: warning: default argument given for parameter 1 of 'void printStatus(int)' [-fpermissive]

void printStatus(int dir = 0){

sketch\Crops.cpp:52:13: note: previous specification in 'void printStatus(int)' here

extern void printStatus(int dir = 0);

sketch\Crops.cpp:552:31: warning: default argument given for parameter 1 of 'void printPHAmount(int)' [-fpermissive]

void printPHAmount(int dir = 0){

sketch\Crops.cpp:53:13: note: previous specification in 'void printPHAmount(int)' here

extern void printPHAmount(int dir = 0);

sketch\Crops.cpp:581:30: warning: default argument given for parameter 1 of 'void printPHDelay(int)' [-fpermissive]

void printPHDelay(int dir = 0){

sketch\Crops.cpp:54:13: note: previous specification in 'void printPHDelay(int)' here

extern void printPHDelay(int dir = 0);

sketch\Crops.cpp:719:27: warning: default argument given for parameter 1 of 'void printOpen(int)' [-fpermissive]

void printOpen(int dir = 0){

sketch\Crops.cpp:59:13: note: previous specification in 'void printOpen(int)' here

extern void printOpen(int dir = 0);

sketch\Crops.cpp:742:50: warning: default argument given for parameter 2 of 'void printECCalibrations(String, int)' [-fpermissive]

void printECCalibrations(String type, int dir = 0){

sketch\Crops.cpp:57:13: note: previous specification in 'void printECCalibrations(String, int)' here

extern void printECCalibrations(String type, int dir = 0);

sketch\DatesTime.cpp:15:149: warning: narrowing conversion of '(((((((unsigned int)tmpInts[5]) & 3u) == 0u) && ((tmpInts[5] % 100) != 0)) || ((tmpInts[5] % 400) == 0)) ? 28 : 29)' from 'int' to 'byte {aka unsigned char}' inside { } [-Wnarrowing]

byte days[12] = { 31, ((tmpInts[5] % 4 == 0 && tmpInts[5] % 100 != 0) || (tmpInts[5] % 400 == 0)) ? 28 : 29, 31, 30, 31, 30, 31, 31, 30, 31, 30, 31 };

sketch\DatesTime.cpp: In function 'void printDateTime(int)':

sketch\DatesTime.cpp:45:31: warning: default argument given for parameter 1 of 'void printDateTime(int)' [-fpermissive]

void printDateTime(int dir = 0){

In file included from sketch\DatesTime.cpp:8:0:

sketch\DatesTime.h:20:13: note: previous specification in 'void printDateTime(int)' here

extern void printDateTime(int dir = 0);

sketch\DatesTime.cpp: In function 'void captureDateTimeDisplays(int, int, int, int)':

sketch\DatesTime.cpp:104:119: warning: default argument given for parameter 1 of 'void captureDateTimeDisplays(int, int, int, int)' [-fpermissive]

void captureDateTimeDisplays(int month = tmpInts[1], int day = tmpInts[2], int hour = tmpInts[4], int min = tmpInts[5]){

In file included from sketch\DatesTime.cpp:8:0:

sketch\DatesTime.h:26:13: note: previous specification in 'void captureDateTimeDisplays(int, int, int, int)' here

extern void captureDateTimeDisplays(int month = tmpInts[1], int day = tmpInts[2], int hour = tmpInts[4], int min = tmpInts[5]);

sketch\DatesTime.cpp:104:119: warning: default argument given for parameter 2 of 'void captureDateTimeDisplays(int, int, int, int)' [-fpermissive]

void captureDateTimeDisplays(int month = tmpInts[1], int day = tmpInts[2], int hour = tmpInts[4], int min = tmpInts[5]){

In file included from sketch\DatesTime.cpp:8:0:

sketch\DatesTime.h:26:13: note: previous specification in 'void captureDateTimeDisplays(int, int, int, int)' here

extern void captureDateTimeDisplays(int month = tmpInts[1], int day = tmpInts[2], int hour = tmpInts[4], int min = tmpInts[5]);

sketch\DatesTime.cpp:104:119: warning: default argument given for parameter 3 of 'void captureDateTimeDisplays(int, int, int, int)' [-fpermissive]

void captureDateTimeDisplays(int month = tmpInts[1], int day = tmpInts[2], int hour = tmpInts[4], int min = tmpInts[5]){

In file included from sketch\DatesTime.cpp:8:0:

sketch\DatesTime.h:26:13: note: previous specification in 'void captureDateTimeDisplays(int, int, int, int)' here

extern void captureDateTimeDisplays(int month = tmpInts[1], int day = tmpInts[2], int hour = tmpInts[4], int min = tmpInts[5]);

sketch\DatesTime.cpp:104:119: warning: default argument given for parameter 4 of 'void captureDateTimeDisplays(int, int, int, int)' [-fpermissive]

void captureDateTimeDisplays(int month = tmpInts[1], int day = tmpInts[2], int hour = tmpInts[4], int min = tmpInts[5]){

In file included from sketch\DatesTime.cpp:8:0:

sketch\DatesTime.h:26:13: note: previous specification in 'void captureDateTimeDisplays(int, int, int, int)' here

extern void captureDateTimeDisplays(int month = tmpInts[1], int day = tmpInts[2], int hour = tmpInts[4], int min = tmpInts[5]);

sketch\Irrigation.cpp: In function 'void printTopOffConcentrate(int)':

sketch\Irrigation.cpp:48:40: warning: default argument given for parameter 1 of 'void printTopOffConcentrate(int)' [-fpermissive]

void printTopOffConcentrate(int dir = 0){