Long-time lurker on the forums, and I recently got my R7L w/ EOS (ozone)/CP from a great and knowledgeable local dealer.
I know I could easily get pretty much any SWCG unit and drape it over, but I'm an engineer and perfectionist, and that's not my style.
I'd like to get something hardwired/hidden/in-line -- looking at ControlOMatic (not sure yet on SmarterSpa vs ChlorMaker -- sensor vs timer operation), and it should be easy enough to install one right after the CP and have chlorine generation in the perfect place.
Here's my conundrum:
With an in-line system there must not be chlorine generation in non-moving water. Hydrogen is a byproduct of SWCG and of course is dangerous in high concentrations, and chlorine itself as I understand it is pretty corrosive and generally bad in higher concentrations as well. So I need to make sure the SWCG power is only on when there's flowing water (CP on). I can do this easily enough with a PP1 AMP splitter or similar, but what I'd really love to do is have CP run 24/7, and have ozone only run during filter cycles. I know I can set a 24/7 filtration cycle, which will run both CP and ozone, but running ozone 24/7 is excessive, it'll wear out the CD ozone unit much more quickly, and it'll constantly eat all my FC, making it nearly impossible to maintain a residual without running the SWCG 24/7 (prematurely wearing out that unit out too).
If I could access the field programming options on the Gecko as outlined in the Start-up guide (in.yt / in.ye / in.yj — GeckoDocs) I could have a perfect, clean setup, but BF seems to have this locked out, and BF tech support either has no idea what I'm talking about or just won't tell me :-\
My current best ideas are:
1. Use PP1 or similar to tie SWCG power to CP power. I don't really like this, as CP comes on at random times, not just filtration cycles. With SWCG only being on with CP I will only be able to monitor/adjust its settings when the CP is on, which is inconvenient.
3. Find a constant power source in the spa pack and tie both CP and SWCG to this. This might be a viable option as well, but I did not see the constant 120v AMP output referenced in the BF/Gecko manual when I was in there for initial hookup. But I'll give it another look. This would be the only scenario I could use a sensor-based SWCG, which is attractive to me, because I could theoretically keep a very very low chlorine residual since I have powerful/effective ozone with EOS combined with mineral sanitizer.
Sorry for the long read, if you read it. I would be forever grateful if you would give me any input.
I know I could easily get pretty much any SWCG unit and drape it over, but I'm an engineer and perfectionist, and that's not my style.
I'd like to get something hardwired/hidden/in-line -- looking at ControlOMatic (not sure yet on SmarterSpa vs ChlorMaker -- sensor vs timer operation), and it should be easy enough to install one right after the CP and have chlorine generation in the perfect place.
Here's my conundrum:
With an in-line system there must not be chlorine generation in non-moving water. Hydrogen is a byproduct of SWCG and of course is dangerous in high concentrations, and chlorine itself as I understand it is pretty corrosive and generally bad in higher concentrations as well. So I need to make sure the SWCG power is only on when there's flowing water (CP on). I can do this easily enough with a PP1 AMP splitter or similar, but what I'd really love to do is have CP run 24/7, and have ozone only run during filter cycles. I know I can set a 24/7 filtration cycle, which will run both CP and ozone, but running ozone 24/7 is excessive, it'll wear out the CD ozone unit much more quickly, and it'll constantly eat all my FC, making it nearly impossible to maintain a residual without running the SWCG 24/7 (prematurely wearing out that unit out too).
If I could access the field programming options on the Gecko as outlined in the Start-up guide (in.yt / in.ye / in.yj — GeckoDocs) I could have a perfect, clean setup, but BF seems to have this locked out, and BF tech support either has no idea what I'm talking about or just won't tell me :-\
My current best ideas are:
1. Use PP1 or similar to tie SWCG power to CP power. I don't really like this, as CP comes on at random times, not just filtration cycles. With SWCG only being on with CP I will only be able to monitor/adjust its settings when the CP is on, which is inconvenient.
- If I go with a timer-based SWCG I'm going to get chlorine levels all over the place. Every time CP turns on SWCG will start a production cycle, which will be every filtration cycle, plus every 30 minutes for its heat check, plus whenever it's heating/cooling. Wildly unpredictable chlorine generation.
- If I go with a sensor-based SWCG I'm going to have the opposite. CP/SWCG turns on, and when chlorine is present SWCG will do nothing except monitor. After awhile chlorine level drops below threshold, SWCG starts producing. CP will turn off whenever it wants, and subsequently SWCG will turn off, very likely before it can complete its chlorine generation.
3. Find a constant power source in the spa pack and tie both CP and SWCG to this. This might be a viable option as well, but I did not see the constant 120v AMP output referenced in the BF/Gecko manual when I was in there for initial hookup. But I'll give it another look. This would be the only scenario I could use a sensor-based SWCG, which is attractive to me, because I could theoretically keep a very very low chlorine residual since I have powerful/effective ozone with EOS combined with mineral sanitizer.
Sorry for the long read, if you read it. I would be forever grateful if you would give me any input.
Last edited by a moderator: