Skip to main content
Network (GVSP Tap) is the default frame source. A GigE Vision camera sends its frames to the RHEED software over the network as a GVSP stream. The tap receives copies of those packets on the same computer and reassembles them into frames. It never opens the camera and never sends it commands, so it works even when the RHEED software holds the camera exclusively.
Because the tap only listens, it can’t ask the camera to resend lost packets. Frames with missing packets are dropped and counted, so a clean network path matters.

Before You Start

  • Windows, with the camera connected to this computer.
  • Integration admin access turned on. Capturing packet copies needs administrator rights. If you skipped it during setup, the integration’s page offers to turn it on when you start it.
  • The RHEED software acquiring from a GigE Vision camera that streams to this computer (unicast).
  • Whole packets. The camera’s packet size must fit the network adapter’s MTU and every switch on the path. If the camera uses jumbo packets, enable jumbo frames on the camera-facing adapter and switches.
  • English Windows. The default capture mode reads Windows Packet Monitor’s English output, so it fails on a localized Windows installation. On non-English Windows, choose another mode in Capture Modes, or use Standard capture (GenTL).

Set Up Network Capture

The defaults need no input, so a new integration is ready to start as soon as it is added.
1

Add the integration

Add a RHEED Camera (GenTL) integration. The app opens its page with Start it when ready. Frame Source is already Network (GVSP Tap) and every capture setting is Auto. For an existing integration that uses another source, stop it, click Configure, select Network (GVSP Tap), and apply.
2

Start it while the RHEED software acquires

Check that the RHEED software is acquiring, then click Start Integration. If admin access is off, the page shows “Network (GVSP Tap) needs Integration admin access, which is off on this computer. Without it, it can’t capture.” Click Enable admin access, have an administrator approve the Windows prompt, and click Start again. With admin access on, the integration adds its own firewall rule and starts without a prompt.
3

Choose the camera if asked

With Camera IP Address blank, Start looks for GigE Vision cameras on this computer’s networks without changing anything on them. With one camera, it uses it and remembers it for later runs. If several answer, the page shows Several GigE Vision cameras answered. Choose the RHEED camera. Click Choose, pick the camera from the list (such as Camera A: 169.254.14.85), apply, and start again.
4

Check the health verdict

The health summary in the Health section of the integration’s page shows Tuning while it measures the stream, then Healthy once frames arrive whole. Idle with No frames are arriving from the camera. is expected while the RHEED software is not acquiring. The activity log shows Data item opened: RHEED Stream @ … once frames arrive, and the stream appears in Atomscale as Stream Active.
5

Optional: set the stage rotation

If the stage rotates, you can get first results sooner by entering its speed. Stop the integration, set Stage Rotation to the speed in RPM, apply, and start it again. If you leave it blank, Atomscale detects whether the stage rotates.
If the camera’s address changes later, for example a 169.254.x.x address after a restart, capture follows it and logs The camera … moved from … to …; capture follows it. To pin a camera, click Detect in Camera IP Address while the integration is stopped, or type the address. To check the network path before uploading anything, turn on Show advanced settings, turn on Diagnostics Only, apply, and start. The Activity Logs report packet counts, incomplete frames, and frame brightness without uploading. Turn Diagnostics Only off when you’re done.

Capture Modes

Capture Mode (advanced) selects how Windows provides the packet copies. Keep the default unless diagnostics show no packets.

Pktmon and Other Users

Packet Monitor is shared by the whole computer. While the integration captures, it owns Packet Monitor’s state, using a filter named AtomscaleRheedGvsp. It never stops or changes someone else’s capture: if another Packet Monitor capture or filter is active when it starts, it refuses to start and says so. Stop the other capture, or run pktmon status in an elevated PowerShell window to see what is running. The integration picks the Packet Monitor component for the camera’s network adapter automatically. If several components match equally, it asks you to set Pktmon Component ID: run pktmon list in an elevated window and enter the ID of the adapter that carries the camera traffic.

Mirror Port Setup

If neither Pktmon nor Windows IP Capture sees the packets, a managed switch can mirror the camera’s traffic to a second network adapter:
  1. Mirror the camera port’s incoming traffic to a spare switch port, and connect it to a second network adapter on the workstation.
  2. Leave the vendor filter driver enabled on the primary adapter and unbind it from the second (monitor) adapter only. Vendor software updates can re-enable the binding, so check it after each update.
  3. Give the monitor adapter a static address outside the camera subnet, with no gateway and no DNS.
  4. In advanced settings, set Capture Mode to Promiscuous NIC Capture, turn on Allow Promiscuous Capture, set Capture Interface IP to the monitor adapter’s address, and set Original Stream Destination IP to the primary camera-facing adapter’s address.
  5. Confirm the mirror path supports the camera’s packet size.

How the Tap Follows the Stream

  • Network adapter. With Capture Interface IP blank, the integration finds the adapter that receives the camera’s stream each time it starts. If it can’t, the error says why and what to set.
  • Stream port. With Stream Destination Port on Auto, the tap learns the port from the first complete, valid frame. After the camera goes quiet for Traffic Report Timeout (10 seconds), it releases the port and validates the next acquisition the same way. A change in image size or format is validated again without a restart.
  • Packet loss. If more than half the frames in a 10-second window are incomplete, the activity log warns. A second such window in a row makes the tap re-validate the stream. 300 incomplete frames in a row with no complete frame stop the integration with an error.

Troubleshooting

For problems with session boundaries or missing data items, see Recording Sessions.