Part = *.stl file

Support = *_vless.stl and/or *_solid.stl file(s), optional

Machine = *.openjz file. Additive Print uses version 2.8 of the EOS API.

You must have an EOSPRINT 2 license, in the form of a dongle or from a license server, from EOS in order to import an EOS build file into Additive Print. If you are using a dongle, do not unplug it until the import availability status changes to "Available." The Additive application uses the EOS build processor only when importing. Once a build file is stored in the Additive Build Files Library, you do not need to consume the license/dongle when you use that build file for a simulation.

EOS M100, M290 and M400 single-laser machines are supported.

The only support scans that will be included in the simulation are supports in the same layers as the part. An EOS build file does not include enough information to identify support scan lines.

When preparing the .openjz file in EOSPRINT, start height and end height (<height> element) should not be zero since it is never the position of any layer. The build file may be rejected upon importing to the Additive application.

If you stop CodeMeter service while importing an EOS build file into the Additive application, the import availability status remains in the processing state indefinitely. You will need to restart CodeMeter and reimport the build file.

When attempting to import an older EOS build file, the Additive application may reject it since version 2.8 of the EOS API is stricter in regards to the OpenJob format. If this happens, you will see an error under the import availability status like this: Input file(s) was not loaded successfully. OpenJz: EOS_ERR_OPENJOB_INVALID.