Open LPBF Buildstylefor Autodesk Fusion
Build part parameters · group grp_scanning

Scanning (laser settings)

Every vector type has its own build style ID (BSID) and its own laser settings: laser number, power, speed and focus. The Scanning group holds one set per vector type. The settings do not change the toolpath geometry, but they decide how much energy each path brings into the powder and how long the build takes.

In Advanced Toolpath Utility

    Try it yourself

    This video was recorded with the previous version of the buildstyle, which printed the estimate in the Build Style Log. The current version writes it to export_info.json on export (estimated_exposure_time_ms): 0:14:54 at 1200 mm/s and 0:11:17 at 1600 mm/s, within a second of the video. The speed settings work exactly as shown.

    Open the parameter profile of your part (Open Profile in the Exposure Preview), expand Scanning and the vector type you want to change, for example Volume hatching. Type a new speed, rebuild, export, and read the new estimate in export_info.json.

    In the demo, ATU reports 1600 mm/s for BSID 500 after the change, and the estimate drops from 0:14:54 to 0:11:18. The demo part parts/hatch_plate.stl is generated by tools/make_parts.py.

    Try it

    1200 mm/s
    volume hatch (BSID 500) first border (BSID 100) delays and jumps ATU estimate in the video

    Speed and build time

    The hatch plate (40 × 28 mm, 100 layers) has about 10 400 mm of volume hatch per layer and only 137 mm of border. Almost all of its exposure time is hatch length ÷ hatch speed. The Build time view uses the same sum as the buildstyle's estimate: marking time, plus a 10 µs mark delay per hatch vector and per contour, a 50 µs jump delay per jump and the jumps at 7000 mm/s (see Laser timing). The curve passes within two seconds of the two estimates ATU printed in the video: 0:14:54 at 1200 mm/s and 0:11:18 at 1600 mm/s.

    Energy per volume

    Speed also changes the energy. A common rule of thumb is the volume energy density E = P / (v · h · t), with power P, speed v, hatch distance h and layer thickness t. The defaults give 280 W / (1200 mm/s · 0.1 mm · 0.03 mm) = 78 J/mm³. At 1600 mm/s it drops to 58 J/mm³, unless the power goes up to 373 W. Try both sliders in the Energy view.

    Different settings for different vector types

    The Vector types view lists the defaults of all fourteen types. Downskin types get far less energy per mm, because there is loose powder below them that cannot carry the heat away. Borders are slower than the hatch for a cleaner surface. The core hatch, hidden inside the part, runs at the highest power and speed.

    Laser number and focus

    The two other settings of a vector type have no slider here. The buildstyle writes them on every path of that type: laser_index (0-based, so laser 1 in the dialog is 0 in the data) and focus, the focus offset in mm from the nominal focus position (0 = nominal). The machine, or an export such as the CLI+ format, then decides which spot size exposes the path. The laser number also counts for the buildstyle: the time estimate and the power optimization keep one timeline per laser, so a vector type on laser 2 runs in parallel with the rest. With laser assignment switched on, the post-processing replaces it by the laser of the scan field. With the defaults every type uses laser 1 and focus 0.

    The build time view is a simplified estimate for this one part: it counts every hatch line as one vector and the jumps between hatch lines as one hatch distance. The energy window is for illustration only; the right values depend on material and machine.

    Parameters (one group per vector type)

    ParameterRangeMeaning
    Laser number1–16Which laser exposes this vector type.
    Power0–2000 WLaser power.
    Speed1–20000 mm/sScan speed of the laser spot.
    Focus−50–50 mmFocus offset; 0 = focused on the powder.

    Jump speed, mark delay and jump delay are platform parameters (group Laser timing); they apply to all vector types.

    In the code

    Follow the settings from the vector type table to the time estimate in How the code works, and change the defaults yourself with the recipes below.

    How the code works

    Six steps from the vector type table to the time estimate. Scroll through them: the drawing on the left shows what each piece of code does. Highlighted lines are the ones the text talks about; the file names link to the source.

    volume hatch first border delays and jumps

      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, compile the project in ATU and rebuild the exposures.
      4. Check the result in the Exposure Preview or the 3D View, like in the video above.