And the valves are operational! Also confirmed the failsafe valve closes on power failure.
Follow along with the video below to see how to install our site as a web app on your home screen.
Note: This feature may not be available in some browsers.
Temp probes are tracking within 0.5 degrees of one another!
Atlas Scientific Ezo-RTD boards with their PT-1000 probes all mounted on a Whitebox Labs Tentacle T3.
Considering dipping the temp probes in some sort of liquid silicone for added protection against saltwater.
Haven’t yet decided if I’m going to try to encapsulate these. The data sheet says explicitly these are saltwater safe, but we all know how saltwater wears on almost everything...It would appear AquaLogic takes the standard probe that comes with Ranco and encloses it in a short piece of Titanium tubing using some sort of thermal epoxy. Just an idea.
Still following this MaddyP.. After allot of work travel, I'm back on my project finally. Focused on the actual aquarium/stand build... I'm back to the Node-Red work this weekend. I've already mastered calibration (well learned that from your work here) and temp/pH control. My focus now will be evap topoffs, water changes with a dosing regimen, and integrating my RO prep and storage. Might be some tricks I'll learn that I can share.
Looking forward to seeing your improvements.
Looking good. Take its easy on yourself. The front end frameworks have a bit of learning curve. We went with react, which supposed to be the easiest one, still it took months if not years to get the whole thing going. We still hit issues, but thankfully have a few folks in the project with very good UI skills to help us out.
I was just thinking about the stack of Widgetlords board I had purchased a few years back for my build and was wondering why they were not used in aquarium controllers more ... and then I stumbled on this thread. Wow. Hats off, you are setting the standard for using these boards. I just hope my hardware (boards) are still current.
To be honest, the Node-Red stuff seems confusing to me (as a developer), but I will wait to see if there are benefits over direct coding.
I am waiting to see how the Atlas Scientific boards work. Again I purchased a bunch of those years ago and ran into some trouble using them in a aquarium controller setting, but they have apparently fixed the issues by adding full isolation. I look forward to confirmation that this is the case.
Lastly the modulating valve actuators look like exactly what I have been searching for. Looking forward to hearing how they work out and any sourcing info on them would be appreciated.** Update **, nevermind on the sourcing. Reading your nano thread I found the reference to the Chinese version and Ebay as the source.
Dennis
I am waiting to see how the Atlas Scientific boards work. Again I purchased a bunch of those years ago and ran into some trouble using them in a aquarium controller setting, but they have apparently fixed the issues by adding full isolation. I look forward to confirmation that this is the case.
Dennis
Glad to hear! Once I start on the client side, I'll share the progress!
As a user of the Atlas-Sci sensors/circuits since the beginning (back when the called them stamps), I can attest to the strides they've made with signal integrity.. the isolation helps.. it gets a little expensive purchasing the individual circuits and then the appropriate carrier boards... But then I recall the time I used to spend designing and putting together my own solutions which were entirely inferior!. I'm done re-inventing the wheel and don't mind throwing a little money at a well designed solution to a problem (something about cost/benefit analysis...). With Atlas-Sci stuff I feel more like a systems integrator, rather than a DIYer...
I'm sticking with Node-RED and even it's dashboard as I already have the device in use. I've modified my flows to resemble yours in the way that I message over the i2c bus... I like the way you scan the bus, fetch addresses and read in the DeviceIDs and run with those to determine your sensor context within your code. I'm using more EZO devices than you and even multiple examples of the same type (eg. EZO pumps), so I I'm working on the extra step of fetching the NAMES to use as my differentiator throughout the flows/code, rather than just the burned in DeviceID. I have a USB carrier that I use to setup each EZO Stamp's initial configuration through Termite.. so that's when I'll set the NAMES and Addresses to differentiate the devices (eg. PMP1, PMP2, RTD1, RTD2, FLO1, FLO2). It's not documented, but the NAME function works over i2c just like UART. (Checked with Ephram and Jordan and they intend to maintain the NAME function for i2c in the EZO circuits).
Relays, PWM, AnalogIN boards, I'm staying with NCD.. even though they are a bit more expensive... it keeps me on the i2c bus and I'm comfortable with it. So far I find the 8channel relay board very reliable.