Open LPBF Buildstylefor Autodesk Fusion
Platform parameters · group grp_laser_timing

Laser timing

The laser spot is moved by two mirrors. Between the vectors it jumps with the laser off, and after every jump and every marked vector the mirrors need a moment to settle. Jump speed, mark delay and jump delay describe this scanner; minimum jump delay and jump length limit let short jumps wait less. They do not change a single path; they are used to estimate the exposure time, for the time column of the LSR export, for the return times of the power optimization and to balance the lasers of a multi-laser machine.

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 and counted a mark delay for every contour edge. The current version stores the estimate with the build and writes it to export_info.json on export, and counts one mark delay per contour, so its numbers are slightly lower.

    Make the profile you edit the platform profile first, otherwise the platform parameters have no effect. Open it, expand Platform Parameter › Laser timing and change a value. Rebuild, export, and read estimated_exposure_time_ms in the export_info.json next to the exported job.

    The demo makes its "Docs demo" profile the platform profile for the recording and restores "default" afterwards. It also checks that the toolpath did not change: layer 50 has the same vectors before and after. The demo part parts/hatch_plate.stl is generated by tools/make_parts.py.

    Try it

    7000 mm/s 10 µs 50 µs 0 µs 0 (off)
    marking (laser on) mark delay jump jump delay

    Where the time goes

    On the hatch plate almost all of the time is marking: 10 405 mm of hatch per layer at 1200 mm/s. The Build time view adds the rest the way the buildstyle's estimate does. A mark delay is spent every time the laser switches off: after each of the 471 hatch vectors of a layer, but only once for the border, whose corners are marked without stopping. Every jump to the next hatch line (0.1 mm) and every jump between the paths adds jump time and a jump delay. Raise the mark delay from 10 to 200 µs and the build gets about 9 s longer.

    Short jumps

    Many scanner controllers let the mirrors settle faster after a short jump. Set a jump length limit above 0 and jumps shorter than the limit wait between the minimum jump delay (length 0) and the full jump delay (length = limit); see the Jump delay view. With a minimum of 10 µs and a limit of 1 mm, the 0.1 mm hatch jump waits 14 µs instead of 50 µs. The limit 0, the default, switches the scaling off.

    Several lasers

    On a multi-laser machine every laser has its own clock: each path counts for the laser it was assigned to, and the layer takes as long as the slowest laser. The same delay rules are used when the load balancer shares the paths between the lasers.

    Short vectors

    The One vector view shows the cycle of one hatch vector: marking, mark delay, the jump to the next line and the jump delay. For a 10 mm vector the delays hardly matter; for a 0.5 mm vector they are already 15 % of the time. Parts with many short vectors, such as fine lattices or small islands, are where the scanner timing shows up in the estimate.

    The estimate is the time the laser needs. Recoating, mirror acceleration and other waiting times of the machine are not included, and the values here are typical defaults, not those of a specific scanner.

    Parameters

    ParameterDefaultMeaning
    Jump speed7000 mm/sSpeed of the spot while the laser is off.
    Mark delay10 µsWait after every hatch vector and at the end of every contour.
    Jump delay50 µsWait after every jump (long jumps, or all jumps without scaling).
    Minimum jump delay0 µsWait after a jump of length 0 when the scaling is on.
    Jump length limit0 mm (off)Jumps shorter than this wait less; 0 switches the scaling off.

    These are platform parameters: ATU reads them from the profile that is set as the platform profile, not from the profile of the part.

    In the code

    Follow the values to the estimate, the power optimization and the LSR export in How the code works, and change the defaults yourself with the recipes below.

    How the code works

    Eight steps from the platform parameters to the places that use them. 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.

    marking mark delay jump jump delay

      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. Export the job and check estimated_exposure_time_ms in export_info.json.