Find the current instructions for the part of the system you are using
ASCAND combines a physical capture system with processing and result-handling workflows in 3D-Scan.Online. The correct instructions therefore depend on what you are using, which configuration you have and what stage you have reached.
Use this Documentation hub when you need current information about:
- ASCAND hardware, components and documented configurations;
- capture-station preparation and recording requirements;
- the current 3D-Scan.Online interface and access path;
- Vision, Laser or Combo processing;
- result representations, exports and downloads; or
- Multi Merge and related downstream steps.
Documentation owns details that can change with a product revision, optional extension or platform interface. Tutorials provide an ordered path through a task. The Knowledge Center explains the underlying technical ideas. Troubleshooting begins with a symptom after something has gone wrong.
Before following a document, verify that it applies to your equipment, configuration and current platform state. A familiar title, recent file date or older successful workflow does not by itself establish that the instructions are current.
Start with ASCAND Getting Started
Choose by task, component and configuration
Begin with the narrowest route that owns your question.
Identify the physical product
Use Product Documentation when you need to identify the ASCAND system, turntable, extension, supplied component or compatible configuration. Establish the exact product before using assembly, power, maintenance or safety instructions.
Prepare or inspect the capture station
Use Capture Documentation for the current physical setup, phone support, framing, object placement, background, lighting and recording requirements.
Use 3D-Scan.Online
Use Platform Documentation for current sign-in, project, source-file, workflow-selection, processing-state, access and interface instructions.
Create a Vision, Laser or Combo result
Use Method Documentation for the workflow selected. Laser-assisted operation also requires current, product-specific installation, classification, calibration and safety information.
Review, export or merge results
Use Result Documentation for result identity, point clouds, meshes, processed variants, formats, companion files, downloads and Multi Merge.
If you do not yet know which route applies, begin with Getting Started. If you know the symptom rather than the responsible stage, begin with Troubleshooting.
Product, turntable and extension documentation
Product documentation should let you identify the equipment in front of you and distinguish it from other revisions or optional configurations. Depending on the documented product, this may include:
- product and component names;
- the scope of the current package;
- required but separately supplied items;
- supported configuration relationships;
- assembly, power and maintenance instructions;
- applicable print files or supporting downloads; and
- warnings, operating boundaries and safety information.
Do not reconstruct a package inventory from an engineering description. Technical material may discuss components, prototypes or historical configurations that are not part of the current offer. A photograph can help identify visible appearance, but it cannot establish exact dimensions, payload, compatibility, electrical operation or the contents of a retail package.
The supplied standard-turntable photograph may be used as factual appearance evidence. It does not show a complete capture station, phone position, object clearance, scale, optional extension or operating capacity.
For a purchase or configuration decision, compare the current product descriptions and confirm unresolved compatibility questions before acting.
Capture-station and recording documentation
Capture documentation owns the current requirements for turning a physical setup into usable source material. It should identify the applicable hardware and explain how to establish and preserve the capture relationship.
Across the documented ASCAND workflow, the camera remains steady relative to the station while the object undergoes the intended rotation. The object must remain stable, and the required coded turntable reference must remain observable. Background, illumination, focus, framing and the physical support must remain controlled across the complete rotation.
Those principles do not define every operational detail. Use current documentation for:
- assembly and placement of the selected configuration;
- supported phones, holders or recording devices;
- required framing and orientation;
- current recording settings or source-file requirements;
- powered operation and cable routing;
- object and rotational-clearance boundaries; and
- any configuration-specific preparation.
Inspect the saved source before upload. A setup that looked plausible at the beginning may still crop the object, lose the coded reference, move, change exposure or become obstructed later in the rotation.
Use the procedural pages when you are ready to act:
3D-Scan.Online platform documentation
Platform documentation is the controlling source for current interface-dependent actions and requirements. It should match the live platform and identify the state or version to which it applies.
Use it to verify:
- account and access requirements;
- project creation or selection;
- accepted source types and file limits;
- upload and transfer completion;
- workflow, scan type or configuration selection;
- submission and processing states;
- result and variant identity;
- available output and download controls; and
- current entitlement, billing or usage behavior where applicable.
Do not infer a control label, default, processing option or access rule from an older screenshot. A technically correct explanation of reconstruction does not prove how the present interface exposes that process.
Screenshots should be used only when the real interface is necessary to complete the task. Each screenshot must reflect the current platform, show the smallest useful area and avoid exposing personal project or account data. A conceptual diagram may explain the route from upload to result, but it must not imitate an actual interface or be presented as product evidence.
Processing acceptance and completion are separate from result suitability. A completed status means that the platform reached a defined workflow state; it does not certify the resulting geometry.
Vision, Laser and Combo workflow documentation
Choose documentation for the evidence workflow actually used.
Vision
Vision documentation should identify the accepted source, applicable turntable configuration, current platform path and result review responsibilities. Vision reconstruction uses the available visual and structured-rotation evidence; completion does not guarantee complete or accurate geometry.
Laser
Laser documentation must identify the exact hardware and keep mechanical installation, alignment, calibration, safety authorization and active operation as separate gates. Never activate a laser module on the basis of a historical design value, a visually straight line or generic advice.
Combo
Combo documentation should identify the required input set and preserve the distinction between the independent Vision and Laser evidence paths before intentional reconciliation. It must not imply that “combined” automatically means more accurate or complete.
Vision, Laser and Combo are not basic, better and best levels. They contribute different observations and have different prerequisites and limitations. When the object or intended result is uncertain, compare the methods before choosing the operating instructions.
Results, exports and Multi Merge documentation
Result documentation should identify what was produced before asking where the file will be used. Keep these questions separate:
- Is the reconstructed geometry suitable enough to retain?
- Is the result a point cloud, mesh or another processed variant?
- Which representation does the next task require?
- Which current export format preserves the needed geometry and attributes?
- Did the export generate and download correctly?
- Does the destination application interpret units, scale, axes, normals, color, texture and companion files as expected?
A file extension is a container choice, not a quality level. Conversion cannot restore unobserved geometry or prove scale, watertightness, dimensional accuracy, print readiness or fitness for purpose.
Multi Merge has a different responsibility. It estimates and validates the spatial relationship among independently reconstructed scans before combining them. Preserve the sources and transformations. Confirm that the scans describe the same unchanged object, contain useful new coverage and share sufficient reliable overlap. Calculation completion, apparent convergence or increased point density does not prove correct registration.
Review, export and download a model
Verify applicability before you act
Before following product-, safety- or interface-dependent instructions, check:
- Title and purpose: Does the document own the task you are performing?
- Product: Does it identify the physical product or module you have?
- Configuration: Does it cover the selected turntable, extension and required components?
- Platform state: Does it match the current interface and workflow?
- Revision: Is a version, revision or publication date shown where needed?
- Applicability: Are supported products, prerequisites and exclusions explicit?
- Supersession: Does the document explicitly replace an earlier instruction where both exist?
- Safety: Are product-specific warnings and controlled-operation requirements present before the relevant action?
- Destination: Do linked files, downloads and next steps exist and match the document?
Do not assume that the newest modification date makes a document authoritative. A newer document supersedes an older one only when it covers the same responsibility and explicitly replaces it.
Stop when the product identity, compatibility, interface state, assembly step, electrical operation, calibration or safety instruction is missing or contradictory. Preserve the source material and describe the uncertainty precisely when requesting help.
Start with symptom-led troubleshootingA reconstructed model is not automatically a printable part. It first represents the result of capture and reconstruction. Additive manufacturing introduces a different set of responsibilities: coherent topology, intended scale, printable physical features, a suitable build orientation and a toolpath that has been inspected for the selected printer, material and process.