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

[Ranjib]

Ive been away for awhile. Wondering if @Ranjib ever got it where steppers could be used for dosing? want to build a doser, but want the precision that a stepper would deliever.

Nope. But this is on my list, just didnt get the time.

 

[Ranjib]

Can anyone provide any details for getting ATO to display properly in grafana, I thought I had it working but it is not showing run time correctly. It shows when its run but always shows the same run time vs the actually run time.

Thanks...

Just specify the metric name, for example, my ato usage is emitted as ato_pico1_usage , where the ato name is pico1. You can skip the {job="pico1-app"} bit. I have 5 different things that is running ato, it is there to distinguish among them.

 

[Mwdsonny]

Nope. But this is on my list, just didnt get the time.

anything I can do to help? I have parts and can test code, Just dont know how to write code.

 

[bishoptf]

Just specify the metric name, for example, my ato usage is emitted as ato_pico1_usage , where the ato name is pico1. You can skip the {job="pico1-app"} bit. I have 5 different things that is running ato, it is there to distinguish among them.

Thanks yeah I understand that much the problem I am having is the scale I believe, I have it in seconds and looks like you are using milliseconds? I dunno something is not right since it always just shows my check frequency of 5 sec. I know the graph on the front page is correct showing how long it runs but not in prometheus and grafana. I'm on the older code so it could be something related to that but I have basically the same set up that you have above and its not that...

Here is a new panel with the defaults notice the always the 5 seconds, maybe I dont have grafana configured to scrape prometheus or prometheus set up correctly...what are you using for a scrape interval from grafana? I was using the default 15s, should that be something else?

Let me know what you think, I'm just trying to reproduce the graphs that are on the main dashboard. :)

 

[bishoptf]

Looks like it's a bug in the version that I am using which I believe is 3.3, but I changed the check frequency to 7 and the next time it topped of it registered 7 instead of the actually fill time.

I will look into upgrading to the latest version, just always hate to do it when things are running stable...

 

[bishoptf]

Updated to 4.1 and its reporting correctly the usage but it doesn't reset to 0 once it runs, the reading stays at the last value. I thought it would read the value and then reset to 0 like its doing on the ATO graph, I'm obviously missing something.

:)

Here is the journalctl entries...

Feb 09 12:55:57 octopi reef-pi[17454]: 2021/02/09 12:55:57 ato-subsystem: sensor: ato-dt  usage: 10
Feb 09 12:56:02 octopi reef-pi[17454]: 2021/02/09 12:56:02 ato-subsystem: sensor: ato-dt state: 1
Feb 09 12:56:02 octopi reef-pi[17454]: 2021/02/09 12:56:02 ato-subsystem: sensor: ato-dt  usage: 10
Feb 09 12:56:05 octopi reef-pi[17454]: 2021/02/09 12:56:05 API Request:'   GET /api/atos/3/usage' from: 10.99.99.146:52618
Feb 09 12:56:07 octopi reef-pi[17454]: 2021/02/09 12:56:07 ato-subsystem: sensor: ato-dt state: 1
Feb 09 12:56:07 octopi reef-pi[17454]: 2021/02/09 12:56:07 ato-subsystem: sensor: ato-dt  usage: 10
Feb 09 12:56:12 octopi reef-pi[17454]: 2021/02/09 12:56:12 ato-subsystem: sensor: ato-dt state: 1
Feb 09 12:56:12 octopi reef-pi[17454]: 2021/02/09 12:56:12 ato-subsystem: sensor: ato-dt  usage: 10
Feb 09 12:56:15 octopi reef-pi[17454]: 2021/02/09 12:56:15 API Request:'   GET /api/atos/3/usage' from: 10.99.99.146:52632
Feb 09 12:56:17 octopi reef-pi[17454]: 2021/02/09 12:56:17 ato-subsystem: sensor: ato-dt state: 1
Feb 09 12:56:17 octopi reef-pi[17454]: 2021/02/09 12:56:17 ato-subsystem: sensor: ato-dt  usage: 10
Feb 09 12:56:22 octopi reef-pi[17454]: 2021/02/09 12:56:22 ato-subsystem: sensor: ato-dt state: 1

