Dirt Diggler's Reef-pi Build

[DirtDiggler2823]

Agree. Pico board was deliberately simplistic to give best bang from a single pi zero, and aimed to completely automate a pico reef :-) . I think it was a good decision since even with pico it took more than a year to sort out everything (note: ph driver is still not available in stable release yet). We do had discussion around more beefier, feature rich system, but we wanted to iterate with small setup first. I also wanted to understand the pros and cons of clustering multiple independent controller vs having a single powerful one.

It works just fine with a pi3b

 

[DirtDiggler2823]

@Ranjib Memory usage has been strange since upgrading and adding the pH probe. Today marked the strangest spike yet. See below

 

[DirtDiggler2823]

@Ranjib , for the most part, 3.0 is stable, but there is a lot of resource usage. I've been up to 45% of memory used up before rebooting. I've had the Web Interface lag when the memory usage gets around that level. Just wanted to provide an update on how the build is performing. Other than the memory usage, I'm pleased with the results.

 

[Ranjib]

@Ranjib , for the most part, 3.0 is stable, but there is a lot of resource usage. I've been up to 45% of memory used up before rebooting. I've had the Web Interface lag when the memory usage gets around that level. Just wanted to provide an update on how the build is performing. Other than the memory usage, I'm pleased with the results.

Thank you for reporting back the stats. I'll keep an watch. I am running couple of 3.0 builds without encountering any serious performance issues. I'll check my 3.0 builds resource usage graphs and post back in the main thread.

I am in the process of wrapping up the pwm profile features. After that, I'll focus on the UI part so that the 3.0 features are usable by others. Next, my focus will be performance issues and documentation.