Laser Powder Bed Fusion · Machine Control

Machine control software for metal laser powder bed fusion

C1 Technologies develops, integrates and supports the software that runs LPBF metal 3D printers: from build data and laser scanning to sensors, operator interface and process data. Built on the open-source Autodesk Machine Control Framework.

Discuss your machine How LPBF works
  • Open-source core
  • C++ drivers & plugins
  • Web-based HMI
  • 3MF Toolpath
One LPBF layer: hatch scan, contour scan, platform lowering and recoating. The hatch direction rotates by 67° from layer to layer.
BSD-3-ClauseOpen-source framework core, no vendor lock-in
Headless C++Control server runs inside the machine
REST · OpenAPI 3.0UI and integrations use the same public API
3MF ToolpathOpen build data from CAD/CAM to the scanner

The process

How laser powder bed fusion works

LPBF, also known as selective laser melting (SLM) or DMLS, builds dense metal parts layer by layer. A laser melts thin layers of metal powder exactly where the part should be. A single build can consist of thousands of layers and millions of laser vectors, and every one of them is executed by the machine control software.

  1. 1Inert gas supply
  2. 2Fiber laser
  3. 3Beam expander
  4. 4Galvo scanner
  5. 5F-theta lens
  6. 6Protective window
  7. 7Layer camera
  8. 8O₂ sensor
  9. 9Laminar gas flow
  10. 10Recoater
  11. 11Powder supply (dosing piston)
  12. 12Part with supports
  13. 13Heated build plate
  14. 14Z axis (build piston)
  15. 15Powder overflow
  16. 16Gas filter
  17. 17Circulation blower
Schematic cross-section of an LPBF machine, not to scale: the layer thickness is exaggerated.

  1. Build preparation

    The 3D model is oriented, supported and sliced into layers. Scan vectors and laser parameters are assigned per part, region and hatch.

    build file import (3MF Toolpath), parameter sets, job queue

  2. Inert atmosphere

    The chamber is flooded with argon or nitrogen until residual oxygen is very low, typically below 0.1 %. A laminar gas flow carries fumes and spatter away from the laser.

    gas and oxygen control, interlocks, alarms

  3. Powder recoating

    A recoater spreads a thin layer of metal powder over the build platform, typically 20–100 µm thick.

    recoater motion, powder dosing, layer imaging

  4. Laser exposure

    Galvanometer scanners steer one or more fibre lasers across the layer. Contour and hatch vectors melt the powder; the melt pool solidifies within milliseconds.

    scanner and laser control, multi-laser coordination, monitoring

  5. Lower and repeat

    The platform lowers by one layer thickness and the cycle starts again, thousands of times over hours or days.

    state machines, recovery after interruptions, build journal

  6. Post-processing

    After cooling, parts are depowdered, stress-relieved and cut from the build plate, then finished by heat treatment, HIP, machining or surface treatment.

    traceable build records for quality assurance

Applications

What LPBF builds

Complex metal parts that are hard or impossible to machine or cast: internal cooling channels, lattices, lightweight structures and assemblies consolidated into one part.

  • Aerospace & spaceInjectors, combustion chambers, brackets, heat exchangers
  • Energy & turbomachineryBurner tips, turbine components, repair
  • Medical & dentalPatient-specific implants, dental frameworks
  • Automotive & motorsportPrototypes, turbochargers, lightweight parts
  • ToolingConformally cooled mould inserts
  • Research & educationAlloy and process development
Hot-fire test of a 3D-printed rocket engine injector at a NASA test stand, with a bright exhaust plume.
Hot-fire test of a 3D-printed rocket injector at NASA Marshall Space Flight Center. NASA/MSFC/David Olive, public domain, via Wikimedia Commons
Scanning electron microscope image of spherical stainless steel powder particles.
Spherical 316L stainless-steel powder (SEM). Michaltoczko, CC BY 4.0, Commons
Prototype turbochargers made by selective laser melting, displayed at a trade fair.
Prototype turbochargers made by selective laser melting. Matti Blume, CC BY-SA 4.0, Commons
Finished metal parts on the build plate inside the chamber of an LPBF machine.
Finished parts on the build plate of an LPBF machine. René Volfík / FZU, CC BY-SA 4.0, Commons
Hot-fire test of a subscale rocket engine on a test stand, with a bright green exhaust plume.
Hot-fire test of a subscale RS-25 engine model with a 3D-printed fuel injector. NASA/MSFC, public domain, via Wikimedia Commons
Metal parts printed by laser powder bed fusion inside the build chamber.
Printed parts in the build chamber. René Volfík / FZU, CC BY-SA 4.0, Commons

What we do

Software and integration for LPBF machines

From a single driver to a complete machine controller: we develop the software layer between your build data, your hardware and your operators.

Machine control software

LPBF controllers built on AMCF: state machines for the complete build cycle, recoating and exposure sequences, interlocks with the PLC and recovery after interruptions.

Hardware & driver integration

Scanner and laser controllers, PLCs, motion axes, gas and oxygen sensors, cameras and pyrometers, wrapped as C++ driver plugins with simulation counterparts for testing.

Build data pipeline

