Firmware restart
A firmware restart reloads the Klipper firmware and all configuration files without rebooting the Raspberry Pi. It is faster than a full reboot (~10–15 seconds vs. ~60 seconds) and is the correct action after most configuration changes.
When to use it
Section titled “When to use it”- After editing any file in
~/printer_data/config/(e.g.,printer.cfg) - After saving new PID values or calibration results that require a config reload
- After a slicer sends
FIRMWARE_RESTARTat the end of a print - When Klipper shows “Klippy not connected” but the Raspberry Pi is still running
When NOT to use it (use full reboot instead)
Section titled “When NOT to use it (use full reboot instead)”- After a G1OS (system) update — use Host Control → Reboot
- If the display or network is unresponsive
- After updating Moonraker or Mainsail
How to do it — from G1OS (Mainsail)
Section titled “How to do it — from G1OS (Mainsail)”- Open
http://g1os.localin a browser - Click the power icon in the top-right corner of the dashboard
- In the dropdown menu, select Firmware restart
- Klipper restarts — the dashboard briefly shows “Klippy not connected” then reconnects automatically within 10–15 seconds
How to do it — from the Klipper console
Section titled “How to do it — from the Klipper console”In Mainsail, open the Console tab and type:
FIRMWARE_RESTARTPress Enter. Same effect as the dashboard button.
How to do it — from the display (KlipperScreen)
Section titled “How to do it — from the display (KlipperScreen)”On the touchscreen display:
- Tap the Settings (gear) icon
- Tap Restart → Firmware restart
What it does
Section titled “What it does”- Reloads
printer.cfgand all included config files - Re-initializes all stepper drivers and heaters
- Clears any Klipper error state (including “Emergency stop” triggered by software)
- Does not reboot the Raspberry Pi or reset the network
- Does not clear uploaded G-code files
After a firmware restart
Section titled “After a firmware restart”- Home the printer before printing — the position is lost on restart
- If you changed temperatures or PID values, they are now active
- If Klipper fails to connect after restart, check the console for config errors
Related notes
Section titled “Related notes”- Klipper firmware update — full G1OS update procedure
- Mainsail dashboard basics — navigating the G1OS interface
- G1OS installation — full system reinstall
- Klipper MCU communication lost — when restart doesn’t help