Looks like a great project. Could you give an update on status. What is happening, where is the project at with code, how many members, when, what, where?
We are Excited about this.
Last edit: xtec 2013-03-10
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi xtec. The project is still in its infancy but I am actively working on the "kickables" daily. The prototyping facility is being built in Columbus, Ohio. Yesterday I planted seedlings in the first "section". It consists of 4, 4' pvc channels set up in a flood and drain configuration with a 4-bulb, 4' T5 fluorescent lighting fixture. At the moment, I'm running the lights 24 hours a day and the nutrient pump is setup on a basic commercial timer that turns it on for 15 minutes every 2 hours.
The next step is to install an Arduino unit to replace the commercial timer and implement a sane light cycle. We have relays, Unos and Megas at our disposal. I have some basic code for this, but it's just bare bones essentials. So, priority 1 for this week is to have a simple program that allows for regular cycling of a pump and a light (2 separate relays).
Next week we will have a good real-time clock that we can install but for now the system can just do "dumb" cycling, e.g. 15 minutes ON, 120 minutes OFF.
Also, the HAPI site will have a high-level control function implemented with a Raspberry Pi. (I'm assuming you've read the system description.) This week, the networking will be completed so that we will have secure access (VPN, SSH) to the Pi in the HPF (Hapi Prototyping Facility). So within a week or two, we will be able to access a live video stream inside the HPF, check logs, control sections remotely and perform live updates to firmware.
On the tech side, the team is just forming. It is myself and another gentlemen who is interested in doing technical documentation (he's been patiently waiting for things to get moving.) I am just about to do a little recruiting for this effort and would appreciate both technical help on the project as well as social help in recruiting.
Ultimately, I'd like to look into building section controllers using UML 2.0 State machines and a cool open source compiler. We're obviously not there yet and for now, I'm much more concerned with just getting relays to cycle so as not to kill the first batch of seedlings :)
I'll post some of the initial code later today so we have a starting point for collaboration. Will also post some pics from the HPF.
Please let me know if I can answer any more questions. We'd be glad to have you aboard!
Thanks,
Tyler
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Sorry I haven't posted any code yet. I have a few pieces that I'm about to stitch together and call the "beginning". I gotten basic remote control functionality working and posted a video of the tech stack on youtube: http://www.youtube.com/watch?v=G59H2Jt0KKQ
I've acquired a ChronoDot v2.1 realtime clock. Does anyone know if it can accessed by multiple arduino boards?
The HPF (HAPI Prototyping Facility) should be online by Tuesday.
Tyler
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
High level conversations regarding technical direction are active. Please join in!
The HPF should have a dedicated IP address within 2 days. At that point, a Pi will be installed to act as the main controller for the site.
I am entering the HAPI project into Makezines Raspberry Pi Design Contest under the Utility category. Working hard to get the KickStarter project launched before we win the contest. http://blog.makezine.com/raspberry-pi-design-contest/
--End Status
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I'm Nikos and I've working with hydroponic systems for several years.
Currently re-doing the logic and interface on an old, plc, CX-Supervisor based system that never really worked well. This experience left with a "there's gotta be a better way.." type of feeling and have been developing parts of a "minimal" system for a while now and possibly I can contribute and learn.
regards
nikos
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi-I would interested in developing web-site and system interface for the hapi. I see that not much as happened,here, since earlier part of the year. Now, I have a little time between projects, and, if there should be interest/need such addition then let's start a discussion. I would expect that the system interface, written in python -- would add feature to handle grow schedule rules [light, water, humidity, etc]. I guess what is important is to be able run a entire system from one rasp machine -- given such a rule base, inputed. But still be able to interface with a server for larger more industrialized entities.
Also, the rules should be able to be published--open source still without computer knowledge..
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for reaching out. You are correct that not much has happened on the SourceForge site in the last few months but this is not due to a lack of activity. Quite the opposite; the project has been very active and I just have not had the time to keep SourceForge updated with our progress. I will post some system documentation within another day or two, it's still be developed. However, I'd like to give you a quick project status here and respond in particular to your offer.
CLI & RTU
At the lowest level, we have implemented a "Command Language Interpreter" (CLI) on the Arduino Mega 2560. It accepts commands over a network connection (via an Ethernet shield) and executes them.
Commands are like:
The CLI can set states on all digital and PWM pins and creates response strings (in JSON) that reflect the status of all pins and analog inputs on the unit. The code also includes the ability to easily add custom functions to the CLI for example, when calling libraries for certain sensors. It also provides the ability to manage what we call "Default States" which is essentially fail-safe state information that we write to and read from EEPROM. I have been hesitant to post this code to SourceForge as I have been porting it to the Uno. The unit, regardless of Arduino model, is referred by the team as an RTU, for Remote Terminal Unit.
Site Control
We have also developed a "Site Controller" function which is currently realized as a Python program running on a Raspberry Pi. The site controller can retrieve command files from an ftp site and pass them to an RTU. It can also get response data from an RTU, package it as a file and push it to the ftp site. The program is called a Command Broker, as its primary function is to carry commands between humans and RTUs. The ftp interface is for scenarios where the grow site is not directly accessible to the user over the internet. We are finishing up the real-time interface that supports direct connections, at which point we will post that code as well.
Power Management
A team of artificial intelligence researchers in Slovakia is creating a smart power management system. It will have the ability to create optimal schedules for assets (lights, pumps, etc) based on power consumption data. The optimization is directed by power costs, timing requirements, etc. This system will become the heart of a HAPI site. Think of it as the "kernel" that manages everything else.
Monitoring and Alerts
We have designed the database schema for an alert system. The system will allow a site to detect fault conditions and send notifications to human operators. The database schema is the only part of this aspect that is complete.
User Interface
We don't have one. We have developed the idea and basic structure (in XML) of a "site map". The site map provides the relationships between assets (pumps, lights, sensors, etc), Pins and/or Functions on the RTUs, and Section which are logically coherent assemblies of these. There have been discussion and false-starts around developing a UI in Processing as well as other platforms, but they have not gotten far. We definitely need people to invest effort in this area.
I hope to be posting RTU and Site Controller code to the SourceForge repository within the next few days.
Thanks,
Tyler
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The mentioned command(s) will simply "feel" the environment but otherwise do nothing.
The Slovak Optimizer will not make these decisions because they need goals to seek optimization. So, there are "flight plans"..so to speak...for each type of grow operation which the optimizer can handle.
In my ever humble opinion, the system architecture needs to fleshed out into
sequence and use case that will guide the construction.
I am not able, at this point, to document this myself and will need some help from you guys.
Once, certain things are define, i can finishing building detail design, and verify the design, publishing it, getting comments, and then getting open source developers let to do their thing.
If you agree, then I will probably take about 3 weeks of back and forths.
If you don't have time to work on this then let me know and i can move on to some other project.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The mentioned commands control assets within the environment as well as provide readings from sensors. It is not "simply feeling the environment".
The "Slovak Optimizer" will certainly make operational decisions. It's goal is to optimize around power management with a hybrid AI algorithm that can be extended to include further dimensions like water usage and labor requirements. It is a multi-dimensional optimization engine that will create flight plans in real-time as requirements and the environment change.
Please understand that the first functional versions of the Site Controller and RTU code will be delivered this week. Quite a bit of thought has gone into the design, we just haven't captured it very well. We'd be glad to have you help commit the design to formal documentation.
Thanks,
Tyler
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Team discussions and code are have not occurred in this forum. When sufficient discussions and code is posted then i will look through the finalized design and I might be able to move further with any proposed next step(s). I guess before you shift into reverse, though, can you state here what you use cases for v1 will be...in this discussion one another thread in general discussion.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Current project status and updates
Looks like a great project. Could you give an update on status. What is happening, where is the project at with code, how many members, when, what, where?
We are Excited about this.
Last edit: xtec 2013-03-10
Hi xtec. The project is still in its infancy but I am actively working on the "kickables" daily. The prototyping facility is being built in Columbus, Ohio. Yesterday I planted seedlings in the first "section". It consists of 4, 4' pvc channels set up in a flood and drain configuration with a 4-bulb, 4' T5 fluorescent lighting fixture. At the moment, I'm running the lights 24 hours a day and the nutrient pump is setup on a basic commercial timer that turns it on for 15 minutes every 2 hours.
The next step is to install an Arduino unit to replace the commercial timer and implement a sane light cycle. We have relays, Unos and Megas at our disposal. I have some basic code for this, but it's just bare bones essentials. So, priority 1 for this week is to have a simple program that allows for regular cycling of a pump and a light (2 separate relays).
Next week we will have a good real-time clock that we can install but for now the system can just do "dumb" cycling, e.g. 15 minutes ON, 120 minutes OFF.
Also, the HAPI site will have a high-level control function implemented with a Raspberry Pi. (I'm assuming you've read the system description.) This week, the networking will be completed so that we will have secure access (VPN, SSH) to the Pi in the HPF (Hapi Prototyping Facility). So within a week or two, we will be able to access a live video stream inside the HPF, check logs, control sections remotely and perform live updates to firmware.
On the tech side, the team is just forming. It is myself and another gentlemen who is interested in doing technical documentation (he's been patiently waiting for things to get moving.) I am just about to do a little recruiting for this effort and would appreciate both technical help on the project as well as social help in recruiting.
Ultimately, I'd like to look into building section controllers using UML 2.0 State machines and a cool open source compiler. We're obviously not there yet and for now, I'm much more concerned with just getting relays to cycle so as not to kill the first batch of seedlings :)
I'll post some of the initial code later today so we have a starting point for collaboration. Will also post some pics from the HPF.
Please let me know if I can answer any more questions. We'd be glad to have you aboard!
Thanks,
Tyler
Sorry I haven't posted any code yet. I have a few pieces that I'm about to stitch together and call the "beginning". I gotten basic remote control functionality working and posted a video of the tech stack on youtube: http://www.youtube.com/watch?v=G59H2Jt0KKQ
I've acquired a ChronoDot v2.1 realtime clock. Does anyone know if it can accessed by multiple arduino boards?
The HPF (HAPI Prototyping Facility) should be online by Tuesday.
Tyler
The post from Jay in the Wiki talks about developing a project direction and overview.
I agree with Jay - Your online documents are great for public info and gathering support.
If the "other gentleman" did the documentation - good job!
I am going to post some thoughts in the Project Direction Area.
Thanks
-- Project Status (3/22/2013 10:30 EDT)
High level conversations regarding technical direction are active. Please join in!
The HPF should have a dedicated IP address within 2 days. At that point, a Pi will be installed to act as the main controller for the site.
I am entering the HAPI project into Makezines Raspberry Pi Design Contest under the Utility category. Working hard to get the KickStarter project launched before we win the contest.
http://blog.makezine.com/raspberry-pi-design-contest/
--End Status
Just a hi from a new guy...
I'm Nikos and I've working with hydroponic systems for several years.
Currently re-doing the logic and interface on an old, plc, CX-Supervisor based system that never really worked well. This experience left with a "there's gotta be a better way.." type of feeling and have been developing parts of a "minimal" system for a while now and possibly I can contribute and learn.
regards
nikos
Hi-I would interested in developing web-site and system interface for the hapi. I see that not much as happened,here, since earlier part of the year. Now, I have a little time between projects, and, if there should be interest/need such addition then let's start a discussion. I would expect that the system interface, written in python -- would add feature to handle grow schedule rules [light, water, humidity, etc]. I guess what is important is to be able run a entire system from one rasp machine -- given such a rule base, inputed. But still be able to interface with a server for larger more industrialized entities.
Also, the rules should be able to be published--open source still without computer knowledge..
Hi,
Thanks for reaching out. You are correct that not much has happened on the SourceForge site in the last few months but this is not due to a lack of activity. Quite the opposite; the project has been very active and I just have not had the time to keep SourceForge updated with our progress. I will post some system documentation within another day or two, it's still be developed. However, I'd like to give you a quick project status here and respond in particular to your offer.
CLI & RTU
At the lowest level, we have implemented a "Command Language Interpreter" (CLI) on the Arduino Mega 2560. It accepts commands over a network connection (via an Ethernet shield) and executes them.
Commands are like:
"doc0121" - Turn on pin 12 (doc=digital output control, 012=pin 12, 1=pin state)
The CLI can set states on all digital and PWM pins and creates response strings (in JSON) that reflect the status of all pins and analog inputs on the unit. The code also includes the ability to easily add custom functions to the CLI for example, when calling libraries for certain sensors. It also provides the ability to manage what we call "Default States" which is essentially fail-safe state information that we write to and read from EEPROM. I have been hesitant to post this code to SourceForge as I have been porting it to the Uno. The unit, regardless of Arduino model, is referred by the team as an RTU, for Remote Terminal Unit.
Site Control
We have also developed a "Site Controller" function which is currently realized as a Python program running on a Raspberry Pi. The site controller can retrieve command files from an ftp site and pass them to an RTU. It can also get response data from an RTU, package it as a file and push it to the ftp site. The program is called a Command Broker, as its primary function is to carry commands between humans and RTUs. The ftp interface is for scenarios where the grow site is not directly accessible to the user over the internet. We are finishing up the real-time interface that supports direct connections, at which point we will post that code as well.
Power Management
A team of artificial intelligence researchers in Slovakia is creating a smart power management system. It will have the ability to create optimal schedules for assets (lights, pumps, etc) based on power consumption data. The optimization is directed by power costs, timing requirements, etc. This system will become the heart of a HAPI site. Think of it as the "kernel" that manages everything else.
Monitoring and Alerts
We have designed the database schema for an alert system. The system will allow a site to detect fault conditions and send notifications to human operators. The database schema is the only part of this aspect that is complete.
User Interface
We don't have one. We have developed the idea and basic structure (in XML) of a "site map". The site map provides the relationships between assets (pumps, lights, sensors, etc), Pins and/or Functions on the RTUs, and Section which are logically coherent assemblies of these. There have been discussion and false-starts around developing a UI in Processing as well as other platforms, but they have not gotten far. We definitely need people to invest effort in this area.
I hope to be posting RTU and Site Controller code to the SourceForge repository within the next few days.
Thanks,
Tyler
The mentioned command(s) will simply "feel" the environment but otherwise do nothing.
The Slovak Optimizer will not make these decisions because they need goals to seek optimization. So, there are "flight plans"..so to speak...for each type of grow operation which the optimizer can handle.
In my ever humble opinion, the system architecture needs to fleshed out into
sequence and use case that will guide the construction.
I am not able, at this point, to document this myself and will need some help from you guys.
Once, certain things are define, i can finishing building detail design, and verify the design, publishing it, getting comments, and then getting open source developers let to do their thing.
If you agree, then I will probably take about 3 weeks of back and forths.
If you don't have time to work on this then let me know and i can move on to some other project.
The mentioned commands control assets within the environment as well as provide readings from sensors. It is not "simply feeling the environment".
The "Slovak Optimizer" will certainly make operational decisions. It's goal is to optimize around power management with a hybrid AI algorithm that can be extended to include further dimensions like water usage and labor requirements. It is a multi-dimensional optimization engine that will create flight plans in real-time as requirements and the environment change.
Please understand that the first functional versions of the Site Controller and RTU code will be delivered this week. Quite a bit of thought has gone into the design, we just haven't captured it very well. We'd be glad to have you help commit the design to formal documentation.
Thanks,
Tyler
Team discussions and code are have not occurred in this forum. When sufficient discussions and code is posted then i will look through the finalized design and I might be able to move further with any proposed next step(s). I guess before you shift into reverse, though, can you state here what you use cases for v1 will be...in this discussion one another thread in general discussion.