reef-pi :: An opensource reef tank controller based on Raspberry Pi.
- Thread starter Ranjib
- Start date
-
- Tags
- controller raspberry-pi
- Tagged users Ranjib
OP
OP
- Checked:Support for multiple ato
- Checked: leak detector
- Checked: Wavemaker
- Telemetry option : Up for debate. Adafruit is launching a plus service 10$/month for unlimited telemetry. I want to have reef-pi to give 7 days history as charts across all the components.
Ryan115
Well-Known Member
As always, you are on top of it!
Alright, I have got reef-pi installed on my Pi3 and the Pi3 sitting on my network. All is good on that front.
As I understand it, you're shooting for a full 1.0 release at the end of the year. And from reading this thread, it looks like a lot of the functionality that you're shooting for in the full release works (haven't seen a lot of discussion about the doser, so I'm not sure about that). Maybe some bugs here and there, but you're getting those squashed.
Would I be correct in assuming that the UI is going to undergo some polish? As it stands now, it's there, but parts are a bit confusing, could be presented in a more clear way for the public (i.e. people who haven't followed this thread), along with changes in labeling as well as a "System Status" monitor.
I know that UI programming is a beast in and of itself. One I have no experience it. I've been part of teams that have done interface design (dear god, design by committee is a recipe for disaster...), but not implemented the backend of them.
Having said all that, would now be a good time to offer mock-ups of UI ideas for discussion?
As I understand it, you're shooting for a full 1.0 release at the end of the year. And from reading this thread, it looks like a lot of the functionality that you're shooting for in the full release works (haven't seen a lot of discussion about the doser, so I'm not sure about that). Maybe some bugs here and there, but you're getting those squashed.
Would I be correct in assuming that the UI is going to undergo some polish? As it stands now, it's there, but parts are a bit confusing, could be presented in a more clear way for the public (i.e. people who haven't followed this thread), along with changes in labeling as well as a "System Status" monitor.
I know that UI programming is a beast in and of itself. One I have no experience it. I've been part of teams that have done interface design (dear god, design by committee is a recipe for disaster...), but not implemented the backend of them.
Having said all that, would now be a good time to offer mock-ups of UI ideas for discussion?
OP
OP
Yes. You are spot on. Our focus right now is to improve ux/ui , improve documentation and squash any outstanding bug in 1.0 feature set, which is
- Power controller (relays , timers )
- Light controller(24 hour cycle)
- Temperature controller
- Ato
- Telemetry
- Camera
This does not mean we can’t have new features in 1.0 other than these (like doser , macros etc), they’ll be just experimental
Last edited:
Ryan115
Well-Known Member
I work with a few Aggies.
Where did you end up after Marine Bio? I am pretty amazed at where the career path can branch off to.
AshwinRavi
Active Member
do the aggies hate OSU Cowboys? 
AshwinRavi
Active Member
My wife and I are both OSU grads
njtiger aquariums
Well-Known Member
@Ranjib not sure if this may help with the button/status confusion.
On my system I design my buttons to be sliders. The outlet override section I can slide it to off (which turns the outlet off), auto (which then runs the schedule), or on (which turns the outlet on.
The two state slider doesn't have text but mimic most smart phone sliders (as to the right it's 'on'/'enabled' and to the left it's 'off'/'disable'. That might help keep your UI easy to understand. Let me know if you want to know how I made those sliders.
On my system I design my buttons to be sliders. The outlet override section I can slide it to off (which turns the outlet off), auto (which then runs the schedule), or on (which turns the outlet on.
The two state slider doesn't have text but mimic most smart phone sliders (as to the right it's 'on'/'enabled' and to the left it's 'off'/'disable'. That might help keep your UI easy to understand. Let me know if you want to know how I made those sliders.
OP
OP
Yeah, your ui makes it very clear and prominent which state the equipment is in.@Ranjib not sure if this may help with the button/status confusion.
On my system I design my buttons to be sliders. The outlet override section I can slide it to off (which turns the outlet off), auto (which then runs the schedule), or on (which turns the outlet on.
The two state slider doesn't have text but mimic most smart phone sliders (as to the right it's 'on'/'enabled' and to the left it's 'off'/'disable'. That might help keep your UI easy to understand. Let me know if you want to know how I made those sliders.
I never found my equipments ui confusing
, till others pointed out. Let’s see what other folks say. If it becomes consistently a problem , I’ll revisit it for sure .
AshwinRavi
Active Member
I think, once all the discussion settled and I wrapped my mind around it, Its not confusing anymore.
OP
OP
njtiger aquariums
Well-Known Member
Yeah, your ui makes it very clear and prominent which state the equipment is in.
I never found my equipments ui confusing
I know what you mean. I developed a system once and I felt it was fine until I put users in front of it. Then I found out other wise. As a developer you know how it should work so it already understandable to you.
njtiger aquariums
Well-Known Member
Also note your UI isn't confusing to me and is an acceptable UI design. In fact I do AV coding in my job and I use the same UI status for projector/equipment status (button labeled says On and color scheme standard when the equipment is off and then switch to saying Off and color scheme to highlight when the equipment is on). If professors can figure that out with no issues then others can as well and should work for your system.
and should work for your system.
Ryan115
Well-Known Member
I would agree. It all makes sense now. It will be interesting to see if new people that start using it are split with how they infer the button meaning, or if I am in the vast minority for that.
As a note for clarification, Ranjib I think it may make the outlet setup easier if instead of "reverse" it would say NC or Normally Closed. That way it also shows that it is expecting NO by default.
Ryan115
Well-Known Member
So looking ahead to getting my sBReefLights in and starting control.
I purchased the 32" Basic, so I will have two circuits to control. While I am digging around inside, I am going to look for a way of dimming the moonlight channel as well.
First test will be 10V PWM, as in the build guide.
If that works, we are all good.
If that has any issues, there are two other approaches to test out.
The first is to add a low-pass filter on the end of the 10v PWM circuit.
If that doesnt work, a pwm to analog module should be the failsafe solution.
http://www.ebay.com/itm/PWM-to-Volt...d=272345411971&_trksid=p2385738.c100677.m4598
I purchased the 32" Basic, so I will have two circuits to control. While I am digging around inside, I am going to look for a way of dimming the moonlight channel as well.
First test will be 10V PWM, as in the build guide.
If that works, we are all good.
If that has any issues, there are two other approaches to test out.
The first is to add a low-pass filter on the end of the 10v PWM circuit.
If that doesnt work, a pwm to analog module should be the failsafe solution.
http://www.ebay.com/itm/PWM-to-Volt...d=272345411971&_trksid=p2385738.c100677.m4598
Similar threads
