BrewPi Remix – What’s Old is New Again

[LBussy]

Well, I guess I can't blame this one on him.

 

[day_trippr]

We like to have fun here

 

[Brewski_59]

0.7.6 Bug Fix Release

Oh no, your not getting me again, last time I did an update it broke it.

 

[day_trippr]

The gauntlet is thrown?

 

[Brewski_59]

The gauntlet is thrown?

Nah

We like to have fun here

 

[LBussy]

Oh no, your not getting me again, last time I did an update it broke it.

Cut me to da bone!

 

[LBussy]

I dropped a hotfix into 0.7.5 master to address an issue where new OneWire sensors would not save correctly. There is no reason to update unless you have been bit by this (and I know of only one person who has been);

Everyone else can wait for a new release.

If you get bit by this, you will have to reset the Arduino to Factory Defaults (Maintenance Panel -> Advanced Settings -> Control Constants -> [Reset Arduino to factor defaults] button.)

 

[blau]

Hi, I have reinstalled.
Good display appearance. I connect the relay, it recognizes it well and it is installed, then I connect the probe to A0 but it is not recognized (I have tested with each of my 3 probes separately)
Tell me if you want me to reset the Arduino with the advanced settings button and flash the firmware again.

 

[LBussy]

The hotfix I referenced is to deal with saving a ghost device only. If your sensors are not showing up, I suggest going back to the test sketch I shared with you and address whatever may be preventing the sensors from being detected. Assuming you have the I2C firmware installed (if the LCD works it is) and you are connected to A0, they should show up.

 

[blau]

Ok, It only occurs to me that the probes are bad. Can you think of a way to check this? We wait for the new probe? any other test? I follow the path that you indicate to me.
Yes I installed I2C and the LCD works fine.

 

[LBussy]

Other than testing the probes one at a time with the test sketch, no.

 

[blau]

It seems there are no mistakes today. Here you have the video of the result on the display

 

[LBussy]

I honestly do not know what to do next with those one wire sensors. I think the only thing remaining is to try a different Uno?

 

[blau]

Ok, any clone "one" for reference? better a "one" than a wired lolin Mini?

 

[LBussy]

If you get a real D1 Mini, we can test that too. Both should work.

The Uno is another item with which I have not had an issue. Some of them do not have serial numbers, which means you can only have one per Pi, but other than that I've been lucky.

 

[duncan.brown]

I know of only one person who has been

Make that two... I should have checked the thread before trying to debug.

 

[duncan.brown]

@LBussy I'm still having trouble configuring my temperature probe after updating to get the fix. The screen shots below show what happens. I see the one-wire probe in the un-configured devices and it looks OK. Then I set it up using the pop-up menus and click Apply. However, it's settings get messed up when it tries to set up the sensor. I did a reset to factory on the board and still no luck. The board is running:

Found BrewPi v0.2.13 build a2fa8f0, running on an Arduino Uno with an I2C shield on port /dev/chronical

Any ideas? Thanks!

 

[duncan.brown]

Software issues aside, the new BrewPi Remix Glycol hardware is finally set up and ready to be configured...

There are temp probes for each fermenter. The thick red/black wires coming out of the top of the black box carry the [email protected] current for the heaters across the basement. The black box has 12VDC in for each heater and 24VDC in and out for the glycol pumps. The board next to it has the Pi B+, connectors for the temperature probes, two Unos, and four 5V relays for the glycol pumps and heaters.

 

[LBussy]

Any ideas? Thanks!

That's the bug I fixed. I think what happened is your browser is caching the JS file. Do a shift-refresh and see if that takes care of it.

That's a sweet setup! So jealous - I need to up my game.

 

[duncan.brown]

That's the bug I fixed. I think what happened is your browser is caching the JS file. Do a shift-refresh and see if that takes care of it.

That was it, thank you. On Safari 14.0.3 you need to be a bit more aggressive and select "Develop -> Empty Caches" with no windows open to make sure that all the JavaScript is flushed.

That's a sweet setup! So jealous - I need to up my game.

Thanks! Configuration and testing starts tonight. I did a quick test and configured the probe as the chamber temperature and the glycol and heater relays as the chamber cooler and heater and I can hear the relays clicking on and off when I use constant chamber temperature and change the temperature setting.

