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

[Ranjib]

Since there are folks out there that aren't "linux-saavy", would it be possible/feasable to create a reef-pi image that already has the /boot/config.txt changes, etc already done for folks? I could easily make the image, hosting it would be another story.

you got the problem right, lets continue discussing about the solution.
We want to be able to configure the /boot/config.txt for builders, but hosting a whole image is probably hard due to large space equirements, and bandwidth is not cheap.
I have some thoughts on this, i'll get to this after 3.0,

 

[dmolavi]

you got the problem right, lets continue discussing about the solution.
We want to be able to configure the /boot/config.txt for builders, but hosting a whole image is probably hard due to large space equirements, and bandwidth is not cheap.
I have some thoughts on this, i'll get to this after 3.0,

Would an ISO of Raspbian Lite be too large for Github? The zip file clock in around 350MB. If Github doesn't care, an image for Pi 3B+ and Pi zero could be hosted there (with an additional set for the baseboards as well...4 total).

Otherwise, @theatrus has a pre-built config.txt on his git repo for his base board. Maybe something like that for a generic reef-pi build, along with a more detailed/explicit how-to. Soup to nuts - getting a headless install w/ ssh and wifi (my post above), config.txt stuff, etc. Basically consolidate all the docs from Pi and Reef-Pi into one place for new users.

 

[Ranjib]

Would an ISO of Raspbian Lite be too large for Github? The zip file clock in around 350MB. If Github doesn't care, an image for Pi 3B+ and Pi zero could be hosted there (with an additional set for the baseboards as well...4 total).

Otherwise, @theatrus has a pre-built config.txt on his git repo for his base board. Maybe something like that for a generic reef-pi build, along with a more detailed/explicit how-to. Soup to nuts - getting a headless install w/ ssh and wifi (my post above), config.txt stuff, etc. Basically consolidate all the docs from Pi and Reef-Pi into one place for new users.

Its not just one image, depending upon the build components (based on the adafruit guide recommended parts or HATs or baseboard), the configuration will change (and may be some software as well.. like motion) , the image path will lead to us hosting at least a handful of images.

 

[ScottF83]

Hey guys

Remember me?

My goal with reef-pi was to create a continual feeding doser, which would drip feed chilled, defrosted frozen food cubes.

Well, using guide 7 and many evenings of soldering, I've got everything together and have just been adding the equipment.

The good news is that the Pi powers up and the dashboard works. There's also power getting to a test pump.

Bad news is that the pump seems to turn on and off at random (still just trying to calibrate it), and I received an error when adding the pumps to the gui.

Anyway, I've disconnected it for tonight and will start a separate build thread tomorrow to get this fixed and also program it properly (you may remember that I need it to feed the food and then reverse direction to clear the tubes thereby avoiding spoilage).

 

[theatrus]

Its not just one image, depending upon the build components (based on the adafruit guide recommended parts or HATs or baseboard), the configuration will change (and may be some software as well.. like motion) , the image path will lead to us hosting at least a handful of images.

I’d actually propose we just package Debian packages for base configurations (Hat, Pico, Guide) which can be installed and maintain the base configs. A quick shared script can be used to safely merge any other configure changes.

I can hack something up here (as terrible as dpkg is over rpm)

 

[DirtDiggler2823]

Upgraded to 2.2. Let's see how it goes!

 

[Ranjib]

Hey guys

Remember me?

My goal with reef-pi was to create a continual feeding doser, which would drip feed chilled, defrosted frozen food cubes.

Well, using guide 7 and many evenings of soldering, I've got everything together and have just been adding the equipment.

The good news is that the Pi powers up and the dashboard works. There's also power getting to a test pump.

Bad news is that the pump seems to turn on and off at random (still just trying to calibrate it), and I received an error when adding the pumps to the gui.

Anyway, I've disconnected it for tonight and will start a separate build thread tomorrow to get this fixed and also program it properly (you may remember that I need it to feed the food and then reverse direction to clear the tubes thereby avoiding spoilage).

I remember. Very interesting use
The doser pumps should work as expected. 2.0 had a bug. What version you are running?

 

[Bigtrout]

Yup. That’s my current estimate ... but it can always change if we encounter bugs(delayed) or get a some free cycles ( faster).

I got my pH board from @Jonathan Troutt today...that gives me time to get a good probe on the way!

 

[bishoptf]

I’d actually propose we just package Debian packages for base configurations (Hat, Pico, Guide) which can be installed and maintain the base configs. A quick shared script can be used to safely merge any other configure changes.

I can hack something up here (as terrible as dpkg is over rpm)

I can help out if we want to package stuff up. What about using p2p torrents for the software, I would be glad to seed a torrent, if we get enough folks to seed then that would be a possibility and no one person would take the bandwidth hit.

 

[bishoptf]

I am using the mini xlrs as well, and I love them. I did not have any issues with my 3.5mm plugs (old radioshack plugs) but I am happy that I switched.
I went with the 3 pin version for my temp probes and I am going to be using the 4 pins for my lighting controls.
https://www.amazon.com/Connector-Au...7&sr=8-10&keywords=3+pin+mini+xlr+panel+mount

