My bullet is v1.5, FW591, RoasTime 3.41. Today I tried to update the FW to Stable 605. When update started, it beeped 2 times, then loud fan, very soon the screen showed error " We encountered an issue updating your firmware". I repeated a few times it ended up that RoasTime could no longer connect with Bullet.
I unplugged the power from the Bullet, uninstalled RoasTime 3.4.1 and reinstall Roastime 2.5.7, updated RoasTime to v3.4.1. Bullet is back to normal. However, I still could not update the FW. Any solutions/suggestions?
I have a 1.5 and had firmware upgrade issues until I reinstalled the OLD roastime and updated the firmware from there. It never worked to upgrade in 3.4.1. Worked like a champ in the old version.
Here’s the change log for f/w updates. 606 is the beta…
Bruce
Update Log
Firmware: 606
Experimental version where the exhaust fan runs at F1 during preheat in order to cool down IBTS and decrease dirt build-up.
Adjusted allowed IGBT frequency for 120V boards even further to increase power at very low line voltages.
Firmware: 605
Increased allowed IR Ambient to 80C
Adjusted allowed IGBT frequency for 120V boards to increase power at very low line voltages.
Added USB command for LED display blink start / stop
Firmware: 602
Fan setting FA now allowed if cooling tray is < C4
Bug fix for V1 & V1.5 Control boards sounding buzzer at startup
More power for 230V induction boards used with lower input voltage and high drum temp
Firmware: 596
More power for 120V induction boards used with lower input voltage
Allows higher temperature on IGBTs - helps with error 32
Firmware: 595
Better support for 120V induction boards used with lower input voltage
Firmware: 591
Support for new Bullet control board revision with new components
The question, for me anyway, is whether the result is worth the journey for a V1.5 board. The change log suggests benefit only if you have very low input voltage, which really isn’t a problem in my neck of the woods.
Brandon - I’m a tick jaded at this point. It’s slightly off topic, but I made the mistake of upgrading from Mac Catalina to Big Sur without understanding that it would crash my Kingston IronKey (secure USB drive). Problem continued because Kingston didn’t have the necessary upgrade patch ready. Once it arrived, it required a Windows computer (which I didn’t have) to upgrade the IronKey. What’s the point? I went from something that was perfectly stable to a train wreck, lost hours and hours to the fix, and when as was said-and-done, the real world performance benefit of the 64-bit operating system was indiscernible (at least to me). Same thing with IOS upgrades. After multiple experiences with my phone’s battery going down faster than a two-dollar h@#ker, I learned to wait for the XX.1 release . The older I get, the more I subscribe to the “if it ain’t broke…” mentality.
totally get it and apologies if I made light of it. I’ve been a software developer for nearly 30 years now and I’m certainly more cautious then I was even 5 years ago. while I think age plays a partial role in that, I also believe software (and hardware) has gotten far more complex so naturally more challenging to catch all the bugs. in addition, regardless if you are working on a small or large team it doesn’t seem like enough time is devoted to bug fixes. all that to say, yeah we should all be more cautious before upgrading.
Gregg, I have the same question as whether it is worth the effort to upgrade my V1.5 FW to the latest version, knowing it may cause more troublesome. Sometimes I felt the power was low and saw FW605 might address this since mine is with 120V board.
Please elaborate as much as possible:
Which platform are you using?
Which hardware?
Does your R1 already connect and can you use RoasTime?
If yes, you don’t need to install drivers.
Show us a screen capture or describe the messages
Does the R1 make any sounds? Beeping? Fans start running?
If on windows does it show up in the device manager? Before / During updating?
The more specific you can be, the better chance we have of fixing it.
Trying the firmware updater it reads:
rodricjohnson@Rodrics-MacBook-Pro-16 ~ % /Users/rodricjohnson/Downloads/firmware-updater-darwin-x64.command ; exit;
This standalone updater is at version 1.0.0.
What firmware version would you like to install? ( (b)eta, (s)table ): s
Will attempt to update firmware. Please wait…
0 / 104 [__________________________________________________________] 0.00% ? p/sFirmware could not be updated: Unable to read 64 bytes from device after getting vars. Please restart the application.
I just tried updating it on my windows machine using roastime 3.4.1. I receive the same error as I did on the Mac using 3.4.1: “We encountered an issue updating your firmware, please try again or contact support.”
. The older I get, the more I subscribe to the “if it ain’t broke…” mentality.