Looks like at the top of the hour it reset to 0, scratching my head now since I am not sure how this is supposed to work.

 

[brian.badge]

So I am mostly guessing here based on limited research. The relay that won't turn off, but tries to may have
1. plates welded together
2. Broken spring
3. Too much residual voltage

Is there a way to diagnose?

I shut the controller down, wiggled some wires, and then rebooted. I an certain I didn't do anything, but now every relay works. I suspect something is going on that I don't understand. I am lost here and don't know what to do to get my relays working reliably....help. For now I will add my equipment again and test.

 

[GaryE]

Thanks, I've been meaning to put something together listing compatible lights and how to connect to PWM output. If you have more pics of it finished or anything special to remove to access those JST's but these are more than enough to get the job done.

I ended up removing the pot from the equation. Direct connect from the reef pi to the pen input on the lights.

One of the lights didn't play nicely with the pots in the mix.

 

[Ranjib]

I ended up removing the pot from the equation. Direct connect from the reef pi to the pen input on the lights.

One of the lights didn't play nicely with the pots in the mix.

i bet its some missing passives.. somewhere in the circuit. im not good at hunting those down.. but i strongly feel thats what it.. passives to filter out noise, aberration (capacitors, resistor etc)

 

[Ranjib]

Updated to 4.1 and its reporting correctly the usage but it doesn't reset to 0 once it runs, the reading stays at the last value. I thought it would read the value and then reset to 0 like its doing on the ATO graph, I'm obviously missing something.

:)

Here is the journalctl entries...

Feb 09 12:55:57 octopi reef-pi[17454]: 2021/02/09 12:55:57 ato-subsystem: sensor: ato-dt  usage: 10
Feb 09 12:56:02 octopi reef-pi[17454]: 2021/02/09 12:56:02 ato-subsystem: sensor: ato-dt state: 1
Feb 09 12:56:02 octopi reef-pi[17454]: 2021/02/09 12:56:02 ato-subsystem: sensor: ato-dt  usage: 10
Feb 09 12:56:05 octopi reef-pi[17454]: 2021/02/09 12:56:05 API Request:'   GET /api/atos/3/usage' from: 10.99.99.146:52618
Feb 09 12:56:07 octopi reef-pi[17454]: 2021/02/09 12:56:07 ato-subsystem: sensor: ato-dt state: 1
Feb 09 12:56:07 octopi reef-pi[17454]: 2021/02/09 12:56:07 ato-subsystem: sensor: ato-dt  usage: 10
Feb 09 12:56:12 octopi reef-pi[17454]: 2021/02/09 12:56:12 ato-subsystem: sensor: ato-dt state: 1
Feb 09 12:56:12 octopi reef-pi[17454]: 2021/02/09 12:56:12 ato-subsystem: sensor: ato-dt  usage: 10
Feb 09 12:56:15 octopi reef-pi[17454]: 2021/02/09 12:56:15 API Request:'   GET /api/atos/3/usage' from: 10.99.99.146:52632
Feb 09 12:56:17 octopi reef-pi[17454]: 2021/02/09 12:56:17 ato-subsystem: sensor: ato-dt state: 1
Feb 09 12:56:17 octopi reef-pi[17454]: 2021/02/09 12:56:17 ato-subsystem: sensor: ato-dt  usage: 10
Feb 09 12:56:22 octopi reef-pi[17454]: 2021/02/09 12:56:22 ato-subsystem: sensor: ato-dt state: 1

Looks like at the top of the hour it reset to 0, scratching my head now since I am not sure how this is supposed to work.

i changed the metrics emission code during 4.0 https://github.com/reef-pi/reef-pi/pull/1121 , so this is expected in all 4.0 installations,

 

[Ranjib]

i changed the metrics emission code during 4.0 https://github.com/reef-pi/reef-pi/pull/1121 , so this is expected in all 4.0 installations,

Just to explain furthers, this is as expected. there was a bug in 3.x , which is why you saw the change in 4.0 upgrade. The current graph is correct, as in it "charts hourly usage, aka pump run time", this metric is useful as the exact time you can see when the pump started (increments should reflect your check interval in seconds) and it will reset to 0 every hour. In long term (2-7 days) this should show the hourly pattern and its variation in seasons and help you set the alert threshold (which is in pump usage / hour).

 

