Beta firmware
Beta builds are pre-release firmware we publish here so the community can help validate fixes and new features before they’re promoted to the stable Firmware page.
- Not for production farms. Run beta builds on a test printer or a single FarmLoop unit you can babysit, not on the whole farm.
- Things may regress. Trigger reliability, OTA behaviour, MQTT routing - anything we changed is fair game for unintended side effects.
- Please report what you see. If a beta misbehaves, send us the OTA log +
.gcode.3mfunder the Technical issue category. Mention the beta version in the subject line. - You can always roll back. Each beta lists the stable build it diverged from - re-flashing that file from the main Firmware page returns you to a known-good state.
Current betas
Section titled “Current betas”The latest stable firmware for every board is on the Firmware page.
Bambu H Series - 3.20 beta (rev 7) · FarmBoard 2
Bambu H2S, H2D, H2C
v3.20-beta-rev7 September 2026 · beta
Release notes
- Steadier printer connection.
- Door blocked detection is off by default.
- Emergency reset clears everything.
- The cycle record shows the bending, safety and final close steps.
- Rev 7 is a bench build, not yet tested on hardware.
- Rev 5 (FarmBoard 3): door-open safety fix.
- Web access over your WiFi released.
- Firmware update in the browser.
- Better support logs.
- Live status and log.
Download OTA .bin · FB2
Flashing a beta
Section titled “Flashing a beta”The flashing procedure is identical to a stable release - pick the route that fits your setup:
- USB-C flash from your browser - recommended when you have a USB-C cable handy.
- OTA upload from the board’s web page - no cable needed; works from any phone or laptop.
Rolling back
Section titled “Rolling back”If a beta misbehaves, re-flash the matching stable build from the main Firmware page. Both USB-C and OTA support the round-trip - there’s no special “downgrade” mode.
Reporting issues
Section titled “Reporting issues”Bug reports are what make betas useful. Please open a Technical issue ticket and attach:
- The FarmBoard log - the Download .txt button on the board’s web page (see Getting logs from the FarmBoard).
- The
.gcode.3mfof any print that triggered the issue. - A one-line description of what you expected vs. what happened.
We read every report and reply within one business day.