Platform parameters · groups grp_scanner_array, grp_laser_assignment
Multi-laser: scanner array and laser assignment
Large LPBF machines have several lasers, each with its own scanner that reaches only part of the
plate, its scan field. The buildstyle describes the scanners as a grid, the scanner array, and
gives every path of a layer to one laser. Where fields overlap, it shares the work so that all lasers finish at
about the same time: the layer is only done when the slowest laser is done.
In Advanced Toolpath Utility
Try it yourself
Make the profile you edit the platform profile first, otherwise the platform parameters have no effect.
Then open it, expand Platform Parameter › Scanner array and describe your machine: number of
scanners, their spacing, the size of one scan field and the platform. Under Laser assignment switch
Enable laser assignment on, choose a strategy and rebuild.
The Exposure Preview then draws every laser in its own colour. In the demo each of the four lasers
reaches the whole plate, so the load balancer is free to give every part to any laser: the busiest one ends
up with 28 % of the hatch length instead of 100 %, close to the ideal quarter, so the layer takes a little
over a quarter of the time of one laser.
The defaults describe a 250 × 250 mm platform with 2 × 2 scanners; the demo sets an array for its
60 × 60 mm plate with thirteen parts (parts/laser_parts.stl, generated by
tools/make_parts.py) and makes its "Docs demo" profile the platform profile for the
recording.
One large part: field split
When a single part is larger than one scan field, whole parts cannot be shared. The Field split
strategy cuts the hatch vectors at the field borders instead. Here four 32 mm fields, 24 mm apart, cover a
40 × 40 mm plate (parts/laser_plate.stl); in the 8 mm overlaps the vectors are shared between
neighbouring lasers, and the slowest laser gets 31 % of the hatch.
Try it
Scanner array
The scanners sit on a regular grid, centred on Array center X/Y, Scanner spacing apart. Every
scanner reaches a rectangle of Scan field width × height around itself. With a spacing smaller than the
field, neighbouring fields overlap and the buildstyle can choose the laser there. The lasers are numbered row
by row, starting at the bottom left, and each gets a colour spread evenly around the colour wheel, so any
number of lasers stays easy to tell apart.
Field split
Every hatch vector is cut at the borders of the scan fields. A piece inside one field goes to that laser; a
piece in an overlap goes to the candidate whose work would be smallest after taking it, measured as estimated
time (jumps, marking, delays from Laser timing) or as marked length. Ties go to
the lower laser number, so the result is the same on every run. Contours are never cut: a whole border goes to
one laser. On the laser plate the slowest laser gets about a third of the hatch, so the layer takes about a
third of the time of one laser.
Swimlanes
The swimlane strategies cut the platform into bands of Swimlane width across the gas flow and expose
them one after the other, the band furthest downstream first, so fumes and spatter are blown onto areas that
are already done. Inside a band the paths go to the lasers whose field contains their centre, again with the
smallest work first; the work counter starts empty in every band.
Swimlane never cuts a path: a whole hatch goes into the band of its centre.
Swimlane + clipping cuts the hatch vectors at the band borders, so no piece lies in two bands.
With Split contours at swimlanes the contours are cut as well.
Swimlane + reassign never cuts a vector: each one goes into the band of its middle point.
The swimlane strategies balance whole paths, so they are made for many parts: every part (or the piece of it
in one band) is exposed by one laser, as in the video above. Because the work counter starts empty in every
band, a band as wide as the platform shares all parts in one go; narrower bands balance each band on its
own.
The balancer works greedily in exposure order and does not look ahead. Parts that only one laser
can reach count against that laser only when their turn comes, so with small scan fields the shared parts
may already have gone to that laser before. The more of the plate every laser reaches, the closer the
result gets to an even split: in Try it, make the scan fields of the thirteen parts smaller and watch
the slowest laser grow. On a single plate, the hatch of one band is one path and goes to one laser; use
Field split there.
Layer time
After the assignment the power optimization runs separately for every laser, then the buildstyle estimates the
time of every laser in the final order. The layer time is the time of the slowest laser. It is stored with the
build (layer_built_time_estimation_ms_<n> per layer, built_time_estimation_ms
in total), and the export writes the total to export_info.json.
Parameters
Parameter
Default
Meaning
Array center X / Y
0 mm
Centre of the scanner grid.
Scanners in X / Y
2
Number of scanners per row and per column (1 … 16).
Scanner spacing X / Y
125 mm
Distance between neighbouring scanners.
Scan field width / height
175 mm
Reach of one scanner, centred on it.
Platform minimum / maximum X, Y
±125 mm
Platform bounds; the swimlanes cover them.
Enable laser assignment
off
Off: every path keeps the laser of its vector type.
Strategy
Field split
Field split, Swimlane, Swimlane + clipping or Swimlane + reassign.
Load balancing metric
Exposure time
Share the work by estimated time or by marked length.
Proximity weight
0
Above 0, geometry close to one scanner is pulled towards it.
Swimlane width
50 mm
Width of one band along the gas flow.
Split contours at swimlanes
off
Also cut contours (Swimlane + clipping only).
These are platform parameters: ATU reads them from the profile that is set as the platform profile, not from
the profile of the part. Every laser gets its own BSIDs: (laser number) × 1000 + vector type, so the volume
hatch 500 becomes 1500, 2500, 3500 and 4500; they use the scanning parameters of their vector type.
In the code
Follow the settings to the laser of every path in How the code works, and
change the defaults yourself with the recipes below.
How the code works
Six steps from the platform parameters to the laser of every path. 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.
Change it yourself
How to try a code change
Work on a copy or a git branch of the buildstyle project.
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.
Make the edit, save, compile the project in ATU and rebuild the exposures.
Check the result in the Exposure Preview or the 3D View, like in the video above.