Noch nicht auf Deutsch übersetzt, daher die englische Fassung.
Dateiformate
Which file does your resin printer read?
It depends on the machine, not the brand. In Encrust's catalogue of 199 profiles from 24 makers, 28 Anycubic machines take 27 different extensions, while 25 Elegoo machines take four names, mostly .goo and .ctb. One app writes the file each profile names, in the format that machine reads.
Twenty-eight Anycubic machines, twenty-seven different extensions: .pwmb, .pm3, .pwma, .pm5 and twenty-three more. Elegoo’s 25 machines need four format names, Creality’s 22 three, Phrozen’s 23 five. Counted from Encrust’s printers.json, which holds 199 printer profiles from 24 makers, the brand tells you very little about the file.
Here is the part that surprised us. The catalogue has 43 format names, and the two biggest are both versions of one container: ctb-encrypted (49 machines) and ctb5 (35) are the Chitu .ctb at two revisions, and together they cover 84 machines. Which revision a machine reads is a property of the machine.
Pick your printer in Encrust and it writes the file that machine reads. The catalogue covers 199 machines, and what Encrust checks is the file itself, read back before you print.
The sections below answer one question each: how many machines per format, what each of the four big brands needs, which eight machines take a file over the network, what Encrust checks and how Encrust chooses the format.
How many machines use each format
The catalogue has 43 format names over 199 machines. The ten biggest cover 163 of them. Counted from src/data/printers.json:
| Format name | Machines | Which makers |
|---|---|---|
ctb-encrypted |
49 | EPAX 13, Phrozen 8, Elegoo 6, Nova3D 6, HIFUN 5, UniFormation 4, ApexMaker 2, Newbie Box 2, EMAKE3D 1, JAMG HE 1, Peopoly 1 |
ctb5 |
35 | EPAX 9, Elegoo 6, QIDI 5, Phrozen 4, Peopoly 4, Creality 3, Wanhao 2, EMAKE3D 1, LYNcase 1 |
cxdlp4 |
14 | Creality 9, PIOCREAT 3, PioNext 2 |
goo |
12 | Elegoo 12 |
crmaslice |
12 | Carima 12 |
zip of greyscale PNGs |
12 | Phrozen 8, Wanhao 2, Kelant 1, Zortrax 1 |
cxdlp3 |
10 | Creality 10 |
cws |
7 | Nova3D 6, Carima 1 |
svgx |
7 | FlashForge 6, Voxelab 1 |
fdg |
5 | Voxelab 3, FlashForge 2 |
| 33 other names | 36 | Anycubic 28, Phrozen 3, Prusa 2, PioNext 2, Elegoo 1, and others |
The last row is mostly Anycubic’s own extensions, plus .prz (2 machines) and .cxline (2) and single-machine names such as goo5, phz, sl1 and sl1s. The .ctb layouts are in the format notes.
Elegoo, Anycubic, Creality and Phrozen
Elegoo’s 25 machines split 12 to 13. Twelve write .goo, the container Elegoo publishes a specification for, one writes goo5, six write ctb-encrypted and six write ctb5.
Creality’s 22 machines are 10 at cxdlp3, 9 at cxdlp4 and 3 at ctb5. The .cxdlp header carries a model code such as CL-60 picked out of the machine’s name, which is why a profile without one is refused rather than guessed at (the Creality notes).
Phrozen’s 23 machines take five formats: 8 write the .zip, 8 ctb-encrypted, 4 ctb5, 2 .prz and 1 .phz. The .zip holds one gcode program, two previews and one greyscale PNG per layer.
Anycubic’s 28 machines are the odd one out. Photon Workshop’s container is one layout at several revisions, and each machine’s firmware looks for its own extension: 27 names for 28 machines, because the Photon M3 Plus and the Photon Mono X 6K both use .pwmb.
.pwmb is the shared one: the Mono X 6K and the M3 Plus both write it, at container revision 517, while other extensions sit at 1, 515, 516, 517 or 518 (the Anycubic notes list every machine). Encrust takes the revision from the printer profile and not from the name you type.
Which eight machines take a file over the network
Eight of 199 profiles can send a file over the network: six over SDCP, two over PrusaLink (what each connection value means). The other 191 take it on a stick, though only 188 of them say connection = "none". The Elegoo Mars 3 Pro, Phrozen Sonic Mini 8K and UniFormation GKtwo name no connection, and the profile code defaults that to a stick.
| Protocol | Machines | Note |
|---|---|---|
| SDCP | Elegoo Saturn 4 Ultra, Mars 5 | version 3 |
| SDCP | Elegoo Saturn 3 Ultra, Mars 4 Ultra | version 1 |
| SDCP | Elegoo Mars 5 Ultra, Saturn 4 Ultra 16K | version not stated in the notes |
| PrusaLink | Prusa SL1, SL1S Speed | writes .sl1 and .sl1s |
The versions are from the SDCP notes: Elegoo ships version 3 from the Saturn 4 Ultra and Mars 5 onwards, version 1 on the Saturn 3 Ultra and Mars 4 Ultra. By the protocol document we read (CBD Technology’s SDCP V3.0.0) and our notes on it, version 3 sends discovery, control and the file upload without encryption or authentication. Whether your network is a place for that is your call; the stick works on every machine here.
What Encrust checks in the file it writes
One app, 199 machines, 24 makers: Encrust writes the container each printer reads, at the revision its profile names. Per the README, Encrust reads back the file it wrote and walks every layer of it for islands, suction cups and weak necks before you print, so the check runs on what the file really cures, not on the model. A wrong island or a thin neck shows up before the print, not in the vat.
Slice your own model for your own printer and read the Check result before you send the file. Print a calibration piece first, and use the exposure your resin maker gives you; the exposure post explains why a number does not carry over between layer heights.
How Encrust chooses the format
The output file’s extension decides the format, and the printer profile decides which extension the save dialog offers first. The command-line reference states the first rule: a name ending .goo writes a .goo, a name ending .ctb writes a .ctb, and a container name is refused without a printer or profile. Pick your printer and the dialog opens on the right name. Type another name and the name wins.
A name cannot carry a revision, so for .pwmb, .cxdlp and .ctb the profile supplies it. That is why the revision comes from the printer you picked. It also means a profile that says the wrong format writes the wrong file: the format column in this post is the one thing in a profile worth checking against your manual before the first print. A browser tab cannot send to any of the eight network machines; the browser build says why.
Quellen
- Encrust: file formats · One note per container, with the offsets and where each reading came from
- Encrust: Anycubic Photon Workshop containers · The extension and revision table, including .pwmb at two revisions
- Encrust: profiles, "How a machine is reached" · What connection none, sdcp and prusa-link mean
- Encrust: SDCP, the network protocol · Which Elegoo machines speak which version
- Encrust: README, "Features" · Reads back the file it wrote and walks every layer