> For the complete documentation index, see [llms.txt](https://docs.freeflysystems.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.freeflysystems.com/products/products/ember-camera/ember-syncbox.md).

# Ember SyncBox

The **Ember SyncBox** synchronizes multiple Ember cameras over a shared bus, distributes a frame trigger, and bridges each camera's GPIO to the sync network. It also passes power through to the camera.

<figure><img src="/files/hdnKwkabWU66vbniBKZ5" alt="" width="563"><figcaption></figcaption></figure>

### Overview

Each SyncBox pairs with **one Ember camera** (via the *Ember GPIO* port) and joins a shared bus that links boxes together. Across that bus, exactly one box acts as the **master** and the rest act as **slaves**:

* **Multi-camera Sync** — the master camera configuration is emitted to the slave cameras.
* **Frame Trigger** — the master emits the frame trigger; every slave receives it.

The master is chosen with the **Bus Authority** switch. Only one box on the bus may have Bus Authority enabled at a time.

### Connectors

<table><thead><tr><th width="127">Label</th><th width="85">Connector</th><th>Description</th></tr></thead><tbody><tr><td><strong>Ember GPIO</strong></td><td>GH-6</td><td>Connects to Ember GPIO. See <a href="/pages/IuqizpqBRE4CBQ7iO0W1">Pinouts / Remote / Sync</a>.</td></tr><tr><td><strong>Power Out</strong></td><td>XT30</td><td>Pass-through power to Ember (12V - 26V).</td></tr><tr><td><strong>Power In</strong></td><td>XT30</td><td>Power input (7.5 V – 26 V).</td></tr></tbody></table>

### Configuration Switches

<table><thead><tr><th width="167">Switch</th><th>Function</th></tr></thead><tbody><tr><td><strong>UART Term</strong></td><td>Termination for the <strong>UART bus</strong>. See <a href="#topology">Topology</a>.</td></tr><tr><td><strong>Bus Authority</strong></td><td><p><strong>ON = master</strong>, <strong>OFF = slave</strong>. </p><p>Exactly one box on the bus may have this ON.</p></td></tr><tr><td><strong>Trig Term</strong></td><td>Termination for the <strong>trigger bus</strong>. See <a href="#topology">Topology</a>.</td></tr></tbody></table>

### Bus Jacks (RJ45)

> ⚠️ **Not Ethernet.** Despite using RJ45 connectors and cabling, these jacks are **not compatible with Ethernet** and provide **no networking capability**. They carry only the Sync Box buses described below. Do **not** connect them to a computer, switch, router, or any Ethernet device.

The three RJ45 jacks carry the bus between boxes over standard RJ45 cabling. The cabling carries **two independent buses**:

<table><thead><tr><th width="134">Bus</th><th>Signal</th></tr></thead><tbody><tr><td><strong>UART bus</strong></td><td>UART @ <strong>115200 baud</strong> — the synchronization channel.</td></tr><tr><td><strong>Trigger bus</strong></td><td>Frame trigger — master <strong>GPO2</strong> to <strong>GPI2</strong> on each slave.</td></tr></tbody></table>

Having three jacks lets a box sit in the middle of a daisy-chain (in one jack, out another) or fan out to multiple boxes in a star/hub layout.

### Camera Setup

The cameras should have their GPIO configuration as follows

* **Master** — GPO Mode: Sync Out ( Frame Pulse + Configuration Sync )
* **Slaves** — GPI Mode: Frame Trigger

> ⚠️ Configure the cameras before connecting the GPIO cable. Otherwise, the trigger bus may start recordings on a slave camera if GPI Mode is set to RS Edge (default).
>
> ⚠️ Without setting GPI Mode: Frame Trigger, slave cameras will not capture new frames at the configured frame rate. Preview on HDMI will be frozen or slow (1Hz).

### Topology

Boxes can be wired in different topology using the RJ45 jacks:

* **Daisy-chain** *(recommended)* — box-to-box, in one jack and out the next.&#x20;
  * Termination is easy: enable first and last box `*Term` switches.

<figure><img src="/files/HOxpHIgpnsf5JpBt9pQ7" alt="" width="563"><figcaption></figcaption></figure>

* **Tree** — box-to-box, with some boxes having 3 connection.
  * Termination is harder to determine and depends on the cable length.

<figure><img src="/files/M2ZyxoGWK5sAkPsP6c18" alt="" width="563"><figcaption></figcaption></figure>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.freeflysystems.com/products/products/ember-camera/ember-syncbox.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.