Advanced Software for Extrusion Additive Manufacturing Data Collection
Roschli, Alex, Borish, Michael, White, Liam et al. · 2025
Read Advanced Software for Extrusion Additive Manufacturing Data Collection by Roschli, Alex, Borish, Michael, White, Liam et al. (2025) in the Tower of Babel, a free online library of public-domain works preserved in clean, searchable text. No sign-up. The full text is served as a plain-text file at a predictable URL, where text is present: https://antarctic-labs.com/tower-of-babel/doe-osti-3827477-advanced-software-for-extrusion-additive.txt.
Introduction
Oak Ridge report ORNL/TM-2025/4154, dated August 2025, closes a user project with small firm Ahead Wind on printing data software. Five authors are printed: Alex Roschli, Michael Borish, Liam White, Cameron Adkins, and Ashley Gannon. Most polymer printers run blind, with no live record of how a build is going. The project linked two tools so sensor data could steer the print itself. Oak Ridge's Slicer 2 plans toolpaths; Ahead Wind's toolkit checks heat behaviour and gathers sensor feeds.
Phase one built the bridge: a socket link with a handshake, passing print files from slicer to toolkit. Phase two aimed to add sensors and printer links, picking an upgrade-friendly Voron printer. Staff changes at Ahead Wind stopped that phase short. Oak Ridge still rebuilt its slicer for cross-platform use and live connections. All lab-side software went out under an open licence.
Catalog record
| CREATOR | Roschli, Alex, Borish, Michael, White, Liam et al. |
|---|---|
| YEAR | 2025 |
| COLLECTION | PAPERS |
| FORMAT | TXT |
| FILE SIZE | 23 KB |
| LICENSE | Public Domain |
| RIGHTS | PUBLIC DOMAIN |
| SOURCE | DOE OSTI |
Browse the full library · About the Tower of Babel
Full text
The opening of the work, from the library's hosted text:
ORNL/TM-2025/4154 Advanced Software for Extrusion Additive Manufacturing Data Collection Alex Roschli Michael Borish Liam White Cameron Adkins USER PROJECT FINAL REPORT Ashley Gannon NN-22-1389 August 2025 Approved for Public Release Distribution is Unlimited ORNL IS MANAGED BY UT-BATTELLE LLC FOR THE US DEPARTMENT OF ENERGY DOCUMENT AVAILABILITY Reports produced after January 1, 1996, are generally available free via OSTI.GOV. Website www.osti.gov Reports produced before January 1, 1996, may be purchased by members of the public from the following source: National Technical Information Service 5285 Port Royal Road Springfield, VA 22161 Telephone 703-605-6000 (1-800-553-6847) TDD 703-487-4639 Fax 703-605-6900 E-mail [email protected] Website http://classic.ntis.gov/ Reports are available to US Department of Energy (DOE) employees, DOE contractors, Energy Technology Data Exchange representatives, and International Nuclear Information System representatives from the following source: Office of Scientific and Technical Information ABSTRACT To date, most Additive Manufacturing (AM) systems run open-loop with no data collection or feedback on how the printing process is going. This requires an operator to manage the print at all times, or risk failing a build. Ahead Wind and ORNL plan to close the gap by improving software capabilities and adding sensors to existing polymer 3D printers so that data can be collected in real-time and used to monitor and adjust the printing process without human intervention. Ahead Wind, makers of a 3D printing toolkit to collect thermal data from existing filament 3D printer sensors, is looking to expand their software capabilities by using their collected data to influence the toolpath generation step. ORNL has developed toolpath generation software, ORNL Slicer 2, that can be used to close the loop for the 3D printing process. This project will provide the resources to collect data from more sensors in real-time so that the printing process can be more accurately modeled and logged to minimize human involvement. The two programs will also be connected to allow for a closed loop control of systems. This new framework for closed loop control will be easily adaptable to other 3D printers and manufacturers. All modifications to ORNL Slicer 2 will immediately be available open source. 1. ADVANCED SOFTWARE FOR EXTRUSION ADDITIVE MANUFACTURING DATA COLLECTION This technical collaboration project (MDF-UP-2022-247) began on June 28, 2022, and concluded in August 2025. The collaboration partner, Ahead Wind, is a small business. The results from phase 1 included developing and testing a framework for advanced network communication both within the ORNL Slicer software and the Ahead Wind software. Phase 2 was unable to be completed by Ahead Wind due to changes within the organization and employee transitions. ORNL was able to complete many tasks including printer selection, connection capabilities within ORNL Slicer 2, and many significant modifications to ORNL Slicer 2 for connectivity and modularity. While the connection to the Ahead Wind Toolkit was not completed, the framework developed and implemented within ORNL Slicer 2 is available open-source and can be utilized for future research with other organizations. 1.1 BACKGROUND The focus of this project revolves around data collection and transmission between two separate pieces of software: ORNL Slicer 2 and the Ahead Wind Toolkit. The ORNL Slicer 2 program is used for toolpathing. It is capable of importing an STL file, slicing into layers, planning toolpaths, and exporting g-code for the 3D printer. The Ahead Wind Toolkit is capable of importing g-code to do basic thermal simulation as well as error checking. The toolkit is also being developed to allow for data collection and processing based on sensor feedback during the printing process. This includes data from optical cameras, thermal cameras, and laser scanners. These two disparate pieces of software are essential for developing and enhancing the 3D printing process but would be more powerful if they worked together to share data. The goal of this project is to connect the programs to allow bi-directional data transfer. With this data exchange, toolpathing can be simulated and improved during the printing process. Future work will enable data collection to monitor for anomalies during the printing process that can be resolved by reslicing and creating new toolpaths. 2. PHASE 1 TECHNICAL RESULTS 2.1 FUNCTIONAL REQUIREMENTS Together, ORNL and Ahead Wind held several meetings to outline the functional requirements needed for the two software packages to exchange data. This included discussions about communication methods, data exchange format, and the printer to be used for testing. It was quickly decided that communication would be initialized via TCP sockets. TCP, transmission control protocol, is a standard for communication used for sharing data over a network by sending messages. Once established, the communication channel remains active until both ends finish sending messages. For the data exchange, commands and a common structure had to be determined. To do this, naming and response conventions were defined based on existing standards from HTTP. Figure 1 shows the handshake initialization and response commands needed to begin communication between programs. //Handshake command { "header": { "request-id": "00000000-0000-0000-0000-000000000000", //(UUID for current operation - alphanumeric, hex) "date": "Mon Aug 30 09:25:00 2023", //formatted Qt datetime stamp - DoW M D hh::mm::ss YYYY "command": "1" //(current command id - int) } } //Handshake response { "header": { "request-id": "00000000-0000-0000-0000-000000000000", "date": "Mon Aug 30 09:25:00 2023", "command": "1" } "data": { "response": "200" //HTTP OK } } Figure 1: Handshake commands for initializing communication. After communication has been established and slicing has been completed, communication is needed to pass the g-code from slicer to toolkit. This can be seen in Figure 2. //Gcode Processing Request { "header": { "request-id": "00000000-0000-0000-0000-000000000000", "date": "Mon Aug 30 09:25:00 2021", "command": "5" //Command for gcode transmission }, "data": { "gcode": "" //full g-code payload } } //Gcode Processing Response { "header": { "request-id": "00000000-0000-0000-0000-000000000000", "date": "Mon Aug 30 09:25:00 2021", "command": "5" }, "data": { "response": "200", "gcode": "" //fully optimized g-code payload } } Figure 2: G-code communication commands between slicer and toolkit. The packets of data being shared via this TCP communication are JSON formatted (JavaScript Object Notation) which can encounter issues with files larger than 1GB. G-code from ORNL Slicer is often significantly smaller than 1GB due to it being a plain text file, but it is still possible to encounter a file that exceeds this 1GB limit. To handle this, the team outlined a strategy for splitting large files and writing packet sequence information so that the receiver can assemble the separated packets. After defining the functional requirements for the framework, ORNL and Ahead Wind needed to outline the 3D printer to be used for initial testing. Ahead Wind uses and supports a variety of small-scale desktop printers but wanted to look at integrating a larger industrial printer to fully showcase the capabilities of their software as well as the partnership with ORNL. Ultimately, ORNL and Ahead Wind planned on using the Cincinnati BAAM Platform for testing due to ease of access and availability at ORNL. Ahead Wind reached out to CI to procure copies of all source code for both the PLC and HMI (human machine interface) on BAAM. Ahead Wind also partnered with other BAAM operators to do some basic software setup and integration testing on the BAAM platform. 2.2 MODIFICATION OF ORNL SLICER 2 Based on the functional requirements, ORNL Slicer 2 needed