Step by step
1Get the buildstyle
The buildstyle is a git repository: github.com/Autodesk/Open-LPBF-Buildstyle. Clone it, or download it as a ZIP from the repository page and unpack it.
git clone https://github.com/Autodesk/Open-LPBF-Buildstyle.git
Everything ATU needs is at the top of the repository: the project file OSS_MPBF_01.fsp,
the entry points in main, the reusable modules in lib and the texts of the user
interface in localization. Work on a git branch or a copy if you plan to change the code.
2Open and compile the project
In ATU choose File › Open › Project… and select OSS_MPBF_01.fsp. ATU opens one
project at a time; while one is open, Project… is greyed out, so File › Close Project
first. The Project Explorer shows the folders main, lib and
localization.
Click Compile in the toolbar (also Project › Compile). Compiling loads the scripts and declares the parameters; compile again after every change to the code. The Build Style Log at the bottom of the window then reports Compiling successful.
3Load a part and set the layer thickness
Open View › Data Management › Input Geometry Files and click Load…. Choose an STL, PLY, OBJ or 3MF file; the Import geometry dialog that follows sets the Layer thickness (µm), the thickness the part is sliced with, and shows the type of every object, here Part (solid). The videos of these pages use 30 µm. After OK the table lists the file as a build part, and Thickness (µm) below the list shows its layer thickness. + adds a further build part, Unload removes the selected one.
Support structures are loaded the same way, with a support type instead of Part (solid), see wall supports and solid supports.
4Create a parameter profile and assign it
All settings of the buildstyle live in parameter profiles. The project comes with a profile called default that cannot be edited, so make your own copy: in the Exposure Preview click Manage Profiles…, select default, click Duplicate… and type a Name of copy.
Then click Assign Profiles…. The table assigns a Parameter Profile to every build part. Below it, Platform Parameter selects the profile whose Platform Parameter groups drive the whole build: laser timing, gas flow and build order, and the export. Pick your profile in both places and confirm with OK.
Every feature page assumes this setup: the profile you edit is assigned to the part and is also the platform profile. A platform parameter changed in a profile that is not the platform profile has no effect.
5Build and inspect the exposures
Click Execute in the toolbar. Under Steps the dialog lists the parts of a run:
Execute Preprocessing, Calculate Exposure Data, Execute Postprocessing and
Export Data; keep the export off for now. Exposure Calculation Range sets the layers: for the
whole part tick Use bottom layer for the start and Use top layer for the end. Click
OK. The dialog keeps its settings for the next run. In the video, recorded with the previous version
of the buildstyle, the Build Style Log shows the estimated exposure time, 0:14:54 for the hatch plate. The
current version writes the estimate to export_info.json when you export (see
Export formats).
The Exposure Preview shows one layer at a time; the slider on its right changes the layer. The
colours are the vector types (build style ids, set in main/vector_types.js): borders red,
fill contours orange, volume hatch green, upskin yellow, downskin hatch blue, supports grey. The
3D View shows the part in 3D and can show the toolpaths of the layers as well.
6Change a parameter and rebuild
Click Open Profile in the Exposure Preview and choose your profile. The dialog shows the parameter tree: build part parameters first (borders, hatching, skins, supports, scanning), then the platform parameters. In the video Hatching › Volume › Pattern goes from Meander to Chessboard. Confirm with OK and click Execute again: the preview shows the new hatch.
Every feature page explains its parameters with an interactive model, starting with hatching. The tutorials page lists all features.
7Export a toolpath package
Click Execute once more, tick Export Data, choose a filter under Use Export Function of Current Project and a file with Select Export Target…, then OK. The buildstyle writes LSR, CLI+ or 3MF toolpath packages with the parameters and a build job image. The dialog keeps the export switched on for the next run. Export formats shows what is in each package.
8Find the code and change a default
The buildstyle is plain JavaScript. Double-click a file in the Project Explorer to open it in ATU, or open
the project folder in an editor such as VS Code: ATU writes jsconfig.json and type
declarations into the folder, so the editor can offer code completion.
| File | What is in it |
|---|---|
main/main.js | The entry points that ATU calls, and a glossary of the terms. |
main/param_groups.js | The parameter tree with the default values. |
main/vector_types.js | The vector types (build style ids) with their default laser, power and speed. |
main/settings.js | Reads the parameters into settings objects and checks them. |
main/exposure_layer.js | Builds the vectors of one layer: contours, hatching, skins, supports. |
main/postprocess.js | Exposure order, power optimization and the time estimate. |
main/export_main.js | The export filters; the writers are in lib/export. |
localization/lang_en.json | The names and descriptions shown in the profile dialog. |
Messages of the buildstyle, such as warnings about settings that do not fit together, go to the
Build Style Log. The estimated exposure time is written to export_info.json on export.
- Find the parameter in
main/param_groups.js(or the vector type inmain/vector_types.js) and edit its default value. - Save the file and compile the project in ATU.
- Create a new profile to get the new defaults: existing profiles keep the values they have.
- Rebuild and check the Exposure Preview.
Every feature page ends with Change it yourself: recipes with the exact edit, for example a faster volume hatch or fill contours on by default, and a walk through the code under How the code works.