BrewPi Remix – What’s Old is New Again

[LBussy]

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.

 

[jasonv]

Yep looks like I am. v0.2.13 How do I roll it back?

 

[jasonv]

Can I use 0.2.12 version and upload the hex file via the web interface?

 

[LBussy]

Yep looks like I am. v0.2.13 How do I roll it back?

Issue the command: sudo /home/brewpi/utils/doFlash.sh --shield

Pick the appropriate one for your setup.

 

[jasonv]

Issue the command: sudo /home/brewpi/utils/doFlash.sh --shield

Pick the appropriate one for your setup.

I currently have a Arduino Uno with a revC shield on port. What firmware version do you recommend?

 

[varnerchris]

Hi, I have an original BrewPi Spark and I am trying to get BrewPi remix up and running. 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.

Any help would be appreciated! cheers!

 

[LBussy]

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.

Have a look at the logs: /home/brewpi/logs/stdout.txt & /home/brewpi/logs/stderr.txt

I currently have a Arduino Uno with a revC shield on port. What firmware version do you recommend?

That one is appropriate if you are not using Glycol, or an I2C LED.

 

[varnerchris]

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.

2023-08-19 08:47:45 [N] Starting 'My BrewPi Remix Run.'
2023-08-19 08:47:45 [N] Opening serial port.
2023-08-19 08:47:45 [N] Waiting 10 seconds for board to restart.
2023-08-19 08:47:55 [N] Checking software version on controller.
2023-08-19 08:47:55 [N] Found BrewPi v0.5.2 build 0.5.2-0-g72e633171, running on a Particle Core with a V1 shield on port /dev/ttyACM0.
2023-08-19 08:47:57 [N] New JSON received from controller.
2023-08-19 08:49:58 [N] New JSON received from controller.
..
2023-08-19 10:12:36 [N] New JSON received from controller.
2023-08-19 10:14:37 [N] New JSON received from controller.


---

2023-08-18 22:13:28 [E] Starting BrewPi.
2023-08-18 22:09:13 [E] Starting BrewPi.
2023-08-19 08:47:45 [E] Starting BrewPi.

 

[LBussy]

2023-08-19 08:47:45 [N] Starting 'My BrewPi Remix Run.'

That looks okay - anything in the java log on the browser?

 

[varnerchris]

That looks okay - anything in the java log on the browser?

Nope, the console is all clear.

 

[LBussy]

Uhhhhhh.... shift-refresh?

Also, check to make sure the script is actually running: sudo systemctl status brewpi

 

[varnerchris]

ya, chec

Uhhhhhh.... shift-refresh?

Also, check to make sure the script is actually running: sudo systemctl status brewpi

ya, checked that as well as running in incognito. Here is the result of checking the script

brewpi.service - BrewPi Remix daemon for: brewpi
Loaded: loaded (/etc/systemd/system/brewpi.service; enabled; vendor preset: enabled)
Active: active (running) since Fri 2023-08-18 22:09:08 CDT; 13h ago
Docs: User Documentation — BrewPi Remix 0.8.0 documentation
Main PID: 820 (bash)
Tasks: 4 (limit: 1595)
CPU: 3min 53.609s
CGroup: /system.slice/brewpi.service
├─ 820 /bin/bash /home/brewpi/utils/doBrewPi.sh -d
├─8806 /home/brewpi/venv/bin/python3 -u /home/brewpi/brewpi.py --log --datetime
└─8810 git cat-file --batch-check

Aug 19 11:17:16 brewpi brewpi[8806]: 2023-08-19 11:17:16 [N] Using default configuration.
Aug 19 11:17:16 brewpi brewpi[8806]: 2023-08-19 11:17:16 [N] No user config file found:
Aug 19 11:17:16 brewpi brewpi[8806]: 2023-08-19 11:17:16 [N] /home/brewpi/settings/config.cfg
Aug 19 11:17:16 brewpi brewpi[8806]: 2023-08-19 11:17:16 [N] Using default configuration.
Aug 19 11:17:16 brewpi brewpi[8806]: 2023-08-19 11:17:16 [N] No user config file found:
Aug 19 11:17:16 brewpi brewpi[8806]: 2023-08-19 11:17:16 [N] /home/brewpi/settings/config.cfg
Aug 19 11:17:16 brewpi brewpi[8806]: 2023-08-19 11:17:16 [N] Using default configuration.
Aug 19 11:17:16 brewpi brewpi[8806]: Logging to /home/brewpi/logs/.
Aug 19 11:17:16 brewpi brewpi[8806]: Output will not be shown in console.
Aug 19 11:17:16 brewpi brewpi[8806]: Starting BrewPi.

 

[LBussy]

