Aqauponics IoT: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
(Redirected page to Aquaponics IoT)
 
Line 1: Line 1:
https://docs.google.com/presentation/d/1eylvUnfdcUgGWrdKg4HHL2i9KCrYHQTlcEEUiPe8Sdc/edit#slide=id.g7250a05ed_0_451
#Redirect [[Aquaponics IoT]]
 
 
<html><iframe src="https://docs.google.com/presentation/d/1eylvUnfdcUgGWrdKg4HHL2i9KCrYHQTlcEEUiPe8Sdc/embed?start=false&loop=false&delayms=3000" frameborder="0" width="960" height="569" allowfullscreen="true" mozallowfullscreen="true" webkitallowfullscreen="true"></iframe></html>
 
=Communications with Aquaponics Lab Team=
'''Gareth, Paulo, Hamish'''. Newest on top.
==Gareth==
See [https://docs.google.com/spreadsheets/d/1prKJsCbrsG3qVW7DIVONan3JLb9TiQtTctdHp4I-RuI/edit#gid=962662503 Aquaponics Lab IoT Interface BOM]]
 
==Hamish==
another salient point is that a good ESP board is $10 from Adafruit: http://www.adafruit.com/product/2471
 
we're runnign a web server on this board, and ok it isn't going to run enterprise java any time soon (or even apache for that matter) but it does do everything a sensor board needs to with the added convenience of wifi + http
 
like I said in my previous mail though, our current stuff is not yet at product or customer ship stage (don't kill me Gareth!)
 
h
==Gareth==
Hello there
 
Parts are all very widely found, apart from pH interface. It is open source hardware and available from Sparky's Widgets - I just checked and it says they are on backorder!! I could post you one I have spare to get you started - plus I've exchanged emails with him (Ryan) in the past and he's a super nice and helpful guy, I'm sure if you could talk to him you could get something worked out. Last resort is to use his board files to get your own boards made somewhere like oshpark?
 
I'll put together a BOM over the next few hours.
 
Our code seems stable, although it is under active development, the two main software authors are both pretty experienced in C and JS respectively. I ran it for 36 hours and didn't see any horrible memory leaks.
 
Display interface is currently a couchdb visualisation - we'll be plugging it into something like freeboard for a dashboard.
The data is being logged, many parameters need only hourly records but some things like light levels have more fine grained changes that are worth sampling and then averaging at least.
We'll be doing something to visualise the data, and yes, everything about the system is available both locally and over the internet (connectivity permitting!)
 
The Dragino seems very capable board, there are lots to choose from in this area, the key for us is to leverage work done already by the community, so platforms that have good community support (arduino and raspberry pi, increasingly esp8266) win out. For a sensor node, it looks a bit too heavy a solution perhaps, running a full linux stack. That's my first impression and thoughts.
 
I'll let you have a full BOM soon.
 
Kind regards
==Marcin==
Thanks. Gareth. This looks good to me. The main questions are:
 
are all parts source able on a 2 week time scale
Is the code stable
What is the display interface
Can this log data so we have an hourly daily record for monitoring/learning purposes
Is the data viewable on the internet via a URL
Are all the sensors readily available?
 
How does this route compare to Seeed Studio's Dragino?
==Gareth==
Gareth Coleman <gareth@aquaponicslab.org>
Oct 21 2015 (11 days ago)
 
to me, Paulo, Hamish
Hello there
 
I'm really excited that the open source ecology project is interested in our aquaponics systems, I've been a massive admirer of your work for a while...
 
Hmm, difficult to advise on your choice, system 2 has some documentation, and we have a working system that has been tested over time. One difficulty is that the radio used is now end-of-life, also the code we have developed against it is no longer maintained.
 
System 3 is moving rapidly to full prototype but has no documentation at present. However it is a better solution as it's based on wifi rather than a custom protocol, plus it's cheaper and simpler.
 
If you just want to build one system right now then perhaps you are better to use system 2 as it would be more straightforward. However, if you want to build a system to act as a model for further systems then system 3 is much better choice.
 
I can produce some basic documentation for system 3 that will be enough for you to replicate our electronics, and both software stacks are on github. Your experiences building it will be very helpful for us to improve our guidance and support. I really want to help you work with us.
 
---
 
I've hacked a quick note of our development schematic and a photo - we've also got code running for air temperature, humidity, light level and pH.
 
You can see our code at https://github.com/hamishcunningham/fishy-wifi/tree/master/ardesp/waterelf
 
Let me know what you think of this approach, I'm confident it is the best way forward even for you on a tight timescale.
 
---
[[Image:al3.jpg|thumb|Aquaponics Lab Generation 3 IoT Hardware prototype, Oct. 2015]][[Image:al3sch.jpg|thumb|Aquaponics Lab G3 IoT Schematic]]

Latest revision as of 13:43, 10 November 2015

Redirect to:

Retrieved from "https://wiki.opensourceecology.org/index.php?title=Aqauponics_IoT&oldid=132471"