bishoptf
Valuable Member
Yeah this is a linux box also, I was looking through the code and started zoning out, context.go and I see the newDriver being called out but it's not finding something it needs, oh well.
reef-pi :: An opensource reef tank controller based on Raspberry Pi.
- Thread starter Ranjib
- Start date
-
- Tags
- controller raspberry-pi
- Tagged users Ranjib
Yeah this is a linux box also, I was looking through the code and started zoning out, context.go and I see the newDriver being called out but it's not finding something it needs, oh well.
bishoptf
Valuable Member
It's not working in a linux environment, I'm looking at the context.go code but its not apparent as to what is missing, I have the dev files installed so it's something else.
So just curious aare you guys trying to make the latest from github? Which version are you trying to make, pi-zero or pi? I can try to see if I can make, I used to have a build environment set up but need to poke at it, just wanted to understand what you are trying to make.
There was a minor issue with the Atlas pH driver when calibrating, Atlas could cope with it by my circuit code couldn't so was looking to make sure everything was good. Sounds like @GaryE has a package, now I'm trying to convince him to send me a copy.
bishoptf
Valuable Member
There was a minor issue with the Atlas pH driver when calibrating, Atlas could cope with it by my circuit code couldn't so was looking to make sure everything was good. Sounds like @GaryE has a package, now I'm trying to convince him to send me a copy.
I was going to offer the same but it's not building on linux and it's not clear what is the issue, something to do with the new sound driver. When I get it working I can also build something if needed, just not sure what the current issue is.
bishoptf
Valuable Member
Thanks for the offer, @GaryE was kind enough to send me the package, what a superstar.
Sure no problem but we still need to figure out why its not compiling on a linux distro, something is needed and its breaking pulling in the oto stuff even though libasound2-dev is installed, I think it has to do with the linker but still looking.
GaryE
Well-Known Member
I saw something about alsa, I don't think that's it though.
OP
OP
probably you have deleted a driver without deleting the corresponding connectors. This breaks UI. We are in process of fixing it: https://github.com/reef-pi/reef-pi/issues/1022So... Anyone familiar with this error while setting up a pH probe? I've never seen it before.
It's on the connector tab in configuration. It's a setup using @Michael Lane 's pH board & it's saying there's no driver for pin 0.
I have him checking to make sure his driver is set up correctly at the right address & verifying the pH probe is being seen with i2cdetect, so *hopefully* that process may give some answers. But I'd never seen this error before & thought some people here may be able to weigh in.
github closed this for stale reasons. i;ll reopen it, we'll get it fixed soonish.
OP
OP
What linux distro you are using? have you installed the audio library?
OP
OP
Just FYI, i use ubuntu and macbook pro, and able to build on both platforms. I cant do cross compile (building pi binaries on laptop or desktop), but normal development flows work.,
OP
OP
Could be, but it should work as long as you dont do cross compile. i.e make go should work, make pi will not work in non-pi setup.
We should move the development discussions in slack or some place else. Its developer onboarding related and little orthogonal to the original thread.
Last edited:
bishoptf
Valuable Member
Sorry about cluttering up the thread, I thought about this last night when going to bed, it's the cross compiling. Make is working, make pi is not. I so an old issue on the Oto stuff that referenced cross compiling, so if you need to make for a pi it needs to be on a pi. Kind of a bummer since my linux box is a whole lot faster, I guess for development and testing you can make and test on linux etc, but when needed to make for a pi it needs to be on a pi. Has it always been that way, I could have sworn in the 2.x days I could make pi on linux, but maybe not.
Thanks for clearing that up, at least for my my bench pc is using Arch.
bishoptf
Valuable Member
I have a question about multiple heaters and temp probes, I have searched but couldnt find what I think is the answer. I am going to run 2 smaller heaters vs one large heater. I do not think one smaller heater will be able if stuck to raise the temp to dangerous levels but will still have reef-pi monitor the temp. When you have more than one heater and more than one temp probe, if the temp rises how do you know which heater is malfunctioning. The scenario is I am using reef-pi as my safety net and using the internal thermostat of the heater, if the temp reaches a certain point I won't reef-pi to turn off the heater. If I have 2 heaters I assume I will have to disable both heaters since I am not sure how to know which heater is mis-behaving.
Hope this makes sense, TLDR, if you have a multiple heater setup how do you distinguish between the two heaters when one is stuck on.
Thanks
PS. right now both of the heaters are the preset kind, I guess another option would be to have one that I can set higher than the other and just use it as a back up, that way I would know which heater is running, need to think this through...
Hope this makes sense, TLDR, if you have a multiple heater setup how do you distinguish between the two heaters when one is stuck on.
Thanks
PS. right now both of the heaters are the preset kind, I guess another option would be to have one that I can set higher than the other and just use it as a back up, that way I would know which heater is running, need to think this through...
Last edited:
I have a question about multiple heaters and temp probes, I have searched but couldnt find what I think is the answer. I am going to run 2 smaller heaters vs one large heater. I do not think one smaller heater will be able if stuck to raise the temp to dangerous levels but will still have reef-pi monitor the temp. When you have more than one heater and more than one temp probe, if the temp rises how do you know which heater is malfunctioning. The scenario is I am using reef-pi as my safety net and using the internal thermostat of the heater, if the temp reaches a certain point I won't reef-pi to turn off the heater. If I have 2 heaters I assume I will have to disable both heaters since I am not sure how to know which heater is mis-behaving.
Hope this makes sense, TLDR, if you have a multiple heater setup how do you distinguish between the two heaters when one is stuck on.
Thanks
You could attach additional temp probes directly to the heaters to see which one is on while the temp is high. Or get more sophisticated with power monitoring if you can.
Des Westcott
Well-Known Member
I have a question about multiple heaters and temp probes, I have searched but couldnt find what I think is the answer. I am going to run 2 smaller heaters vs one large heater. I do not think one smaller heater will be able if stuck to raise the temp to dangerous levels but will still have reef-pi monitor the temp. When you have more than one heater and more than one temp probe, if the temp rises how do you know which heater is malfunctioning. The scenario is I am using reef-pi as my safety net and using the internal thermostat of the heater, if the temp reaches a certain point I won't reef-pi to turn off the heater. If I have 2 heaters I assume I will have to disable both heaters since I am not sure how to know which heater is mis-behaving.
Hope this makes sense, TLDR, if you have a multiple heater setup how do you distinguish between the two heaters when one is stuck on.
Thanks
PS. right now both of the heaters are the preset kind, I guess another option would be to have one that I can set higher than the other and just use it as a back up, that way I would know which heater is running, need to think this through...
I have also been comnemplating this as I run 2 x heaters. My solution which I have tested in concept, but still need to implement is to use the one temp probe and have each heater on it's own temp control. My plan is to have one heater with a setpoint of 25 degrees and the second with a setpoint of 24.5 degrees. The thinking being that if the temp is dropping slowly, one heater should catch it and heat the water back up slowly. If the ambient is very cold, the temp should drop to the 24.5 point despite the first heater and the second will kick in and do its job. The main benefit to this is that I can have separate alerts on each heater and monitor the usage on the graph. Maybe we could ask for usage alerts on temp like ATO has?
Des
bishoptf
Valuable Member
Yeah there are lots of ways to do this, I am more concerned with the failing in a stuck on mode, I think that is the more common failure mode and it bakes the tank. I think over heating is probably worse than under heating but that is just my assumption. I think you have a good idea with tracking run times of each heater, you could set a threshold and set it for each heater that if out side of that run time its turned off. Then one issue I see is how do you tie a heater to a single temp probe, I can have multiple temp probes but how do you know that a heater is misbehaving, well you know if the temp is hi or low but how do you know which heater it is. One thought is it doesnt matter and I turn both off, or I turn one off,whether its the right one or not is irrelevant since my heaters are undersized it won't bake the tank.
That is what I think I am going to go with, I will have 2 undersize heaters and set one temp to turn off one unit if it goes over 80 degrees and if the tempo keeps rising above 81 degrees I will turn the second unit off and alert on both of them. I will still have to figure out which unit is really busted but this is my current thinking right now. With the size of the units that I am using right now one unit in the winter will probably not even keep it at 78deg, it will take both working to do that, that is at least my thinking right now...
Des Westcott
Well-Known Member
Then one issue I see is how do you tie a heater to a single temp probe, I can have multiple temp probes but how do you know that a heater is misbehaving, well you know if the temp is hi or low but how do you know which heater it is.
From what I've tested. you can have multiple individual "Temp Controls" all using the same sensor. So you can have 2 "Temperature Control" and each can have its own parameters, alerts and control its own equipment but can be controlled by the same one temp probe.
bishoptf
Valuable Member
Yup understand that part but the problem is how do you know which heater is baking the tank, if I have 2 or more heaters and one probe it only sees that the tank is reaching 81 degrees, how can you know which heater is the one stuck on. I mean you can tell since it's on but not sure you have that logic in reef-pi, if I have 2 heaters and the temp reaches 80deg see which heater is on and turn it off. I need to play with it some more and im sure I've made things lots more complicated but with multiple heaters I am not sure how you identify a mis-behaving heater vs the one that is working properly.
Clear as mud
Neat graph of three preset heaters....
Des Westcott
Well-Known Member
Yup understand that part but the problem is how do you know which heater is baking the tank, if I have 2 or more heaters and one probe it only sees that the tank is reaching 81 degrees, how can you know which heater is the one stuck on. I mean you can tell since it's on but not sure you have that logic in reef-pi, if I have 2 heaters and the temp reaches 80deg see which heater is on and turn it off. I need to play with it some more and im sure I've made things lots more complicated but with multiple heaters I am not sure how you identify a mis-behaving heater vs the one that is working properly.
Clear as mud
It seems that this is a good case for letting reef-pi control the heater and having the heater's internal thermostat as the "high safety". You could have a heater with the contacts welded closed and never know until reef-pi has a brain-fart. By the same argument, you could have a 10 year old heater that the thermostat has never been used.
Yes, and at that moment you wish you had a backup temp sensor for if the one is failing.... Is that possible to have 2 temp sensors (1 to control and 1 as failsafe) to control the heater(s)? Or is that overkill?
Similar threads
- Shipping Available
