For Orbbec’s documented CTI JCB002 synchronization route, the host is the master and both Gemini 335Lg cameras are configured as Secondary-synced. Start by matching the Jetson, carrier, deserializer board and driver. Then configure the supported host-generated trigger path and check the resulting frames. Two cameras on the same Jetson capture independently until that trigger path is in place.
The configuration record below makes a real setup and its evidence reviewable by someone else on your team.
Pick a supported hardware stack before picking a script
The Orbbec GMSL host requirements list complete systems and modular combinations. One listed route combines a Jetson AGX Orin SOM, a CTI Forge AGX201 carrier and JCB002. Other carrier combinations are listed separately. Each carrier keeps its own pinout and software image, even with a supported camera board.
Record the actual parts before installation:
| Part of the setup | Record from the equipment or supplier |
|---|---|
| Jetson compute module | Exact model and memory variant |
| Carrier and deserializer | Product names, board revisions and supported combination |
| Each camera | Gemini 335Lg serial number and firmware |
| Software | Jetson Linux/JetPack, camera driver, SDK and Viewer versions |
| Cabling and power | Approved cable types, connection ports and each board’s specified supply |
| Trigger implementation | Board-specific script or configuration and where its version came from |
Keep this record with the configuration. If someone replaces the carrier or updates the kernel, you can identify which dependency changed instead of treating “Jetson” as a complete hardware specification. The broader depth-camera selection guide covers choosing a sensing method; this step is about a particular camera integration.
Separate basic image acquisition from trigger configuration
Bring up each camera’s ordinary stream before attempting multi-camera synchronization. That gives you a known working data path against which to diagnose the trigger path.
The GMSL quickstart instructs readers to identify the Jetson Linux version, obtain a matching driver and verify the installed driver. Its worked installation uses an FG96 deserializer-board script. That script is specific to FG96. Obtain the instructions for the selected carrier and deserializer combination before installing or rebooting a working system.
The same quickstart illustrates why /dev/video* entries overcount cameras: its Gemini 335Lg example exposes separate image and metadata nodes for multiple streams. Record camera serial numbers and the stream you opened instead of inferring identity from the first video-node number.
At this stage, the useful observation is “each intended camera produces the intended stream with this software stack.” Label it synchronized only after the trigger step below.
Follow the JCB002 host-master route as one complete configuration
Orbbec’s Gemini 335Lg hardware synchronization page describes two trigger paths: through GMSL2/FAKRA and through the 8-pin AUX connector. For the GMSL route, the trigger is transferred through the deserializer and serializer to the camera. The page’s JCB002 example puts both cameras in Secondary-synced mode and uses the provided board-specific PWM script.
For that example, keep the roles explicit:
Host trigger configuration
-> supported JCB002/deserializer path
-> GMSL link to camera A, configured as secondary
-> GMSL link to camera B, configured as secondary
The model-specific page states that Gemini 335Lg is a synchronization slave in this arrangement. Keep both cameras secondary even if a general multi-camera diagram for another model shows a primary camera.
The documented trigger is rising-edge active, with a default 3.3 V level and a pulse width of at least 1 ms. Use the board manufacturer’s pinout and the applicable signal specification when implementing it; this diagram is a role map only. Use the GPIO mapping for your verified board revision in place of the source’s examples.
Treat the AUX route as a separate integration choice
Orbbec also documents using a multi-device sync hub with the 8-pin interface. Its external synchronization guide covers hub and cable preparation, topology and model-specific configuration examples.
Choose the appropriate adapter and supported topology as a complete assembly. A synchronization cable runs in addition to the camera’s data and power path. Also distinguish the guide’s generic Gemini 335 examples from the Gemini 335Lg host-master limitation above. The similar product names are a reason to check model scope before combining any two diagrams.
Record frame timing and arrival timing as different evidence
The external synchronization guide distinguishes frame timestamps from a system timestamp recorded after a complete UVC frame is received. That distinction matters when software queues or transport delay separate capture from arrival.
For the exact interface and SDK you use, establish what each timestamp field means before comparing it across cameras. A shared host clock alone leaves open whether two exposures occurred together. The PTP and hardware timestamp guide explains the wider timing problem alongside this camera-specific trigger setup.
Use a short observation record for the first synchronized run:
| Observation | Keep with the result |
|---|---|
| Camera identity | Serial number, stream type and configured mode |
| Trigger | Source, configured rate and pulse settings |
| Frame association | Frame number or other available identifier used to pair observations |
| Timing | Exact timestamp field, unit and clock meaning |
| Missing frames | Count and where gaps occurred during the observation interval |
| Shared scene | A visible moving event that helps compare the frames’ content |
Orbbec recommends comparing frame timing and the scene content of moving objects. Define your application’s acceptable offset before testing, and state how the observation was made. Measure your installed cameras even when the vendor states an accuracy figure.
If a camera stays dark, return to power, driver and data-path checks. If it streams in the basic test but ignores the intended trigger configuration, inspect that camera’s mode and the supported trigger path. If both produce frames but pairing is inconsistent, inspect frame identity, timestamp meaning, dropped frames and configuration changes before adjusting unrelated clock settings.
The completed result should identify the hardware stack, the selected trigger route and the evidence that the required streams align. With those three items, another integrator can reproduce and troubleshoot the installation. Orbbec documentation checked October 13, 2026.