I think I remember that you said for glycol I want the probe as Beer Temperature (not chamber) but if I do that, then it doesn't seem to trigger the cooling and heating relays. Is there something else that I need to set up for glycol?

 

[LBussy]

I need to get back and take a look at my notes in the code. I remember it the way you do, but a chamber temp is probably as effective because a single beer temp probe would revert to that type of control.

I’ll be interested to hear how it works for you, I’ll probably code any changes around your use case so please feel free to take copious notes about what you see and what you’d like to see.

 

[duncan.brown]

I’ll be interested to hear how it works for you, I’ll probably code any changes around your use case so please feel free to take copious notes about what you see and what you’d like to see.

Will do, thanks!

 

[duncan.brown]

@LBussy I played with the glycol code this afternoon and have a few initial thoughts. This is just a dry run with nothing in the fermenters. Wort goes in tomorrow.

I think there's a minor bug in the glycol firmware that causes it to return the wrong code to the script for the shield type. It returns 6, which gets parsed as null and the pin configuration goes crazy. I set this to 5 so that it behaves like the I2C shield:

use i2c code for glycol · duncan-brown/[email protected]

Arduino Firmware for the BrewPi Remix Project. Contribute to duncan-brown/brewpi-firmware-rmx development by creating an account on GitHub.

github.com

The temperature of my glycol is regulated by a separate thermostat in the chiller (which is always at 28F) so that control loop is independent of BrewPi. My setup has a single temperature probe inside the fermenter's thermowell so it's in direct contact with the fermenting beer. I'm controlling the glycol pump to cool, which sends 28F glycol through the fermenter's internal cooling coil, and a heating pad in direct contact with the cone of the fermenter to heat.

Given this, I think the easiest way to get BrewPi to behave in a similar way to the normal fridge and fermenter setup is to configure the temperature probe as the beer sensor. To get the heating and cooling to work with no physical fridge sensor, I set the firmware to use the address of the beer sensor as the fridge sensor if it's compiled for glycol:

use the beer sensor for fridge when using glycol · duncan-brown/[email protected]

Arduino Firmware for the BrewPi Remix Project. Contribute to duncan-brown/brewpi-firmware-rmx development by creating an account on GitHub.

github.com

This seems to do the right thing; heating and cooling works as expected and the logging and UI look right.

Since there zero penalty for short delay on the heating and not too much on the cooling, I tightened up the minimums for the short-delay cycles:

Changes for using glycol and direct heat on an SSBrewtech Unitank by duncan-brown · Pull Request #26 · brewpi-remix/brewpi-firmware-rmx

BREWPI_SHIELD_GLYCOL needs to be set to 5, otherwise the script doesn't know that it is supposed to be using an I2C shield when the firmware is compiled for glycol. The most straightforward way...

github.com

These numbers are more similar to the numbers on my old FTSS controller, so I'll start there.

All of this is in a pull request, if it looks reasonable to you:

Changes for using glycol and direct heat on an SSBrewtech Unitank by duncan-brown · Pull Request #26 · brewpi-remix/brewpi-firmware-rmx

BREWPI_SHIELD_GLYCOL needs to be set to 5, otherwise the script doesn't know that it is supposed to be using an I2C shield when the firmware is compiled for glycol. The most straightforward way...

github.com

Tomorrow is a brew day and I'll work on tuning the PID and see how that goes. There's only an uncountably infinite number of combinations of numbers that I can use for Kp, Ki, and Kd, so I'm sure I'll get it right eventually...

 

[LBussy]

Thanks, Duncan. I merged all but the shield definition into the glycol branch. I apparently forgot to add the glycol shield definition to the script, so that's been done in the ironically named glycol branch of the scripts. I'm sure you know how to pull that branch without my help.

I know you have the glycol temp controlled already. I'm interested to hear if you find any value in seeing the glycol temp in the display, want to control it (multi-chamber would work for this), or what other changes make sense.

 

[duncan.brown]

Great, thanks! Life got in the way of brewing yesterday, so I'll start playing around when I brew next weekend.

Although I don't need glycol temperature control, I might drop a couple of spare DS18B20's in the glycol and monitor that as the room temperature in BrewPi. That might be a good way to see what effect the thermal load of the cooling has on the glycol temp as the temperatures will be displayed on the same graph.

 

[LBussy]

Once we decide on a direction, the visualization should be fairly easy.