[Ranjib]

I shut the controller down, wiggled some wires, and then rebooted. I an certain I didn't do anything, but now every relay works. I suspect something is going on that I don't understand. I am lost here and don't know what to do to get my relays working reliably....help. For now I will add my equipment again and test.

Just to reiterate, there was no errors in reef-pi log?

 

[Ranjib]

anything I can do to help? I have parts and can test code, Just dont know how to write code.

i mean, we have to do some design & coding work, and follow up testing/validation. The design work will involve at least settling on a common stepper driver (e.g. 8825??) for the standard build, the coding work i.e. HAL integration and any UI(driver??) work, and finally testing it out.

 

[brian.badge]

Just to reiterate, there was no errors in reef-pi log?

Correct no errors.

 

[brian.badge]

Correct no errors.

And I have a different relay stuck on. I came downstairs to find my sump lights on despite being turned off in the UI. When I manually turned it on then back off nothing happened. I have moved my sump light over to a mechanical timer just in case its causing the issue. Its a zet light LED and its plug converts ac to 24 v DC. I will restart and hope the relay starts working again.

 

[Ranjib]

And I have a different relay stuck on. I came downstairs to find my sump lights on despite being turned off in the UI. When I manually turned it on then back off nothing happened.

You probed the GPIO output at every junction till it connects to the relay input, and validated the voltages are as expect (if i recall correctly, it should be around 3.3v at GPIO on). This should help you isolate the problem at circuit vs relay itself.

 

[brian.badge]

And I have a different relay stuck on. I came downstairs to find my sump lights on despite being turned off in the UI. When I manually turned it on then back off nothing happened. I have moved my sump light over to a mechanical timer just in case its causing the issue. Its a zet light LED and its plug converts ac to 24 v DC. I will restart and hope the relay starts working again.

I think I know what is happening. Power off the reboot did nothing. Power off, tap the relay with a screw driver and reboot and it functions correctly. That suggests they are sticking due to arcing right? If that is the case what do I do?

 

[bishoptf]

Just to explain furthers, this is as expected. there was a bug in 3.x , which is why you saw the change in 4.0 upgrade. The current graph is correct, as in it "charts hourly usage, aka pump run time", this metric is useful as the exact time you can see when the pump started (increments should reflect your check interval in seconds) and it will reset to 0 every hour. In long term (2-7 days) this should show the hourly pattern and its variation in seasons and help you set the alert threshold (which is in pump usage / hour).

Thanks @Ranjib for the quick reply that is exactly what I am seeing, I knew it had to be coded since it reset on the hour. I will update my other reefpi installation to the latest, the upgrade so far was painless and everything appears to be working fine. My goal is to replicate all the graphs with grafana and just use it to monitor vs the dashboard, that way I will free up resources on the pi.

One more question, I am using a dosing module but do not see anything on prometheus to allow to monitor the dosing module, is that correct or did I miss it?

Thanks :)

 

[GaryE]

i bet its some missing passives.. somewhere in the circuit. im not good at hunting those down.. but i strongly feel thats what it.. passives to filter out noise, aberration (capacitors, resistor etc)

Nope. After I removed the pots, I noticed the blue channel on that light wasn't dimming. Tested everything and came down to something in the driver. Had power, ground and pwm signal all the way to the driver.

Traced the pwm pin from the jst on the driver board to something that looked suspiciously like a smoked AO3400 mosfet. Just so happened to have a spare on my desk.

May not be that exact mosfet, but good enough. It's working correctly now.

Well, more like the d@mned thing is off like it should be for this time of night. We'll see tomorrow.. ;-)

 

[babrooks]

Ive been away for awhile. Wondering if @Ranjib ever got it where steppers could be used for dosing? want to build a doser, but want the precision that a stepper would deliever.

It is possible to rig up an Arduino board to read the doser signal from reef-pi and then run stepper motor drivers. This is what I did on my tank for dosing and AWC with DIY peristaltic pumps. You can read about it on my build thread.