Well this is pretty slick...

I just roasted a bunch of coffee. To try to keep the roasts consistent using what RT3 (the roasting software) refers to as Recipes. Recipes are a set of button pushing commands to the roaster that can be based upon Time (the default) or Temperature AND Time (that's the logical AND meaning both). They provide consistency that seems to be lacking when I just follow the button pushes of an earlier roast. Easy-peasey. But the results have been inconsistent and I end up with roasts that have a graph that varies a lot. And I mean a lot.

Thru some odd accumulation of good fortune I did a roast that seemed to have all the right shapes to the curves that are recorded during the roast. At the same time I needed to answer a few questions from the software developer about how the Recipe feature works in RT3. So...

I decided to create a new version of the Recipe using the roast that had come out *looking* like I wanted. But instead of using the in-built roast-to-recipe conversion which is mechanized in RT3 using Time, I instead used the temperature values from the IR sensor (part of what the mfr calls the IBTS) that occurred near each power, fan and drum speed control setting I had used. There's nothing earth-shaking here: users have been doing this to one extent or another from the git-go. I just hadn't tried it myself. Well that whole approach has definitely opened my eyes! 

Here's a list of the steps that's a Copy/Paste of what RT3 saved as a Recipe. The Time values are pretty much meaningless- they just have to be =/> 5 seconds.

  • P4, D4, F2 [Initial settings]
  • P7, D8 (Msg- YP=330.00°F)


Comments

Popular posts from this blog

Uh-oh... the 'season' has started!

'Tis the season...

Monsoons? What monsoons?!