reef-pi :: An opensource reef tank controller based on Raspberry Pi.

[Schreiber]

Woo-hoo! Thanks @Ranjib & @Michael Lane (and I'm sure many others) for the awesome new features! I'll be trying this out first free night I get, probably Friday.

Also, with the pH probe ability to control equipment now, does that extend to dosing pumps? Or is that further on the future?

 

[Bigtrout]

Hive minds,
It's less than one month for thanksgiving, and we are heads down busy wrapping up reef-pi 3.0. Its mostly feature frozen (no new things) from now on. I just wrapped up the last bit of new things and that demands a new beta release. So,
reef-pi 3.0.0-beta is out now: https://github.com/reef-pi/reef-pi/releases/tag/3.0.0-beta
This is by far the biggest changeset (highest amount of code) we have done for reef-pi., Here is the summary of key things, copying as it is from the release notes, with some explanations:

• Timer module improvements:
  • Ability to rigger macro: Yes, users can now trigger macros periodically.
  • Support weekly & monthly schedules: We;ll be able to say things like every Monday, in timer module.
• Control system:
  • Temperature module supports calibration
  • ph module can control equipment: Calcium reactor, CO2 injectors etc.
  • Hysteresis support in temperature and ph based controls: reef-pi can now act exactly same as heater's inetrnal thermostat. Makes it suitable for chiller and other equipment
  • Temperature and ph module can use macro instead of equipment as control target: Useful if you want to control multiple equipment. Just model them as a single macro.
• Drivers
  • Jacks can be reversed: We are moving the active high/low option from light channel to jacks. Similar to outlet and inlets, jacks can also be reveresed. This has exactly same effect as light channel high/low. So we are not really adding/deleting any feature, just moving it to a more semantically correct place.
  • kasa smartplug & powerstrip support: Control hs300 powerstrip, hs100/hs110 smart plugs,. This driver also exposes the current monitoring as analog inputs that you can use as fake ph probes.
  • File driver: This is a nifty feature where an arbitrary file can be used to provide a value. Think of an external script writing a single value in a text file and reef-pi can now seamlessly integrate with it, by reading that file periodically and treating as analog input (ph)
• New PWM profiles:
  • Sine: Typical sine curve for a given start-> end period
  • Arbitrary interval profile: Specify pwm values at fixed interval for a given start->end period. This is a generic version of the current 2 hour interval profile,. User can now use 1 hour or 15 min or any other fixed interval.
  • Random profile: generate incremental random values for a given time period and intensity range. I expect this to be useful for wavemakers
  • Composite profile: Allows combining above three profile (and fixed value profile). Think of pulse mode wavemaker profile can be implemented with an alternate diurnal and fixed interval profile.
• Internationalization:
  • Chinese language support
  • Portugese language support
  • Dutch language support
• Other:
  • reef-pi db subcommand: A new reef-pi db list/show/update/create/delete command that can work directly with the database., The controller has to be turned off for this. This can be used to investigate and fix reef-pi during troubleshooting.

We still have a few things to sort out, the pwm profiles UI is still not done yet. Michale is been working on it. Internationalization in not uniform yet (since we added quiet a bit of new things recently). We could really use your help in getting all the language support and above everything testing the beta release if possible. I have tried my best to test each of these bits, but I can certainly use more. I definitely wont be able to test all the possible software combination, let alone the hardware variations. So, if you have some free time or a test build , please give it a shot and let us know what you think. If everything goes well, we'll wrap up the UI bits, fix any critical bugs we found and ship 3.0 right before thanksgiving.

Can someine running 3.0 alpha just upgrade to 3.0 beta without problems, or does this entail a while new configuration to be done?

 

[Ranjib]

Thanks @Ranjib i think you may have answered my question in your patch notes.

I've just replaced my temp sensor ... the old one was getting a tiny rust spot on the bottom.
I replaced it like for like with a new DS18B20 .... the problem is, the temperature reading is different by about 2 degrees.
I've checked the temp of the tank with a calibrated photography thermometer and it's definitely out.
so my question is can i put an offset into pi so the temp readout is correct ?

I think i spotted in the patch notes for pi 3.0 the ability to calibrated the temperature is that what i need ?

Yes. You'll need to apply a single point calibration with -2 or +2 depending upon whether its reading above or below the expected value.

 

[Ranjib]

Can someine running 3.0 alpha just upgrade to 3.0 beta without problems, or does this entail a while new configuration to be done?

I think so. Nothing I can think of that will break the old data. If it does break please let me know, I have shipped a new sub command (reef-pi db) that is capable of altering/viewing the raw database, and we should be able to use it to selectively fix things even if the controller is not up.

 

[Ranjib]

I will be definitely running this by tonight (cst) and provide feedback.

Thank you, much appreciated.

 

[Ranjib]

Woo-hoo! Thanks @Ranjib & @Michael Lane (and I'm sure many others) for the awesome new features! I'll be trying this out first free night I get, probably Friday.

Also, with the pH probe ability to control equipment now, does that extend to dosing pumps? Or is that further on the future?

Yes and No. Let me explain:


After using the dosing pumps for one year (since 2.0), I have learned I only change the speed/pwm during calibration or other type of tweaks, i.e. I never changed the pwm/speed value once the dosing regimen is fixed/calibrated. Actual dosing is good old timer based switch on/off. My 3.0 setups, uses a potentiometer for calibration and the dosing unit is directly powered by a 12V 1A power supply, which I then put on timer. Similar to ATO. This is a simple but more robust solution for me.

If you are trying to dynamically set the PWM value during dosing and the pumps are modeled as dosing pump then No.. you need to longer workaround, but it's doable. I'll talk about it later (it involves switching pwm profiles using macro and triggering the macro with timers).

I'm open to feedback from all of you regarding what type of enhancements you think will be good for the dosing module. I already have one (using volume, like ml or cc in the UI and let reef-pi auto-calculate the regimen) that I think we'll be able to ship after 3.0 (since it only needs UI code, no controller changes), but happy to hear more.

 

[burningbaal]

Question on ATO with reef-pi:
I'm keenly interested in redundancy for the ATO, maybe I'm especially paranoid, but we've all heard the horror stories.

I'm thinking I want four level sensors, with the logic a bit...special:

1. High sensor: If this is ever wet while the return pump is on, make sure ATO pump is off and raise alarm
2. Low sensor: if this is ever dry (especially while not running a water change macro or something), raise an alarm
3. Middle pair of sensors: If high-sensor and both of these are all dry, turn on ATO. If high-sensor is dry and both of these are wet, turn off ATO.

Now the logic is a bit interesting, and maybe doesn't nestle into reef-pi as-is, but that I'm less worried about (I can modify the source code in a fork or something). My question is in wiring the middle sensors. I kinda need something that only changes the output when both inputs have changed, not a typical logic gate, it's kind of tracking a null (and not changing the output) until the actual state is changed. Or maybe I can actually have 4 ATO sensors on the reef-pi?

I've Michael Lane's goby hat, so I'm thinking maybe I put two sensors on the unassigned GPIO ports? Maybe if I make the high/low sensors mechanical sensors, I can just connect them to the 5V and one GPIO? when they get signal, they're wet (or vice versa)?

Right now, I'm using a kamoer (ebay) ATO, so the reef-pi is just switching it on/off with the 110v. It does have a high-sensor, but when I move ATO control fully into the rpi, I want to add this redundancy, and some kind of mini pcb board combining the two middle sensors seems like the best choice, but I don't know what I'm doing with hardware...

 

[Schreiber]

Yes and No. Let me explain:


After using the dosing pumps for one year (since 2.0), I have learned I only change the speed/pwm during calibration or other type of tweaks, i.e. I never changed the pwm/speed value once the dosing regimen is fixed/calibrated. Actual dosing is good old timer based switch on/off. My 3.0 setups, uses a potentiometer for calibration and the dosing unit is directly powered by a 12V 1A power supply, which I then put on timer. Similar to ATO. This is a simple but more robust solution for me.

If you are trying to dynamically set the PWM value during dosing and the pumps are modeled as dosing pump then No.. you need to longer workaround, but it's doable. I'll talk about it later (it involves switching pwm profiles using macro and triggering the macro with timers).

I'm open to feedback from all of you regarding what type of enhancements you think will be good for the dosing module. I already have one (using volume, like ml or cc in the UI and let reef-pi auto-calculate the regimen) that I think we'll be able to ship after 3.0 (since it only needs UI code, no controller changes), but happy to hear more.

Gotcha! If definitely be interested in learning more about switching the PWM profiles in the future. I'd hate to give up a few equipment slots, especially for bulky power supply plugs that typically occupy the space of 2 plugs.

 

[Ranjib]

Gotcha! If definitely be interested in learning more about switching the PWM profiles in the future. I'd hate to give up a few equipment slots, especially for bulky power supply plugs that typically occupy the space of 2 plugs.

Remember you can use 12V DC pumps (submersible or peristaltic) and switch them with l293D or uln2803a, and thus not using a full ac adapter, socket and the whole enchilada.

My recent 3d printed enclosures for all these units are very flexible. I use barrel connectors on the dosing pump enclosure which i can directly hook up to a reef-pi controller via male-male barrel jack connector or via a 12V dc wallwart which is hooked to an AC outlet.

 

[Schreiber]

Remember you can use 12V DC pumps (submersible or peristaltic) and switch them with l293D or uln2803a, and thus not using a full ac adapter, socket and the whole enchilada.

My recent 3d printed enclosures for all these units are very flexible. I use barrel connectors on the dosing pump enclosure which i can directly hook up to a reef-pi controller via male-male barrel jack connector or via a 12V dc wallwart which is hooked to an AC outlet.

I have my dosing pumps running on the L293D now. To control via pH level, could I just disable the dosing feature altogether, & control the "virtual equipment" set up for each pump? I'll try that this weekend.

 

[Ranjib]

I have my dosing pumps running on the L293D now. To control via pH level, could I just disable the dosing feature altogether, & control the "virtual equipment" set up for each pump? I'll try that this weekend.

Yes.

 

[sfgabe]

This is great, thank you @Ranjib and team! I'm taking 3.0 for a spin now.

How would I add the tplink hs300 driver? It asked for an address, but if I leave it blank I get an error.

 

[AquaRaider44]

@Ranjib I am having issues on the new version it will not let me set up my lights.

The old light settings are not working as well. I need to have my lights work. How do I downgrade to the alpha.

 

[Ranjib]

This is great, thank you @Ranjib and team! I'm taking 3.0 for a spin now.

How would I add the tplink hs300 driver? It asked for an address, but if I leave it blank I get an error.

add "IP:9999" as the address for the driver and choose among hs300/hs110/hs103, whatever is appropriate.

 

[Ranjib]

@Ranjib I am having issues on the new version it will not let me set up my lights.

The old light settings are not working as well. I need to have my lights work. How do I downgrade to the alpha.

Let me check it out. Lighting and internationalization has some rough edges, https://github.com/reef-pi/reef-pi/issues/859

 

[dmolavi]

upgraded and now one of my temp sensors isn't being seen....

It still shows up in the /sys/bus/w1....or whatever that directory is, and dmesg shows it being added, but reef-pi can't read the stats from it.

pi@reefpi:/sys/bus/w1/devices $ ls
28-00000a998f71  28-00000a9a89af  w1_bus_master1
pi@reefpi:/sys/bus/w1/devices $ cat 28-00000a998f71/w1_slave 
96 01 4b 46 7f ff 0a 10 0a : crc=0a YES
96 01 4b 46 7f ff 0a 10 0a t=25375
pi@reefpi:/sys/bus/w1/devices $ cat 28-00000a9a89af/w1_slave 
95 01 4b 46 7f ff 0b 10 0b : crc=0b YES
95 01 4b 46 7f ff 0b 10 0b t=25312
pi@reefpi:/sys/bus/w1/devices $

 

[brandon clow]

upgraded and now one of my temp sensors isn't being seen....

It still shows up in the /sys/bus/w1....or whatever that directory is, and dmesg shows it being added, but reef-pi can't read the stats from it.

pi@reefpi:/sys/bus/w1/devices $ ls
28-00000a998f71  28-00000a9a89af  w1_bus_master1
pi@reefpi:/sys/bus/w1/devices $ cat 28-00000a998f71/w1_slave 
96 01 4b 46 7f ff 0a 10 0a : crc=0a YES
96 01 4b 46 7f ff 0a 10 0a t=25375
pi@reefpi:/sys/bus/w1/devices $ cat 28-00000a9a89af/w1_slave 
95 01 4b 46 7f ff 0b 10 0b : crc=0b YES
95 01 4b 46 7f ff 0b 10 0b t=25312
pi@reefpi:/sys/bus/w1/devices $

I second this, I lost both temp sensors with a xx_w1 device not found. I will try to grab logs also. I opened the profile for each but neither populated with the sensor id.

 

[brandon clow]

Let me check it out. Lighting and internationalization has some rough edges, https://github.com/reef-pi/reef-pi/issues/859

I did a quick test run and lost one light out of three while the others remained. I am using diurnal and also observed that when attempting to edit the values with nothing changed, it would not save and stated to correct an error. Nothing was highlighted as an error but noticed that the pca9685 under connectors was now active high and the lighting profiles stated active low.

I did downgrade successfully to alpha and everything returned to the previous working state. I will upgrade again tonight once home life calms down and try to gather logs/observations.

 

[dmolavi]

I second this, I lost both temp sensors with a xx_w1 device not found. I will try to grab logs also. I opened the profile for each but neither populated with the sensor id.

After I did the manual read at the command prompt, it started getting readings, but only for a couple of minutes, then they got lost again.

downgraded back to alpha-2 and all is good again.

 

[Ranjib]

upgraded and now one of my temp sensors isn't being seen....

It still shows up in the /sys/bus/w1....or whatever that directory is, and dmesg shows it being added, but reef-pi can't read the stats from it.

pi@reefpi:/sys/bus/w1/devices $ ls
28-00000a998f71  28-00000a9a89af  w1_bus_master1
pi@reefpi:/sys/bus/w1/devices $ cat 28-00000a998f71/w1_slave
96 01 4b 46 7f ff 0a 10 0a : crc=0a YES
96 01 4b 46 7f ff 0a 10 0a t=25375
pi@reefpi:/sys/bus/w1/devices $ cat 28-00000a9a89af/w1_slave
95 01 4b 46 7f ff 0b 10 0b : crc=0b YES
95 01 4b 46 7f ff 0b 10 0b t=25312
pi@reefpi:/sys/bus/w1/devices $

Thats strange . I tested the temperature module last night and it worked ok. Can you check the logs , particularly when you try to to add new probe , and share it here.