I have the latest fw and sw in place. First roast today and with the Charge command, loaded beans and the roaster took off, but the software hung.
For whatever reason I decided to disconnect/reconnect the USB cable. The Active presentation on the software came back to life, and plotted all of its updates from the time the roast started until it caught up. Working as expected now.
Check out the screen shot with the curious drop, apparently where I lost the connection(?)
You probably have this figured out but thatās pretty much a classic USB dropout. Could be the USB cable not seated completely, or a cable thatās āpast its primeā and has become intermittent, or an issue with the connector mounted on the control board. Iād start with the USB cable.
Thanks Bruce. I can see now many USB related issues. This is the first time it has occurred for me so considered it might be software related.
One possibility is as you suggest. I have my PC on a rolling stand of sorts, with a USB extension to allow foe additional distance and movement. I suppose its possible that could have loosened.
Iāll continue to monitor that. Appreciate the comment.
The roaster has an internal buffer, but if your disconnection lasted longer than the buffer could hold - you may see a drop like that. I agree with Bruce, this specific case looks more like a hardware issue (USB unseated) than a software one. Usually a software issue in this regard would not recover.
Also worth noting that your main version is out of date. v4.10.3 is actually the latest version for x64. We can not auto update Mac OS userās main versions because it would break for users on < 10.15, but you can download from the website at https://roastime.aillio.com.
So with USB, I would think that there might be a timeout included in the USB protocol, and possibly one included with Roastime(?), but regardless it was interesting watching the data points chart out after reconnection.
Looks like I failed to mention that Iām on Win 11 and before roasting I always bring the Win patches up to date, and launch Roastime twice, and manually check for Firmware changes prior to roasting.