> ## Documentation Index
> Fetch the complete documentation index at: https://docs.atomscale.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Standard Capture (GenTL)

> Open a RHEED camera read-only through its vendor GenTL producer

With the **Standard (GenTL)** frame source, the integration opens the camera read-only through the camera vendor's GenTL producer, alongside your RHEED software. Use it for cameras that are not GigE Vision, or when [network capture](https://docs.atomscale.ai/gateway/rheed/network-capture.md) is not possible on this computer. It doesn't need integration admin access.

Some RHEED software opens the camera exclusively, which blocks any second viewer. [Diagnostics](#check-the-camera-with-diagnostics) tell you if that is the case; for a GigE Vision camera, use network capture instead.

## Before You Start

* **The camera vendor's SDK or driver package** installed on this computer. It provides the **GenTL producer**, a file ending in `.cti`.
  * The producer must match the integration's architecture: the 64-bit SDK on 64-bit Windows.
  * Most SDKs register their producer in the `GENICAM_GENTL64_PATH` (or `GENICAM_GENTL32_PATH`) environment variable, which the integration searches. If you installed the SDK after starting Atomscale, quit and reopen Atomscale so it sees the variable.
* **The RHEED software able to acquire** from the camera.
* **For GigE cameras**, a network path that supports the camera's packet size. If the camera uses jumbo packets, enable jumbo frames on the camera-facing network adapter and on any switch in between.

## Set Up Standard Capture

You can ask the [Gateway assistant](https://docs.atomscale.ai/gateway/assistant.md#set-up-an-integration) to set **Frame Source** to **Standard (GenTL)** and apply the producer path or camera ID you provide. Install the vendor SDK or driver yourself first.

**1. Select the frame source**

Add a **RHEED Camera (GenTL)** integration, or stop an existing one and click
Configure. Set **Frame Source** to **Standard (GenTL)**.

**2. Choose the producer and camera**

* **GenTL Producer**: leave blank to search automatically, or enter the full path to the
  `.cti` file, for example `C:\Program Files\Vendor\producer.cti`.
* **Camera**: leave blank if the producer sees exactly one camera. Otherwise enter its serial
  number or ID exactly as the producer reports it.

**3. Fill in the growth details**

Optionally set **Stage Rotation** to the stage speed in RPM for faster first results on a
rotating stage. Left blank, Atomscale detects whether the stage rotates. Review the
[session settings](https://docs.atomscale.ai/gateway/rheed/sessions.md).

**4. Apply the configuration**

Click Apply Configuration. The integration loads the producer
and looks for the camera; if it can't, the affected field shows why (see
[Troubleshooting](#troubleshooting)). It also runs a quick camera check and writes the result to
the activity log.

**5. Start the integration**

Click Start Integration. On Windows, the first start asks an
administrator to approve an inbound firewall rule for the camera's network stream (see
[Windows Firewall Rules](https://docs.atomscale.ai/gateway/reference/network.md#windows-firewall-rules)). Without it, a GigE camera's
frames may be blocked.

**6. Acquire**

Start acquisition in your RHEED software. The activity log shows Data item opened: RHEED Stream @ …,
and the stream appears in Atomscale as Stream Active.

## Check the Camera with Diagnostics

Run diagnostics when setting up a new camera or when frames don't arrive. They check the camera and stream without creating data items or uploading.

1. Stop the integration, open Configure, and turn on Show advanced settings.
2. Turn on Diagnostics Only and apply.
3. Start the integration, start acquisition in the RHEED software, and read the **Activity Logs**. Diagnostics report whether a frame arrived, the frame size and pixel format, frame brightness, and common problems such as a packet size larger than the network adapter supports or software that holds the camera exclusively.
4. Stop the integration, turn Diagnostics Only off, and apply.

## Troubleshooting

| Message | Cause and fix |
| - | - |
| No GenTL producer (.cti) was found. | The vendor SDK is not installed, or its producer isn't on the search path. Install the vendor's SDK, restart Atomscale, or enter the full **GenTL Producer** path. |
| GenTL producer does not exist or is not a file: … | The **GenTL Producer** path is wrong. |
| No loadable GenTL producer matches this … adapter. | The producer is for a different architecture, such as a 32-bit `.cti` with the 64-bit integration. Install the matching SDK. |
| No camera was enumerated by the installed GenTL producer. | The producer loaded but sees no camera. Check camera power, the network or USB connection, and the vendor driver. |
| No camera matches "…". Available cameras: … | **Camera** doesn't match any camera. Copy the serial or ID from the list. |
| More than one camera is available. | Enter the intended camera's serial number or ID in **Camera**, exactly as listed. |
| … the camera's host software may hold exclusive access … | The RHEED software opened the camera exclusively. For a GigE Vision camera, use [Network Capture](https://docs.atomscale.ai/gateway/rheed/network-capture.md). |
| Stream packet size … exceeds this computer's …-byte MTU … | Enable jumbo frames on the camera-facing network adapter and every switch on the path, or lower the camera's packet size in the RHEED software. |
| This camera's transport is … | A non-GigE camera (such as USB3 Vision). Some GigE-specific checks don't apply; frames can still arrive. |

For problems with session boundaries or missing data items, see [Recording Sessions](https://docs.atomscale.ai/gateway/rheed/sessions.md#troubleshooting).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.