Those do look nice but pricey, I have some different panel audio jacks and they lock in really well these are the ones - https://www.amazon.com/CESS-Stereo-...1312&sr=8-20&keywords=panel+mount+audio+jacks

 

[bishoptf]

Sooo I know this has been discussed but what is the proper way to upgrade, do we stop the reef-pi service do the install and start the service back up? I'm used to just doing apt-get etc, I assume we can just do a dpkg -i vs removing and re-installing but thought I'd ask.

 

[bishoptf]

Upgraded to 2.2, now to go and change the default stats

 

[b4tn]

I just do a dpkg -i. I don’t stop any services or anything and it has worked for me.

 

[Ryan115]

Those do look nice but pricey, I have some different panel audio jacks and they lock in really well these are the ones - https://www.amazon.com/CESS-Stereo-...1312&sr=8-20&keywords=panel+mount+audio+jacks

Agreed they are a bit more expensive, but they are soooo nice!
You can get them cheap on ebay (or elsewhere from china) if you have the time.

 

[bishoptf]

Agreed they are a bit more expensive, but they are soooo nice!
You can get them cheap on ebay (or elsewhere from china) if you have the time.

Yeah a much better connector for sure, those audio jacks I listed are good too, really hard to pull out etc but will never be as good as an xlr jack.

 

[bishoptf]

Since there are folks out there that aren't "linux-saavy", would it be possible/feasable to create a reef-pi image that already has the /boot/config.txt changes, etc already done for folks? I could easily make the image, hosting it would be another story.

I still think if we beef up the documentation and help provide more guidance by providing links and or examples it should be good enough. Plus since this is DIY they should want to learn that side of it also since you will need to do software upgrades tc from time to time. I think that should be part of the learning experience also, I know it can be frustrating for sure but there are lots of tutorials with how to use nano etc. that we could leverage that should be able to help get the point across.

Willing to help on that front also...

 

[Ranjib]

I just do a dpkg -i. I don’t stop any services or anything and it has worked for me.

that should be enough

 

[Ranjib]

Just completed the analong input connector CRUD (create, retrive, update, delete) API and UI coding. Here is a run through of the flow:
1) An analog input connector is always associated with a driver capable of analog to digital capability. ph Board is an example. We start with
declaring a new driver. This is reef-pi 3.0 feature, where we are introducing HAL (hardware abstraction layer), aka drivers. This gives builder ability to use multiple pca96985 and other new drivers. Connectors (jacks, inlets,outlets etc) are always associated with a specific driver. Currently rpi, pca9685 drivers are present. I am testing the ph board driver. The new driver (hal) feature allows providing custom configuration for individual drivers as well (for example different pca9685 drivers can have different i2c address and can operate at different pwm frequency). Individual drivers can offer different capabilities (digital in/out, pwm , analog in etc). Among the current drivers only ph board provides analog input capability, we'll need this driver to create an analog input connector.

2) Next we create an analog input connector (physically it can be a panel mount female bnc connector ) and associate it with the ph board driver.

Next I'll work on integrating this connector with the ph subsystem, which is currently using only an i2c address as configuration assuming its an ezo circuit. I'll change the ph module to use an analog input connector instead if i2c value, I'll have to convert the current ezo circuit driver as hal driver as well, to get it working with the new scheme of things,...

 

[Mendeln]

I saw these postings this morning but unable to post from work, actually I would like being able to write to disk also, although I wouldn't write to the SD card I would write to a network share (NFS to be exact). I think this would be nice so if you do restart the reef-pi it reads the file and picks up from where it left off. I would also like to know if you can backup the database file and restore to a new installation so you don't have to re-configure things.

Great discussions as always, just thought I would weigh in.

+1 for the ability to store the data in the network (synology nas)

I can help out if we want to package stuff up. What about using p2p torrents for the software, I would be glad to seed a torrent, if we get enough folks to seed then that would be a possibility and no one person would take the bandwidth hit.

would love to seed the images from my synology. the nas is 24/7 online

 

[Diamond1]

Just completed the analong input connector CRUD (create, retrive, update, delete) API and UI coding. Here is a run through of the flow:
1) An analog input connector is always associated with a driver capable of analog to digital capability. ph Board is an example. We start with
declaring a new driver. This is reef-pi 3.0 feature, where we are introducing HAL (hardware abstraction layer), aka drivers. This gives builder ability to use multiple pca96985 and other new drivers. Connectors (jacks, inlets,outlets etc) are always associated with a specific driver. Currently rpi, pca9685 drivers are present. I am testing the ph board driver. The new driver (hal) feature allows providing custom configuration for individual drivers as well (for example different pca9685 drivers can have different i2c address and can operate at different pwm frequency). Individual drivers can offer different capabilities (digital in/out, pwm , analog in etc). Among the current drivers only ph board provides analog input capability, we'll need this driver to create an analog input connector.

2) Next we create an analog input connector (physically it can be a panel mount female bnc connector ) and associate it with the ph board driver.

Next I'll work on integrating this connector with the ph subsystem, which is currently using only an i2c address as configuration assuming its an ezo circuit. I'll change the ph module to use an analog input connector instead if i2c value, I'll have to convert the current ezo circuit driver as hal driver as well, to get it working with the new scheme of things,...

So I'm assuming that all the new releases will be 3.x?
The UI looks good and easy to navigate.