This is my first time using the Aillio Bullet R2 (and my first time roasting on a professional roaster). Before this, I only roasted on a Behmor 1600 .
This roast was:
350 g green coffee
Ethiopia Uraga Haro (washed, Heirloom varieties) from Sweet Maria’s Finished in 6:32 min
My goal is a light (City) roast with approximately 11-12% weight loss . I’m still learning the R2, so I’m not sure which parameters I should adjust first.
My first two batches finished in 4:46 and 6:10 , respectively, which both seemed much too fast for this coffee.
I’d really appreciate any feedback on my profile. If anyone has roasted this coffee, or a similar washed Ethiopian on the R2, I would also be grateful if you could kindly share your profile or any suggestions on what changes you would make.
I’ll cup all batches tomorrow and report back with the results.
Before reading too much into the curve, I’d trust the weight loss over everything else on that screen, since it’s the one number coming off your scale and not the IBTS. 9.9% on a washed Ethiopia is a touch light, which lines up with you wanting 11 to 12%.
I’d hold off on the temps for now though. Like @jedsadazisz said, that IBTS spike after 165°C is a real thing, and if the sensor’s reading high then your first crack and end temps (and the rate of rise off them) are probably showing the roast hotter and faster than it actually ran.
That said, a couple things do line up with a quick roast: 240°C is a bit hotter than Aillio’s usual 220°C start for 350g, and jumping to P8 early puts a lot of energy in up front. Your development came out pretty short too. Getting to 11 to 12% is really about carrying a little more roast overall, not just holding longer past first crack, so I’d ease the power back before it colors up and let it ride a bit longer from there.
How did it end up cupping?
If you want a closer look, send me your raw export and I’ll dig into the whole curve for you.
I’d also avoid changing several parameters until you have a clean roast after the firmware update. Cup that roast, record the weight loss, and then use the same saved recipe for the next test. If it is still finishing too quickly or tasting underdeveloped, change one upstream Power or Fan step rather than simply extending the time after first crack.
I developed RoastRecipeAdvisor to help with this type of decision. It reviews the completed roast in the context of the recipe that drove it, connects the IBTS/RoR behavior with the Power, Fan, and Drum actions, and helps identify one recipe change to test next. In this case, though, I would wait for the post-update roast so the recommendation is based on more trustworthy sensor data.
