Encrust
Alle Anleitungen

Noch nicht auf Deutsch übersetzt – die englische Version wird angezeigt.

Das Projekt unterstützen · Anleitung 17 von 17

Confirm your printer with one test print

5 Min. Lesezeit

A profile is confirmed when someone prints an Encrust file on that machine. Slice a small piece in your printer's own software, slice the same piece in Encrust, compare what both files state, print Encrust's, then report the result on GitHub with the vendor's file attached. Plan for the length of one small print.

Before you start

You need Encrust set up for your printer and one print behind you or about to happen, as in Your first print. Have the printer’s own slicer installed (the one the maker supplies) and a GitHub account, since reports live on GitHub. Resin, gloves and cleaning are as for any print.

Check whether your printer is confirmed

Open your printer under Printers. “Printed and confirmed” means someone has given it a 👍 on GitHub; “Not confirmed yet” means nobody has. As of 2026-10-07, the README names the ELEGOO Saturn 4 Ultra as the printer that has printed a file Encrust wrote. The printer’s own page shows its current state.

An unconfirmed profile isn’t known to be wrong. Its numbers are transcribed from a vendor specification or a public machine list, not measured, and every shipped file carries an UNVERIFIED header. A confirmation replaces “probably right” with “someone printed it”.

Slice a small piece in your printer’s own software

Slice a 10 mm cube, or any small model you made yourself, in the software that came with the printer. Save the file in the format it offers by default. Don’t use a model you didn’t make: the file goes public in the last step.

The project asks for this file because the vendor’s own slicer is the only source of what the machine expects. A sliced file’s header states the panel in pixels, the display size, the layer thickness, the mirror flags and the machine’s name (the .goo header is one example). The firmware matches that name string, so the profile has to spell it as the vendor’s file does.

Compare it with a file Encrust writes

  1. In Encrust, choose File, then Open sliced file…, and open the vendor’s file (the steps). Note Format, Machine, Panel, Stack and Layer height.
  2. Slice a piece with your printer and resin chosen in the Print block, open what Encrust wrote the same way, and read the same rows.

Format and Panel should match. If they don’t, say so in the report; that is a wrong profile and worth more than a confirmation. A different Machine text is worth reporting too. Differences in exposure and lift are expected: they belong to the resin and the profile, not the machine.

Copy Encrust’s file to the printer the way you copy any file and print it. Exposure and lift in a profile are starting points. The settings your resin maker and printer manual give you come first.

Look at three things: the printer accepted the file, the piece is the right size, and it isn’t mirrored. The mirror flags in a file say how the panel is mounted and come from the profile, so a mirrored print points at the profile.

Report it

On the printer’s page, press “Report a test print”. It opens that printer’s discussion on GitHub. A 👍 says it printed; a 👎 and a line saying what went wrong help just as much. The site counts these reactions to mark a printer confirmed.

Where the profile needs correcting, or the printer isn’t listed, open an issue with the “Printer profile” form instead. It asks for:

  • Printer: make, model and revision.
  • What you’re reporting: an unsupported printer, a wrong profile, or a working one.
  • Machine details: resolution in pixels, build volume in mm and the file extension its own slicer writes.
  • A small sliced file from its own slicer, zipped if GitHub refuses the extension.
  • Resin and settings you print with, if you want to share them.
  • What happened when you tried Encrust’s file, including “it printed fine”.

What a report makes public

Issues and discussions on Encrust’s repository are public. Anyone can read your GitHub username, your text and any attachment. A 👍 or 👎 is public too and shows your GitHub account. Before you attach the vendor’s file, know what it holds. A .goo has fields for the slicer’s name and version, the time it was sliced, the machine, the resin profile’s name, a price, two preview pictures of the model and anything else its header holds. Other containers differ. Attach only a model you made, from a slicer profile whose resin name and price you’re happy to publish.

Don’t paste photos with location data, screenshots showing your network addresses, the printer’s serial number or your computer’s user name in a file path.

If something goes wrong

The printer won’t take Encrust’s file

Compare the Machine text of both files, then the format and its version. Report both values in an issue; the machine name is what the firmware matches.

The print is mirrored or the wrong size

The profile’s mirror flags or panel size are wrong. Report it with the vendor’s file; the mirror flags are among the header fields in it.

GitHub won’t accept the file

Zip it and attach the zip.

Quellen