it opens all of them then when a pour is started it closes the ones not pouringknow what valve to open After I tag a card
it opens all of them then when a pour is started it closes the ones not pouringknow what valve to open After I tag a card
it opens all of them then when a pour is started it closes the ones not pouring
off the back, no it seems like you enabled debugging so it should give you the error after 1Wire Temperature:but I don’t see any more details in the log. It works fine for 5 to 10 min then bombs until I restart flow monitor, Any suggestions ?
1Wire Temperature: list index out of range | 1 | |
2021-01-10 21:25:39 | FlowMonitor | I |
Can you tell me what files you have in the /sys/bus/w1/devices/28*/w1_slave directories (28* indicates directories that start with 28)?Ok here is the error log message I get. i haven’t put my system in the keezer yet so the temps are in the 75 degree range. Would that cause an out of range scenario?
he other thing that will help me is if you add the following lines to 746 of FlowMonitor.py
exc_type, exc_value, exc_traceback = sys.exc_info()
traceback.print_tb(exc_traceback, limit=1, file=sys.stdout)
Can you tell me what files you have in the /sys/bus/w1/devices/28*/w1_slave directories (28* indicates directories that start with 28)?
Looks like the same code that I tested with but I don't see the stack trace printed out... wondering if its not outputting to the file like I did for meHere is the code I am running
Looks like the system detected 1 temp probe 3c01d075b9ec/sys/bus/w1/devices/28-3c01d075b9ec
Can you post the file?
/sys/bus/w1/devices/28-3c01d075b9ec/w1_slave
Thanks, I setup my test system with that info, but it didn't break....$ cat w1_slave
If you could make htat change
That's not intuitive - I can see using a stronger pull-up (lower resistance value) but not the other way around.I did change out my PU resistor from 4.7K to 10K to see if that would help and interesting in that it was running for a long time without a failure.
That's not intuitive - I can see using a stronger pull-up (lower resistance value) but not the other way around.
Ill keep it running and report back
you need to remove the trace_back.print_tb line. you removed the definition for exc_tracebackPerhaps I didnt update the code properlywith that second error message.
did you make sure the config.py has debug enabled?d23029 today but I don’t get any further detail in /var/log/rpints.log.
did you make sure the config.py has debug enabled?
config['flowmon.debug' ] = True
Or change the debug lines (748-749) to log in FlowMonitor.py?
restart just the flomonitor service to load new codeDo I need to completely restart the pi machine or just restart the flow monitor to loan the new code?
restart just the flomonitor service to load new code
dont get further error records in the /var/log/rpints.log file
that's what I needed. It appears the file is empty on some of the reads, probably when the probe is updating itI got the following error
Traceback (most recent call last): File "/var/www/html/python/FlowMonitor.py", line 727, in run temp = self.get_temp(device) File "/var/www/html/python/FlowMonitor.py", line 693, in get_temp status = lines[0][-4:-1] IndexError: list index out of range
I have committed that to github
curl -L install.rpints.com | sudo bash
I am already powering off a separate power supply based on other recommendations in this thread, I am also on my 3rd USB cable. I can try that again.
Any suggestions on proven brands of USB cables?
if you restart the flowmon service without changing anything, does it start working? Im running into something similar with mine where the shield will just stop, I haven't tracked it down yet.Is there anything else that I can try? It is basically not functional like this.
The pour for python is in /python/FlowMonitor.py ~line 337execfile('send.py TAP Ounces') to run the send.py script using the two arguments, TAP and ounces
I am a noob when it comes to python. Any help in pointing me to where i could include this command in the rpints code an what are the variable names for the tap and the volumn of the pour would be really helpful.
let me test something, I think it may have to do with how I subtract the amount from the keg, I don't compare keg unit to pour unit. So if the keg unit is Imperial but pours are in Metric then this would happenconversion bug
Yes please If you don't fix it though it won't be a huge issue. A good opportunity to learn imperial units I am back at my hometown at the moment as my University is closed down due to Covid. The kegerator is back at the apartment by the Uni so i won't be able to help you troubleshoot at the moment though. To replicate the issue consistently i have found you need to use metric units, make a pour to calibrate the amount poured and after that the keg and pour amount will be different.let me test something, I think it may have to do with how I subtract the amount from the keg, I don't compare keg unit to pour unit. So if the keg unit is Imperial but pours are in Metric then this would happen
View attachment 714324
if you restart the flowmon service without changing anything, does it start working? Im running into something similar with mine where the shield will just stop, I haven't tracked it down yet.
What is the log before the restart? mine usually shows the last status check time. Im working to look at the serial log to see if the Shield is actually doing anything or if the python is not responding.Log after restarting RP or restarting flowmon service
I want to put in a timer that says if the Shield doesn't send anything in x minutes then restart it.It's too bad that IF this situation happens, to just restart the flowmon service automatically.
What is the log before the restart? mine usually shows the last status check time. Im working to look at the serial log to see if the Shield is actually doing anything or if the python is not responding.
I want to put in a timer that says if the Shield doesn't send anything in x minutes then restart it.
I believe that the Shield should always check the pi for a status even if it is not used (it really is for RFID but if RFID isn't configured I think it still checks)
Yep that was it. I fixed the issue now (its in github if you update)To replicate the issue consistently i have found you need to use metric units, make a pour to calibrate the amount poured and after that the keg and pour amount will be different.
FlowMonitor D Sending Status;N;-1;0;0;0;0;0;0;| 95472021-01-14 12:19:58 PintDispatch D valve update: RPU:VALVE:0=0 1
..
2021-01-14 12:17:46 PintDispatch D valve update: RPU:VALVE:4=0 1
2021-01-14 12:16:11 FlowMonitor D Sending Status;N;-1;0;0;0;0;0;0;| 9547
Enter your email address to join: