In your /home/brewpi/logs/stdout.txt there should be a line with the firmware information when the script starts.That's possible. How can I tell?
In your /home/brewpi/logs/stdout.txt there should be a line with the firmware information when the script starts.That's possible. How can I tell?
Issue the command:Yep looks like I am. v0.2.13 How do I roll it back?
sudo /home/brewpi/utils/doFlash.sh --shield
I currently have a Arduino Uno with a revC shield on port. What firmware version do you recommend?Issue the command:sudo /home/brewpi/utils/doFlash.sh --shield
Pick the appropriate one for your setup.
Have a look at the logs:I have gone through the installation and have the web interface up and running but am stuck with "Script starting up."
the controller reads all my temperature sensors fine, but am just hung up with the script.
/home/brewpi/logs/stdout.txt
& /home/brewpi/logs/stderr.txt
That one is appropriate if you are not using Glycol, or an I2C LED.I currently have a Arduino Uno with a revC shield on port. What firmware version do you recommend?
2023-08-19 08:47:45 [N] Starting 'My BrewPi Remix Run.'Have a look at the logs:/home/brewpi/logs/stdout.txt
&/home/brewpi/logs/stderr.txt
That one is appropriate if you are not using Glycol, or an I2C LED.
That looks okay - anything in the java log on the browser?2023-08-19 08:47:45 [N] Starting 'My BrewPi Remix Run.'
Nope, the console is all clear.That looks okay - anything in the java log on the browser?
sudo systemctl status brewpi
ya, checked that as well as running in incognito. Here is the result of checking the scriptUhhhhhh.... shift-refresh?
Also, check to make sure the script is actually running:sudo systemctl status brewpi
sudo systemctl stop brewpi
sudo /home/brewpi/utils/doPerms.sh
sudo systemctl start brewpi
Still stuck with "Script Starting Up" Ill try tinkering and doing a fresh install with another Pi. Thanks for your help!Well, the "universal first aid" would be:
Optionally, and maybe even recommended, reboot after that.Bash:sudo systemctl stop brewpi sudo /home/brewpi/utils/doPerms.sh sudo systemctl start brewpi
That's very weird ... it looks like the query is not working. A clean install may just fix it all. If not, let me know and we can figure it out.Still stuck with "Script Starting Up" Ill try tinkering and doing a fresh install with another Pi. Thanks for your help!
That's very weird ... it looks like the query is not working. A clean install may just fix it all. If not, let me know and we can figure it out.
I see two issues here:C:{"tempFormat":"F","heater1_kp":10.00,"heater1_ti":600,"heater1_td":60,"heater1_infilt":1,"heater1_dfilt":4,"heater2_kp":10.00,"heater2_ti":600,"heater2_td":60,"heater2_infilt":1,"heater2_dfiltnull,"minimum":-10.0000,"maximum":10.0000},"inputError":null,"Kp":2.0000,"Ti":7200,"Td":1200,"p":0.0000,"i":0.0000,"d":0.0000,"actuatorIsNegative":false}]}
heater2_dfilt
is improper. "heater2_dfiltnull,
should be "heater2_dfilt":null,
.I see revc is the correct type for me what about the release to match the revc?Have a look at the logs:/home/brewpi/logs/stdout.txt
&/home/brewpi/logs/stderr.txt
That one is appropriate if you are not using Glycol, or an I2C LED.
0.2.13 would be it. There are very few material changes, but using the latest/stable version always makes sense.I see revc is the correct type for me what about the release to match the revc?
Hi,0.2.13 would be it. There are very few material changes, but using the latest/stable version always makes sense.
Its a pepsi fridge the cooling fins are in the top with a fan to direct the cool air down into the chamber. The sensor is on the back all in the middle.My best guess without seeing the graph (and that would help) is that your temp sensor is right next to the cooling plate/fins. Do you have a small fan in there? If not, you might try adding one.
Would you please zoom into the chart (you can click-drag on the chart to do so) to a smaller area like this?
View attachment 828070
.... be sure to include the bottom part.
It seems like either the PID is wound up, or the script may be crashing/restarting (most likely.) Have you looked through the logs to see if there's anything there?So far the cooling is still short cycling with the fridge sensor in water. It turns on for a few seconds then waiting for peak until the next short cooling cycle.
In the stdout and stderr logs no errors. I switched back to the fridge sensor where it was in the fridge and changed the setting to fridge consistent It holds that set temp with no issues.It seems like either the PID is wound up, or the script may be crashing/restarting (most likely.) Have you looked through the logs to see if there's anything there?
It might not be an error - do you see the script restarting?In the stdout and stderr logs no errors.
Can you swap the fridge and vessel sensors maybe and see if that does anything?I switched back to the fridge sensor where it was in the fridge and changed the setting to fridge consistent It holds that set temp with no issues.
Is this restarting? See pic.It might not be an error - do you see the script restarting?
Can you swap the fridge and vessel sensors maybe and see if that does anything?
I'm leaning away from a logical issue simply because there's a long track record of this "just working."
If you stop BrewPi (sudo systemctl stop brewpi) and let it run "headless" for a bit, what happens? This assumes you either have an LCD or some other way of checking temps without the UI of course.
No, that's the updates from the controller to the script. It's set at 120 seconds by default, which is generally fine.Is this restarting? See pic.
I currently run headless only. I can hook up a monitor how do I check temps with out the UI?No, that's the updates from the controller to the script. It's set at 120 seconds by default, which is generally fine.
When you say LCD screen is that via hdmi port?Okay so more background.
The BrewPi application doesn't actually control temperatures. It receives Jason packets from the Arduino, and forwards them to the web UI. The controller will happily manage temperatures without the application, you just have no visibility without an LCD screen.
The above instructions will allow you to view the periodic JSON coming from the controller, or the LCD contents. Both will be in JSON, however, you should be able to pick up which field is which in short order.
Would it be easer to wipe the OS and reinstall?Sorry, I should have been more clear:
BrewPi has an "LCD screen" that is actually several separate concepts:
The controller will do everything on its own; the only "control" that happens from the script/UI is setting changes and a temp profile if you use one. Otherwise, you can use an Arduino without a Pi. If you have an LCD (as in #1 above) and a rotary encoder, you can even skip needing the UI for temp setting changes.
- A physical 20x4 LCD, either connected to the Arduino in parallel or in later firmware, serial
- The "LCD" visible in the web UI. A dated look, but we all seem to like it
- The JSON report, which is sent over the serial connection from the Arduino to the host that provides the information for #2 above
What I am suggesting is you remove the BrewPi script from the equation and see if it behaves the same. If the problem goes away, then we will suspect something in the script. If it does not go away, we either have a hardware or firmware issue to diagnose.
The instructions above will allow you to power the Arduino from your Pi (or any handy laptop), connect via the serial connection established over USB, and have rudimentary visibility to the system's state.
It's easy, but it's work that may not get you anywhere. I'd be pretty frustrated if I did that and it didn't help. Unless you made some changes to the Pythion scripts, there's no reason to believe those are at fault. This will allow us to find out right away.Would it be easer to wipe the OS and reinstall?
Enter your email address to join: