Mainsail dashboard basics

How to use the G1OS web interface (based on Mainsail) to monitor and control the G1 printer. Accessible from any browser on the same network.

Connecting to the dashboard

Ensure the printer is powered on and connected to your Wi-Fi
Open a browser on the same network and go to http://g1os.local
If g1os.local doesn’t resolve:
- Try restarting the router (mDNS can take a moment to propagate)
- Find the printer’s IP in your router’s device list and connect directly (e.g. http://192.168.1.XXX)
- Note: the IP can change between sessions — use the hostname g1os.local to avoid tracking it

Temperatures: live temperatures for all three heating zones (Extruder / Extruder1 / Extruder2), bed, Raspberry Pi, and octopus board
Toolhead panel: axis positions, manual jogging controls
Macros: quick buttons for bed leveling, homing, etc.
Click the temperature graph to expand — useful for diagnosing temperature instability

Accessible from the left sidebar → Heightmap.

Shows the bed mesh from the last bed leveling run
Select “global” view to see the full bed surface
A flat mesh (all values near 0) means the bed is well-leveled
Large deviations (> 1 mm) indicate the bed needs releveling — adjust the Z lead screws manually

Upload .gcode files here for printing via Wi-Fi (more reliable than USB for large files)
Supports drag-and-drop
Files can also be sent directly from Ginger Slicer if the printer IP is configured in the slicer

The most important section for maintenance:

Config Files — edit Klipper configuration files directly in the browser:

Update Manager — keep all components up to date:

Click the refresh arrow (top right) to check for updates
Components: Klipper, Mainsail, Moonraker, Crowsnest, GingerConfigs, KlipperScreen, System
Click UPDATE ALL COMPONENTS to update everything at once
See Klipper firmware update for the full update procedure

System Loads — live CPU/RAM of the Raspberry Pi. If CPU is consistently > 80%, the Pi may be overloaded.

Devices panel — shows connected MCU boards (mcu, extruder_board) and their firmware versions

When reporting an issue to Ginger Additive support, include the log files:

Go to Machine section
Scroll to Config Files → click on the log files:
- klippy.log — main Klipper events and errors
- moonraker.log — API server logs
- crowsnest.log — camera service logs
Download and attach to your support message

Top-right power icon → opens Klipper Control and Host Control:

Option	What it does
Restart	Restarts Klipper software only (fast)
Firmware Restart	Restarts Klipper and flashes MCU firmware
Reboot	Full Raspberry Pi reboot (~60 s)
Shutdown	Powers down the Pi (printer will need physical power cycle)

Pauses longer than ~10 minutes leave a visible line on the print surface (a seam where layer deposition resumed). To minimize this:

Keep pauses under 5 minutes if possible
The printer maintains zone temperatures during a pause — the visual artifact is from material oozing during the pause, not from temperature loss
For very long pauses: lower all zone temperatures to reduce oozing, then reheat before resuming

Problem	Cause	Fix
`g1os.local` not found	mDNS not resolving	Use IP address, or restart router
Dashboard loads but shows “Disconnected”	Klipper crashed	Click Firmware Restart in the power menu
Temperature shows “Off” for all zones	MCU not connected	Check USB cable between Pi and Octopus board; see Klipper MCU communication lost
”Klippy is not running” banner	Klipper service stopped	Go to Machine → restart Klipper service
Dashboard slow / unresponsive	Raspberry Pi overloaded	Check CPU % in System Loads; reduce camera resolution if Crowsnest is running