Maybe you've seen this, but if not: {link}

Wow, thanks for the lively discussion, guys. I'm reading with great interest and learning lots. Based on what I'm learning, this drop-the-heat-on-charge process might be useful for me, because I've settled into a lower charge temp due to problems I was having with underdevelopment. I was trying to a...

I appears to me that a lot of roasters seem to follow a practice where they 1) preheat the roaster, 2) charge, 3) turn off heat, 4) wait until the bean probe temp turns around or some set amount of time, and 5) turn heat back on. I've seen this prescribed for gas roasters (the guys at Mill City) as

I roast 225 gram batches and I charge slightly below 200 Celsius. The actual charge temp for me depends on my target roast level. In general, the darker I want, the cooler I charge, to give myself more development time. However, the actual range is quite narrow and the qualities of bean itself (dens...

Last night I did my first roast with the new version. I love the option to change the phase time LCDs to be percentages! Thanks, Marko!

I wanted to post a quick follow-up for those who may be interested, and for future forum searchers. For me, the best results came by lowering the charge temperature. This lets me use the same power adjustments and the same overall ROR curve, while giving the whole roast a little more time to develop

While this is good advice in general (I too have had good luck accelerating the mid phase), it doesn't help acheive this particular goal. Getting to 1C faster will surely increase my time time ratio after 1C to be higher than 25%. Is anyone using Rao's "rules" and doing dark roasts?

Like many, I've been experimenting with the roasting guidelines proposed in "Coffee Roaster's Companion." For me, this is producing good results at light roast levels. I am interested in going a little darker for some beans, but I'm not sure how. Assuming I want to keep a declining ROR throughout th...

Thanks, Marko! I noticed this as well, but am not experienced enough with the software to know whether it was a bug or whether I was just using it wrong