Many people think I am “just” building a paludarium… But they don’t see the complex world of automation behind it. In fact, there is a full blown application running the paludarium, build in a limited-but-functional cloud-native architecture.
This architecture is limited… Because you can have multiple instances of your microservices… But in the end there is only one piece of hardware to control. A single relais, a single led light, a single pump, a single valve and a single level sensor. And this is a problem; what if multiple microservices all talk to the one hardware platform at the same time? I needed a way to put a lock on who can send commands, and Redis came to the rescue.
The limitations of having “one hardware”
What if you have all kinds of microservices and functions that all want to talk to a single hardware platform? There are several functions and services that want to talk to the hardware:
In the past I have always had wooden hoods on top of my paludariums which I call “the Canopy”. The latest one did not have a hood, as I placed lighting and fans in the open on top. For this new and big design that will not work, so once again it is off to the store to get wood cut to size.
Modules, modules everywhere.
In the past I used the Canopy to mount everything I needed directly in to. I even had a version that had a full-blown PC power supply mounted on top. Not this time. I want everything to be removable, modules everywhere. So I had plywood sawed to size not just for the Canopy itself, but also for up to 4 modules which slide into the Canopy. As I do not want to remove the canopy whenever I need to make a change, this time I will build a detachable front element which is held in place by magnets.
So far I have only two modules in mind, one that carries a few pumps (rain pump, backdrop moisturization pump), nothing too fancy.
The second module is more interesting. It holds the complete “air conditioning” system. There are two 120mm regulated fans in there, an air heater and two mistmakers. This is quite a complex module, as it will measure air going in (to get an ambient reading), and have multiple connections for osmosis water pumped through (for the mistmakers), connections for the air heater and of course the fans.
These modules will be covered in a later post.
Constructing the Canopy
For the Canopy itself, I just need some holes for feeding through cables, sliders to mount the modules, and a system rail in front where I can mount a series of power leds. Also, I’d like to maximize accessibility. The idea is that I’ll build an “inner layer” of plywood that sits on top of the paludarium, and a thinner “outer layer” that neatly falls over the edges of the glass paludarium, hiding the top two centimeters or so. First it is off to the inner layer construction. Yet it always seems to start with a saw:
Assembling the inner layer of the Canopy
Using the sawed corner supports it was relatively simple to build the basic construct. As usual the fit was ALMOST right. So I guess there will be some sanding and filling in my near future 😉
I needed to add some holes in the rear of the Canopy for feeding through cables and such. Not quite sure how big the holes should be, so I settled on a slit of 28mm high (just because I had a 28mm drill handy 😉 ). Hopefully all connectors I will ever use will fit through! In line with the other 2 holes I just added some holes in the back (yes, 28mm as well 😉 ).
Furthermore I have added fan guards to the 120mm holes on top. The biggest struggle will probably be to get the air conditioning module to align with these holes 😉
Finally, a cozy look from the inside of the Canopy that demonstrates the shape of the Canopy a bit more:
What next?
So up next is figuring out a way how to fix the top in a more solid way and not just on the edges. Anyway, I’ll figure that one out soon enough. Then it is on to constructing the outer layer and the sliders for the modules and the lighting rail. Not to mention the lighting rail itself 😉
[…] to the “C”. Today I still program in both “C” and Python for fun (Arduino and Raspberry Pi […]
[…] I got a phone call that my paludarium was ready for delivery… So I needed to speed up the…
Hi Loek! Kan zeker, misschien wel handig om even te wachten totdat in ieder geval de hardware is opgebouwd en…
Goedemorgen Erik, Ik wil dat graag een keertje live bekijken. Kunnen we een afspraak maken?
Thinking this through... Even if I have 256x WS2818's I'd use 3*256 = 768 bytes of memory for R,G,B... The…
This website uses cookies to improve your experience. We'll assume you're ok with this, but you can opt-out if you wish. Cookie settingsACCEPT
Privacy & Cookies Policy
Privacy Overview
This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience.
Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website. These cookies do not store any personal information.
Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies. It is mandatory to procure user consent prior to running these cookies on your website.
[…] to the “C”. Today I still program in both “C” and Python for fun (Arduino and Raspberry Pi […]