Recipe Designer Fermentation Schedule Entry?

[JIm S.]

It’s curious that there is no fermentation data entry section in the Recipe Designer (e.g., similar to Mash Guidelines section).

QUESTIONS:
- What does the group find to be the best and cleanest way to enter fermentation schedule information into the Recipe Designer (as opposed to entering in Brew Sessions)?

- Any considerations by the developers to include this in the Recipe Designer?

Thanks as always for the help!

 

[Donoroto]

Welcome!

I’d never considered a fermentation schedule. I just let it ferment at the recipe temperature until gravity is stable for 3 days, then consider it ready for packaging.

 

[Bigbre04]

Without taking gravs i wouldnt trust a fermentation schedule that could change temps. my fermentations are VERY consistent but a day or 2 plus or minus would cause problems if i wasnt constantly checking gravs.

 

[BarbarianBrewer]

I think that would be a very useful feature especially when fermenting a lager where you have fermentation for x days (or until y gravity is reached), then raise to temp z for a diacetyl rest, then down to lager temp for a month or three. It would be nice to have those milestones identified up front. Much like a future dry hop addition can be specified in when the brew session is created.

 

[JIm S.]

Without taking gravs i wouldnt trust a fermentation schedule that could change temps. my fermentations are VERY consistent but a day or 2 plus or minus would cause problems if i wasnt constantly checking gravs.

Like the rest of the recipe and mashing schedule, fermentation information is the planned roadmap.

Agreed that the planned fermentation needs evaluation against actual specific gravity, temperature, fermentation activity. etc.

Thanks

 

[Bigbre04]

Like the rest of the recipe and mashing schedule, fermentation information is the planned roadmap.

Agreed that the planned fermentation needs evaluation against actual specific gravity, temperature, fermentation activity. etc.

Thanks

oh, totally misunderstood! ya that could be preplanned.

 

[Bigbre04]

I think that would be a very useful feature especially when fermenting a lager where you have fermentation for x days (or until y gravity is reached), then raise to temp z for a diacetyl rest, then down to lager temp for a month or three. It would be nice to have those milestones identified up front. Much like a future dry hop addition can be specified in when the brew session is created.

It could be based on attenuation milestones. But i would assume that would require a lot more sampling then the average home brewer does??? i guess if you had a tilt and trusted it it would work?

 

[Mont Y. Märzen]

It could be based on attenuation milestones. But i would assume that would require a lot more sampling then the average home brewer does??? i guess if you had a tilt and trusted it it would work?

I'm pretty sure someone has already use a Pi to tie a Tilt and an Inkbird controller together to adjust temps based on attenuation. Sorry, I don't have that link handy. (The Wifi Inkbirds can be scheduled based on triggers. I've used time and temp for mine during crashing. You likely need outside software to incorporate gravity.)

 

[Donoroto]

It could be based on attenuation milestones. But i would assume that would require a lot more sampling then the average home brewer does??? i guess if you had a tilt and trusted it it would work?

I use a tilt to watch specific gravity. No care of the value, just when it is a flat line for 3 days.

 

[JIm S.]

Thanks for the responses!

The inquiry (and feedback) really dealt with the organized ability to include fermentation information into the recipe the same as ingredients, mash schedule, etc. and much as other brewing software does.

"Fermentation Temp." can be documented in the BFriend Yeast Section but not temperatures/times for things like diacetyl rest, cold crash, conditioning, or secondary fermentation.

Guess the idea is thinking-through and including all relevant information into the recipe to guide the process.

Thanks again!