Local printer transfer

Move G-code to a Moonraker printer.

Connect EFUGY to a compatible Klipper and Moonraker endpoint on the same local network, or export through Files when direct transfer is not available.

Version 3.2 note

Factory QREATTE Slice1 systems using Moonraker v0.8 can reject direct uploads in Version 3.2. Manual Fluidd upload remains available.

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
Use in a browser for the Version 3.2 manual-upload workaround

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

Use direct transfer when it works. Use Files when it does not.

Both paths begin with the same preview and machine check.

Optional

Direct Moonraker transfer

Connect to a compatible endpoint, upload the reviewed G-code, confirm the destination, and follow the printer’s status before starting.

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.

Factory Slice1 in Version 3.2

No printer-side change is required.

Moonraker v0.8 returns an older access and upload response format that Version 3.2 does not recognize. The printer configuration can still be correct.

  1. 01

    Export from EFUGY.

    Save the reviewed G-code through Files or another available iOS destination.

  2. 02

    Open Fluidd.

    Use the printer’s Fluidd web interface on the same trusted local network.

  3. 03

    Upload the file.

    Confirm the filename, size, destination, and visible upload result before selecting it.

  4. 04

    Verify before starting.

    Review the printer state, then use a raised-nozzle dry run for a new or changed profile.

Coming next

The next update improves Slice1 transfer compatibility.

The update accepts both response formats while keeping EFUGY’s existing upload and print-start checks. Check the installed version before using direct transfer.