Mainsail and OctoPrint Integration

Theoretical Background & Network Architecture

Modern additive manufacturing has evolved beyond manual file transfers via SD cards and USB drives. Today's industrial and hobbyist 3D printers rely on network-based host managers to orchestrate, monitor, and automate printing processes. In the OrcaSlicer ecosystem, this is achieved through direct API integrations with remote printer controllers like Mainsail/Fluidd (powered by Moonraker/Klipper) and OctoPrint.

Understanding the underlying communication protocols and network workflows is essential for configuring a reliable, secure, and automated print environment.

       +-------------------------------------------------------------+
       |                         OrcaSlicer                          |
       |  (Slicing Engine, G-code Generator, Web-view Interface)     |
       +------------------------------+------------------------------+
                                      |
                       HTTP POST      |  WebSocket
                    (REST API File    | (Real-time Telemetry,
                       Uploads)       |  Status Subscriptions)
                                      v
       +-------------------------------------------------------------+
       |             Printer Host Controller / API Gateway           |
       |      - Moonraker (Klipper) or Flask Backend (OctoPrint)     |
       +------------------------------+------------------------------+
                                      |
                                      |  Unix Socket / Serial (UART)
                                      v
       +-------------------------------------------------------------+
       |               Microcontroller Unit (MCU) / Firmware          |
       |          - Klipper-MCU, RepRapFirmware, or Marlin           |
       +-------------------------------------------------------------+

1.1 Remote Printer Management Concepts

Remote printer management decouples the computational slicer (which translates 3D models into path instructions) from the printer controller (which manages the execution of these instructions) and the MCU (which executes hardware-level motion control).