V1R2 + RW 4.8.0 + fw 617 + macOS 27 developer beta = unusable roaster

Roasting on the Bullet
1

Had to manually update to RW 4.8.0 after upgrading to macOS 27 beta on my M1 MacBook.

Now the roaster is spontaneously changing state.

I preheated the roaster, and let it settle into charge state, and when I hooked up the MacBook, RoastTime showed the preheat selection screen. Within a matter of seconds the roaster went to roast without dropping beans.

I eventually got things to a state where RT and the roaster agreed on the charge state and dropped the beans. Roaster went to the roast state but RT didn’t seem to be updating the roast profile graph, and in about a minute, the roaster went spontaneously to the cooldown state.

It’s not just these state changes - I’m seeing it go from OFF to preheat as well, which is disconcerting.

I see there’s a 645 firmware update available so I’ll try updating to that and see whether that addresses the sociopathic behavior. I’ll search existing topics as well as I haven’t been on RW in a bit, but has anyone else seen this?

2

Hi @john_l

Firmware v645 may not resolve this issue and does not correctly support legacy IBTS versions. If your Bullet uses a legacy IBTS, the roast graph may be affected at around 180°C.

Please do not update to v645. Kindly contact Aillio Support so the team can investigate the unexpected state changes:

[email protected]

Thank you.

3

Sorry, too late, what now?

On the plus side, the roaster behaves predictably again on the 645 firmware.

I didn’t see any problems with my roast graph: Log in | Roast.World.

Questions:

  • When you say “legacy IBTS” do you mean a V1R2 IBTS, as opposed to a V2 IBTS?
  • Are there any safety or reliability issues with running 645? I can deal with UI glitches for a batch or two and just roast by smell/sound past 180C if I need to.
  • How soon do you anticipate a firmware revision that would work with roasters having a “legacy IBTS”? I roast only for myself so for me I’m in no rush to do another batch (as long as my “twice roasted” Ethiopian from today isn’t total garbage).
1 Like
4

Hi @john_l

  1. Your roast profile shows IBTS MLX90614 B1C2, so it is not a legacy IBTS. A legacy IBTS normally appears as Unknown IBTS or (?) in RoastTime or the roast profile.

  2. We have not seen any safety or reliability issues in your roast data so far. Your roast graph after updating looks similar to your previous roast with v617.

  3. The fix is currently under beta testing and handled case by case. We plan to release it soon. You can follow the updates here:

We’ll continue monitoring your next roast to confirm there are no roast graph issues.

Thank you.

5

Thanks! v645 seemed to work fine for the one roast I did with it. If anything comes up I’ll follow up but things seem to be back to normal.

1 Like