Hi Anderson
Thanks so much for the kind words!! And, sorry you're having problems.
I've talked to 4 people who are having (what I think is) the same problem. They report that the temp is doubled. Depending on your charge temps, and that they may be changing rapidly, I can see where it appears to be doubled, when in fact it might be actually translated to F, or vice versa. I cannot reproduce it with my Bluetherm, so I'm relying on the info from users to try and pinpoint the cause. Thanks for the detailed explanation.
I can tell you I just got a new SDK from the manufacturer. I've inquired about this problem, because I do not think it's happening in Roastmaster's code. I haven't heard back yet. Once I can test the new SDK, I'll do an update with the hopes it's been fixed. My BD unit is from the first production run. I fear that they maybe changed the firmware sometime into production in an area I need to account for in Roastmaster. Unfortunately, the manufacturer doesn't supply version and bug documentation, so I'm I'm trying to "feel my way" through this.
The next time it happens, would you be able to:
- Exit the roast without altering any data, just saving if you need to.
- Wait at least 15 seconds (RM shuts down idle probes in 15 second intervals)
- Open the roast again and see if the problem is there
The third step will give you a fresh connection to the BD. You'll be able to tell it's been refreshed if the start/stop button is yellow for 1-2 seconds, then turns green (as opposed to turning green right away).
Other than that, can you tell me if your workflow makes use of curve templates via profiles? Or do you define and roast and manually create your curves and bind them to probes each time. The only consistent info I have thus far is that it appears to happen sporadically after a number of roasts have been performed - not on the first roast. My workflow uses curve templates, so probe links never really have a chance to shut down. I'm looking into that now - to see if that might be why I haven't been able to reproduce on my end - even after countless hundreds of test roasts.
Thanks for reporting it.
Please let me know any details you can.