> For the complete documentation index, see [llms.txt](https://docs.roboflow.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.roboflow.com/deployment/self-hosted/enterprise/deployment-manager/making-changes/configure-line-scan-cameras.md).

# Configure Line Scan Cameras

Set line rate, frame size, exposure, and camera triggers for Basler and Lucid line scan cameras.

A line scan camera captures one row of pixels at a time. These rows form frames for your Workflow. Set the line rate and rows per frame to match the speed of the objects you inspect.

{% hint style="info" %}
Basler and Lucid industrial cameras are available on Enterprise plans. To enable them, [contact the sales team](https://roboflow.com/sales).
{% endhint %}

## Capture Settings

1. Open your device in Deployment Manager, then select a Stream. To create one, follow [Add a Stream](/deployment/self-hosted/enterprise/deployment-manager/setting-up/add-a-stream.md) and choose "Basler Line Scan" or "Lucid Line Scan". For "Basler Line Scan", enter the camera's IP address or serial number.
2. In the Stream's "Configuration" panel, click "Edit" and open "Capture Settings".
3. Set the frame size and timing:
   * "Width (px)": pixels in each scan line.
   * "Line Rate (Hz)": scan lines captured per second when the camera uses its configured line rate.
   * "Lines Per Frame": scan lines grouped into each frame.
   * "Exposure Time (µs)": exposure for each line, in microseconds.
4. Check the timing message below the fields, then click "Save Changes". Wait for the device to apply the change and [check the Stream preview](/deployment/self-hosted/enterprise/deployment-manager/monitoring/view-a-stream.md).

For a free-running camera, the estimated frame rate is the effective line rate divided by lines per frame (ex: 1,000 lines per second and 500 lines per frame gives 2 frames per second). A longer exposure can reduce the line rate. The exposure field shows the line period, and a warning explains when exposure limits capture speed.

<figure><img src="https://1583372177-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FoksNmwps1HmYr8TqHDnX%2Fuploads%2Fgit-blob-3d02febbffc728116acb27876fc637ff0fe77813%2Fline-scan-timing-draft.png?alt=media" alt="Unsaved Basler Line Scan Stream draft with a 1,000 Hz line rate, 500 lines per frame, 2,000 microseconds of exposure, and an exposure-limited timing estimate"><figcaption><p>Unsaved Basler Line Scan Stream draft. Exposure limits the estimated line rate to 500 Hz, giving about 1 frame per second.</p></figcaption></figure>

These values are estimates from your settings. Use the Stream's reported Camera FPS to check the rate the camera achieves.

## Basler Framing and Triggers

In "Capture Settings", turn on "Enable acquisition line rate" to use the configured software line rate when no line trigger is set. With no line trigger and this toggle off, the camera runs as fast as exposure permits.

Turn on "Software line assembly" to group scan lines into frames on the device. You can also set "Min Lines Per Frame" and "Grab Timeout (ms)".

To capture lines from an external signal, enter its input in "Line Trigger Source" (ex: `Line1`) and choose the edge under "Trigger Activation". The timing message then identifies that source, since capture speed follows the signal.

To use a signal to mark frame boundaries, set "Frame Boundary Source", "Frame Boundary Mode", and "Frame Boundary Edge":

* "Gated: frame spans the active boundary signal": the signal controls the frame span, up to "Lines Per Frame".
* "Trigger only: boundary edge starts a fixed-height frame": the selected edge starts a frame with the configured line count.

Click "Save Changes" after editing.

## Camera Nodemap

Use "Camera Nodemap" for camera-specific settings beyond the capture controls. Basler settings appear under "Pylon Nodemap" and Lucid settings under "Arena Nodemap". Use node names and values supported by your camera.

For Lucid cameras with external line or frame triggering, the timing message avoids a fixed frame-rate estimate because the signal controls capture timing.

Camera triggers control image capture. The Stream's ["Triggered" mode](/deployment/self-hosted/enterprise/deployment-manager/making-changes/trigger-a-stream.md) controls when its Workflow runs.