Local printer transfer

Move G-code to a Moonraker printer.

Version 3 connects to compatible Klipper and Moonraker printers on the same local network, including the factory QREATTE Slice1 environment.

Available in Version 3

Moonraker v0.8 access responses and direct HTTP 201 upload receipts are supported. The factory Slice1 configuration does not need to change.

Before connecting

Use the direct Moonraker endpoint.

The printer and Apple device must be reachable on the same trusted local network. Fluidd is the web interface; Moonraker is the API EFUGY connects to.

Address
Your printer’s current local-network address
Protocol
HTTP unless your setup intentionally uses HTTPS
Moonraker port
Commonly 7125
Route prefix
Blank for the factory Slice1 configuration
API key
Off for the factory Slice1 setup unless its authorization was changed
Fluidd
Available in a browser as a manual transfer path

Keep private addresses private: do not publish your printer’s local IP, network name, credentials, or API key in screenshots or support posts.

Two ways to move the file

Choose direct transfer or Files.

Both paths begin with a complete preview and end with a separate decision to start the printer.

In-app option

Direct Moonraker transfer

Connect to a compatible endpoint, upload the reviewed G-code, verify the receipt and destination, then confirm the print start separately.

Manual option

Files and Fluidd

Export G-code from EFUGY, open Fluidd in a browser, upload the file, inspect the receipt and destination, then start only when the machine is ready.

Improved in Version 3.3

Factory Slice1 response formats now work in the app.

Version 3.3 supports Moonraker v0.8 without asking the owner to edit the factory printer configuration.

  1. 01

    Connect to Moonraker.

    EFUGY accepts the smaller /access/info response returned by v0.8, even when newer optional fields are absent.

  2. 02

    Upload the reviewed file.

    The app accepts both wrapped upload results and the direct HTTP 201 JSON receipt used by the factory Slice1 environment.

  3. 03

    Check the receipt.

    Authorization, checksum, byte count, and destination-path checks remain part of the transfer flow.

  4. 04

    Start only when ready.

    Upload does not automatically start the printer. Check the machine state and confirm the start separately.

Manufacturer Beta note: API-format support does not certify every firmware or machine configuration. Preview the file and use a raised-nozzle dry run before a first physical print.

Factory Slice1 connection

Use Moonraker on port 7125.

Enter the printer’s current local address, use port 7125, leave the route prefix blank, and keep the API key off unless the factory authorization has been changed. Port 80 opens Fluidd, not the direct Moonraker API.