reef-pi :: An opensource reef tank controller based on Raspberry Pi.
- Thread starter Ranjib
- Start date
-
- Tags
- controller raspberry-pi
- Tagged users Ranjib
Aaron Smith
Active Member
- Joined
- Apr 9, 2017
- Messages
- 250
- Reaction score
- 273
- Location
- Oregon
- What state or country do you live in
- Oregon
Super interesting that you scoped a controller and it was pwm with a low pass filter. I know reef angel is configurable between 5v pwm 10v pwm and 10v analog. Apex uses 10v analog.
Cary
Well-Known Member
This stuff is waaaaay over my head. The electronics are what worries me...though I will be documenting the procedure as I go to help any others . We can add it to fill out the build and general guides
Aaron Smith
Active Member
- Joined
- Apr 9, 2017
- Messages
- 250
- Reaction score
- 273
- Location
- Oregon
- What state or country do you live in
- Oregon
Don't be intimidated by the lingo. Ranjib has done all the hard work, only thing left is assembly[emoji41]
You can see from my posts early on that I had no prior pi experience and I have had reef-pi running for quite some time now. I am glad to see more people jumping in. [emoji3]
OP
OP
- Joined
- Apr 16, 2016
- Messages
- 9,848
- Reaction score
- 17,081
- Location
- Pleasant Hill, Concord
- What state or country do you live in
- California
N
nope. Just USB ttl cable will do. In fact with no display or console connection will boot as well
OP
OP
- Joined
- Apr 16, 2016
- Messages
- 9,848
- Reaction score
- 17,081
- Location
- Pleasant Hill, Concord
- What state or country do you live in
- California
Don't worry, it may not be a smooth experience, since this is diy and the project is relatively young. But you won't fail. And these steps will get easier as time passes
Aaron Smith
Active Member
- Joined
- Apr 9, 2017
- Messages
- 250
- Reaction score
- 273
- Location
- Oregon
- What state or country do you live in
- Oregon
I will say that anyone not comfortable with 120volt wiring should ask questions or find a friend who is an electrician to look things over. Wiring the low voltage pi connections pose no safety concern, but 120 can ultimately burn the place down or cause harm to you or others. Ok I'm done preaching my trade[emoji846]
OP
OP
- Joined
- Apr 16, 2016
- Messages
- 9,848
- Reaction score
- 17,081
- Location
- Pleasant Hill, Concord
- What state or country do you live in
- California
I learned electronics couple of years back. I am more familiar with software and biology (job is in software, and education in biology) , the whole openhardware movement and forums like this made electronics/IoT approachable for me
Cary
Well-Known Member
Yep I studied marine biology but write technical manuals...I can do just about anything that has something written down and just needs filling out. I think the wiring diagram in the power controller is straight forward but surely check with you all and check with a dvm before I light myself up...thanks all
Aaron Smith
Active Member
- Joined
- Apr 9, 2017
- Messages
- 250
- Reaction score
- 273
- Location
- Oregon
- What state or country do you live in
- Oregon
Post a pic of the driver. Both open and closed it will be helpful for seeing what you have and will also be good documentation for the thread.[emoji41]
OP
OP
- Joined
- Apr 16, 2016
- Messages
- 9,848
- Reaction score
- 17,081
- Location
- Pleasant Hill, Concord
- What state or country do you live in
- California
I got most of the core code refactoring done. reef-pi codebase is now fairly modular. Theres lot more to be done., but that can be on-going effort, at least the biggest code sphaggettis are gone. I was able to write unit tests for most of the logic, here a screen shot of the coverage:
Equipments, lighting channels all are dynamic again. i.e we should be able to add/remove equipment using ui . This used to be the case in the beginning , but later I had removed it to make the overall usage simple, and geared for only a pico tank with 4 equipments. .right before maker faire. We have learned a lot since then. Equipments have to be dynamic, UI driven, it can be configuration based. Its just silly that we have to edit a config file to add a new equipment
. So, thats fixed now.
I have also added UI testing. From now on, each module will have at least a single end to end testing.
If you are interested to watch it in action, heres a screen capture:
Just to reiterate. I am planning for a 1.0 release of reef-pi before /around X-mas, and I have a few basic goals for that:
1) Get reef-pi controller software refactored with clear API (1.0 API will be supported 1 year. 4 year LTS)
2) Get handful of core modules (lights, equipments, temperature, ato ...) tested, documented (build guide)
3) Reduce the pain around setting up reef-pi (have sane defaults, let everything be configurable from UI).
I am pretty confident of getting to 1, it will positively impact 3 as well. Getting the build guides in shape will be some major work
Equipments, lighting channels all are dynamic again. i.e we should be able to add/remove equipment using ui . This used to be the case in the beginning , but later I had removed it to make the overall usage simple, and geared for only a pico tank with 4 equipments. .right before maker faire. We have learned a lot since then. Equipments have to be dynamic, UI driven, it can be configuration based. Its just silly that we have to edit a config file to add a new equipment
. So, thats fixed now.I have also added UI testing. From now on, each module will have at least a single end to end testing.
If you are interested to watch it in action, heres a screen capture:
Just to reiterate. I am planning for a 1.0 release of reef-pi before /around X-mas, and I have a few basic goals for that:
1) Get reef-pi controller software refactored with clear API (1.0 API will be supported 1 year. 4 year LTS)
2) Get handful of core modules (lights, equipments, temperature, ato ...) tested, documented (build guide)
3) Reduce the pain around setting up reef-pi (have sane defaults, let everything be configurable from UI).
I am pretty confident of getting to 1, it will positively impact 3 as well. Getting the build guides in shape will be some major work
Cary
Well-Known Member
Just looked at one of the last commits of Ranjibs code that was just committed. Of course I don't understand it, but noticed he includes tooltips. Very cool.
This made me wonder if we needed a glossary of terms. Things like cron, commit, pull, etc., are common in software work but not in everyday life. I would be happy to begin this if anyone thinks it might be useful.
Ranjib, what do you think? This would not be more work for you, except to review it and load it on github. Maybe we can even define the components..okay, not a real glossary, but something that explains terms and components most people are not familiar with.
This made me wonder if we needed a glossary of terms. Things like cron, commit, pull, etc., are common in software work but not in everyday life. I would be happy to begin this if anyone thinks it might be useful.
Ranjib, what do you think? This would not be more work for you, except to review it and load it on github. Maybe we can even define the components..okay, not a real glossary, but something that explains terms and components most people are not familiar with.
- Joined
- May 19, 2016
- Messages
- 2,434
- Reaction score
- 2,543
That would be so, so helpful to me because I have no idea what most of these words are and it just feels like a huge barrier to entry.
