> For clean Markdown of any page, append .md to the page URL.
> For a complete documentation index, see https://docs.stereolabs.com/llms.txt.
> For AI client integration (Claude Code, Cursor, etc.), connect to the MCP server at https://docs.stereolabs.com/_mcp/server.

# Multi-Camera Synchronization

This page explains how the ZED Link Mono, Duo and Quad [GMSL2](/docs/products/embedded/zed-link-capture-card/gmsl2#what-is-gmsl2) capture cards synchronize several cameras, how to wire a trigger signal through their GPIO header to synchronize several devices, and which configurations are not supported. For the ZED Link MIPI Quad, see [ZED Link MIPI capture cards](/docs/products/embedded/zed-link-capture-card/mipi): its four channels are synchronized by an onboard FPGA.

Each ZED Link card has one or two **deserializers**, the chips that receive the camera streams. A deserializer in **master** mode generates the trigger signal that starts each frame and outputs it on the GPIO header; a deserializer in **slave** mode follows a trigger signal received on the GPIO header.

Synchronization happens at three levels:

1. **Cameras on the same deserializer** are synchronized natively, with no configuration.
2. **Deserializers on the same Jetson™ device**, for example the two deserializers of a ZED Link Quad, or two ZED Link Mono cards, are synchronized with the `sync_mode` setting and a wire on the GPIO header.
3. **Several Jetson™ devices**, or a ZED Link card and an external trigger source, are synchronized by sharing one trigger signal through the GPIO header.

Synchronized cameras start their frame acquisition within 15 µs of each other, on the same device or across several devices.

> **Note**
>
> Hardware synchronization aligns the frame acquisition, not the software timestamps. Timestamps are assigned when the driver receives each frame and may show millisecond-level jitter. Frames are considered synchronized when the difference between their timestamps is less than one frame period (`1000/FPS` ms).

## Synchronization capabilities of each card

| Feature                                        | ZED Link Mono                  | ZED Link Duo                | ZED Link Quad                                            |
| :--------------------------------------------- | :----------------------------- | :-------------------------- | :------------------------------------------------------- |
| Deserializers                                  | 1x MAX9296A                    | 1x MAX96712                 | 2x MAX96712                                              |
| Natively synchronized cameras                  | The single camera              | All the cameras of the card | The cameras on the same Quad FAKRA-Z connector, J1 or J2 |
| Synchronization of all the cameras of the card | Not applicable                 | Native                      | `sync_mode=1` and a wire between pins #13 and #16 of J17 |
| Trigger pins                                   | Separate input and output pins | One pin, input or output    | One pin per deserializer, input or output                |
| Trigger signal level                           | 3.3V logic                     | 3.3V logic                  | 3.3V logic                                               |

The pinout, the photos of the connectors and the oscilloscope captures of the trigger signals are on the GPIO triggering page of each card: [ZED Link Mono](/docs/products/embedded/zed-link-capture-card/gmsl2/zed-link-mono/zed-link-mono-gpio-triggering), [ZED Link Duo](/docs/products/embedded/zed-link-capture-card/gmsl2/zed-link-duo/zed-link-duo-gpio-triggering), [ZED Link Quad](/docs/products/embedded/zed-link-capture-card/gmsl2/zed-link-quad/zed-link-quad-gpio-triggering).

## Synchronization modes

The synchronization mode is set with the `sync_mode` parameter of the ZED X daemon, in the file `/etc/systemd/system/zed_x_daemon.service`:

| `sync_mode`   | Mode                            | Behavior                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                   |
| ------------- | ------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| `0` (default) | Master                          | Each deserializer runs on its own clock and outputs its own trigger signal on the GPIO header. On a ZED Link Quad, the cameras on J1 are not synchronized with the cameras on J2. The comment in the service file calls this mode "no sync".                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                               |
| `1`           | Master/slave on the same device | The first deserializer is the master; the other deserializers of the device follow its trigger. Use it for the two connectors of a ZED Link Quad, or for two ZED Link Mono or Duo cards on the same Jetson™ device. It requires a wire on the GPIO header: see [Enable full onboard synchronization](/docs/products/embedded/zed-link-capture-card/gmsl2/zed-link-quad/jetson-orin-agx-devkit-setup#enable-full-onboard-synchronization) for the Quad, and the GPIO triggering page of the [Mono](/docs/products/embedded/zed-link-capture-card/gmsl2/zed-link-mono/zed-link-mono-gpio-triggering#masterslave-mode---multiple-zed-link-mono-cards-synchronization) or [Duo](/docs/products/embedded/zed-link-capture-card/gmsl2/zed-link-duo/zed-link-duo-gpio-triggering#masterslave-mode---multiple-zed-link-duo-cards-synchronization). |
| `2`           | Slave                           | All the deserializers follow the trigger signal received on the GPIO header. Use it on the slave devices of a multi-device setup, or with an external trigger source.                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                      |

Change the mode with the following commands, replacing `<mode>` with `0`, `1` or `2`:

```bash
sudo sed -i 's/^sync_mode=./sync_mode=<mode>/' /etc/systemd/system/zed_x_daemon.service
sudo systemctl daemon-reload
sudo systemctl restart zed_x_daemon.service
```

The mode is kept across reboots.

In slave mode, check that each deserializer accepted the configuration:

```bash
sudo dmesg | grep Sync
```

The output reports `Sync mode configured` once for each deserializer: one line for a ZED Link Mono or Duo, two lines for a ZED Link Quad.

### The ZED Link Duo trigger pin

The ZED Link Duo has a single deserializer, so its four cameras are always synchronized together. Its GPIO header exposes a single trigger pin, `MFP10` on pin #5, which is an output in master mode and an input in slave mode, never both. A ZED Link Duo in slave mode therefore cannot forward the trigger to another device.

External triggering on the ZED Link Duo requires [ZED X Driver 1.4.1](/docs/development/zed-x-driver/release-notes/1-4#141) or newer.

## Single master, multiple slaves

To synchronize the cameras of several Jetson™ devices, one device is the **master** and generates the trigger signal. All the other devices are **slaves** and follow it. The trigger output of the master is split to the trigger input of each slave, in a **star** configuration, and all the devices share a common ground. With a ZED Link Mono master, there is no limit on the number of slaves. With a ZED Link Duo or Quad master, keep the trigger wires short, because long wires to many slaves can degrade the trigger signal.

<title id="zlSyncStarTitle">
  Star wiring: the trigger output of the master ZED Link card is split to the trigger input of each slave ZED Link card, and all the grounds are connected together
</title>

<defs>
  <path d="M 0 0 L 10 5 L 0 10 z" fill="#3a9ae0" />
</defs>

<rect x="28" y="157" width="3" height="90" rx="1.5" fill="var(--color-lime)" />

Master

Jetson + ZED Link + cameras

sync_mode=0

one Mono or Duo

sync_mode=1

Quad, or two cards

GND

TRIG OUT

<circle cx="320" cy="202" r="4" fill="#3a9ae0" />

<circle cx="320" cy="72" r="4" fill="#3a9ae0" />

<circle cx="320" cy="180" r="4" fill="#3a9ae0" />

<circle cx="320" cy="334" r="4" fill="#3a9ae0" />

Split point

One branch per slave

TRIG IN

TRIG IN

TRIG IN

<rect x="420" y="43" width="3" height="58" rx="1.5" fill="var(--grayscale-8)" />

Slave 1

Jetson + ZED Link + cameras

sync_mode=2

<rect x="420" y="151" width="3" height="58" rx="1.5" fill="var(--grayscale-8)" />

Slave 2

Jetson + ZED Link + cameras

sync_mode=2

⋮

<rect x="420" y="305" width="3" height="58" rx="1.5" fill="var(--grayscale-8)" />

Slave N

Jetson + ZED Link + cameras

sync_mode=2

GND, common to all the devices

Trigger signal (15, 30, 60 or 120Hz)

Ground

The pins to use on each card are:

| Card          | Master: trigger output             | Slave: trigger input                 | Ground |
| :------------ | :--------------------------------- | :----------------------------------- | :----- |
| ZED Link Mono | J4 pin #6 (`MFP0`)                 | J4 pin #5 (`MFP1`)                   | Pin #1 |
| ZED Link Duo  | J13 pin #5 (`MFP10`)               | J13 pin #5 (`MFP10`)                 | Pin #9 |
| ZED Link Quad | J17 pin #13 or #16, wired together | J17 pins #13 and #16, wired together | Pin #2 |

To set up the synchronization:

1. Choose one device as **master**:
   * With one ZED Link Mono or Duo, keep the default `sync_mode=0`.
   * With a ZED Link Quad, set `sync_mode=1` and connect pin #13 to pin #16 of J17, as described in [Enable full onboard synchronization](/docs/products/embedded/zed-link-capture-card/gmsl2/zed-link-quad/jetson-orin-agx-devkit-setup#enable-full-onboard-synchronization). The cameras of both connectors then follow the trigger sent to the slaves.
   * With two ZED Link Mono or Duo cards, set `sync_mode=1` and wire the two cards as described on their GPIO triggering page. Take the trigger for the slaves from the wire that links the two cards.

2. On each **slave** device, set `sync_mode=2` and reload the systemd configuration:

   ```bash
   sudo sed -i 's/^sync_mode=./sync_mode=2/' /etc/systemd/system/zed_x_daemon.service
   sudo systemctl daemon-reload
   ```

3. Connect the ground pin of the master to the ground pin of each slave.

4. Split the wire from the trigger output of the master, and connect one branch to the trigger input of each slave. On a ZED Link Quad slave, the branch must reach both pins #13 and #16, one for each deserializer.

5. Restart the ZED X daemon on each slave, and on the master if you changed its mode:

   ```bash
   sudo systemctl restart zed_x_daemon.service
   ```

6. On each slave, check that `sudo dmesg | grep Sync` reports `Sync mode configured`.

7. Open the cameras with the **same frame rate** on all the devices. The trigger frequency follows the frame rate of the master.

Once configured, the frames returned by `grab()` on all the devices are captured on the same trigger edge of the master.

> **Tip**
>
> Keep the trigger wires as short as possible, and twist each trigger wire with a ground wire.

### Use an external trigger source as the master

To synchronize the cameras with another system, for example a LiDAR, a PLC or a signal generator, use the external source as the master and set **all** the devices to slave mode, `sync_mode=2`. Split the trigger signal of the source to the trigger input of every device, as in the diagram above, and connect the ground of the source to the ground of every device.

The external trigger signal must have the following characteristics:

* Waveform: square
* Level: 3.3V logic, never above 3.6V
* Frequency: equal to the camera frame rate set in the ZED SDK (15, 30, 60 or 120Hz)

![GMSL2 sync input signal](/_fern-files/_img/419179dcf35ad06e1d2d256cb8dae1a2cc9b230dd9b20106b0f48474ea2ba64b.webp)

> **Warning**
>
> The trigger pins of the [ZED Box 2](/docs/products/embedded/zed-box-series/zed-box-2/using-gmsl#multi-device-synchronization) are **1.8V** signals. Always use a level shifter between a ZED Box 2 and a ZED Link card, in either direction. The ZED Link trigger pins are not 5V tolerant: use a level shifter with 5V devices too.

## Trigger external sensors from a ZED Link card

In master mode, the trigger output can also drive other sensors, so that they capture at the same time as the cameras. The rising edge of the trigger signal is synchronized with the end of the exposure phase of the camera sensors. The width and period of the signal for each frame rate are given on the GPIO triggering page of each card.

## Mixing camera models

You can connect different camera models to the same card, for example a ZED X One GS and a ZED X in the same Group. The **Multi-camera configurations** section of each setup guide lists the supported combinations.

All the cameras that follow the same trigger signal must run at the **same frame rate**, equal to the trigger frequency. The slowest camera configuration therefore sets the frame rate of the whole synchronized system: a ZED X One 4K in 4K or QHDPLUS resolution runs at 15fps, so all the cameras synchronized with it must also run at 15fps.

## Limits and unsupported configurations

* **USB 3 cameras** (ZED 2i, ZED 2, ZED Mini) cannot be hardware-synchronized with the GMSL2 cameras or with each other: they only support software synchronization based on timestamps.
* **ZED Link Quad connectors**: in the default `sync_mode=0`, the cameras on J1 are not synchronized with the cameras on J2, and the two trigger outputs are not synchronized with each other.
* **Daisy chain**: a ZED Link card in slave mode does not output the trigger signal, so slave devices cannot be chained one after the other. Always use the star wiring above.
* **Trigger frequency**: frequencies other than 15, 30, 60 and 120Hz are not supported.
* **Trigger voltage**: the trigger pins use 3.3V logic. 5V signals are not supported, the trigger input must never exceed 3.6V, and the trigger input of a ZED Link Mono must not be driven while the card is powered off.