From CAD/CAM such as Autodesk Fusion to the scanner: 3MF Toolpath import, parameter sets per part and hatch, build validation and job management.

Operator interface (HMI)

Web-based operator UI configured on the server side: roles and permissions, live machine status, layer and toolpath viewers, charts and alarms, on the machine and in the browser.

Process data & traceability

A complete build journal with sensor time series and user actions, linked to every layer and part and exportable through the REST API to MES, QMS and analytics tools.

Retrofit & research systems

Modernise existing LPBF machines or build open research platforms where every parameter, sensor and scan strategy is accessible to your engineers.

Engineering across the life cycle
  • Requirements & architecture
  • Simulation & automated tests
  • Commissioning on site
  • Training for your team
  • Long-term maintenance

The platform

Built on the Autodesk Machine Control Framework

AMCF is an open-source middleware framework that connects CAD/CAM software with machine hardware in a closed-loop system. It was originally developed for laser-based additive manufacturing and is published by Autodesk under the BSD-3-Clause license.

A headless C++ server runs inside the machine. Machine logic and hardware drivers are plugins, separated from the framework core. Operators and other systems work through a web interface and a documented REST API.

AMCF documentation Source code on GitHub
Architecture of an AMCF-based LPBF machine controller CAD/CAM, the operator HMI and factory systems connect to the AMCF server through 3MF Toolpath files and the REST API. Inside the server: REST API, state machines, machine plugins, driver plugins, journal and user management. Driver plugins connect to scanner and laser, PLC and axes, recoater, gas and oxygen control, sensors and cameras. CAD / CAM e.g. Autodesk Fusion Operator HMI web browser MES / QMS / Analytics factory IT 3MF REST REST AMCF server headless · C++ · inside the machine REST API · OpenAPI 3.0 State machines Machine plugins Driver plugins Journal · SQLite Users & roles Scanner & laser PLC & axes Recoater & dosing Gas flow & O₂ Sensors & cameras

Open source, BSD-3-Clause

The framework is free to use, modify and ship. You keep full control of your machine software and its roadmap.

Plugin architecture

Machine logic and drivers are separated from the framework core, with independent release cycles.

Strict state machines

Deterministic, inspectable machine behaviour that can be visualised in the user interface.

Complete journal

State and variable changes are recorded, so complete builds can be replayed and analysed.

Simulation drivers

Machine logic is developed and tested without hardware, before it reaches the machine.

Users and permissions

Login, roles and permissions; every action is attributed to a user and a point in time.

Who we work with

For the people who build and run LPBF machines

Machine builders

Launch a new LPBF system with a modern, open control stack instead of developing one from scratch.

Research institutes

Open research machines with full access to scan strategies, process parameters and raw data.

Component suppliers

Make your scanner, laser, optics or sensor available to LPBF machines as an AMCF driver.

Production users

Retrofit and extend existing machines and connect them to factory IT and quality systems.

How we work

From first workshop to long-term support

  1. Discovery

    Requirements, hardware inventory, process goals and constraints.

  2. Architecture

    Control concept, state machines, interfaces and the safety split between PLC and PC.

  3. Integration

    Drivers and plugins, developed against simulation and covered by automated tests.

  4. Commissioning

    On the machine, together with your process engineers, up to the first builds.

  5. Support

    Updates, new features, training and maintenance over the machine's life.

Why C1 Technologies

Software engineers who speak LPBF

01 / OPEN

Open by default

Your machine software is built on an open framework. Source access, open data formats, no lock-in.

02 / PROCESS

LPBF know-how

Lasers, scanners, recoating, gas flow and monitoring: we understand the process the software controls.

03 / QUALITY

Production-grade code

Modern C++, versioned builds, continuous integration, automated tests and simulation.

04 / PARTNER

One partner

From the first architecture sketch to commissioning and long-term support.

FAQ

Frequently asked questions

What is the Autodesk Machine Control Framework?

AMCF is an open-source middleware framework, published by Autodesk, that integrates CAD/CAM software with machine hardware. It was originally developed for laser-based additive manufacturing. A headless C++ server runs on the machine; drivers and machine logic are plugins; clients use a REST API documented with OpenAPI 3.0.

Do we have to pay licence fees for the framework?

No. AMCF is licensed under BSD-3-Clause, so you can use, modify and ship it in your product. We offer engineering, integration and support around it.

Can you integrate our existing hardware?

Usually yes. If a component has an SDK or a documented protocol, it can be wrapped as an AMCF driver plugin. We also write a simulation driver for it, so that the machine logic can be tested without the hardware.

Can an existing LPBF machine be retrofitted?

Often yes, depending on access to the scanner, the laser and the PLC. We start with a hardware inventory and a short feasibility study.

Which CAD/CAM systems are supported?

AMCF uses the 3MF Toolpath format for build data and connects to Autodesk Fusion. Other build file sources can be connected through import plugins; tell us about your workflow.

Does the machine need a cloud connection?

No. The AMCF server runs inside the machine, and the operator interface runs in a browser on the local network. Connections to factory or cloud systems are optional and go through the REST API.

Contact

Let’s talk about your machine

New machine, retrofit, research system or a single driver: tell us what you are building. An engineer will get back to you.