Open LPBF Buildstylefor Autodesk Fusion
Platform · export filters

Export formats

A machine does not read the ATU project, it reads a file. The buildstyle declares six export filters for three formats: LSR, a plain table with one line per vector; CLI+, the common layer interface with laser settings per path; and the 3MF toolpath extension with one XML file per layer. LSR and CLI+ come as a ZIP with one file for the whole build or one file per layer. The 3MF filters differ in how the power changes along a path. Every package also contains the build job image, the parameters and an export info file.

In Advanced Toolpath Utility

    Try it yourself

    Click Execute in the toolbar. In the dialog tick Export Data next to the exposure steps, set the layer range (for the whole part: Use bottom layer and Use top layer), pick a filter under Use Export Function of Current Project and choose the file with Select Export Target…. OK builds the exposures of the range and writes the package in one run.

    The dialog keeps its settings for the next run, including the export. Untick Export Data again if the next Execute should only build the exposures.

    In the video the power wedge (100 layers, power optimization on) is exported as CLI+ in a single file: a 542 KB package whose toolpath.cli has 2610 lines, $$LAYERS/100, one $$HATCHES and three $$POLYLINE lines per layer. The last two slides show the content of that very package. The demo writes only into the project's work\exports folder and sets the Execute dialog back to its previous settings afterwards. The part parts/power_wedge.stl is generated by tools/make_parts.py.

    Try it

    1 / 5
    hatch, thicker = more power contour selected path
    
              

    In the package (red: toolpath files, filled: the file shown above)

      Click a line of the file, or move the slider, to see which path it describes.

      One layer, three formats

      The drawing is a small island of layer 50 at z = 1.5 mm: four hatch vectors and the contour around them, with the powers of the power optimization (shorter vector, less power). The text below is what the writers of the buildstyle produce for it, line for line; it is the output of the real writer code, run on this layer.

      • LSR has one line per vector: power, a direction vector (0 0 −1), the start and end point, focus, speed and the start time. The start time comes from the laser timing; in a single file it runs on over all layers, in a file per layer it starts at 0.
      • CLI+ writes a header and then, per layer, every path with its parameter set, laser, power, speed and focus. A contour is a $$POLYLINE that repeats its first point, the hatch is one $$HATCHES line. When the power changes along a path, $$POWERS lists where it changes.
      • 3MF toolpath stores the coordinates in µm and every power as a factor of the profile maximum. Every path becomes one segment, and the factor sits on its children: one f per hatch line, and on every contour point the f of the line it closes. With ramps, hatch pieces that touch and point the same way get f1 and f2, so the power runs smoothly from piece to piece. Contours always keep one power per line.

      Turn on Segment splitting to see the difference: every vector becomes a row of short pieces with rising power. LSR gets one line per piece, CLI+ a $$POWERS list and 3MF ramps. Without segment splitting the two 3MF filters write the same file.

      The six filters

      Filter in the Execute dialogPackageToolpath files
      LSR toolpath (ZIP, single file).ziptoolpath.lsr
      LSR toolpath (ZIP, one file per layer).ziplayers/layer_00001.lsr …
      CLI+ toolpath (ZIP, single file).ziptoolpath.cli
      CLI+ toolpath (ZIP, one file per layer).ziplayers/layer_00001.cli …
      3MF toolpath with power ramps.3mfToolpath/layer30.xml …
      3MF toolpath with power per edge.3mfToolpath/layer30.xml …

      Next to the toolpath every package has build_job_image.png, the platform parameters and the parameters of every part as JSON, and export_info.json with the project, the filter, the date, the number of layers, the layer thickness and the estimated exposure time. The 3MF package puts them under Metadata/ and adds the 3D model of the parts.

      Things worth knowing, checked in the exported files: the time column of the LSR adds up to the estimated exposure time (280.57 s for the 100 layers of the power wedge). LSR writes the powers with 9 significant digits, so a power of 150.6 W can appear as 150.600006; CLI+ rounds to 0.1 W. A single CLI+ file has a $$LAYER line for every layer of the part, also outside the exported range, while the files per layer skip empty layers.

      Sample packages

      The power wedge of the video, exported with all six filters. To keep the downloads small they only contain layers 49 to 51 (z = 1.47 to 1.53 mm). Power optimization and segment splitting are on, so the power changes along the vectors and the two 3MF variants differ.

      In the code

      Follow a layer from the toolpath of ATU to the files in the package in How the code works, and change the number format or the compression with the recipes below.

      How the code works

      From the filter declaration to the files in the package. Scroll through the steps: the drawing on the left shows the layer and the line the step writes. Highlighted lines are the ones the text talks about; the file names link to the source.

      hatch contour written line

        Change it yourself

        How to try a code change
        1. Work on a copy or a git branch of the buildstyle project.
        2. 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.
        3. Make the edit, save and compile the project in ATU.
        4. Export again with Execute, like in the video above, and open the package.