# LumiScan X 2.0.0.10 – complete documentation

> All pages of the LumiScan X 2.0.0.10 manual (language: en) by HD Vision Systems GmbH, in navigation order. Each page starts with a level-1 heading followed by its URL; cite that URL. Manual: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/

# LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/index.html

|   |   |   |
| --- | --- | --- |
| ![Front of LumiScan X with 13 lenses](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/intro/step-1.svg)<br><br>**13 cameras in one housing.** A light field camera array with 1.2 MP per camera. | ![Thirteen views combined into a depth map](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/intro/step-2.svg)<br><br>**Depth from 13 views.** Passive 3D that copes with shiny surfaces and cluttered bins. | ![Point cloud coloured by depth](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/intro/step-3.svg)<br><br>**Point cloud and depth map.** 1280 × 960, up to 6 frames per second. |

LumiScan X is a light field 3D camera made of 13 synchronized 1.2 MPix cameras, built for robotics, automation and quality inspection. It measures depth passively from the 13 views, which helps with shiny surfaces and cluttered bins, and delivers a point cloud and depth map of 1280 × 960 points. Variants cover opening angles from 30° to 60°; it runs on 24 V DC or PoE and connects over Ethernet.

For licensing, see [Licence](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#licence). Questions? See the [FAQ](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/faq.html). A problem or an error message? See [Troubleshooting](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html).

The manual for the LumiScan X 3D camera. Use the navigation on the left to browse the individual chapters.

# Introduction – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/introduction.html

## About this Manual {#sec-about-this-manual}

This document contains important information about the features of the LumiScan X camera system; how it works, how to use and install it safely, and how to use the associated software.

Read this manual carefully before using the camera.

## Formatting Convention {#sec-formatting-convention}

This guide uses special formatting to highlight certain words and phrases:

- Keywords/important information and buttons are highlighted in bold (e.g. Then click on **Install**).
- Links and references are highlighted in gold (e.g. [info@hdvisionsystems.com](mailto:info@hdvisionsystems.com)).
- File and path names are highlighted in a special font (e.g. `last_session.xml`)

# General Safety Information and Recommendations – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/safety.html

## User Qualifications and Intended Use {#sec-user-qualifications}

These instructions facilitate the safe and efficient use of the product and should be available to the user at all times.\
Failure to do so may result in fire, electric shock, or other injury or damage.

The LumiScan X system is intended for use as described. It should only be operated by trained users and only with the equipment described in this documentation and under the conditions described in this documentation.

The LumiScan X system is not intended for use in security applications, particularly where the safety of persons is dependent upon the operation of the device.

The user bears sole responsibility for the consequences of improper use and failure to follow the safety instructions in this documentation.

## Temperature range {#sec-temperature-range}

**Table 1. Permissible ambient conditions**

|   |   |
| --- | --- |
| Operating temperature | 0 - 55 °C |
| Storage temperature | 0 - 65 °C |
| Relative humidity (non condensating) | 5% - 85% |

Make sure that the system has reached the optimum temperature before you achieve the best results.\
The manufacturer is not responsible for any malfunction caused by exposing the product to temperatures outside of this range.

## Accessories Compatibility {#sec-accessories-compatibility}

Use of an unauthorized power supply may result in electric shock, fire, and/or burns. This could result in serious injury or even death:

- Only use power supplies that meet Safety Extra Low Voltage (SELV) and Limited Power Source (LPS) requirements.
- If a powered HUB or switch is used, it must also meet the LPS requirements.

## Repairs {#sec-repairs}

Repairs, especially those that require opening the unit, may only be performed with the express permission and assistance of the manufacturer’s service department.\
Unauthorized opening voids the warranty and may result in electric shock, personal injury and/or damage to the product.

## Safety Instructions {#sec-safety-instructions}

The LumiScan X camera is a precision instrument. To minimize the risk of damage to the device or personal injury:

- Inspect the unit for damage before use. If the product is damaged, contact our customer service department.
- Do not use a damaged product.
- Do not drop the device and do not expose it to physical stress.
- Do not use the device near heat sources, food, excessive dirt, dust, oil, chemicals, or in direct sunlight.
- Prevent liquid, flammable or metallic substances from entering the camera housing.
- Do not expose the device to rain, snow, fog, or other moisture. Water can penetrate the hardware components and cause corrosion, which may shorten the service life or cause malfunction.
- Do not use a hair dryer, tumble dryer, or microwave oven to dry your device. If your device gets wet, gently wipe it with a clean, dry cloth.
- Do not open the housing of the camera. Touching it may damage internal components.
- Do not place magnets near the product.
- Avoid static electricity.
- Make sure that the required voltage and frequency match the available power source.

## Symbols and Terms Used in this Manual {#sec-symbols-and-terms}

**Table 2. Symbols and signal words used in this manual**

| Symbol/Signal word | Meaning |
| --- | --- |
| ![Electric shock warning sign](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/symbol-electric-shock.png) | Electric Shock Warning Sign. |
| Warning | Warns of possible product damage, personal injury or death. |
| NOTE | Describes an important fact or condition. |

# Product Description – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html

LumiScan X enables the LumiScan technology of 13 discrete 1.2 MPix cameras. Its use is optimized for robotics, automation, and quality inspection.

How the light field technology of the LumiScan X works is explained in [Technology](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/index.html).

Each LumiScan X camera has its own unique number (e.g. LX20230101). This number can be found on the back of the camera housing.

Measurement distances and measurement volumes can be varied over a wide range. Optimum results are achieved with measurement distances of 250 - 3000mm and measurement volumes of 200 - 3360mm, depending on configuration.

## LumiScan X Technical Specifications {#sec-technical-specifications}

LumiScan X cameras are available in three versions depending on the angle of view: 60, 40 and 30:

**Table 1. Opening angle for 3 variants in X and Y direction**

| Camera Variant | X | Y |
| --- | --- | --- |
| LumiScan X60 | 60° | 45° |
| LumiScan X40 | 40° | 35° |
| LumiScan X30 | 30° | 20° |

## Camera Housing Dimensions {#sec-camera-housing-dimensions}

**Table 2. Camera housing specifications**

| Specification | LumiScan X |
| --- | --- |
| Casing dimensions: | 112 mm × 112 mm × 56 mm |
| Weight: | 737 g |
| Protection: | IP54 |
| Threads: | M4 screws, Depth: 4 mm |

The camera is mounted using four M4 threaded holes. The maximum thread depth is 4 mm.\
The precision holes are optional and can be used for more precise positioning of the camera.

![Camera dimensions (fig 01)](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-01-camera-dimensions.png)

*Figure 1. LumiScan X camera dimensions.*

## Sensor Technical Specifications {#sec-sensor-technical-specifications}

**Table 3. Sensor technical specifications**

| Specification | LumiScan X |
| --- | --- |
| Resolution (depth map) | 1.2 MP (1280 × 960) |
| Point-to-point distance | 0.84 mm (at 1 m edge measurement field) |
| Calibration accuracy | ≤ 0.50 mm (at 1 m edge measurement field) |
| Temporal Z noise | ≤ 0.50 mm (at 1 m edge measurement field) |
| Maximum frame rate | 6 fps |
| Single Capture / Snapshot | 1000 µs |
| Acquisition time (object detection) | 1 s |
| Recommended measuring distance | 250 - 3000 mm |
| 3D point throughput | 7.2 million points per second |
| Camera-array | 13 × 1.2 MPix, Monochrome, 12 Bit |

## Sensor Electrical Specifications {#sec-sensor-electrical-specifications}

**Table 4. Sensor electrical specifications**

| Specification | LumiScan X |
| --- | --- |
| Power supply | 24 V DC or PoE (IEEE 802.3af) |
| Power consumption (typical) | 5.5 W |

## Standard Configurations {#sec-standard-configurations}

To simplify the manufacturing process, standards are defined for the focus and calibration distances that are used most frequently.

**Table 5. Standard configurations: focus, calibration range and field of view**

| Configuration | Lens focal length | Set focus | In-focus range | Standard calibration range | Field of view at minimum working distance | Field of view at maximum working distance |
| --- | --- | --- | --- | --- | --- | --- |
| LumiScanX-60-F035 | 4.14 mm | 350 mm | approx. 250 mm - 450 mm | 250 mm - 450 mm | approx. 180 mm x 100 mm | approx. 400 mm x 280 mm |
| LumiScanX-60-F055 | 4.14 mm | 550 mm | approx. 400 mm - 700 mm | 400 mm - 700 mm | approx. 350 mm x 230 mm | approx. 700 mm x 500 mm |
| LumiScanX-60-F150 | 4.14 mm | 1500 mm | 800 mm - infinity | 800 mm - 3000 mm | approx. 810 mm x 580 mm | approx. 3360 mm x 2490 mm |
| LumiScanX-40-F055 | 6 mm | 550 mm | approx. 400 mm - 700 mm | 400 mm - 700 mm | approx. 200 mm x 120 mm | approx. 440 mm x 300 mm |
| LumiScanX-40-F150 | 6 mm | 1500 mm | 1000 mm - infinity | 1000 mm - 3000 mm | approx. 680 mm x 480 mm | approx. 2280 mm x 1680 mm |
| LumiScanX-30-F150 | 8 mm | 1500 mm | 1200 mm - infinity | 1200 mm - 3000 mm | approx. 600 mm x 420 mm | approx. 1680 mm x 1230 mm |

![Standard configurations: field of view](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-standard-configurations-fov.svg)

*Figure 2. Field of view of the standard configurations at the minimum and maximum working distance.*

## Power Supply {#sec-power-supply}

For the power supply of the LumiScan X, we recommend using a Safety Extra-Low Voltage (SELV) supply.

If this is not feasible, a Protective Extra-Low Voltage (PELV) supply with safe electrical isolation may also be used. In this case, however, it is essential that all grounding conductors are connected to a common star grounding point.

Failure to follow this requirement may result in unwanted leakage or compensating currents and sensor malfunctions.

The difference between SELV and PELV supplies is illustrated in [Comparison of SELV and PELV power supplies](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#fig-selv-pelv).

![Fig selv pelv comparison](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-selv-pelv-comparison.png)

*Figure 3. Comparison of SELV and PELV power supplies*

## Pin Assignment IO-Link & Power {#sec-pin-assignment-io-link}

**Table 6. Pin assignment of the IO-Link & Power connector**

| Pin | Assignment |
| --- | --- |
| Pin 1 (brown) | Sensor 24 V |
| Pin 2 (white) | Trigger GND |
| Pin 3 (blue) | Sensor GND |
| Pin 4 (black) | Trigger IN |
| Pin 5 | Trigger OUT |

![Pin assignment of the IO-Link and Power connector](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-02-pin-assignment-io-link.png)

*Figure 4. Pin assignment of the IO-Link & Power connector on the LumiScan X.*

## Trigger In Signal {#sec-trigger-input-signal}

The LumiScan X can be used in Hardware Trigger Mode using an external trigger signal to capture images. This trigger signal has to fulfill the following requirements:

- minimum voltage high level: 5V
- optimum voltage high level: 24V
- minimum signal length: depends on internal resistance of source (up to 5 milliseconds)

![Fig trigger input waveform](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-trigger-input-waveform.png)

*Figure 5. Example waveform of a trigger input signal*

## Trigger Out Signal {#sec-trigger-out-signal}

The Trigger Out signal can be used to connect a flash light such as the pattern projector LumiScan SL. The signal output is an open collector and has no voltage potential. To generate a voltage to trigger the light, the output must be wired with a pull-up resistor ([Schematic diagram of the LumiScan X connection with a pull-up resistor to generate the voltage for the trigger output.](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#fig-trigger-pullup)).

![Trigger pullup schematic (fig 03)](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-03-trigger-pullup-schematic.png)

*Figure 6. Schematic diagram of the LumiScan X connection with a pull-up resistor to generate the voltage for the trigger output.*

The LumiScan SL is supplied with the necessary resistor and can be connected to the LumiScan X as described in the LumiScan SL’s manual.

The Trigger Output of the LumiScan X can be used to trigger other hardware (e.g. flashlights like the LumiScan SL) simultaneously. To activate the trigger output, the parameter "line source" needs to be set to "timer1active". In the newest version of our SDK this is set automatically when a LumiScan X is connected.

The output signal using a pull-up resistor has the following characteristics:

- High-level signal duration: 400 – 800 µs
- High level: approx. 5 V
- Low level: approx. 0 V
- Time between trigger signals (in stream mode): 166 ms

![Fig trigger output pulse](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-trigger-output-pulse.png)

*Figure 7. Waveform of the trigger output signal: High-level signal duration*

![Fig trigger output period](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-trigger-output-period.png)

*Figure 8. Waveform of the trigger output signal: interval between two trigger signals in stream mode*

## Pin Assignment of Ethernet Connection {#sec-pin-assignment-ethernet}

Electrical and mechanical specifications are based on a properly mated connector pair.

**Table 7. Ethernet connection specifications**

| Specification | Ethernet Connection |
| --- | --- |
| Signal category: | CAT6A |
| Number of pins: | 8 |
| Current rating: | 500 mA |
| Supply voltage: | 24 V DC |
| Rated pulse voltage: | 1.5 kV |
| Contact resistance: | 20 mΩ |
| Type description: | SACC-CI-M12FSX-8P SMD SH T |

**Table 8. Ethernet connector color coding**

| Pin | Color Coding |
| --- | --- |
| 1 | white/orange |
| 2 | orange |
| 3 | white/green |
| 4 | green |
| 5 | white/brown |
| 6 | brown |
| 7 | white/blue |
| 8 | blue |

![Ethernet port assignment](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-04-ethernet-port-assignment.png)

*Figure 9. Ethernet port assignment on LumiScan X.*

## Ethernet Cable Characteristics {#sec-ethernet-cable-characteristics}

A CAT6A Ethernet cable with an M12 connector (LumiScan X side) to RJ45 connector (computer side) is required to properly connect the LumiScan X (see [Hardware Requirements](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-hardware-requirements)).\
The connection diagram for the two connectors is shown in [Connection diagram for M12 and RJ45 connectors in the Ethernet cable.](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#fig-m12-rj45).

![M12 rj45 wiring (fig 05)](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-05-m12-rj45-wiring.png)

*Figure 10. Connection diagram for M12 and RJ45 connectors in the Ethernet cable.*

For connecting the camera, the use of cables from Phoenix Contact GmbH & Co. KG is recommended.

- For angled connectors: Part number 1295151
- For straight connectors: Part number 1408647

The connector must be tightened to a torque of 0.4 Nm to ensure a secure and reliable connection.\
The appropriate tool is available from Phoenix Contact under part number 1208432.

> [!NOTE]
> When using cables from other manufacturers, the connector dimensions must be carefully observed. Larger connectors may cause damage to the LumiScan X.

## Hardware Requirements {#sec-hardware-requirements}

- LumiScan X camera system
- Power supply unit (24 V DC)
- Ethernet cable CAT6A, S/FTP shielded, M12 male to RJ45 male, TIA-568B variant
- Sensor/actuator cable, 5-pin, free cable end to M12 socket
- Computer with following minimum configuration:
  - Processor: Intel i5 2.4 GHz or better
  - RAM: 8 GB
  - Graphics card: NVIDIA GTX 1650 or better
  - Network: Intel Ethernet Adapter I210 or better

## Software Requirements {#sec-software-requirements}

- Windows 10 (NVIDIA driver version 475 or higher)
- Ubuntu 18.04 (CUDA 11.8)
- Embedded (NVIDIA Jetson Nano and TX2)

# Technology – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/index.html

This section explains the physical and geometric principles behind the LumiScan X. It is written for engineers who are new to light field imaging, and it gives readers who know computer vision and optical measurement enough detail to judge what the LumiScan X measures and what limits its results. You do not need it to install or operate the camera; for that, see [Installation](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html) and [LumiScan Software](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html).

- [Light Field Imaging](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/light-field-imaging.html): the plenoptic function, the four-dimensional light field, and how parallax between viewpoints yields depth.
- [Light Field Acquisition Architectures](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/acquisition-architectures.html): microlens-based plenoptic cameras and camera arrays compared, with their trade-offs.
- [How LumiScan X Works](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/lumiscan-x-architecture.html): camera arrangement, calibration and depth reconstruction of the LumiScan X, the factors that determine measurement quality, a summary and the references.

# Light Field Imaging – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/light-field-imaging.html

This page introduces the physical foundations of light field imaging. It is independent of a particular camera; [How LumiScan X Works](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/lumiscan-x-architecture.html) describes how the LumiScan X applies these principles. The publications cited are listed in [References](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/lumiscan-x-architecture.html#lsx-references).

## What Is Light Field Imaging? {#lf-what-is}

Light field imaging is a computational imaging technique that records not only the intensity of the light arriving at an image sensor, but also the directions from which it arrives. A conventional camera integrates the light from all directions in each pixel and records a two-dimensional projection of the three-dimensional scene; most of the directional information is lost. A light field camera preserves part of it by observing the scene from several viewpoints: it samples the light rays by both their position and their direction.

This additional information enables:

- **Depth estimation**: determining the distance between the camera and the visible surfaces.
- **3D reconstruction**: recovering the three-dimensional geometry of objects.
- **Digital refocusing**: changing the focal plane computationally after the image has been taken.
- **Perspective synthesis**: generating views from viewpoints within or near the captured angular range.
- **Occlusion handling**: recovering surfaces that are hidden from some viewpoints but visible from others.

This makes light field imaging attractive for industrial tasks that need reliable three-dimensional information.

## The Plenoptic Function {#lf-plenoptic-function}

The theoretical basis of light field imaging is the plenoptic function (Adelson and Bergen, 1991). It describes the light present at every position in space, in every direction, at every wavelength and at every point in time:

$$
P(x, y, z, \theta, \phi, \lambda, t)
$$

| Parameter | Description |
| --- | --- |
| \\(x, y, z\\) | Position in three-dimensional space |
| \\(\\theta, \\phi\\) | Direction of light propagation |
| \\(\\lambda\\) | Wavelength of the light |
| \\(t\\) | Time |

The plenoptic function is therefore a seven-dimensional description of the light in a scene. If it were known completely, the view from any position in any direction could be synthesized. Measuring all seven dimensions is not practical, so light field cameras capture a subset of the plenoptic function under specific assumptions.

### Reduction to Four Dimensions {#lf-reduction}

For machine vision, the following assumptions usually hold:

1. The scene is observed at one point in time.
2. The measurement uses a defined spectral range.
3. Light propagates along straight rays through a homogeneous medium.
4. Absorption and scattering between the object and the camera are negligible.

Under these conditions, the radiance along a ray in free space is constant, so the position along the ray does not have to be represented. The description reduces to four dimensions: the four-dimensional light field, the mathematical basis of most practical light field cameras.

## The Four-Dimensional Light Field {#lf-four-dimensional}

A convenient representation of the light field is the two-plane parameterization (Levoy and Hanrahan, 1996; Gortler et al., 1996): each ray is described by its intersections with two parallel reference planes ([Two-plane parameterization: each ray is identified by its intersection points (u, v) and (s, t) with two parallel reference planes.](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/light-field-imaging.html#fig-lf-two-plane)).

$$
L(u, v, s, t)
$$

Here \\((u, v)\\) is the intersection of the ray with the first reference plane and \\((s, t)\\) its intersection with the second. Together, the four coordinates identify an oriented ray.

![Two parallel reference planes, (u, v) and (s, t), crossed by three light rays; one ray is highlighted together with its two intersection points](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/lf-two-plane-en.svg)

*Figure 1. Two-plane parameterization: each ray is identified by its intersection points (u, v) and (s, t) with two parallel reference planes.*

The two planes can be read as viewpoints and image positions, but their exact physical meaning depends on the optical architecture. In a camera array, for example, the first plane can represent the camera positions and the second the position within each camera’s image. Each camera then samples a two-dimensional subset of the four-dimensional light field, and the images of several cameras together provide samples in both the spatial and the angular dimensions.

### Spatial and Angular Resolution {#lf-spatial-angular}

Light field imaging has two kinds of resolution:

- **Spatial resolution** is the ability to distinguish small features within an image.
- **Angular resolution** is the number and distribution of the viewing directions from which the scene is observed.

More angular samples show more of how the appearance of the scene changes with the viewpoint, and this is the information from which depth is reconstructed. Spatial and angular sampling compete for the available measurement resources, and the architectures resolve this differently: microlens-based cameras divide the pixels of one image sensor between spatial and angular sampling, while camera arrays such as the LumiScan X record complete images from several viewpoints on separate image sensors. [Light Field Acquisition Architectures](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/acquisition-architectures.html) compares the two.

## From Light Fields to 3D Reconstruction {#lf-3d-reconstruction}

Depth estimation from a light field relies on parallax: the apparent displacement of an object when it is observed from different viewpoints. Objects close to the camera are displaced more between the viewpoints than distant objects, so measuring the displacement yields the three-dimensional position of the visible scene points.

### Parallax, Disparity and Depth {#lf-parallax-disparity}

Consider two calibrated cameras with known relative position and orientation that observe the same object point. The point is projected to a different image location in each camera; the displacement between these corresponding image points is the disparity. For a simplified stereo configuration with parallel optical axes, depth and disparity are related by:

$$
Z = \frac{f\,B}{d}
$$

| Variable | Description |
| --- | --- |
| \\(Z\\) | Distance of the object point from the cameras |
| \\(f\\) | Focal length of the cameras, in pixels |
| \\(B\\) | Baseline: the distance between the two camera centers |
| \\(d\\) | Disparity between the corresponding image points, in pixels |

Depth is therefore inversely proportional to disparity: a point twice as far away shows half the disparity. Light field cameras extend this principle to many viewpoints. They evaluate correspondences across several images instead of two, which adds geometric constraints and can make the depth reconstruction more robust.

### Multi-View Reconstruction {#lf-multi-view}

A multi-view reconstruction typically involves these steps:

1. **Image acquisition**: capture images from different viewpoints.
2. **Geometric calibration**: determine the intrinsic and extrinsic parameters of the cameras.
3. **Correspondence**: identify the observations that belong to the same scene point.
4. **Depth estimation**: calculate the depth from the geometry of the corresponding observations.
5. **3D reconstruction**: generate a depth map or a point cloud.
6. **Quality evaluation**: identify uncertain or inconsistent measurements.

Depending on the algorithm, correspondence estimation uses local image features, dense matching, cost-volume optimization, epipolar geometry or learned representations. The result is a representation of the scene geometry that subsequent machine vision tasks can use.

### Applications {#lf-applications}

Light field 3D reconstruction supports industrial applications such as:

- robot guidance and object localization
- automated bin picking
- 3D inspection and surface reconstruction
- object recognition and pose estimation
- dimensional measurement and quality control

The achievable accuracy and robustness depend on the optical configuration, the surface properties, the working distance, the calibration and the reconstruction algorithms.

# Light Field Acquisition Architectures – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/acquisition-architectures.html

All light field cameras are based on the same physical principles (see [Light Field Imaging](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/light-field-imaging.html)), but they acquire the spatial and angular information in different ways. The two main approaches are microlens-based plenoptic cameras and camera arrays ([Microlens-based plenoptic camera (left): the rays from one object point reach different pixels behind one microlens. Camera array (right): each camera records the object point from its own viewpoint; B is the baseline between two cameras.](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/acquisition-architectures.html#fig-lf-architectures)). Both sample the four-dimensional light field; they differ in their optical construction, in the geometry of their angular sampling and in how they use the resolution of their image sensors.

![Left: main lens, microlens array and image sensor of a plenoptic camera; right: four small cameras, each with lens and sensor, observing the same object point](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/lf-architectures-en.svg)

*Figure 1. Microlens-based plenoptic camera (left): the rays from one object point reach different pixels behind one microlens. Camera array (right): each camera records the object point from its own viewpoint; B is the baseline between two cameras.*

## Microlens-Based Plenoptic Cameras {#arch-microlens}

A microlens-based plenoptic camera consists of a main lens, a microlens array and an image sensor. The main lens collects the light from the scene. The microlens array between the main lens and the sensor separates the light by position and direction, so the sensor records a structured image that contains several angular observations of the scene. From this image, algorithms derive sub-aperture images, estimate depth and synthesize images with different focus settings.

### Plenoptic 1.0 {#arch-plenoptic-1}

In the classical plenoptic camera, often called plenoptic 1.0 (see Ng et al., 2005), the microlens array is placed near the image plane of the main lens, and each microlens forms an image of the main lens aperture on the sensor. The pixels behind one microlens therefore correspond to different directions of propagation. This yields angular information at the expense of spatial resolution: on a sensor with a fixed number of pixels, more angular samples leave fewer independent spatial samples.

### Focused Plenoptic Cameras (Plenoptic 2.0) {#arch-focused-plenoptic}

In the focused plenoptic camera, also called plenoptic 2.0 (Lumsdaine and Georgiev, 2009), the microlenses are focused on the intermediate image formed by the main lens instead of on its aperture. This distributes the spatial and angular information differently and can give a comparatively high effective spatial resolution while keeping angular information for depth reconstruction and digital refocusing. Some designs combine microlenses with different focal lengths to extend the usable depth range.

Microlens-based cameras are used in industry where a compact system, short working distances and 3D information from a single optical assembly and a single exposure are important, for example in close-range inspection.

## Camera Arrays {#arch-camera-array}

A camera array acquires the light field with several physically separated cameras, each with its own optics and image sensor. The cameras observe the scene from different positions and thus sample the light field over a spatially distributed set of viewpoints. The angular information comes from the physical separation of the cameras, not from a microlens array, and each camera records a conventional image at the native resolution of its sensor.

### Light Field Sampling {#arch-sampling}

An array of \\(N\\) cameras records the images

$$
I_i(x, y), \qquad i = 1, \ldots, N
$$

where \\(I_i\\) is the image of camera \\(i\\). Each camera has a known position and orientation in a common coordinate system. With the intrinsic and extrinsic calibration parameters, every pixel can be assigned to a ray in three-dimensional space, and all these rays together form a discrete sample of the four-dimensional light field. For a regular, rectified camera array, this can be written as:

$$
L(u_i, v_i, s, t)
$$

Here \\((u_i, v_i)\\) is the viewpoint of camera \\(i\\) and \\((s, t)\\) are the coordinates in a common image parameterization. The number and arrangement of the cameras determine the angular sampling; the image sensors and optics determine the spatial sampling.

### Advantages of Camera Arrays {#arch-array-advantages}

- **Independent spatial sampling:** Each camera records an image at its native sensor resolution. The angular information comes from additional viewpoints, not from dividing one sensor into spatial and angular samples.
- **Selectable baseline:** The distance between the viewpoints is set by the physical arrangement of the cameras and can be chosen to suit the working distance and the depth requirements.
- **Multiple observation directions:** A surface that is hidden from one camera may be visible from another, which gives additional opportunities to observe and reconstruct the scene geometry.
- **Configurable optics:** The lenses and the array geometry can be chosen for different measurement volumes and fields of view.

### Engineering Considerations {#arch-array-challenges}

Camera arrays also bring challenges:

- Accurate 3D reconstruction requires precise knowledge of the relative positions and orientations of all cameras.
- The cameras must expose synchronously, particularly when objects move. LumiScan X exposes all 13 cameras at the same time (see [Multi-Camera Image Acquisition](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/lumiscan-x-architecture.html#lsx-acquisition)).
- The algorithms must find corresponding features in images that can differ considerably because of parallax, occlusions and viewpoint-dependent reflections.
- With more cameras, the amount of image data and the computing effort generally increase.

The design of a camera array therefore balances geometric accuracy, spatial resolution, angular sampling, computing effort and acquisition speed.

## Comparing the Two Architectures {#arch-comparison}

The main difference between microlens-based plenoptic cameras and camera arrays is the scale and geometry of their angular sampling ([Microlens-based plenoptic camera and camera array compared](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/acquisition-architectures.html#tbl-lf-architectures)).

**Table 1. Microlens-based plenoptic camera and camera array compared**

| Characteristic | Microlens-based plenoptic camera | Camera array |
| --- | --- | --- |
| Optical configuration | Main lens and microlens array | Several cameras with individual lenses |
| Image sensors | Typically one | Several |
| Angular sampling | Within one optical system | Across physically separated viewpoints |
| Baseline | Limited by the optical design and the entrance pupil | Defined by the camera positions |
| Spatial resolution | Shared with the angular sampling on one sensor | Native resolution of each camera |
| Calibration | Main lens and microlens geometry | Individual cameras and their relative poses |
| Synchronization | Inherent in the single exposure | Requires coordinated acquisition |
| System size | Potentially very compact | Depends on the camera arrangement |
| Reconstruction | Plenoptic disparity and other light field methods | Multi-view correspondence and triangulation |

Neither architecture is better in general. Microlens-based plenoptic cameras offer compact optics, dense angular sampling within a limited aperture and effective solutions for close-range inspection. Camera arrays offer more freedom in the choice of the physical baseline, the camera arrangement and the spatial resolution. The most suitable architecture depends on the application.

## Architectural Trade-offs {#arch-trade-offs}

### Baseline and Depth Sensitivity {#arch-baseline}

The baseline is the effective distance between the viewpoints used for triangulation. For an ideal rectified stereo configuration with \\(Z = f B / d\\) (see [Parallax, Disparity and Depth](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/light-field-imaging.html#lf-parallax-disparity)), an uncertainty \\(\\sigma_d\\) of the estimated disparity causes a depth uncertainty of approximately (to first order):

$$
\sigma_Z \approx \frac{Z^2}{f\,B}\,\sigma_d
$$

Two properties follow. First, for a fixed baseline, focal length and disparity uncertainty, the depth uncertainty grows approximately with the square of the distance. Second, a longer baseline can reduce the depth uncertainty. However, a longer baseline also increases the differences between the viewpoints, which makes correspondence estimation more difficult and introduces additional occlusions. The best baseline therefore depends on the measurement volume, the object geometry, the surface properties and the reconstruction method.

> [!NOTE]
> This relationship is not a complete accuracy model. The actual measurement uncertainty also includes calibration, optical, matching and systematic effects.

### Spatial and Angular Resolution {#arch-resolution}

Microlens-based plenoptic cameras record spatial and angular information on one sensor, so their effective spatial resolution depends on how the pixels are divided between these dimensions. Camera arrays record the spatial information on several sensors. This avoids the single-sensor trade-off, but adds cameras, data transfer and reconstruction effort.

The total number of sensor pixels of a camera array does not directly determine the spatial resolution of its depth map. The effective 3D resolution depends on the reconstruction method, the scene texture, the camera geometry and the visibility of corresponding features.

### Occlusions {#arch-occlusions}

An occlusion occurs when a surface is hidden by another object from a particular viewpoint. Because a light field camera observes the scene from several directions, it can recover information that a single viewpoint does not provide. How well it resolves occlusions depends on the angular extent and the distribution of the viewpoints: a wider angular range reveals more surfaces, but can make it more difficult to match corresponding features.

### Reflective and Textureless Surfaces {#arch-surfaces}

Depth estimation based on image correspondence becomes difficult when surfaces lack distinctive image features. Specular surfaces, in addition, look different from different viewpoints. The additional observations of a light field help the reconstruction algorithms check geometric consistency across the viewpoints, but angular sampling alone does not guarantee a reliable reconstruction of reflective or textureless surfaces. A pattern projected onto a textureless surface gives it an artificial texture in which correspondences can be found; LumiScan X uses the pattern projector LumiScan SL for this (see [Passive 3D Imaging and Illumination](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/lumiscan-x-architecture.html#lsx-passive)). The result depends on the illumination, the optical configuration, the surface properties and the algorithms.

# How LumiScan X Works

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/lumiscan-x-architecture.html

LumiScan X is a camera-array light field camera of HD Vision Systems for industrial 3D machine vision. This page describes how it acquires and reconstructs three-dimensional data and which factors determine the quality of the results. The general principles are explained in [Light Field Imaging](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/light-field-imaging.html) and [Light Field Acquisition Architectures](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/acquisition-architectures.html).

## Camera-Array Light Field Imaging {#lsx-overview}

Instead of a microlens array in a single optical system, LumiScan X acquires the light field with 13 cameras in one compact housing. Each camera observes the scene from a different viewpoint, and together their images contain the spatial and angular information from which the three-dimensional geometry of the scene is reconstructed. LumiScan X is optimized for robotics, automation and quality inspection, for example robot guidance, object recognition and 3D inspection.

The multiple viewpoints provide additional observations of every scene point, which improve depth estimation and reduce ambiguity. This is a particular advantage for objects with shiny surfaces and reflections, where a highlight looks different from each viewpoint, and in cluttered scenes such as bin picking, where parts are hidden from some cameras but visible to others. The achievable reconstruction accuracy and robustness depend on the scene properties, the camera geometry and the algorithms used.

### Camera Arrangement {#lsx-camera-arrangement}

The camera array consists of 13 monochrome cameras with 1.2 MPix and 12 bit each ([Sensor Technical Specifications](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#tbl-sensor-technical)). The cameras observe the same measurement volume from different positions; their relative positions and orientations define the angular sampling of the system. Because the viewpoints are physically separated, every scene point appears with parallax between the camera images, and this parallax provides the geometric information for depth estimation.

In the LumiScan Viewer, the **Frame** tab shows the images of the 13 individual cameras, and **Capture Center View** exports the image of the center camera (see [User Interface](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-user-interface) and [Data Export](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-data-export)). LumiScan X is available with three opening angles: 60°, 40° and 30° ([Opening angle](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#tbl-opening-angle)).

### Passive 3D Imaging and Illumination {#lsx-passive}

LumiScan X is a passive 3D camera: unlike structured-light or laser triangulation systems, it does not fundamentally require a projected light pattern to determine the geometry of a scene, but derives the depth from the images of its cameras. It does need enough image information for correspondence estimation, however, so depending on the application, suitable ambient or application-specific illumination is necessary.

For surfaces without texture, the pattern projector LumiScan SL projects a pattern onto the surface: an artificial texture that makes it possible to find correspondences. The Trigger Out signal of LumiScan X triggers the LumiScan SL simultaneously with the image acquisition ([Trigger Out Signal](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-trigger-out-signal)).

## Multi-Camera Image Acquisition {#lsx-acquisition}

All 13 cameras of LumiScan X expose simultaneously, so each frame contains 13 images of the scene taken at the same moment; in the LumiScan Viewer, **Capture Whole Frame** saves these 13 individual images as raw data. If the cameras exposed one after another, an object that moves between the exposures would appear at different positions in the images, and the observations would no longer match. Because the exposures are simultaneous, LumiScan X can also capture and measure moving objects.

The **Trigger** setting determines when LumiScan X acquires a frame: continuously (**Stream**), on a software trigger, or on an external hardware trigger, for example from a PLC ([Camera Settings](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-camera-settings), [Trigger In Signal](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-trigger-input-signal)). The maximum frame rate is 6 fps; with the pixel format **Mono12**, the frame rate is limited to 3 fps, but the results can be more accurate.

### Image Formation Model {#lsx-image-formation}

Each camera can be described by a calibrated perspective projection model, provided that this is an adequate approximation of its optics. A point \\(\\mathbf{X}\\) in the reference coordinate system is transformed into the coordinate system of camera \\(i\\):

$$
\mathbf{X}_{c,i} = R_i\,\mathbf{X} + \mathbf{t}_i
$$

Here \\(R_i\\) is the rotation matrix and \\(\\mathbf{t}\_i\\) the translation vector of camera \\(i\\), and \\(\\mathbf{X}\_{c,i}\\) is the point in camera coordinates. The point is then projected into the image with the intrinsic camera matrix \\(K_i\\). In homogeneous coordinates, the ideal pinhole projection onto the image point \\((x_i, y_i)\\) is:

$$
\lambda_i
\begin{bmatrix} x_i \\ y_i \\ 1 \end{bmatrix}
=
K_i
\begin{bmatrix} R_i & \mathbf{t}_i \end{bmatrix}
\begin{bmatrix} X \\ Y \\ Z \\ 1 \end{bmatrix}
$$

where \\(\\lambda_i\\) is a scale factor. Lens distortion is modeled separately. With these parameters, every image observation can be related to a ray in a common three-dimensional coordinate system.

## Geometric Calibration {#lsx-calibration}

Accurate geometric calibration is essential for camera-array 3D reconstruction: it determines the mathematical relationship between image coordinates and the corresponding rays in space. Two groups of parameters are involved.

### Intrinsic Parameters {#lsx-intrinsic}

The intrinsic parameters describe the optical properties of an individual camera: the focal lengths, the principal point and the lens distortion parameters. They determine how a point in space is projected onto the image sensor (\\(K_i\\) and the distortion model in [Image Formation Model](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/lumiscan-x-architecture.html#lsx-image-formation)).

### Extrinsic Parameters {#lsx-extrinsic}

The extrinsic parameters describe the position and orientation of each camera relative to a common coordinate system: a three-dimensional translation and a three-dimensional rotation (\\(\\mathbf{t}\_i\\) and \\(R_i\\)). Together with the intrinsic parameters, they define the geometry of the complete camera array.

### Calibration of LumiScan X {#lsx-calibration-practice}

Calibration errors act directly on the reconstructed 3D points: small errors in the orientation, position or focal length of a camera can cause systematic depth deviations. A camera array therefore needs a mechanically stable construction and an accurate calibration, and changes to the optical configuration or to the relative camera geometry can make a recalibration necessary.

The calibration file (`.hdvcal`) of LumiScan X contains the intrinsic and extrinsic parameters of all 13 cameras:

- The serial number in the file name must match the serial number of the connected LumiScan X, which is on the back of the camera housing.
- By default, the calibration files are stored in `C:\ProgramData\HD Vision Systems GmbH\calibration`. Enter the file location in the **Calibration** section of the LumiScan Viewer; **Help → Show Calibration** shows information about the currently loaded calibration.
- Each standard configuration has a defined standard calibration range ([Standard configurations](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#tbl-standard-configurations)). A calibration file that does not match the current measurement distance results in a poor point cloud.
- If the point cloud remains poor despite correct settings and a clean front glass, send the camera to HD Vision Systems for recalibration ([FAQ: The point cloud is poor](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/faq.html#faq-poor-point-cloud)).

For details, see [Calibration](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-calibration) and [FAQ: Where are the calibration files and which one do I need?](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/faq.html#faq-calibration-file).

## Depth Reconstruction {#lsx-depth-reconstruction}

Once the camera images and the calibration are available, the scene geometry can be reconstructed: the image observations of the same physical point are identified, and the known camera geometry yields its three-dimensional position.

### Correspondence and Epipolar Geometry {#lsx-correspondence}

The first task is to find corresponding image locations across the viewpoints. A surface point appears at different pixel coordinates in each camera, and correspondence algorithms identify these observations from the image content. In a calibrated system, epipolar geometry restricts the search: for two cameras, the point that corresponds to a point in the first image must lie on a known line in the second image, the epipolar line. This reduces the search space for matching. The reconstruction of LumiScan X uses this epipolar constraint between its calibrated cameras.

### Multi-View Triangulation {#lsx-triangulation}

With more than two viewpoints, a scene point can be observed by several cameras, and each observation adds a geometric constraint. The three-dimensional position can be estimated by minimizing the deviation between the projected point and its observations. A common formulation is:

$$
\mathbf{X}^{*} = \underset{\mathbf{X}}{\arg\min} \sum_{i \in V} w_i \left\| \pi_i(\mathbf{X}) - \mathbf{x}_i \right\|^2
$$

| Symbol | Description |
| --- | --- |
| \\(\\mathbf{X}^{\*}\\) | Estimated three-dimensional point |
| \\(V\\) | Set of cameras that observe the point |
| \\(\\pi_i\\) | Projection function of camera \\(i\\) |
| \\(\\mathbf{x}\_i\\) | Measured image location in camera \\(i\\) |
| \\(w_i\\) | Optional confidence weight |

> [!IMPORTANT]
> This formulation illustrates the principle of multi-view triangulation. It is a general mathematical model and does not imply that LumiScan X uses this particular optimization algorithm internally.

### Depth Maps and Point Clouds {#lsx-depth-maps-point-clouds}

The reconstruction can produce different representations of the scene. A **depth map** assigns a distance to each image location; a **point cloud** is a set of reconstructed three-dimensional points in a coordinate system. LumiScan X computes depth maps with a resolution of 1.2 MP (1280 × 960) and a 3D point throughput of 7.2 million points per second. The LumiScan Viewer displays the result as a point cloud. Its coordinate system is the one output by LumiScan X: the camera is at the origin and aligned in the direction of the Z axis, and the unit is meters.

Further processing removes invalid measurements, evaluates confidence or extracts geometric features. In the LumiScan Viewer:

- **Depth Range** limits the calculated distances to the range in which the measurement object lies, which also improves performance ([Depth Range](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-depth-range)).
- **Confidence Threshold** filters out low-quality or uncertain points. The median and **Smooth Outlier** filters reduce noise but also smooth edges; the box filter and the ROR filter remove points outside a cuboid or with too few neighbors ([Processing](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-processing)).
- Point clouds can be exported as `.ply` or `.pcd` ([Data Export](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-data-export)).

## Technical Characteristics {#lsx-technical-characteristics}

[Key values of LumiScan X](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/lumiscan-x-architecture.html#tbl-lsx-key-values) summarizes the key values of LumiScan X. The complete specifications are in [Sensor Technical Specifications](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#tbl-sensor-technical), [Camera Housing Dimensions](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#tbl-housing), [Opening angle](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#tbl-opening-angle) and [Standard Configurations](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#tbl-standard-configurations).

**Table 1. Key values of LumiScan X**

| Characteristic | LumiScan X |
| --- | --- |
| Imaging principle | Camera-array light field imaging |
| Camera array | 13 × 1.2 MPix, Monochrome, 12 Bit |
| Resolution (depth map) | 1.2 MP (1280 × 960) |
| Recommended measuring distance | 250 - 3000 mm |
| Opening angle (X / Y) | 60° / 45°, 40° / 35° or 30° / 20°, depending on the variant |
| Maximum frame rate | 6 fps |
| Single Capture / Snapshot | 1000 µs |
| Point-to-point distance | 0.84 mm (at 1 m edge measurement field) |
| Calibration accuracy | ≤ 0.50 mm (at 1 m edge measurement field) |
| Temporal Z noise | ≤ 0.50 mm (at 1 m edge measurement field) |
| Casing dimensions | 112 mm × 112 mm × 56 mm |
| Protection | IP54 |

The measurement volume and the performance that can be achieved in an application depend on the configuration and the application conditions.

## What Determines Measurement Quality {#lsx-measurement-quality}

### Accuracy, Precision and Resolution {#lsx-accuracy-precision}

The quality of a three-dimensional measurement cannot be described by a single resolution or accuracy value. The following properties must be distinguished:

- **Accuracy:** How closely a measurement agrees with a reference value.
- **Precision:** How well measurements repeat under specified conditions.
- **Depth resolution:** The ability to distinguish differences in depth.
- **Spatial resolution:** The ability to resolve separate features across the measurement field.

These properties are related but not interchangeable. A depth map can contain many pixels and still show considerable uncertainty in their depth values, and a system can repeat its measurements very well and still have systematic geometric errors. For this reason, the specifications of LumiScan X state the point-to-point distance, the calibration accuracy and the temporal Z noise as separate values, each for a 1 m edge measurement field ([Key values of LumiScan X](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/lumiscan-x-architecture.html#tbl-lsx-key-values)); none of them can be read as the absolute accuracy of any measurement. Evaluate accuracy, precision, spatial resolution and measurement conditions separately.

### Baseline {#lsx-baseline}

Depth sensitivity depends on the baseline between the viewpoints ([Baseline and Depth Sensitivity](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/technology/acquisition-architectures.html#arch-baseline)). For a given baseline, the disparity becomes smaller with increasing distance, so the depth estimation becomes more sensitive to small correspondence errors. A longer baseline improves the geometric depth sensitivity, but increases the perspective differences between the cameras, which can make it more difficult to find corresponding features, especially on objects with complex geometry.

A camera array contains several camera pairs with different relative positions and therefore different baselines. Shorter baselines give smaller perspective differences, which can simplify correspondence; longer baselines give more parallax and can improve depth sensitivity where reliable correspondences are available. The reconstruction of LumiScan X uses several baselines of its camera array and combines their information, which balances these properties.

### Spatial Resolution {#lsx-spatial-resolution}

Each camera of LumiScan X records a conventional image at its native sensor resolution: unlike a microlens-based plenoptic camera, the array does not divide the pixels of one sensor among several angular samples. The number of reconstructed depth values does not, however, indicate the smallest geometric feature that can be resolved. Spatial resolution is influenced by:

- pixel sampling
- lens quality
- working distance
- camera geometry
- image texture
- reconstruction algorithms
- measurement confidence

The size of a pixel projected onto the object grows with the distance: a detail that is resolved at a short working distance may no longer be distinguishable at a larger one. Evaluate the achievable resolution for the intended measurement configuration.

### Occlusions and Angular Sampling {#lsx-occlusions}

A single camera records only the surfaces that are visible from its viewpoint. A multi-view system observes the scene from several directions, so a surface that is hidden from one camera can remain visible from another. Consider an object with a recess: from one viewpoint, the side wall hides part of the bottom; from another viewpoint, this part is visible. By evaluating the observations of several cameras, a light field camera can reconstruct more of the scene geometry than a single camera. Surfaces that are hidden from every viewpoint cannot be reconstructed without additional assumptions, so how far occlusions are reduced depends on the actual visibility and the camera geometry.

The spacing of the viewpoints determines the angular information: closely spaced viewpoints give small changes of perspective, widely spaced viewpoints more geometric diversity. A light field camera has to balance the density of its angular sampling against the required baseline, the field of view and robust correspondence.

### Challenging Surfaces {#lsx-challenging-surfaces}

Industrial machine vision frequently meets surfaces that are difficult to measure: metallic and polished components, dark materials, objects with weak texture, fine structures and complex geometries with recesses or occlusions.

- **Reflective surfaces:** Specular reflections depend on the viewing direction, the illumination direction and the surface orientation, so a highlight appears at different image positions in different cameras. This violates the assumption that corresponding points have the same intensity in all images, and intensity-based correspondence methods can then produce wrong matches. The additional viewpoints of a light field can be checked for consistency, which, depending on the reconstruction method, helps to separate stable geometric information from viewpoint-dependent appearance. Strongly reflective surfaces remain difficult, especially where large areas are saturated or contain too few identifiable features. **Show Overexposure** in the LumiScan Viewer marks overexposed pixels in red ([Camera Settings](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-camera-settings)); adapt the exposure time or the illumination accordingly.
- **Textureless surfaces:** A surface with almost uniform intensity contains little local image information, which makes unique correspondences between the viewpoints difficult. Additional cameras add geometric observations but do not create missing image texture. For such surfaces, the pattern projector LumiScan SL, triggered through the Trigger Out signal of LumiScan X, projects a pattern onto the surface; this artificial texture makes it possible to find correspondences. Depending on the application, other controlled illumination or additional surface information can also help.
- **Complex geometry:** Recesses, overlapping structures and rapidly changing surface orientations cause considerable occlusions. Several viewpoints improve the geometric coverage, but the observations must still allow reliable correspondence. The measurement quality depends on how the visible surfaces are distributed across the camera array.

### Working Distance and Measurement Volume {#lsx-working-distance}

The working distance is the distance between the camera and the measured object; the measurement volume is the region in which a reliable three-dimensional reconstruction is possible. Both depend on the optical configuration. For a given field of view, the observed area grows with the distance while the projected size of a feature decreases, and the depth sensitivity changes as well. Choosing the working distance is therefore a compromise between measurement volume, spatial resolution, depth sensitivity, visibility and optical configuration: short working distances favor high geometric detail, while large objects or robot work spaces may require longer ones.

With LumiScan X, optimum results are achieved at measuring distances of 250 - 3000 mm and measurement volumes of 200 - 3360 mm, depending on the configuration. Each standard configuration defines the focus, the standard calibration range and the field of view at the minimum and maximum working distance ([Standard Configurations](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-standard-configurations)). Select the configuration according to the requirements of the application, and set **Depth Range** to the actual position of the measurement object.

### Interpreting and Validating Results {#lsx-validation}

A reconstructed point cloud is an estimate of the visible scene geometry, not a validated measurement. Individual points can carry uncertainty from the calibration, the correspondence, optical effects or the surface properties. For industrial measurement tasks, evaluate the results against known reference objects or geometries. Depending on the application, validation can include:

- comparison with reference measurements
- evaluation of systematic deviations
- repeatability tests
- an assessment of the measurement uncertainty
- tests across the intended working volume
- tests under representative illumination and surface conditions

**Enable Capture Statistics** in the LumiScan Viewer shows the valid points and the valid ratio of a capture ([Data Export](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-data-export)). Document the resulting performance together with the measurement conditions, particularly when 3D data is used for dimensional inspection, robot positioning or automated quality decisions.

## Summary: Why Camera-Array Light Field Imaging? {#lsx-summary}

Light field imaging extends conventional image acquisition by capturing both the spatial distribution and the propagation directions of light, which makes it possible to reconstruct three-dimensional geometry from several perspectives. Microlens-based plenoptic cameras capture the angular information within a single optical system; camera arrays acquire several viewpoints with physically separated cameras.

LumiScan X follows the second approach: it combines 13 simultaneously acquired images in a calibrated geometric arrangement. This provides:

- image acquisition at native resolution from several viewpoints
- physical baselines suitable for industrial measurement geometries
- multi-view observations that can improve the geometric coverage
- passive three-dimensional reconstruction
- a compact sensor for industrial machine vision

The resulting data serves applications such as 3D inspection, robot guidance, object recognition and pose estimation. The camera-array approach does not eliminate the fundamental challenges of three-dimensional imaging; it gives additional freedom in choosing the geometry and the sampling of the light field acquisition. LumiScan X uses this freedom to bring camera-array light field imaging into industrial automation.

## References {#lsx-references}

1. Adelson, E. H., and Bergen, J. R. (1991). *The Plenoptic Function and the Elements of Early Vision.* In: Computational Models of Visual Processing. MIT Press.
2. Levoy, M., and Hanrahan, P. (1996). *Light Field Rendering.* Proceedings of SIGGRAPH.
3. Gortler, S. J., Grzeszczuk, R., Szeliski, R., and Cohen, M. F. (1996). *The Lumigraph.* Proceedings of SIGGRAPH.
4. Ng, R., et al. (2005). *Light Field Photography with a Hand-Held Plenoptic Camera.* Stanford University.
5. Lumsdaine, A., and Georgiev, T. (2009). *The Focused Plenoptic Camera.* IEEE International Conference on Computational Photography.

# Installation – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html

> [!WARNING]
> **Electric Shock Hazard**
>
> Use of unauthorized power supplies may result in electric shock, fire, and/or burns. This could result in damage to the product, serious injury or even death.
>
> - Ensure that the network and power connections at the installation site are compatible with the product and easily accessible.
> - Ensure that power sources are sized according to product specifications and are free of quality defects.
> - Use only power supplies that meet safety extra-low voltage (SELV) guidelines and limited power supply (LPS) requirements.
> - If a power supply unit or switch is used, it must also meet the LPS requirements.

> [!WARNING]
> **Electric Shock Hazard**
>
> Incorrect operating voltage may result in electric shock, fire and/or burns. This could result in damage to the product, serious injury or even death.
>
> - Device must be operated with 24 V nominal voltage only.
> - Make sure that the required voltage and frequency match the available power source.
> - Do not use negative voltage on the signal line.
> - Ensure that the specified voltage is applied constantly and that there are no fluctuations. These can lead to malfunctions of the LumiScan X.

## Mounting the Camera {#sec-mounting-the-camera}

Mount LumiScan X to a suitable fixture using the four rear screw holes ([Connectors of the LumiScan X Camera System: Dimensions in mm.](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#fig-camera-connectors)).

![Camera connectors (fig 06)](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-06-camera-connectors.png)

*Figure 1. Connectors of the LumiScan X Camera System: Dimensions in mm.*

> [!NOTE]
> Pay attention to the orientation of the LumiScan X during installation. The camera should be oriented so that a cross (+) and not an x is visible on the front screen ([LumiScan X camera orientation.](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#fig-camera-orientation)). The housing is then rotated by 45°: the arms of the cross are vertical and horizontal, and the logo is at about 10 o’clock.

![Camera orientation](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-07-camera-orientation.png)

*Figure 2. LumiScan X camera orientation.*

## Connecting the Camera System {#sec-connecting-the-camera-system}

> [!NOTE]
> Do not use pliers or similar tools to twist the plug. This may damage the product.

**If you are using an AC adapter for power supply:**

1. Screw the M12 plug of the Ethernet cable into the corresponding 8-pin socket on the back of the camera.
2. Carefully tighten the plug (maximum hand-tight).
3. Connect the RJ-45 plug of the Ethernet cable to the Ethernet port on your computer.
4. Screw the M12 connector of the sensor/actuator cable to the 5-pin connector on the back of the camera.
5. Carefully tighten the plug (maximum hand-tight).
6. Connect the 24 V power supply to the sensor/actuator cable (for pin assignment, see [Pin Assignment IO-Link](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#fig-pin-io-link)).

**If you are using Power over Ethernet (PoE) with a PoE-enabled computer:**

1. Connect the M12 plug of the Ethernet cable to the corresponding 8-pin socket on the back of the camera.
2. Connect the other end of the cable to the PoE-enabled Ethernet port on your computer.

**If you use Power over Ethernet (PoE) with a PoE injector:**

1. Plug one end of an Ethernet cable into the In port on the Power Injector.
2. Plug the other end of the cable into the Ethernet port on your computer.
3. Connect the RJ45 connector of the Ethernet cable to the Out port of the PoE injector.
4. Connect the M12 plug of the cable to the corresponding 8-pin socket on the back of the camera ([Connectors of the LumiScan X Camera System: Dimensions in mm.](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#fig-camera-connectors)).
5. Connect the injector to an electrical outlet using the power cord.

The camera starts up as soon as the power supply is connected and is ready to use in about 30 seconds.

## Network Settings {#sec-network-settings}

1. Open the Ethernet settings and select **Change adapter options** ([Ethernet settings](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#fig-ethernet-settings)).
2. Open the settings for the Ethernet port to which the LumiScan X is connected.
3. On the **Networking** tab, select **Configure** ([Ethernet settings: Networking](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#fig-ethernet-networking)).

![Ethernet settings](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-08-ethernet-settings.png)

*Figure 3. Ethernet settings*

![Ethernet settings: Networking](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-09-ethernet-networking.png)

*Figure 4. Ethernet settings: Networking*

4. Switch to the **Advanced** tab.
5. Select **Maximum (9014 bytes)** for jumbo frames.
6. Set:
   - **Receive Buffers** to 2048
   - **Transmit Buffers** to 2048
7. If these settings are not possible, update the driver.

## Windows Firewall {#sec-windows-firewall}

The LumiScan software should be added to the inbound rules of the Windows firewall. Either once for TCP/UDP together or separately via two entries. With an automatic entry via Windows, two rules are created by default.

When the LumiScan software is started for the first time, Windows Defender automatically asks if the software should be allowed to access the network.\
Confirm the access permission for the LumiScan software.

![Two rules created by Windows Firewall](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-10-firewall-rules.png)

*Figure 5. Two rules created by Windows Firewall*

If access is denied or the prompt does not appear at the first start, the camera cannot be found by the LumiScan software. The user will be informed by a message from the software.\
One way to resolve this is to restart the software so that Windows asks for permission again. Alternatively, or if the automatic Windows prompt fails, firewall settings can be made manually. See also [The LumiScan software does not find the camera after the first start](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-firewall-camera-not-found).

## Manual Access to the Network {#sec-manual-network-access}

A program can be manually granted network access rights by adding it to the list of allowed applications in the Windows Defender firewall settings.

To do this:

1. To do this, go to **Start → Settings → Privacy & security → Windows Security → Open Windows Security**.

2. In the Windows Security window, on the left menu bar, click **Firewall and Network Protection**.

3. Then click **Allow application access through firewall**.

   √ A window opens with the advanced settings for the application permissions.

4. Click on **Change settings → Allow other app**.

5. Select the `LumiScanViewer` file. It is located in the `bin` subfolder of the installation directory.

6. No further changes are required.

7. Then click the **Add** button.

8. Click on the **Done** button.

   √ The new rule is activated.

## Virus Protection {#sec-virus-protection}

> [!NOTE]
> Please note that your anti-virus software does not use Deep Packet Inspection. This can lead to a considerable drop in performance. It is recommended that you assign a fixed network adapter to the LumiScan X and deactivate Deep Packet Inspection for this adapter.

## Installing CodeMeter Runtime {#sec-codemeter}

The LumiScan software is licensed with the LumiScan Key and needs CodeMeter Runtime 9.00 or later. Install CodeMeter Runtime and connect the LumiScan Key as described in [Installing CodeMeter Runtime](https://docs.hdvisionsystems.com/en/lumiscan-licensing/1.0.4/installing-codemeter.html).

## Licence {#licence}

How LumiScan X is licensed depends on where you bought it and where it runs:

| Bought from | Runs on | Licensing |
| --- | --- | --- |
| HD Vision Systems | PC with the LumiScan software | The licence is held on your LumiScan Key.<br><br>[Licensing path: bought from HD Vision Systems](https://docs.hdvisionsystems.com/en/lumiscan-licensing/1.0.4/path-hdvs.html) |

Each device on which LumiScan X runs at the same time needs its own LumiScan Key. Keys can be exchanged between devices.

How to install CodeMeter Runtime and how to request, renew and move licences is described in [LumiScan Licensing](https://docs.hdvisionsystems.com/en/lumiscan-licensing/1.0.4/index.html).

## Installation {#sec-installation-software}

**Installing the LumiScan software on Windows:**

1. Close all open applications on your computer.
2. Navigate to the location of the LumiScan installer.
3. Double-click on the file: `Installer_LumiScanX_va_b_c_d.exe`\*.
4. The installation is prepared and the license agreement window opens.
5. Accept the license terms by clicking on **Accept**.
6. If you want to change the default installation location, click **Browse**.
7. Navigate to the desired storage location.
8. Press **OK** to confirm your selection.
9. Otherwise, click the **Next** button to continue.
10. If desired, select the Start Menu folder for the program links.
11. If you do not want to create shortcuts, select the **Do not create links** option.
12. Then click on **Install**.
13. When the installation is complete, you will see a dialog box.
14. Click **OK**.
15. Click **Finish**.

For more information about the LumiScan software, refer to the [LumiScan Software](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#ch-lumiscan-software) chapter.

\* where a, b, c, d are variables that depend on the version of the software.

## Metered Connection and Remote Desktop {#sec-metered-connection}

> [!NOTE]
> Metered and Remote Desktop Connections have a significant impact on camera performance. Avoid using a remote desktop connection while the camera is running.

# LumiScan software – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html

> [!NOTE]
> By accessing or using these commercial software products, you expressly agree to the following terms and conditions.
>
> Any attempt to use a debugger to examine, analyze, or tamper with the software provided by HD Vision Systems is strictly prohibited and may have immediate and irreversible consequences.
>
> If the software detects the presence of a debugger, security protocols will be activated to protect the intellectual property, functionality and stability of the software. This may result in, among other things, immediate suspension of the associated Software license, loss of data, and, in extreme cases, forced termination of all instances of the Software operating under the same license, as well as legal consequences.
>
> By using the Software, you acknowledge that you have read, understood and accepted the terms of this Disclaimer (see also [Disclaimer](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/disclaimer.html#ch-disclaimer)).

## User Interface {#sec-user-interface}

To start the software, click **Start → HD Vision Systems → LumiScan Viewer**. The main window of the LumiScan software opens ([LumiScan Viewer user interface overview](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#fig-ui-overview)).

![User interface overview (fig 11)](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-11-user-interface-overview.png)

*Figure 1. LumiScan Viewer user interface overview*

The main window is divided into two sections:

- The left area (the Viewer) displays the current camera images.
- The right part is the control panel where you can change the camera settings.

At the top of the display are the two tabs **Frame** and **Point Cloud**, which can be used to switch the current output of the Viewer between the LumiScan Viewer and the Point Cloud:

- The **Frame** displays the recorded images (frames) from the camera in real time. It is possible to switch between the images of the 13 individual cameras. This display is very useful for setting the exposure time of the camera and for positioning the measurement object.
- The **Point Cloud** tab displays the point cloud generated by LumiScan from the 3D image data of the target. The object can be viewed from all sides and the depth parameter settings can be edited and displayed live.

The **Menu** and **Help** options are located in the Menu bar.

- In **Menu** you will find the entries **Save Parameters**, **Load Parameters**, **Show log** and **IP Configuration**:
  - With **Save Parameters**, selected camera settings can be saved for later use.
  - With **Load Parameters** a previously saved parameter file can be loaded and its configuration settings\* applied to LumiScan Viewer. All stored parameters from the selected file are loaded and applied automatically. Supported file formats `.json` `.ini`.
  - **Show log** opens the window in which the log is saved. Provides additional information about the processes in the program ([LumiScan Log.](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#fig-lumiscan-log)).
  - **IP Configuration** allows to configure the IP address settings for your GenICam-compatible camera.
- In the **Help** option you will find the **Show Calibration** and **About** items.
  - **Show Calibration** provides information about the currently loaded calibration.
  - Under **About**, you can view the currently installed LumiScan version.

> [!NOTE]
> \*The parameters **Trigger**, **TriggerOut** and **TriggerOutDuration** are excluded from loading and will retain their current values.

![LumiScan Log](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-12-lumiscan-log.png)

*Figure 2. LumiScan Log.*

At the bottom right of the main window you will find information about the device temperature and acquisition control panel.\
Acquisition control contains three buttons:

- **Start capturing**: Click this button (green triangle icon) to start continuous capturing and streaming. The button now displays a blue square. Click the button again to stop capturing.
- **Export capture**: Clicking on the photo icon saves a single capture of the measurement object.
- **Export capture**: (continuous) Clicking on the red recording icon starts the continuous export of captures.

## Camera IP Configuration {#sec-camera-ip-configuration}

For stable and high-performance operation, it is strongly recommended to use a **Static IP** rather than **DHCP**.\
To start the IP Configuration, click **Menu → IP Configuration**.

![Camera IP Configuration](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-13-camera-ip-configuration.png)

*Figure 3. Camera IP Configuration*

## IP Configuration Settings {#sec-ip-configuration-settings}

**Table 1. IP Configuration dialog controls**

| Nr | Description |
| --- | --- |
| 1 | The **Refresh** button is used to search for all cameras currently connected to the network. Before using this function, ensure that the camera is properly connected and powered. When the button is pressed, the application scans the available network interfaces and populates the Camera Selection Dropdown with all detected devices. |
| 2 | The **Camera Selection Dropdown** displays all cameras detected on the network after a refresh. To continue configuration, select the desired camera from the list. Once selected, the camera’s current IP configuration is automatically shown in the fields below. |
| 3 | The **DHCP / Static IP Options** define how the camera receives its network address.<br><br>- **DHCP**: When this option is enabled, the camera automatically obtains an IP address from the network’s DHCP server. This mode simplifies setup but is not recommended for high-performance or industrial applications, as the assigned IP address may change, leading to possible connection interruptions.<br>- **Static IP**\*: This option allows the user to manually assign a fixed IP address to the camera. It ensures stable communication and consistent accessibility of the device. |
| 4 | The **Computer Network Information** section displays the current network configuration of the host PC.<br><br>- **NIC (Network Interface Card)**: Shows the active network adapter used for communication with the camera.<br>- **IP & Subnet Mask**: Indicates the current IP address and subnet mask of the computer.<br><br>The camera and computer must be located within the same subnet for proper network communication. |
| 5 | The **Camera Network Settings** section allows configuration of the camera’s IP parameters.<br><br>- **IP**: Enter the desired static IP address for the selected camera.<br>- **Subnet Mask**: Defines the network structure. In most cases, the value 255.255.255.0 is used.<br><br>Ensure that the camera IP is within the same subnet as the computer but not the same IP.<br><br>Example:<br><br>- PC IP: 192.168.71.5<br>- Camera IP: 192.168.71.6 |
| 6 | The **Apply** button saves the entered network configuration and writes it to the camera.<br><br>The **Cancel** button discards any unsaved changes and retains the previous configuration. |
| 7 | The **Status Check** function verifies the connection between the camera and the computer.<br><br>- **Check Status Button**: Initiates a connectivity test.<br>- **Status Display**: Indicates whether communication between the camera and computer was successful and confirms that both devices are located within the same subnet. |

> [!NOTE]
> \*Always select **Static IP** for better control and reliability.

## Configuration Steps {#sec-configuration-steps}

Next Configuration Steps are recommended:

1. Connect your camera to the network.
2. Click **Refresh** to detect the camera.
3. Select the camera from the dropdown list.
4. Enable **Static IP** and enter your desired IP address.
5. Verify subnet settings to match your computer’s network.
6. Click **Apply** to save changes.
7. **Check Status** to confirm successful configuration.

## Camera Settings Configuration {#sec-camera-settings-configuration}

To obtain the most accurate point cloud from the LumiScan X depth data, the acquisition parameters must first be set. To simplify the setup, the measurement parameters can be varied during operation.

## Camera Settings {#sec-camera-settings}

The following measurement parameters must be set individually for each measurement object.

At the Camera Setting are the two tabs **Basic** and **Advanced**.

In **Basic** you will find the entries Parameters ([LumiScan Viewer: Camera Settings, Basic](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#fig-camera-settings-basic)):

- **Pixel Format**: The pixel format of images captured by the camera.
  - **Mono8**: Images are captured as 8-bit grayscale images. With 8-bit images, the sensor can capture 6 frames per second (FPS).
  - **Mono12**: Images are captured as 12-bit grayscale images. With 12-bit images, the frame rate of the sensor is limited to 3 frames per second, but the sensor can provide more accurate results.
- **Exposure Time [μs]**: The exposure time used to capture the image. Higher values produce brighter images.
- **Enable Autoexposure**: This option can be used to automatically set the exposure time.

![LumiScan Viewer: Camera Settings Basic](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-14-camera-settings-basic.png)

*Figure 4. LumiScan Viewer: Camera Settings, Basic*

- **Target Intensity**: It is displayed only when **Enable Auto Exposure** is selected. You can use Target Intensity to adjust the brightness of the image. The higher the value, the brighter the image.
- **Enable Trigger Output**: Option to enable the Trigger Out Signal.
- **Trigger**: Defines when the camera takes an image:
  - **Stream (trigger off)**: The camera continuously captures new images. Useful for quickly displaying updates in the user interface.
  - **Software Trigger**: The camera is triggered by the software. To capture an image, you must use the middle button with the photo icon. To enable this button in this option, the valid path must be selected in the Export Folder window in the Capture Panel.
  - **Hardware Trigger**: The capture will be triggered by an external line. This option should be used when using a process control device (PLC). This mode is also useful when external devices, such as sample projectors, are to be triggered simultaneously.

If you select the **Hardware Trigger** option, additional options are displayed: **Trigger Edge** and **Trigger Delay**.

- **Trigger Edge**: This is the time the image was taken. There are two possibilities:
  - **Falling Edge**: The image is captured when the signal drops out.
  - **Rising Edge**: The image is captured when the signal rises.
- **Trigger Delay [μs]**: The trigger signal is sent to the camera, which waits a certain amount of time before it starts recording.

![LumiScan Viewer: Camera Settings Advanced](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-15-camera-settings-advanced.png)

*Figure 5. LumiScan Viewer: Camera Settings, Advanced*

In **Advanced** you will find the entries Parameters ([LumiScan Viewer: Camera Settings, Advanced](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#fig-camera-settings-advanced)):

- **TriggerOut Delay [μs]**: Defines the time interval between the internal trigger event of the LumiScan X and the activation of the external trigger output signal.
- **TriggerOut Duration [μs]**: Defines the duration of the high-level output signal.
- **Show Overexposure**: When enabled, this feature highlights overexposed pixels in the image display. Each pixel value is compared to the configured Overexposure Limit.
  - If a pixel’s intensity exceeds the defined threshold, the pixel is rendered in red to visually indicate overexposure ([LumiScan Viewer: Overexposure Example](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#fig-overexposure)).
  - Pixels with intensity values below or equal to the threshold are displayed normally.
- **Overexposure Limit**: Defines the maximum allowable pixel intensity before it is considered overexposed. The parameter can be set within a range from 0 (black) to 255 (white)\*.

> [!NOTE]
> \*When the MONO12 pixel format is used, pixel intensity values are represented in the range 0–4095.
>
> For comparison with the Overexposure Limit, these values are linearly scaled to the range 0–255.
>
> This scaling ensures consistent threshold behavior across different image formats.

![LumiScan Viewer: Overexposure Example](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-16-overexposure.png)

*Figure 6. LumiScan Viewer: Overexposure Example*

## Depth Range {#sec-depth-range}

The depth range in millimeters used for the calculation. All calculated values will be within this range. The size of the measurement range has a direct effect on performance. Therefore, setting the depth range to the actual position of the measurement object can significantly improve performance.

![LumiScan Viewer: Depth Range](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-17-depth-range.png)

*Figure 7. LumiScan Viewer: Depth Range*

## Calibration {#sec-calibration}

![LumiScan Viewer: Calibration](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-18-calibration.png)

*Figure 8. LumiScan Viewer: Calibration*

Enter the location of the calibration file (`.hdvcal`). By default, the calibration files are stored in the following path:\
`C:\ProgramData\HD Vision Systems GmbH\calibration`.

- **Non Uniformity**: Enabling this option improves image quality by compensating for differences in object lighting. Enabling this option requires a separate file in the calibration window. This file can be found in the calibration folder.

## Processing {#sec-processing}

The processing area consists of three tabs: **Basic Processing**, **Box Filter** and **ROR Filter**.

The following options can be set in the **Basic Processing** tab ([LumiScan Viewer: Basic Processing](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#fig-basic-processing)):

- **Preprocessing**: Configures the filter to use for preprocessing:
  - **None**: The captured images are used directly for the calculation.
  - **Blur**: Smoothes the image data before processing (low-pass filter).
- **Postprocessing Filter**: Configures the postprocessing filter applied to the resulting depth information:
  - **None**: No filter is applied
  - **Median filter**: A median filter is applied to smooth the results. This reduces the noise in the data. However, edges in the resulting geometry are also smoothed, which may not be desirable.
  - **Smooth Outlier**: This option also applies a median filter. Compared to the Median Filter option, the data is smoothed to a greater extent.
- **Confidence Threshold**: This numerical cutoff value (0.0-1.0) is used to filter out low-quality or uncertain data points. A higher confidence threshold eliminates outlier points.

![LumiScan Viewer: Basic Processing](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-19-basic-processing.png)

*Figure 9. LumiScan Viewer: Basic Processing*

In the **Box Filter**, the parameters of the box filter can be set ([LumiScan Viewer: Box Filter](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#fig-box-filter)).

![LumiScan Viewer: Box Filter](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-20-box-filter.png)

*Figure 10. LumiScan Viewer: Box Filter*

This filter removes all points from the resulting point cloud that do not lie within the specified cuboid box.\
The center and extent of the box can be set for the X, Y and Z axes. The coordinate system used is identical to that output by the LumiScan X. The camera is located at the origin of the coordinates and is aligned in the direction of the Z-axis. The unit of the coordinate system is meters.

In **ROR Filter**, the parameters of the Radius Outlier Removal Filter can be set. ([LumiScan Viewer: ROR Filter](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#fig-ror-filter)).

![LumiScan Viewer: ROR Filter](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-21-ror-filter.png)

*Figure 11. LumiScan Viewer: ROR Filter*

This filter removes all points from the resulting point cloud that have too few other points in their vicinity. The following parameters can be set for the filter:

- **Minimum number of neighbors**: Specifies how many neighboring points must be around a point.
- **Radius**: Defines the maximum distance between the neighboring points and the point in question.

The radius used is specified in meters.

## Image Capture {#sec-image-capture}

Once all measurement parameters are set, the camera’s recording function can be activated:

1. Click the start capturing button (green triangle icon).
2. The recorded camera image then appears in the LumiScan Viewer (frame display).
3. You can switch between the individual cameras of the LumiScan X system by clicking on one of the thirteen preview images at the edge of the viewer.
4. The image from the selected camera is displayed in the main area of the Viewer.
   - The display can be zoomed by scrolling with the mouse wheel.
   - To move the image to the desired position, click and hold the left mouse button.

## Point Cloud Viewer {#sec-point-cloud-viewer}

Switch to the **Point Cloud** tab to display the calculated point cloud of the measurement object ([The Point Cloud Viewer for viewing captured 3D point clouds.](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#fig-point-cloud-viewer)).

By default, you will first see a plane represented by a white grid. This is the camera plane, i.e. the origin of the light field.\
Behind this plane is the three-dimensional structure of the target, which is made up of individual measuring points.\
Together, these points form the point cloud of the captured object.\
You can use the Point Cloud Viewer to view these points in detail:

- The view can be zoomed in and out by scrolling the mouse wheel.
- If you hold down the left mouse button and move the mouse pointer, you can rotate the display around this point.
- By holding down the right mouse button, you can move the image horizontally and vertically.

![The Point Cloud Viewer](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-22-point-cloud-viewer.png)

*Figure 12. The Point Cloud Viewer for viewing captured 3D point clouds.*

## Data Export {#sec-data-export}

You can set the desired data export settings in the Settings Panel under **Capture**:

- **Export Folder**: Enter the desired export path. The default export path is:\
  `C:\Users\Username\HDVisionSystems\LumiScan\export`.
- **Capture Center View**: Select this option if you want to export the image from the center camera.
- **Capture .ply/.pcd Point Cloud**: Select this option if you want to export the point cloud in ply or pcd format. Both options can be set independently.
- **Capture Whole Frame**: Select this option if you want to save all raw data - 13 individual images per frame (high storage space requirement).
- **Frame Compress Level**: An option to compress an image to reduce memory requirements without losing quality. When this option is enabled, saving and exporting data takes longer.
- **Prefix**: By default, each exported file is saved with the date and time in the filename. If you want to use a specific prefix in the file name for a measurement series, you can specify it here.

![LumiScan Viewer: Capture](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-23-capture.png)

*Figure 13. LumiScan Viewer: Capture*

- **Enable Capture Statistics**: Enabling this option displays capture statistics.
  - **Capture Statistic**: Here you will find information about the **Valid Points** and the **Valid Ratio**.

The recorded data can be exported. There are two options:

1. **Export single capture**: Click the photo icon to export a single capture of the measurement object.
2. **Export recording**: (continuous) Clicking the Record icon starts the continuous export of the captures. Each frame captures is saved; at 6 FPS, this is equivalent to 360 frames per minute.\
   Click the Record icon again to stop the export.

> [!NOTE]
> This option uses a lot of memory when recording over a long period of time.

## Software Update {#sec-software-update}

For software updates, you will receive a link to the website and a protected access password ([Software Update: Protected access password](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#fig-software-update-password)).

1. After entering your password, you will be redirected to the update download page.
2. Download the update to your computer.
3. Click on the downloaded file.
4. A dialog box appears ([Installation dialog box](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#fig-installation-dialog)).
5. Click on the **Install** button.
   - Installing the update is similar to the initial installation (see chapter [Installing the Software](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-installation-software)).
   - If an error occurs, the software should be uninstalled and reinstalled (see [An error occurs while installing a software update](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#ts-update-error)).

![Software Update: Protected access password](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-24-software-update-password.png)

*Figure 14. Software Update: Protected access password*

![Installation dialog box](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-25-installation-dialog.png)

*Figure 15. Installation dialog box*

# Troubleshooting – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html

This page describes problems with the LumiScan X and the LumiScan software, grouped by category. Start with the [General checks](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#general-checks): they rule out the most frequent causes. Then find your symptom or the exact message in the category list and follow the steps of that entry.

## General checks {#general-checks}

Carry out these checks first. Each of them is a precondition for stable operation of the LumiScan X.

1. Check the power supply - expected: 24 V nominal voltage, applied constantly and without fluctuations (fluctuations can lead to malfunctions of the LumiScan X), or Power over Ethernet (IEEE 802.3af). If you use a PELV supply instead of a SELV supply, all grounding conductors must be connected to a common star grounding point; otherwise unwanted leakage or compensating currents and sensor malfunctions may occur. See [Power Supply](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-power-supply).
2. Wait after switching on - expected: the camera starts as soon as the power supply is connected and is ready to use in about 30 seconds.
3. Check the temperature at the installation site - expected: within the operating temperature of 0 - 55 °C, and the system has reached the optimum temperature before you measure (see [Temperature range](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/safety.html#sec-temperature-range)). Material components attract dust, which can cause the hardware to overheat: check regularly for excessive dust accumulation.
4. Check the computer against the [Hardware Requirements](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-hardware-requirements) and [Software Requirements](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-software-requirements) - expected: at least an Intel i5 2.4 GHz, 8 GB RAM, an NVIDIA GTX 1650 and an Intel Ethernet Adapter I210 (or better).
5. Check the settings of the Ethernet port to which the LumiScan X is connected (**Networking** tab > **Configure** > **Advanced** tab) - expected: jumbo frames **Maximum (9014 bytes)**, **Receive Buffers** 2048, **Transmit Buffers** 2048. If these settings are not possible, update the driver. See [Network Settings](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-network-settings).
6. Check the inbound rules of the Windows Firewall - expected: the LumiScan software is listed, either once for TCP/UDP together or in two entries (Windows creates two rules by default). See [Windows Firewall](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-windows-firewall).
7. Check the anti-virus software - expected: a fixed network adapter is assigned to the LumiScan X and Deep Packet Inspection is deactivated for this adapter. See [Virus Protection](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-virus-protection).
8. Check how the computer is used while the camera is running - expected: no remote desktop connection and no metered connection; both have a significant impact on camera performance. See [Metered Connection and Remote Desktop](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-metered-connection).
9. In the LumiScan Viewer, open **Menu → IP Configuration**, click **Refresh**, select the camera and click **Check Status** - expected: the status display confirms that communication between camera and computer was successful and that both are in the same subnet. Camera and computer must not have the same IP address. A **Static IP** is strongly recommended instead of **DHCP**. See [Camera IP Configuration](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-camera-ip-configuration).
10. Open **Menu → Show log** - the log window provides additional information about the processes in the program. See [User Interface](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-user-interface).

## Connection and network {#connection-and-network}

### Problem: The LumiScan software does not find the camera after the first start {#faq-firewall-camera-not-found}

**Symptoms**

After the LumiScan software was started for the first time, it does not find the camera. The software informs you with a message.

**Possible causes**

- At the first start, network access for the LumiScan software was denied in the Windows Defender prompt.
- The Windows Defender prompt did not appear at the first start.

**Diagnostic procedure**

1. Check the inbound rules of the Windows Firewall - expected: the LumiScan software is listed (by default in two rules created by Windows, see [Two rules created by Windows Firewall](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#fig-firewall-rules-ts)).

![Two rules created by Windows Firewall](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/fig-10-firewall-rules.png)

*Figure 1. Two rules created by Windows Firewall*

**Resolution**

- **If access was denied:** restart the LumiScan software so that Windows asks for permission again, and confirm the access permission for the LumiScan software.

- **If the prompt did not appear, or the automatic Windows prompt fails:** allow the app manually in the Windows Defender Firewall settings:
  1. Go to **Start → Settings → Privacy & security → Windows Security → Open Windows Security**.

  2. In the left menu bar, click **Firewall and Network Protection**.

  3. Click **Allow application access through firewall**. A window opens with the advanced settings for the application permissions.

  4. Click **Change settings → Allow other app**.

  5. Select the `LumiScanViewer` file in the `bin` subfolder of the installation directory. No further changes are required.

  6. Click **Add**, then **Done**. The new rule is activated.

     See [Manual Access to the Network](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-manual-network-access).

**If the problem persists**

Continue with [Problem: `Device not found.`](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-device-not-found). Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with the message of the software and a screenshot of the inbound rules of the Windows Firewall.

### Problem: `Device not found.` {#faq-device-not-found}

**Symptoms**

The LumiScan software shows the message `Device not found.`

**Possible causes**

- A hardware start error.
- A network configuration error.
- The camera is blocked by the Windows Firewall or the virus protection.
- A firmware error: the LumiScan X is not found even after repeated restarts, and its current is approx. 80 mA instead of the usual 160-250 mA.

**Diagnostic procedure**

1. Check the power supply and the cables of the camera - expected: the camera is powered (24 V via the sensor/actuator cable or PoE) and the Ethernet cable is connected to the Ethernet port of the computer. See [Connecting the Camera System](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-connecting-the-camera-system).
2. Wait about 30 seconds after switching on - expected: the camera has started.
3. Check the IP address of the computer: in **Menu → IP Configuration**, section **Computer Network Information** - expected: the **NIC** is the network adapter to which the camera is connected, and its IP and subnet mask are in the same subnet as the camera.
4. Click **Refresh** - expected: the camera appears in the **Camera Selection Dropdown**.
5. Check the Windows Firewall inbound rules and the virus protection as described in the [General checks](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#general-checks) - expected: the LumiScan software is allowed and the adapter is not subject to Deep Packet Inspection.
6. If the camera is still not found after repeated restarts, check the current of the camera - expected: 160-250 mA. A current of approx. 80 mA indicates a firmware error.

**Resolution**

- **If a hardware start error occurred:** unplug the camera, wait 10 seconds and reconnect it. Wait about 30 seconds until the camera is ready.
- **If the network configuration is wrong:** set the IP address of the computer and of the camera so that both are in the same subnet but do not have the same IP address (example: PC 192.168.71.5, camera 192.168.71.6, subnet mask usually 255.255.255.0). Use **Static IP** for the camera. See [Configuration Steps](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-configuration-steps).
- **If the camera is blocked by the firewall or the virus protection:** allow the LumiScan software as described in [Problem: The LumiScan software does not find the camera after the first start](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-firewall-camera-not-found) and deactivate Deep Packet Inspection for the adapter of the LumiScan X (see [Virus Protection](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-virus-protection)).
- **If a firmware error occurred (approx. 80 mA):** the LumiScan X must be sent to HD Vision Systems for repair. Contact customer support.

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with the serial number of the camera, the IP addresses of the computer and the camera, and the current you measured.

### Problem: `Access denied.` {#faq-access-denied}

**Symptoms**

The LumiScan software shows the message `Access denied.`

**Possible causes**

- Another software uses the camera.
- The previous program was not terminated normally.

**Diagnostic procedure**

1. Check whether another program that uses the LumiScan X is open on the computer - expected: no other program uses the camera.

**Resolution**

- **If another software uses the camera:** close the other program that uses the LumiScan X.
- **If no other program uses the camera (previous program not terminated normally):** turn the LumiScan X off and turn it on again after 15 seconds.

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with the names of the other programs that were running on the computer.

### Problem: `Incomplete Frames` {#faq-incomplete-frames}

**Symptoms**

The LumiScan software shows the message `Incomplete Frames`.

**Possible causes**

- Incorrect network settings of the computer.

**Diagnostic procedure**

1. Open the settings of the Ethernet port to which the LumiScan X is connected: **Change adapter options** > Ethernet port > **Networking** tab > **Configure** > **Advanced** tab - expected: jumbo frames are set to **Maximum (9014 bytes)**, **Receive Buffers** and **Transmit Buffers** to 2048.

**Resolution**

- **If the network settings are incorrect:**
  1. Select **Maximum (9014 bytes)** for jumbo frames.

  2. Set **Receive Buffers** to 2048 and **Transmit Buffers** to 2048.

  3. If these settings are not possible, update the driver.

     See [Network Settings](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-network-settings).

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with the name and driver version of the network adapter and a screenshot of its **Advanced** tab.

## Image acquisition {#image-acquisition}

### Problem: `Acquisition timeout.` {#faq-acquisition-timeout}

**Symptoms**

The LumiScan software shows the message `Acquisition timeout.`

**Possible causes**

- Incorrect settings: the exposure time is longer than the timeout.
- Incorrect settings: with a hardware trigger, the trigger signal does not reach the LumiScan X.
- An incorrect network connection or network configuration.

**Diagnostic procedure**

1. Check **Exposure Time [μs]** on the **Basic** tab of the camera settings - expected: the exposure time is not longer than the timeout.
2. If **Trigger** is set to **Hardware Trigger**, check the wiring of the IO-Link & Power connector - expected: the trigger signal is connected to pin 4 (black, Trigger IN) and pin 2 (white, Trigger GND). See [Pin Assignment IO-Link & Power](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-pin-assignment-io-link).
3. Check the trigger signal - expected: high level at least 5 V (optimum 24 V); the minimum signal length depends on the internal resistance of the source (up to 5 milliseconds). See [Trigger In Signal](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-trigger-input-signal).
4. Check the network settings, the Windows Firewall and the virus protection as described in the [General checks](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#general-checks).

**Resolution**

- **If the exposure time is longer than the timeout:** reduce **Exposure Time [μs]**. See [Camera Settings](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-camera-settings).
- **If the hardware trigger signal does not reach the camera:** correct the wiring or the trigger signal so that the requirements above are met.
- **If the network configuration is incorrect:** check and optimize the network configuration (see [Virus Protection](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-virus-protection) and [Windows Firewall](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-windows-firewall)).
- **If nothing helps:** contact HD Vision Systems to check the timeout threshold and increase it if necessary.

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with the exposure time, the **Trigger** mode and, with a hardware trigger, a description of the trigger source and signal.

### Problem: A timeout message appears and only a black image is displayed during recording {#faq-timeout-black-image}

**Symptoms**

A timeout message appears. Only a black image is displayed during recording, although the connected sensor is recognized and appears in the drop-down menu.

**Possible causes**

- The firewall is configured incorrectly: the camera is recognized, but its data is blocked.
- The virus protection blocks the camera.

**Diagnostic procedure**

1. Check the inbound rules of the Windows Firewall - expected: the LumiScan software is listed (see [Windows Firewall](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-windows-firewall)).
2. Check the anti-virus software - expected: Deep Packet Inspection is deactivated for the network adapter of the LumiScan X.

**Resolution**

- **If the firewall blocks the camera:** allow the LumiScan software in the Windows Defender Firewall as described in [Problem: The LumiScan software does not find the camera after the first start](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-firewall-camera-not-found).
- **If the virus protection blocks the camera:** assign a fixed network adapter to the LumiScan X and deactivate Deep Packet Inspection for this adapter (see [Virus Protection](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-virus-protection)).

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with the exact timeout message and a screenshot of the inbound rules of the Windows Firewall.

### Problem: Frames are missing when using the hardware trigger {#faq-missing-frame}

**Symptoms**

With **Trigger** set to **Hardware Trigger**, not every trigger signal results in an image (missing frame).

**Possible causes**

- The hardware trigger is faster than the image acquisition.

**Diagnostic procedure**

1. Compare the interval between two hardware trigger signals with the minimum image capture time - expected: the trigger interval is greater. For orientation: with the pixel format **Mono8** the sensor captures 6 frames per second, with **Mono12** the frame rate is limited to 3 frames per second (see [Camera Settings](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-camera-settings)).

**Resolution**

- **If the hardware trigger is faster than the image acquisition:** set the hardware trigger interval greater than the minimum image capture time.

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with the trigger interval, the pixel format, the exposure time and the **Trigger Delay [μs]**.

### Problem: No image is displayed in the LumiScan Viewer when using the software trigger {#faq-no-image-software-trigger}

**Symptoms**

**Trigger** is set to **Software Trigger**, and no image is displayed in the LumiScan Viewer.

**Possible causes**

- No software trigger is sent to the camera.
- The button with the photo icon is not enabled, because no valid path is selected in **Export Folder** under **Capture**.

**Diagnostic procedure**

1. Check the button with the photo icon in the acquisition control panel - expected: the button is enabled.
2. Check **Export Folder** under **Capture** in the settings panel - expected: a valid path is selected.

**Resolution**

- **If no software trigger was sent:** click the button with the photo icon. It sends a software trigger that captures exactly one image.
- **If the button is not enabled:** select a valid path in **Export Folder** under **Capture** (see [Data Export](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-data-export)).

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with the export folder path you selected.

### Problem: The LumiScan Viewer shows noisy, incorrect images {#ts-noisy-images}

**Symptoms**

The images in the LumiScan Viewer are noisy or incorrect.

**Possible causes**

- The camera is not configured correctly.

**Diagnostic procedure**

1. Check the camera settings on the **Basic** and **Advanced** tabs (**Pixel Format**, **Exposure Time [μs]**, **Enable Autoexposure**, **Target Intensity**) - expected: they are set for the current measurement object. The measurement parameters must be set individually for each measurement object.
2. Enable **Show Overexposure** on the **Advanced** tab - pixels whose intensity exceeds the **Overexposure Limit** are displayed in red.

**Resolution**

- **If the camera is not configured correctly:**
  1. Stop recording.
  2. Check and correct the camera configuration (see [Camera Settings Configuration](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-camera-settings-configuration)).
  3. Restart recording.

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with a parameter file saved with **Menu → Save Parameters** and a screenshot of the image.

## Point cloud {#point-cloud}

### Problem: No point cloud is displayed {#faq-no-point-cloud}

**Symptoms**

The **Point Cloud** tab shows no point cloud of the measurement object.

**Possible causes**

- Incorrect settings:
  - The serial number in the calibration file name does not match the connected LumiScan X.
  - The minimum and maximum depth (**Depth Range**) do not include the measurement object.
  - The images are too bright or too dark.
  - The **Confidence Threshold** is too high, or the pre-/postprocessing filters are unsuitable.

**Diagnostic procedure**

1. Compare the serial number in the name of the calibration file (`.hdvcal`) entered in the \*Calibration section with the serial number on the back of the camera housing (for example LX20230101) - expected: they match. **Help → Show Calibration** shows information about the currently loaded calibration.
2. Check **Depth Range** - expected: the minimum and maximum depth in millimeters include the actual position of the measurement object.
3. On the **Frame** tab, check the images - expected: not too bright and not too dark. **Show Overexposure** on the **Advanced** tab highlights overexposed pixels in red.
4. Check **Basic Processing** (**Confidence Threshold**, **Preprocessing**, **Postprocessing Filter**) and the **Box Filter** - expected: the confidence threshold does not filter out the measurement object, and the box of the **Box Filter** contains the measurement object (the filter removes all points outside the box).

**Resolution**

- **If the calibration file does not match:** enter the calibration file whose name contains the serial number of the connected LumiScan X. By default, the calibration files are stored in `C:\ProgramData\HD Vision Systems GmbH\calibration`. See [Calibration](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-calibration).
- **If the depth range is wrong:** set the minimum and maximum depth to the actual position of the measurement object. See [Depth Range](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-depth-range).
- **If the images are too bright or too dark:** adjust **Exposure Time [μs]**, or **Target Intensity** with **Enable Autoexposure**. See [Camera Settings](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-camera-settings).
- **If the confidence threshold or the filters are unsuitable:** reduce the **Confidence Threshold** and change the pre-/postprocessing filters. See [Processing](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-processing).

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with the name of the calibration file, the output of **Help → Show Calibration**, a parameter file saved with **Menu → Save Parameters** and, if possible, an exported capture.

### Problem: The point cloud is poor {#faq-poor-point-cloud}

**Symptoms**

A point cloud is displayed, but its quality is poor.

**Possible causes**

- Incorrect calibration.
- Incorrect settings.
- A dirty front cover (front glass).
- The calibration file does not match the current measurement distance.
- The camera sensor is not focused.

**Diagnostic procedure**

1. Carry out the diagnostic procedure of [Problem: No point cloud is displayed](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-no-point-cloud).
2. Check the front glass - expected: no contamination.
3. Compare the distance between camera and measurement object with the standard calibration range and the in-focus range of your camera configuration - expected: the distance is within both ranges. See [Standard Configurations](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-standard-configurations).
4. Enable **Enable Capture Statistics** under **Capture** - the **Capture Statistic** shows the **Valid Points** and the **Valid Ratio**, which let you compare captures before and after a change.

**Resolution**

- **If the calibration or the settings are incorrect:** follow the resolution of [Problem: No point cloud is displayed](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-no-point-cloud).
- **If the front glass is dirty:** disconnect the power and clean the front glass as described in [Cleaning the Coated Front Glass](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/maintenance.html#sec-front-glass-cleaning). Do not use microfiber cloths, solvents or alcohol-based cleaners.
- **If the calibration file does not match the measurement distance, the camera sensor is not focused, or nothing helps:** the camera must be sent back to HD Vision Systems for recalibration. Contact customer support.

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with the serial number of the camera, the measurement distance, the name of the calibration file and, if possible, an exported point cloud (`.ply` or `.pcd`).

## Licensing and software update {#licensing-and-software}

### Problem: `Not enough license.` {#faq-not-enough-license}

**Symptoms**

The LumiScan software shows the message `Not enough license.`

**Possible causes**

- The licence is insufficient.
- The licence is used by another program.
- The licence has not yet been released after the previous program was terminated.

**Diagnostic procedure**

1. Check whether another LumiScan program is open on this computer, also by another user - expected: none.
2. Open CodeMeter Control Center, **License** tab - expected: the LumiScan Key is listed as **CmStick/C** with a serial number of the form `3-1234567`. See [Recognising the key](https://docs.hdvisionsystems.com/en/lumiscan-licensing/1.0.4/lumiscan-key.html#recognising-the-key).

**Resolution**

- **If the licence is used by another program:** close all other LumiScan programs, also those opened by other users.
- **If the previous program was just terminated:** try again in 5 to 10 seconds.
- **If the LumiScan Key is not listed:** follow [Key not detected](https://docs.hdvisionsystems.com/en/lumiscan-licensing/1.0.4/troubleshooting.html#key-not-detected).
- **If the licence is insufficient:** one LumiScan Key is needed for each device on which the software runs at the same time (see [One key per device](https://docs.hdvisionsystems.com/en/lumiscan-licensing/1.0.4/lumiscan-key.html#one-key-per-device)). If you permanently need more licences, create a licence request as described in [Requesting a Licence Update](https://docs.hdvisionsystems.com/en/lumiscan-licensing/1.0.4/requesting-a-licence-update.html).

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to [licenses@hdvisionsystems.com](mailto:licenses@hdvisionsystems.com), together with the serial number of your LumiScan Key. See also [Licensing troubleshooting](https://docs.hdvisionsystems.com/en/lumiscan-licensing/1.0.4/troubleshooting.html).

### Problem: An error occurs while installing a software update {#ts-update-error}

**Symptoms**

An error occurs while you install a software update of the LumiScan software.

**Possible causes**

- No specific cause is documented. The resolution below applies to every error during the update.

**Diagnostic procedure**

1. Note the exact error message of the installation dialog.

**Resolution**

- **If an error occurs during the update:** uninstall the LumiScan software and install it again (see [Installation](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-installation-software) and [Software Update](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-software-update)).

**If the problem persists**

Send the information listed under [Information for support](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#support-information) to support, together with the file name of the installer and the exact error message.

## Information for support {#support-information}

If a problem persists, send the following information to customer support:

- **Software version:** the installed LumiScan version, shown under **Help → About**.
- **Operating system:** the operating system of the computer and the NVIDIA driver version (the supported versions are listed under [Software Requirements](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-software-requirements)).
- **Camera:** the serial number of the LumiScan X (on the back of the camera housing, for example LX20230101).
- **Log:** the content of the log window (**Menu → Show log**).
- **Error:** the exact error message, a screenshot and the time the error occurred.
- **Communication status:** the network configuration from **Menu → IP Configuration** (**Computer Network Information**, the IP and subnet mask of the camera, **DHCP** or **Static IP**) and the result of **Check Status**.
- **Configuration files:** a parameter file saved with **Menu → Save Parameters** (`.json` or `.ini`), the name of the calibration file (`.hdvcal`) and the output of **Help → Show Calibration**.
- **Licensing:** the serial number of the LumiScan Key, if the problem concerns licensing.

Customer Support: +49 6221 6721905\
E-mail: [customer.success@hdvisionsystems.com](mailto:customer.success@hdvisionsystems.com)

Licence requests and licensing questions: [licenses@hdvisionsystems.com](mailto:licenses@hdvisionsystems.com)

# FAQ – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/faq.html

Short answers to common questions about LumiScan X. Each entry links to the page with the details.

> [!TIP]
> Each entry has a fixed anchor (for example `#faq-camera-ip-address`). Error messages and other problems are described in [Troubleshooting](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html); search that page for the exact error message.

## Installation and connection

### What hardware do I need to operate the LumiScan X? {#faq-hardware-requirements}

- **Answer:**
  - LumiScan X camera system and a 24 V DC power supply unit
  - Ethernet cable CAT6A, S/FTP shielded, M12 male to RJ45 male, TIA-568B variant (recommended: Phoenix Contact part number 1295151 for angled or 1408647 for straight connectors)
  - Sensor/actuator cable, 5-pin, free cable end to M12 socket
  - Computer with at least an Intel i5 2.4 GHz processor, 8 GB RAM, an NVIDIA GTX 1650 graphics card and an Intel Ethernet Adapter I210 (or better)
- **More:** [Hardware Requirements](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-hardware-requirements), [Ethernet Cable Characteristics](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-ethernet-cable-characteristics)

### How can the LumiScan X be powered? {#faq-power-supply}

- **Answer:** Operate the device with 24 V nominal voltage only and avoid voltage fluctuations. The camera starts as soon as power is connected and is ready in about 30 seconds. There are two options:
  - 24 V DC via the 5-pin sensor/actuator cable (IO-Link & Power connector: pin 1 brown = Sensor 24 V, pin 3 blue = Sensor GND).
  - Power over Ethernet (IEEE 802.3af) from a PoE-enabled Ethernet port on the computer or from a PoE injector.
- **More:** [Connecting the Camera System](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-connecting-the-camera-system), [Pin Assignment IO-Link & Power](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-pin-assignment-io-link)

### How do I mount the camera and which orientation is correct? {#faq-mounting-orientation}

- **Answer:** Mount the LumiScan X using the four rear M4 threaded holes (maximum thread depth 4 mm); the optional precision holes allow more precise positioning. Orient the camera so that a cross (+), not an x, is visible on the front screen; the logo is then visible at an angle. Tighten the connectors carefully by hand and do not use pliers or similar tools.
- **More:** [Mounting the Camera](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-mounting-the-camera), [Camera Housing Dimensions](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#sec-camera-housing-dimensions)

## Network and firewall

### Which network settings does the computer need for the LumiScan X? {#faq-network-adapter-settings}

- **Answer:** In the settings of the Ethernet port to which the camera is connected (**Networking** tab > **Configure** > **Advanced** tab):
  - Set jumbo frames to **Maximum (9014 bytes)**.
  - Set **Receive Buffers** and **Transmit Buffers** to 2048.
  - If these settings are not possible, update the network driver.
  - Assign a fixed network adapter to the LumiScan X and deactivate Deep Packet Inspection of the anti-virus software for this adapter.
  - Avoid remote desktop and metered connections while the camera is running; they significantly reduce camera performance.
- **More:** [Network Settings](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-network-settings), [Virus Protection](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-virus-protection), [Metered Connection and Remote Desktop](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#sec-metered-connection)

### How do I assign a static IP address to the camera? {#faq-camera-ip-address}

- **Answer:** A **Static IP** is strongly recommended instead of **DHCP**, because a DHCP address may change and interrupt the connection. Camera and computer must be in the same subnet but must not have the same IP (example: PC 192.168.71.5, camera 192.168.71.6, subnet mask usually 255.255.255.0).
  1. In the LumiScan Viewer, open **Menu → IP Configuration**.
  2. Click **Refresh** and select the camera from the dropdown list.
  3. Enable **Static IP**, enter the IP address and check the subnet settings.
  4. Click **Apply**, then **Check Status** to confirm the connection.
- **More:** [Camera IP Configuration](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-camera-ip-configuration), [Configuration Steps](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-configuration-steps)

## Calibration

### Where are the calibration files and which one do I need? {#faq-calibration-file}

- **Answer:** Calibration files (`.hdvcal`) are stored by default in `C:\ProgramData\HD Vision Systems GmbH\calibration`; enter the file location in the **Calibration** section of the LumiScan Viewer. The serial number in the calibration file name must match the serial number of the connected LumiScan X, which is on the back of the camera housing (for example LX20230101). **Help → Show Calibration** shows information about the currently loaded calibration.
- **More:** [Calibration](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/lumiscan-software.html#sec-calibration), [Product Description](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/product-description.html#ch-product-description)

## Troubleshooting {#troubleshooting}

Problems and error messages are described step by step in [Troubleshooting](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html):

- [The LumiScan software does not find the camera after the first start](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-firewall-camera-not-found)
- ["Device not found."](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-device-not-found)
- ["Access denied."](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-access-denied)
- ["Incomplete Frames"](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-incomplete-frames)
- ["Acquisition timeout."](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-acquisition-timeout)
- [A timeout message appears and only a black image is displayed during recording](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-timeout-black-image)
- [Frames are missing when using the hardware trigger](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-missing-frame)
- [No image is displayed in the LumiScan Viewer when using the software trigger](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-no-image-software-trigger)
- [The LumiScan Viewer shows noisy, incorrect images](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#ts-noisy-images)
- [No point cloud is displayed](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-no-point-cloud)
- [The point cloud is poor](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-poor-point-cloud)
- ["Not enough license."](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#faq-not-enough-license)
- [An error occurs while installing a software update](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/troubleshooting.html#ts-update-error)

## Licensing, maintenance and support

### How is the LumiScan software licensed? {#faq-licence}

- **Answer:** The LumiScan software is licensed with the LumiScan Key and needs CodeMeter Runtime 9.00 or later. Install CodeMeter Runtime and connect the LumiScan Key. One LumiScan Key is needed per device that runs the software at the same time; keys can be exchanged between devices.
- **More:** [Licence](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/installation.html#licence), [Installing CodeMeter Runtime](https://docs.hdvisionsystems.com/en/lumiscan-licensing/1.0.4/installing-codemeter.html), [Licensing FAQ](https://docs.hdvisionsystems.com/en/lumiscan-licensing/1.0.4/faq.html)

### How do I clean the front glass? {#faq-cleaning-front-glass}

- **Answer:** Disconnect the power before cleaning. The front glass has a sensitive optical coating:
  - Use only clean, soft cotton cloths or clean chamois leather and a water-based, neutral or mildly alkaline glass cleaner without abrasive components.
  - Remove coarse particles without rubbing them across the surface, keep the surface well wetted, clean with minimal pressure and wipe from the center toward the edges.
  - Do not use microfiber cloths, solvents or alcohol-based cleaners, acids, descaling agents, cleaners with a high ammonia content or with chlorine, or abrasive cleaners.
- **More:** [Cleaning the Coated Front Glass](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/maintenance.html#sec-front-glass-cleaning)

### Where can I get further help? {#faq-support}

- **Answer:** See the site-wide [LumiScan FAQ](https://docs.hdvisionsystems.com/en/faq.html). Contact customer support at [customer.success@hdvisionsystems.com](mailto:customer.success@hdvisionsystems.com) or +49 6221 6721905. For licences, write to [licenses@hdvisionsystems.com](mailto:licenses@hdvisionsystems.com).

# Maintenance – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/maintenance.html

## Maintenance {#ch-maintenance}

> [!WARNING]
> **Electric shock hazard**
>
> When performing maintenance on a powered device, there is a risk of electric shock. This could result in damage to the product, serious injury or even death.
>
> - Unplug the power cord and turn off the power before cleaning.

> [!NOTE]
> Material components attract dust, dirt, carpet fibers, animal hair and smoke particles. These can cause the hardware to overheat:
>
> - Check for excessive dust accumulation on a regular basis

### Cleaning the Camera Housing {#sec-cleaning-the-camera-body}

Observe the following instructions when cleaning the surface of the camera housing:

- Do not use solvents, as they may damage the surface of the camera housing.
- Use a clean, soft, and dry cloth that does not become statically charged during cleaning, such as a cotton cloth.
- Remove stubborn contamination using a soft cloth slightly moistened with a neutral cleaning agent.
- Do not use paper towels, facial tissues, or dish towels. Particles may detach from these materials and contaminate the camera housing.

#### Cleaning the Coated Front Glass {#sec-front-glass-cleaning}

The front glass has a sensitive optical coating. Contamination, scratches, or damage to the coating may impair the performance of the camera. Therefore, clean the front glass only in accordance with the following instructions.

> [!NOTE]
> These instructions also apply to the previous version of the front glass. There is no need to distinguish between the two versions.

**Suitable Cleaning Agents and Materials**

- Use only clean, soft cotton cloths or clean chamois leather.
- Use a water-based, neutral, or mildly alkaline glass cleaner.
- The glass cleaner must not contain any abrasive or scouring components.

**Cleaning Procedure**

1. Carefully remove coarse particles and contamination from the glass surface. Do not rub the particles across the surface.
2. Use a sufficient amount of cleaning fluid to ensure that the surface remains well wetted during cleaning.
3. Clean the glass with minimal pressure. Avoid dry rubbing and do not allow the cleaning cloth to squeak against the surface.
4. Wipe the glass from the center toward the edges.

**Unsuitable Cleaning Agents and Materials**

Do not use any of the following agents or materials, as they may damage the optical coating:

- alkaline washing solutions, such as curd soap and certain laundry detergents;
- alkaline solutions and strongly alkaline cleaners, such as toilet cleaners;
- acids, such as hydrochloric acid, vinegar, or lemon juice;
- descaling agents, especially products based on citric acid;
- degreasing agents, such as acetone, methylene chloride, trichloroethylene, or gasoline;
- cleaning agents with a high ammonia content;
- cleaning agents containing chlorine or hypochlorite;
- solvents and alcohol-based cleaning agents, in particular ethanol, isopropanol, other alcohols, or hexane;
- abrasive cleaners, steel wool, scouring pads, blades, or coarse cloths;
- cloths containing woven metal threads;
- microfiber cloths.

# Disposal – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/disposal.html

According to the European Directive on Waste Electrical and Electronic Equipment (WEEE Directive 2012/19/EU), this product must be disposed of as electronic waste.\
If the product is used outside the European Union, it must be disposed of in accordance with the national regulations of the country in which it is used.

![WEEE disposal symbol](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/symbol-weee.png)

*Figure 1. WEEE symbol: do not throw in the household waste.*

Do not throw in the household waste!

# Warranty – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/warranty.html

HD Vision Systems GmbH provides a one-year warranty for this camera. To ensure that your warranty remains valid, please follow these guidelines:

- **Read the manual**: Read the manual carefully before using the camera.
- **Do not remove the serial number label from the camera**: If the label is removed and the serial number cannot be read from the camera’s registers, the warranty is invalid.
- **Do not open the camera housing**: Touching internal components can damage them. If the camera needs to be serviced, only HD Vision Systems GmbH qualified personnel should perform this service. Unauthorized opening of the housing will void the warranty.
- **Prevent foreign objects from entering or being introduced into the camera housing**: Do not allow liquid, flammable, or metallic substances to enter the camera body. Foreign objects may cause the camera to malfunction or cause a fire.
- **Avoid electromagnetic fields**: Do not use the camera near strong electromagnetic fields. Avoid electrostatic charges.
- **Clean carefully**: If you need to clean the camera body, follow the instructions in the [Maintenance](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/maintenance.html#ch-maintenance) section.

# CE Declaration – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/ce-declaration.html

The CE Declaration of Conformity is available as a PDF document.

![CE Declaration of Conformity](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_images/ce-declaration-of-conformity.jpg)

[Download CE Declaration of Conformity (PDF)](https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/_attachments/ce-declaration-of-conformity.pdf)

# General Terms and Conditions – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/terms-and-conditions.html

If any section or part of a section of these terms and conditions is found to be invalid, void, or unenforceable, then that section or part of a section shall be severed from these terms and conditions and the remaining terms and conditions shall remain in full force and effect.

These warranty conditions are subject to the law of the country in which the product was purchased. This choice of law shall not include the provisions of international private law or the United Nations Convention on Contracts for the International Sale of Goods.

HD Vision Systems GmbH is entitled to subcontract the performance of HD Vision Systems GmbH’s obligations to third parties or to transfer HD Vision Systems GmbH’s obligations to perform the contract to third parties. However, this does not release HD Vision Systems GmbH from its obligations to you.

HD Vision Systems GmbH shall not be liable for any failure to perform or delay in performing the Product Warranty if such failure or delay is due to circumstances beyond the reasonable control of HD Vision Systems GmbH.

You agree that all information and data you provide to HD Vision Systems GmbH under this Product Warranty is neither confidential nor proprietary. You also agree that HD Vision Systems GmbH may collect and process your data on your behalf in order to provide the services. This may include the transfer of your data to companies or service providers affiliated with HD Vision Systems GmbH, which may be located in countries that do not provide the same level of data protection as your country of residence, including Australia, Canada, member states of the European Union, India, Japan, China and the United States.

HD Vision Systems GmbH has security measures in place to protect your information from unauthorized access or disclosure and from unauthorized destruction. You are responsible for any instructions you give HD Vision Systems GmbH regarding the processing of your data. HD Vision Systems GmbH will endeavor to comply with such instructions to the extent reasonably necessary to provide the Services and support obligations under the Product Warranty. If you do not agree with the above, or if you have any questions about how the described processing affects your data, please contact HD Vision Systems GmbH directly.

There are no oral representations, warranties or ancillary agreements to this warranty. Changes and/or additional agreements are only valid if they are documented in writing and signed in a legally binding manner. This also applies to agreements concerning the written form requirement itself.

The exclusive place of jurisdiction is the registered office of HD Vision Systems GmbH. Exclusive statutory places of jurisdiction remain unaffected by this.

# General Disclaimer – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/disclaimer.html

The manufacturer is not liable for damage to life, body or health or damage to property resulting from improper use, but the operator is. Please note that operating and/or connection errors are beyond our control. Understandably, we cannot accept any liability for damage resulting from this.

Any damage caused by unauthorized debugger-based activities to inspect, analyze, or manipulate the LumiScan software is the sole responsibility of the user. Any attempt to use a debugger is strictly prohibited and may result in irreversible consequences such as loss of data, interruption of service, and even legal action. The manufacturers, developers and distributors of the software are not liable for any damage or loss resulting from the user’s failure to comply with this warning.

Claims for damages on the part of the purchaser arising from culpa in contrahendo, breach of secondary contractual obligations and tort are excluded, unless they are based on intent or gross negligence on the part of HD Vision Systems GmbH itself or one of our vicarious agents.

Recourse claims in the sense of §12 of the Product Liability Act are excluded, unless the party entitled to recourse proves that the defect was caused by HD Vision Systems GmbH and was at least due to gross negligence.

If any provision of this Agreement is or becomes invalid or unenforceable, the validity of the remaining provisions shall not be affected. The invalid or unenforceable provision shall be replaced by a valid and enforceable provision whose effects come as close as possible to the economic purpose pursued by the parties with the invalid or unenforceable provision. The above provisions shall apply mutatis mutandis in the event that the contract proves to be incomplete. German courts shall have exclusive jurisdiction over any disputes arising in connection with this disclaimer.

For further information on the warranty, please contact the manufacturer.

# Imprint – LumiScan X

URL: https://docs.hdvisionsystems.com/en/lumiscan-x/2.0.0/imprint.html

|   |
| --- |
| CEO: |
| PD Dr. Christoph Garbe |
| Headquarters: |
| Heidelberg |
| Register court: |
| Amtsgericht Mannheim |
| Register number: |
| HRB 726917 |
| Tel.: |
| +49 (6221) 67219-00 |
| Fax: |
| +49 (6221) 67219-01 |
| Email: |
| [info@hdvisionsystems.com](mailto:info@hdvisionsystems.com) |
| WWW: |
| <https://www.hdvisionsystems.com/> |

HD Vision Systems GmbH\
Palo-Alto-Platz 11\
69124 Heidelberg

**Copyright © 2025 HD Vision Systems**

- All rights reserved.
- The image processing system and software described in this manual are the intellectual property of HD Vision Systems GmbH in Heidelberg.
- All rights to the system, the principle of the system, the drawings, the circuit diagrams and the software are the property of the manufacturer and are subject to the Copyright and Related Rights Act (UG) of 9.9.1965 in the currently valid version.
- No part of this document may be reproduced without the written permission of the publisher.
- Technical changes reserved.

Version_2025_12_11
