PeeBee
Brewer
This has been moved out of another thread because it is a bit off-topic for that thread.
I could be seen as presumptuous suggesting this is a "bug report", but having found the source of my problem I can now look up dozens of threads reporting the same thing. Perhaps mine will be the last?
I'd devised a work-around so I could automate a "strike temperature" (as calculated by Beersmith) step into a Grainfather (using GF Connect). The Grainfather brewing system has no concept of "strike". Obviously a "strike temperature" step is going to have a hotter step temperature than the following step.
But in Beersmith that is a "no-no". As soon as the program is restarted it reorganises the mash steps into ascending order of "step temperature". This is an unusually draconian action by Beersmith, which generally has a more relaxed and flexible approach to brewing.
Others report the same issue, but have a range of reasons for wanting successive mash steps to reduce in temperature.
I could be seen as presumptuous suggesting this is a "bug report", but having found the source of my problem I can now look up dozens of threads reporting the same thing. Perhaps mine will be the last?
I'd devised a work-around so I could automate a "strike temperature" (as calculated by Beersmith) step into a Grainfather (using GF Connect). The Grainfather brewing system has no concept of "strike". Obviously a "strike temperature" step is going to have a hotter step temperature than the following step.
But in Beersmith that is a "no-no". As soon as the program is restarted it reorganises the mash steps into ascending order of "step temperature". This is an unusually draconian action by Beersmith, which generally has a more relaxed and flexible approach to brewing.
Others report the same issue, but have a range of reasons for wanting successive mash steps to reduce in temperature.