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

1549578603932.jpg
Question...I have a panel mount DC jack and a terminal block DC jack for the pico board. I know the center pin goes to the positive terminal. Do I solder the other 2 together and to the negative?
 
1549578603932.jpg
Question...I have a panel mount DC jack and a terminal block DC jack for the pico board. I know the center pin goes to the positive terminal. Do I solder the other 2 together and to the negative?

Yes, though when a cable is inserted only one makes contact with the outer sleeve (assuming this is a switched contact)
 
To be honest I always plug in the other side and verify which pins go to which contact. My guess only one is needed for the shell ground.
Same here :0) .
 
I have a small question if you all don’t mind. Reef-pi reports temperature to four decimal places, but the sensor only has a resolution of 0.0625°C, which converts to 0.1125°F. If reef-pi could round the temp data to .1°F (one decimal place) there would be no loss of resolution, and the graphs would be easer to read. Any thoughts on this?
 
I have a small question if you all don’t mind. Reef-pi reports temperature to four decimal places, but the sensor only has a resolution of 0.0625°C, which converts to 0.1125°F. If reef-pi could round the temp data to .1°F (one decimal place) there would be no loss of resolution, and the graphs would be easer to read. Any thoughts on this?
The historical values are hourly average, hence can be of higher precision (like the average of 45.2 and 45.3 is 45.25) than the actual readings. Though I have seen couple of time higher precision in current readings due a glitch. If you are experiencing that, let us know, its a bug.
 
i should probably also call out that its a minor UX bug that should not impact any controller behavior.
 
The historical values are hourly average, hence can be of higher precision (like the average of 45.2 and 45.3 is 45.25) than the actual readings. Though I have seen couple of time higher precision in current readings due a glitch. If you are experiencing that, let us know, its a bug.
I have this issue on current temperature display. Right now I am getting 4 decimal display. I have seen more. I am running version 2.1 so if it was fixed after this than it is my fault for not upgrading.
 
So I left my ATO switch in the on position all last night and can see where PI shut it off after the selected amount of time but then it came back on again every hour after that for the duration of the time between when it activated and my alert time. Is this intentional? I was under the impression that the alert would disable it until I worked on it. It appears it disables for 1 hour and then reenables the device. My primary concern here is if I'm out of town and the switch fails in the on position every hour it'll turn on my pump and run it for the duration I selected and eventually overflow my sump.
 
I changed my host name and rebooted and now none of my temperature sensors are showing up.
My temps are still on my dashboard and being read properly but I am being spammed with email alerts.
If I try and add a new temperature I can't because the sensors aren't showing anymore.

temperror2.PNG


temperror.PNG


***EDIT- I tried to reboot but it didn't work so I powered off and back on and all my sensors are working as they should be.
 
Last edited:
I changed my host name and rebooted and now none of my temperature sensors are showing up.
My temps are still on my dashboard and being read properly but I am being spammed with email alerts.
If I try and add a new temperature I can't because the sensors aren't showing anymore.

temperror2.PNG


temperror.PNG


***EDIT- I tried to reboot but it didn't work so I powered off and back on and all my sensors are working as they should be.
I hear you. I dont have anything immediately planned, but when I start working on temperature calibration (after ph driver is finished), I may touch upon this. I think if we use a moving average of some sort that will eliminate those cases where ds18b20 gives bad data in the very beginning. As for this particular case, do you think setting the limit on alerts (throttle setting under telemetry) will help? I'll keep noting down these signals so that I can attack them collectively (as many as I can) when I work on that part.
 
Thank you very much for your response. I do not know if it is a glitch, but my temperature graph is out to 4 decimal places
IMG_0019.JPG
. I am running version 2.2 on a Pi Zero W.
Some of this can also happen due to celsius to fahrenheit conversion logic.

Do you all think two decimal precision is enough? I personally think so. If we all agree I can make that a standard thing across all reef-pi metrics.
 
Some of this can also happen due to celsius to fahrenheit conversion logic.

Do you all think two decimal precision is enough? I personally think so. If we all agree I can make that a standard thing across all reef-pi metrics.
I think 1 digit is enough. The resolution of the sensor is 0.11 F. Showing precision beyond the resolution might make someone feel good but it has no meaning.
 
The specs for this state it's for panels up to 0.075in (2mm). This is gonna be a tough nut to crack. I could countersink the hole, but it would need to be done by hand, as there isn't enough room for my drill to get into where it needs to be.
 

TOP 10 Trending Threads

ARE YOU READY TO CONFESS TO CRAZIEST, DUMBEST, FUNNIEST THING YOU’VE EVER DONE IN REEFING?

  • Yeah, I'll confess! (Share your story in the comments!)

    Votes: 26 61.9%
  • Nah, I'll keep mine a secret...(Don't be like that, share with the class!)

    Votes: 16 38.1%
Back
Top
Home
Post thread…
Market
What's new