I'm not trying to dissuade you at all with moving forward with the Pi project, only trying to be realistic and point out potential issues you make come across along the way. It sounds like a fun project to me and if I wasn't over my head with other projects it would be one I would do as well.
If I were to do this type of project, knowing the issues that can occur with using an OS based controller, I would use it on a test tank with nothing living for at least 6 months to ensure there are no bugs that would cause things like an ATO to not function as expected, or heater, or any other critical piece to an aquarium. I have yet to find an OS that doesn't have occasional issues that require at least a reboot every so often. Unix, Linux, BSD, Windows, etc. If my movie freezes up 1/2 way through and I have to reboot the Pi (which takes a minute and hope no critical OS files were corrupted when it locked up), no big deal, but if it freezes up when the ATO kicks on and no one is around to fix it, it starts to become a big deal very quickly.
Going the Raspberry Pi route adds so much more complexity to doing simple tasks that to me it brings reliability into question. Can reliability issues be solved? More than likely, but the amount of time and programming to do so is beyond most people. For me, Arduino coding was easier to learn than BASIC since I knew some programming (not C++). It only took me a couple hours to pick it up. On the other hand, learning C++, that's not going to happen in a weekend for most people. Point being, it is not above most people to be able to figure out Arduino programming to update/troubleshoot a controller, but it is beyond most people to learn C++ to do the same.
For you zemuss, since you do know C++, that doesn't seem to be the case, so a Pi controller may be more up your ally and a lot more fun for you. I really do wish you all the success with the Pi project. I would love to see one working. :bigsmile:
If I were to do this type of project, knowing the issues that can occur with using an OS based controller, I would use it on a test tank with nothing living for at least 6 months to ensure there are no bugs that would cause things like an ATO to not function as expected, or heater, or any other critical piece to an aquarium. I have yet to find an OS that doesn't have occasional issues that require at least a reboot every so often. Unix, Linux, BSD, Windows, etc. If my movie freezes up 1/2 way through and I have to reboot the Pi (which takes a minute and hope no critical OS files were corrupted when it locked up), no big deal, but if it freezes up when the ATO kicks on and no one is around to fix it, it starts to become a big deal very quickly.
Going the Raspberry Pi route adds so much more complexity to doing simple tasks that to me it brings reliability into question. Can reliability issues be solved? More than likely, but the amount of time and programming to do so is beyond most people. For me, Arduino coding was easier to learn than BASIC since I knew some programming (not C++). It only took me a couple hours to pick it up. On the other hand, learning C++, that's not going to happen in a weekend for most people. Point being, it is not above most people to be able to figure out Arduino programming to update/troubleshoot a controller, but it is beyond most people to learn C++ to do the same.
For you zemuss, since you do know C++, that doesn't seem to be the case, so a Pi controller may be more up your ally and a lot more fun for you. I really do wish you all the success with the Pi project. I would love to see one working. :bigsmile: