marspeed
Member
What exactly did everybody buy?
we went thru that already
What exactly did everybody buy?
So nick did very little programing and all this about him being close to a finshed product was a bunch of crap.
Skip the Web interface; it is prohibitively expensive to the point where buying a controller becomes more viable.I wouldn't say "very little" but there is tons more to be done, needless to say. If you look at the code on his Google project page there is a fair amount there. And there may be more that he hasn't published due to it not working - developers tend to release code as they create compilable/working solutions. It's just highly unfortunate that he has disappeared before getting to the state where he was ready to release the next version of his codebase.
As I've mentioned before I unfortunately don't have tons of time to work on the project, but I am happy to contribute and share ideas/code with people when I can. I plan on keeping my project posted publicly via GitHub - where I currently have an empty project sitting.
I am in the process of cobbling together my own controller using the aforementioned parts and re-purposing code from various projects such as this one, Jarduino, Open Reef, Hydra, Arduarium, etc...
First order of business for me is getting the 5" screen wired up along with an RTC and a protoshield that lets me access the remaining Due pins. Then get the screen to run at full resolution with some kind of framework UI in place. Second, get some sensors connected and display the data. Then get it communicating with my Mega and controlling my LEDs. Then my web interface (actually this may come sooner as I just came across some code that makes this part seem incredibly easy.) A project like this really is a huge task though and I don't anticipate getting even close to completion by the end of the year.
First order of business for me is getting the 5" screen wired up along with an RTC and a protoshield that lets me access the remaining Due pins.
Then get it communicating with my Mega and controlling my LEDs. .
Skip the Web interface; it is prohibitively expensive to the point where buying a controller becomes more viable.
The best way to access extra pins is to simply remove the female headers entirely.
I hope your controller comes through!
I also wouldn't bother with the web interface. That can be phase 2![]()
If I'm reading this right, you are planning on using a Due and Mega is that right?
I tried the protoboard route, but it didn't work. The spacing of the accesable pins is different. It's hard to describe.I think I've already spent enough that I could own a top end controller! For me, this is more about the fun of the build than about being economical. I like making things.
What do you mean by "The best way to access extra pins is to simply remove the female headers entirely." Are you referring to the female headers on the Due board or the male pins on the ITB_02 shield?
What I was thinking of doing is setting up a protoboard that makes use of the pins not used by the ITB shield (mainly need to have pins available for I2C communication and the RTC chip) and then put stackable headers on that protoboard so that I can plug the ITB shield on top of that.
Seems like it will be easy enough, looking at this code: http://www.openreefs.com/webserver-example-explained
But if it doesn't go smoothly the first time I try - it will simply be pushed aside until later!
!