Skip to main content
The kSA 400 integration uploads the frames that k-Space kSA 400 sends from one Image Streamer filter. They arrive in Atomscale as RHEED data items named after their start time, for example kSA 400 @ 4:15 PM, Oct 23, 2026. It is separate from RHEED Camera (GenTL). It reads only what kSA 400 streams, never opens the camera, and never starts, stops, or changes an acquisition.

Before You Start

  • The image stream’s frame rate. Note the rate kSA 400 sends, including any filters that change it. It must be at most 120 FPS.
  • kSAComm, if you want one data item per kSA 400 acquisition (the kSA Acquisition Status boundary mode). In kSA 400, open Options > General > Chamber Interface and select kSAComm (port 1800). Make sure Save settings at program exit is enabled, then restart kSA 400. kSAComm accepts connections only after the restart.
  • A network path, if the gateway runs on another computer. The gateway connects over TCP to the kSA 400 computer on the Image Streamer port and, with kSAComm, on port 1800. On the kSA 400 computer itself, no network setup is needed.
Supported pixel formats are mono at 1, 2, or 4 bytes per pixel and 8-bit BGR or BGRX color. Frames are converted to 8-bit grayscale before upload.

Set Up

Once you’ve added an Image Streamer filter in kSA 400, you can ask the Gateway assistant to install and configure the Atomscale integration. Give it the kSA 400 computer’s address, the Image Streamer port, and the frame rate.
1

Add an Image Streamer filter in kSA 400

Open the camera’s Live Video window and open its properties. On the Filters tab, choose Image Streamer in a filter slot. A streamer in slot 1 sends unprocessed camera frames; later slots send frames after the filters before them. Click Properties and note the TCP port (4000 by default).
2

Add the integration

On the Integrations page, click Add Integration, then Add on kSA 400. See Working with Integrations.
3

Configure the connection

  • kSA 400 Computer: leave 127.0.0.1 when the gateway runs on the kSA 400 computer. Otherwise enter its host name or IP address, without a port or protocol.
  • Image Streamer Port: the port shown in the Image Streamer filter’s properties.
  • Frame Rate (FPS): required. Enter the stream rate configured in kSA 400. The integration trusts this value and does not detect a mismatch, so update it whenever the stream rate changes.
4

Choose the data item boundary

Set Data Item Boundary Mode. See Choose a Boundary Mode.
5

Apply and start

Click Apply Configuration, then Start Integration.
6

Confirm it works

Open Activity Logs. Image stream connected means the integration reached the Image Streamer. Data item opened: kSA 400 @ … means frames are uploading.
To group recordings with the tool log from the same growth, link the integration to its Growth Instrument.

Choose a Boundary Mode

kSA 400’s live video streams whether or not kSA 400 is acquiring, so the mode decides which frames upload. In every mode, a change in frame size or pixel encoding closes the current data item. In kSA Acquisition Status mode, boundaries are accurate to kSA Status Poll Interval, so a stop and restart shorter than one poll ends up in one data item. If kSAComm stops answering, the integration keeps the last status it confirmed. After kSA Status Timeout it closes the open item and uploads nothing until kSA 400 answers again. When kSA 400 reports a stable stage rotation as an item opens, the item records it; otherwise Atomscale detects rotation from the video.

Settings

Settings marked Advanced appear only with Show advanced settings turned on. Mode-specific settings appear only in their mode.

Troubleshooting

Status changes appear in the activity log as kSA acquisition started, kSA acquisition paused, kSA acquisition resumed, and kSA acquisition stopped. Each closed item logs Data item closed: kSA 400 @ … with the reason.
This page describes kSA 400 version 0.2.6.