tessafab rewrites one sliced plate with the pattern of a project saved by the app. Because it can rewrite the file in place, it also works as your slicer’s post-processing script, so every slice comes out patterned.
tessafab --project FILE [-o OUT] [-q] GCODE
| Argument | Meaning |
|---|---|
GCODE |
One plate’s G-code: plain .gcode or binary .bgcode. Rewritten in place unless -o is given. |
--project FILE |
The project to apply (.tessafab.json, saved by the app). It says which pattern, where the pieces sit and the settings. Also --project=FILE. |
-o, --output OUT |
Write the result here instead. Also --output=OUT. |
-q, --quiet |
No per-block log. |
-h, --help |
Print the usage. |
tessafab --project coaster.tessafab.json plate_1.gcode
tessafab --project coaster.tessafab.json -o patterned.gcode plate_1.gcode
Where to get it
| Build | Patterns | Where |
|---|---|---|
| In the app (Pro build) | Follows the app’s licence on this computer: one chosen piece in the free edition; every piece on the trial or with Pro. | macOS: /Applications/TessaFab.app/Contents/MacOS/tessafabWindows: %LOCALAPPDATA%\TessaFab\tessafab.exe |
| Built from source | One piece on one plate. | Build from source |
How a plate is matched
A project can cover many plates. tessafab finds which of the project’s plates this file is by its pieces, so the same project works for every plate of the model: run it once per plate file.
Before you can apply a project, its pieces must be placed (in the app’s Assemble step, or with the pattern on each piece). A project with no placed pieces is refused.
Output and exit status
On success it prints a summary to standard error (unless -q) and exits with 0:
tessafab: 3 block(s) rewritten, 0 kept -> plate_1.gcode
Without -q it also logs each top-surface block it rewrote or kept, and why.
| Exit | When |
|---|---|
0 |
Done. Also when the file was already processed: it’s left unchanged, so running twice is safe. |
1 |
The G-code couldn’t be patterned (a file not found or unreadable, a project problem, a plate the project doesn’t cover, an edition limit). |
2 |
Bad arguments, or a .3mf was given. |
On any problem the G-code is left unchanged and the exit status is not 0, so a slicer reports it instead of printing the wrong pattern:
tessafab --project: this project has no placed pieces; open it in the app to place them
The G-code was left unchanged.
A
.3mfis refused. Give one plate’s.gcodeor.bgcode; open a.gcode.3mfin the app instead. (Slicers pass plain G-code to post-processing scripts, so the hook isn’t affected.)
Your own patterns
The tool reads your patterns and presets from the app’s data folder, so projects using them work as in the app. Set TESSAFAB_LIBRARY to read them from another folder. See Files and folders.