When I got my Bullet, roasting using the IBTS was a revelation. I was very impressed with the repeatability it brought to the game. Per Morten Munchow, I’d do an establishing roast for new varieties of beans and find out at what (IBTS) temps FC and SC happen and then engineer my subsequent roasts from there. Irrespective of my charge size, FC was very nearly the same temp every time.
This continued for dozens of roasts and, with occasional cleanings, I was a happy camper.
However, over the last few months, the IBTS has been apparently getting dirty very quickly. Now, I can do a thorough cleaning and the IBTS vs bean temp behaves as it always has. By the second near back-to-back roast (I move directly to Preheat as soon as the last batch of beans is cool), the difference between the IBTS and bean probe is getting smaller. By the third or fourth roast the bean temp crosses the IBTS temp and by the fifth, the IBTS is completely useless and I have to clean it again.
I know it is the IBTS underreporting the temp because, if I let the roast go to the desired IBTS temp, it is badly overroasted.
IBTS fan is showing in the high 15K’s.
Have taken apart the front panel several times and the IBTS fan is clean, the assembly well seated and nothing appears to be amiss.
I am good about otherwise cleaning the machine. Impeller is reasonably clean and freely spinning. The small fan at the back of the drum is freely spinning.
When I take off the front plate to clean the IBTS (yet again!), the front plate is not particularly dirty, though it is kind of dusty. Maybe the IBTS porthole is kind of dusty, too.
As usual, the cotton buds that i clean the sensor with rarely show much of anything.
It is my impression that the area under the drum accumulates more chaff and other schmutz than it did in the past. I blow it out after every roast.
My typical roast is -
500g
PH - 250°C
P8, F2, D9 to 2:30
P5, F2, D9 to 200°C
P3, F2, D9 to dump, usually somewhere near 215°C.
I am ready to replace the IBTS assembly, though I can’t really come up with a fault that might explain this behavior (and the engineer in me demands one!).
Thoughts, anyone?
Thanks!
-Gray