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.
In theory yes...that would eliminate spikes thru the mains
Is it an ac or dc pump?
Is the pump leaking voltage into the water?It's AC. It's also very old. I got it used 3 years ago & it already looked pretty well-worn then. I've already got a backup on standby, so I may just go ahead & switch it out.
It's AC. It's also very old. I got it used 3 years ago & it already looked pretty well-worn then. I've already got a backup on standby, so I may just go ahead & switch it out.
Yea I am having a similar issue with trying to show my light control on the dashboard. I can not get it to save ans show up, just the health check will show.Anyone on 3.1 having issues with the Dashboard and displaying temp readings? Was working fine in 3.0. I did a clean install of 3.1 on a new SD card.
Every time I add current or historical Temp readings to dashboard, nothing shows up...just a blank page. Health check seems to display current and historical info fine. Temp does not. Going directly to temp probes in Temperature tab, shows correct reading and graph.
Yea I am having a similar issue with trying to show my light control on the dashboard. I can not get it to save ans show up, just the health check will show.
Is the pump leaking voltage into the water?
It may not be enough to caise a shock but only a couple of volts could cause this.
It wouldnt take much because ph is read in millivolts.
Glad you sorted your issue out. What still doesn't make sense to me though is why you would experience spikes, when the return pump would have been leaking voltage into the tank water 24/7.It looks like this was the issue. I swapped out the pump & now everything is smooth sailing. It actually fixed the calibration bug I was encountering too, where it kept telling me to enter a valid value. Thankfully, with the pump being in my sump, I didn't zap any fish over the last few years!
Since the spike is coinciding with the return pump it is likely EMI (electromagnetic interference) created by the current draw of the pump (right hand rule - field is inducing into your pH signal). A few posts above I recommended installation of ferrite cores/beads on current drawing devices. These ferrite cores act as filters to the noise generated. Other options include use of single pole filters which use capacitors or inductors connected to ground at the connector.
Another option, which you "kinda" went after was shielding the pH cable. However, you need the shield to be grounded. When you wrapped the pH cord in aluminum you created an antenna (some people call it the pigtail effect). The best option is to use a shielded cable that is grounded 360 deg to the housing like the image below. The housing is then grounded to the connector and common circuit ground at the plug.
How would you suggest using the ferrite core like you suggested above?
Anyone on 3.1 having issues with the Dashboard and displaying temp readings? Was working fine in 3.0. I did a clean install of 3.1 on a new SD card.
Every time I add current or historical Temp readings to dashboard, nothing shows up...just a blank page. Health check seems to display current and historical info fine. Temp does not. Going directly to temp probes in Temperature tab, shows correct reading and graph.
How would you suggest using the ferrite core like you suggested above?
Scheiber is correct. Simply buy the clamp on cores and attach them anywhere on the cable. The device is basically a magnet that focus the interference to the ferrite core and disappates heat to a ceramic core.
The practice of "wrapping" the cable is from the use of ferrite rings. By wrapping on the ferrite ring you create an inductor that creates impedance or resistance to the interference. No need to wrap on a clamp.
the adafruit io error likely indicate a temp or ph or ato name has space in it (that causes wrong feed name), the ph driver error is something i have experienced as well. Its either another electrical device interferring or some issues with driver / code. I have never seen it persistently in a stable build.I just noticed the amount of errors in my reef-pi dashboard and decided to check them out. I normally ignore them because I don't understand what the majority of them mean and I can virtually never fix any of them LOL.
But I noticed quite a few of them were about an invalid url for AIO. AIO is set up and seems to be working just fine. Curious why it should be generating errors.
Second I noticed that there are occasional errors related to pH. I'm currently trying to see if them relate to the anomalous reading I get occasionally.