There are several options for software monitoring when roasting coffee, but I have chosen RoastLogger to start with, primarily for its compatibility with multiple meter models, and its being written in Java, which allows it to run on multiple platforms.
The software itself is free, but you will need to find a compatible multimeter. I chose the Victor 86B model, for its compatibility with the software, as well as the model’s compatibility with older connectors
I had to order the meter from E-bay, as I could not find it in stock with US-based resellers. The E-bay seller shipped from China (2 week shipping), so there was a bit of delay. I also ordered a K style thermocouple from Amazon, but discovered that it used an older blade style connector, over the more standard “banana” style plugs. The same seller also sold a converter so there was another few days delay as I waited for that. Once everything was connecting, a dry run with the meter showed temperature readings as expected, however, the meter only displays data in Celsius, which will take some getting used to.
I chose a peaberry coffee bean to test the meter with, because of their size they present a roasting challenge, especially in a Whirley Pop. Initial tries with a standard candy thermometer yielded decent results, however, it was difficult to achieve an even roast with the pre-meter setup. Most of the time the roast ended up hitting second crack, yielding a FC+ roast level, rather than the Full City sweet spot.
Once the Whirley Pop configured with the new thermocouple, and the meter connected to my laptop which was running RoastLogger, it was time to do a roast! RoastLogger has some manual inputs for Beans Added, First Crack Started, First Crack Ended, Second Crack Start, etc. I hit the button for Beans Added, actually added the beans and the roast was underway. About 2 minutes into the roast, I realized that I did not have the thresholds converted into Celsius, but luckily, my phone was nearby and I was able to determine when and where I should expect First/Second crack.
One of the benefits of RoastLogger is that it samples the temperature data every 5 seconds, down to one-tenth of a degree, and logs that data into a text file, which is also used to generate a graph of the temperatures over time.
The main thing I like about the application is that along with the log data, it stores everything in templates, which can be used to record details of the roast process, as well as tasting info, which should help me standardize my output and make future entries easier!
All in all, having more detailed temperature data, and being able to view the graph as the roast progressed, I was able to map first crack of the beans, when it completed, and also helped me to draw out the time between first and second crack by lowering the temperature, and seeing HOW it affected the roast temperatures, which was more important. I could see the beans edging back up in temperature, which meant second crack was approaching, and I was able to eject the beans before it started. All in all, it was a great first test.
You must be logged in to post a comment.