Skip to content

Choose your trigger mode - Mechanical vs Digital

The FarmBoard runs your machine through a four-step cycle on every print:

  1. Close door
  2. Open door + fan
  3. Bending
  4. Close door, return to idle

You can drive this cycle two ways, and both run automatically during a print - neither needs a person standing at the machine. In Mechanical mode the printer’s bed presses the limit switch via the print’s G-code moves; in Digital mode the printer tells the FarmBoard over Wi-Fi. Digital mode is recommended for production. Mechanical mode is the always-available fallback and works without any network.

Mechanical

Mechanical mode Diagram: two ways to drive the cycle. Mechanical: the printer's bed moves down and presses the limit switch, and the switch tells the FarmBoard which step to run. Digital (Full MQTT): the printer reports its state over your Wi-Fi network (local MQTT, LAN-only mode) and the FarmBoard fires each step itself. Either way the FarmBoard drives the door opener, the fan and the bender. bed moves down FarmBoard Limit switch drives door, fan and bender

The printer's bed presses the limit switch via the print's G-code moves. No operator, no network.

Digital (Full MQTT)

Digital mode Diagram: two ways to drive the cycle. Mechanical: the printer's bed moves down and presses the limit switch, and the switch tells the FarmBoard which step to run. Digital (Full MQTT): the printer reports its state over your Wi-Fi network (local MQTT, LAN-only mode) and the FarmBoard fires each step itself. Either way the FarmBoard drives the door opener, the fan and the bender. bed Your Wi-Fi FarmBoard printer reports its state (MQTT) limit switch off while connected drives door, fan and bender

The printer tells the FarmBoard over Wi-Fi, on your local network (LAN-only mode). The limit switch is disabled while Digital mode is connected.

Schematic, not to scale.

Mechanical

  • ✓Wi-Fi required: No
  • ✓LAN-only mode required: No
  • ✓Reliability: High

Digital (Full MQTT)

recommended for production
  • ✓Wi-Fi required: Yes
  • ✓LAN-only mode required: Yes
  • ✓Reliability: Very high

You can switch between modes any time from the OTA page - both stay configured.

Each cycle step is triggered by pressing the limit switch on the machine - the printer’s bed presses the switch automatically as part of the print’s G-code moves, so no operator is needed. The different press patterns (long presses and taps, shown below) are produced by the programmed bed movements. Works on every kit regardless of network connection, and is always available as a fallback even when Digital is enabled.

Each step and the bed press pattern that triggers it (bar = long press, dots = taps):

1. Close doorLong press (3-6 s) + short tapDoor closes, print can begin
2. Open door + fanLong press (4-8 s) at end of printDoor opens, fan starts cooling
3. Start bendingTriple tap within 8 sFan off, bending cycle runs
4. Close door + finishLong press (4-8 s)Door closes, returns to idle

A few helpers on top of the four steps:

Safety check (current sense)Double-tapDuring the safety window
Skip safety checkLong pressDuring the safety window
Emergency resetFour quick taps within 10 sHomes the bender and returns to idle

The FarmBoard talks directly to your Bambu Lab printer over Wi-Fi. The printer publishes its state in real time and the FarmBoard fires each step at the exact right moment - door close at print start, door open + fan at the last layer, bender after cooldown, door close on finish. No button presses.

Same network

  • ✓The printer and the FarmBoard on the same Wi-Fi network.

Printer settings

  • ✓LAN-only mode on (Bambu Studio settings → Network → LAN Mode → on). Digital mode talks to the printer over the local MQTT broker, which is only exposed in LAN-only mode.
  • ✓Developer mode on (printer Settings → General → Developer Mode → on). Required for Bambu's LAN MQTT access.

Print file

  • ✓Processed by the FarmLoop app, version 2.7 or higher. The app renames the processed file with an FL_S2_ prefix and injects the silent timing markers the FarmBoard listens for.

FarmBoard

  • ✓Digital mode enabled on the FarmBoard's OTA page, with your printer's IP address and LAN access code entered.
  1. Enter OTA mode on the FarmBoardThe per-board gesture and web-UI access (http://farmloop.local) live on the Accessing the board (OTA mode).
  2. Fill in the Printer Connection card on the OTA pageWi-Fi SSID + password (your home / shop network) · Printer IP: printer Settings → Wi-Fi · LAN access code: printer Settings → Network → LAN Mode (8 digits) · Serial number: printer Settings → Device
  3. Tick Enable MQTT auto-triggerClick Save Printer Config, then Exit OTA Mode.

After reboot, the LED tells you what happened:

After the reboot

  • Wi-Fi and MQTT both connected5 slow blinks + 10 fast blinks. You're set.
  • Wi-Fi failed2 long blinks. Recheck SSID + password
  • MQTT failed4 long blinks. Recheck the printer IP and LAN access code, and confirm LAN Mode is enabled on the printer

LED on LED off · each strip shows 4 seconds

  • The limit switch is disabled while Digital mode is connected, so an accidental press during a running print doesn’t interfere. To use the limit switch for testing or maintenance, turn Digital mode off on the OTA page or take the printer off the network.
  • Local-only. MQTT runs on your LAN. Nothing leaves your network.
  • Wi-Fi drop fallback. If the connection drops mid-print, the FarmBoard falls back to manual mode automatically. When the network returns, MQTT reconnects.
  • Cancelled prints. Cancel from Bambu Studio or the printer screen and the FarmBoard opens the door and homes the bender automatically - no manual reset needed.
  • “Stopped” in Bambu Studio. Bambu Studio sometimes labels a successful FarmLoop print as Stopped instead of Finished. That’s a display quirk in how it reads the gcode end. The FarmBoard completes its sequence correctly regardless.
  • Testing the kit, doing one-off prints, or your printer isn’t on Wi-Fi → Mechanical.
  • Production, unattended runs → Digital. Set it up once; every FL_S2_* file after that runs the full cycle automatically.

With your trigger mode chosen, move on to Step 5, verify your installation.