Well, the "universal first aid" would be:

sudo systemctl stop brewpi
sudo /home/brewpi/utils/doPerms.sh
sudo systemctl start brewpi

Optionally, and maybe even recommended, reboot after that.

 

[varnerchris]

Well, the "universal first aid" would be:

sudo systemctl stop brewpi
sudo /home/brewpi/utils/doPerms.sh
sudo systemctl start brewpi

Optionally, and maybe even recommended, reboot after that.

Still stuck with "Script Starting Up" Ill try tinkering and doing a fresh install with another Pi. Thanks for your help!

 

[LBussy]

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.

 

[varnerchris]

Alright, I am back. I did a clean install using this (detected dubious ownership in repository · Issue #65 · brewpi-remix/brewpi-tools-rmx) on an older Raspberry Pi, one that i used to use for the original BrewPi. I ran into the same problem with getting stuck on "Script Starting Up" and did the same suggestions listed above to see if anything would work and I am still in the same spot.

Here are the most recent logs for the clean install using a Raspberry Pi 2014 B+ V1.2

2023-08-23 19:08:48 [E] Starting BrewPi.
2023-08-23 19:10:25 [E] Starting BrewPi.
2023-08-23 20:09:04 [E] Starting BrewPi.
Terminating due to fatal serial error //Reboot
2023-08-23 20:10:31 [E] Starting BrewPi.
2023-08-23 20:11:55 [E] Starting BrewPi.
2023-08-23 20:14:53 [E] Starting BrewPi.

----

2023-08-23 20:14:53 [N] 0.8.1 (main) [c16adae]
2023-08-23 20:14:53 [N] Starting 'My BrewPi Remix Run.'
2023-08-23 20:14:53 [N] Opening serial port.
2023-08-23 20:14:53 [N] Waiting 10 seconds for board to restart.
2023-08-23 20:15:03 [N] Checking software version on controller.
2023-08-23 20:15:03 [N] Found BrewPi v0.5.2 build 0.5.2-0-g72e633171, running on a Particle Core with a V1 shield on port /dev/ttyACM0.
2023-08-23 20:15:07 [N] New JSON received from controller.
2023-08-23 20:15:08 [N] JSON decode error: Expecting ':' delimiter: line 1 column 199 (char 198)
2023-08-23 20:15:08 [N] Line received was: 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}]}
2023-08-23 20:17:08 [N] New JSON received from controller.

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.

 

[LBussy]

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}]}

I see two issues here:

1. BrewPi Remix does not support two heaters. I never had a Spark so testing with one was never in the cards. I assumed that the Legacy BrewPi would support the spark but that does not seem to be the case. This issue is overshadowed by:
2. This is not valid JSON. The part where it transitions to heater2_dfilt is improper. "heater2_dfiltnull, should be "heater2_dfilt":null,.

Has this hardware ever worked? If that firmware is not working right, I can't address it. I never took on Spark development.

 

[jasonv]

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.

I see revc is the correct type for me what about the release to match the revc?

 

[LBussy]

I see revc is the correct type for me what about the release to match the revc?

0.2.13 would be it. There are very few material changes, but using the latest/stable version always makes sense.

 

[jasonv]

0.2.13 would be it. There are very few material changes, but using the latest/stable version always makes sense.

Hi,
Still have something wrong. Example brewed a lager last night fill wort in fermenter at 70 degrees set beer temp at 50 expecting it to be 50 the next day to pitch was only 57. I can see the target temp for the chamber is 33.8 yet it never keeps the cooling on long enough to hit the target temp it just short cycles the cooling. I tried flashing to older firmware's to see if I would notice any change. No luck there.
Thanks for the help!

 

[LBussy]

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.

 

[jasonv]

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.

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.

 

[day_trippr]

May be a long shot: check the setting: Maintenance Panel - Advanced Settings - Control Constants - Temperature setting minimum
The default 33.8°F value may be too high...

Cheers!

 

[LBussy]

Would you please zoom into the chart (you can click-drag on the chart to do so) to a smaller area like this?

.... be sure to include the bottom part.

 

[jasonv]

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.

 

[LBussy]

I think part of what is happening here is that the logging interval (120 seconds) fails to catch the actual temperature drop. I do believe you are probably dropping to the fridge set point, but that the thermal mass in there is causing the temp to raise by quite a bit before it reaches the end of the cooling min-off time.

One thing that might help is to drop your fridge probe in a glass of water to give it a thermal buffer.

 

[jasonv]

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.

 

[LBussy]

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.

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?

 

[jasonv]

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?

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.

 

[LBussy]

In the stdout and stderr logs no errors.

It might not be an error - do you see the script restarting?

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.

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.