In Dimensioning Mode, the Import Tool loads aDocumentation Index
Fetch the complete documentation index at: https://support.lumafield.com/llms.txt
Use this file to discover all available pages before exploring further.
.STEP file as the nominal CAD body for your scanned part. The imported CAD is the reference geometry that Profile evaluates the scan against, and is also where you define the CAD-side half of your Datum Reference Frame using the Datum Tool.
This page covers the Dimensioning Mode workflow for nominal CAD import. For the broader Import Tool — including
.STL Mesh import in Analysis Mode — see the main Import Tool article.Why a separate workflow
Nominal CAD import is the only point in 3D Auto-Dimensioning where data enters Voyager from outside the scanner. The CAD body provides:- The exact nominal geometry that Profile compares against your scan.
- A surface on which you can build a CAD-side Datum Reference Frame that mirrors the DRF defined on the scanned part.
Workflow
Switch to Dimensioning Mode
Select the Dimensioning tab from the Mode tabs on the left-hand side of Voyager.
Open the Import Tool
Select the Import Tool from the Toolbar. In Dimensioning Mode the Import Tool accepts
.STEP files.Upload your .STEP file
Choose the STEP file representing the nominal part. The imported body appears in the Data Panel as a new Data Object.
Define datums on the imported CAD
Use the Datum Tool to build a DRF on the imported CAD that mirrors the DRF on the scanned part. Matching labels (for example,
A, B, C) make datum correlation in Profile trivial.Run Profile
With matching DRFs on both the part and the CAD, run Profile to evaluate deviation.
File guidance
A few practical tips for clean STEP imports:- Single body per file. If your CAD model contains assemblies or fixtures, export only the part to be evaluated.
- Native units preserved. STEP files declare their own units; Voyager respects them. There is no scale field to set, unlike the
.STLflow in Analysis Mode. - Geometry, not tessellation. STEP is exact geometry, so polygon count is not a concern — unlike the
.STLflow used by the Compare Tool, where polygon density affects accuracy.
Related pages
- Import Tool — main article covering both
.STLand.STEPworkflows - Voyager Modes
- 3D Auto-Dimensioning
- Datum Definition
- Profile
- Voyager 2.0 Release Notes and Monthly Highlights