Originally posted by ArnhemR
View Post
I'll have a crack at your 600g 180 degree preheat and full on for the rest of the roast suggestion with some of these african beans. That's close to what I did when I first built the KKTO for my first few months of roasting in it, and is similar to my approach for softer beans - but keeping an eye on the upper temperatures of the system.
I'm using Artisan to record my profiles - prior to that I was using RoastLogger, which I actually preferred, but I have an Arduino with a TC4 as my logger and controller of element, and at the time I was rigging it all together Artisan was going to be more straight-forward. Now they're much for muchness, and I might move back to RoastLogger at some point. It has much better smoothing, and doesn't poll the Arduino for data points, but takes all the raw data and processes it itself.
Paul and I have had a number of conversations over the past 12 months, mostly in terms of build, but some in terms of roasting approach. A lot of our conversations have been documented elsewhere on this forum. The 'set and forget' might be great for most, but what I'm really after is to be able to manipulate my roast, control the 3 phases of the roast to enhance or suppress bean characteristics, much like Matt and Mal do with their Corretto setups. It could just be that the KKTO isn't agile enough for it, but I'm giving it a go! I like a lot of the KKTO package, but I'm not convinced there isn't an opportunity for improvements (a la my experiments in the past). It's just a question of whether I have the time, tools and tenacity to do it.
I'd love to be able to hit my preferred flavour profile with a simple approach - but over the past 12 months, it hasn't yet come up the goods.
I probably sound really ungrateful for the conversation and advice - I'm not, I do appreciate all of the input everyone is putting in. It would just be exhausting to outline everything that I've tried in my roaster thus far, and all of the conversations I've had on and offline with various people.



Leave a comment: