Skip to main content

Configure GMSL Cameras on ASR702 with UniCAM

UniCAM is Advantech's GMSL camera configuration utility for ASR702, bringing camera connection mapping, exposure synchronization, and ROS 2 startup management into a single workflow. For a multi-camera setup, you can assign a supported camera model to each of the eight GMSL connectors, check detected hardware and configuration validation messages, and configure a shared trigger for cameras that support synchronization. This gives developers a common place to review the camera setup before applying it.

UniCAM provides a graphical interface for desktop systems, a text interface for headless systems, and command-line tools for configuration and ROS service management. Its key features include per-connector camera assignments and ROS startup controls, selectable synchronization frequencies, and IR controls for supported Gemini and D457 cameras. By combining these settings with validation and configuration generation, UniCAM helps make multi-camera setup and maintenance more consistent. Save the configuration and reboot for camera configuration changes to take effect; the first configuration requires the full power cycle described below.

This guide covers GMSL camera configuration with UniCAM on an ASR702 equipped with Jetson AGX Thor and JetPack 7.2.

Understand the channel topology​

ASR702 has two MAX96712 deserializers. Deserializer 1 serves CH1–CH4, and deserializer 2 serves CH5–CH8. Each deserializer provides eight video pipes and can carry at most eight simultaneous image streams. A camera can consume more than one stream: the source gives ZED X as a two-stream example and Gemini 335Lg as a four-stream example.

Diagram mapping Deserializer 1 Link A to CH4, Link B to CH3, Link C to CH2, and Link D to CH1; and Deserializer 2 Link A to CH8, Link B to CH7, Link C to CH6, and Link D to CH5

Figure 1. ASR702 uses reverse channel order within each deserializer: Deserializer 1 maps Links A–D to CH4–CH1, while Deserializer 2 maps Links A–D to CH8–CH5.

Install with Robotic Suite​

Install the required environment through Robotic Suite Complete instead of running a standalone camera-package installer. Follow the Robotic Suite Complete installation guide and obtain adv-robotic-suite-installer.run as described on its download page.

Before installation, confirm that Advantech SUSI is installed and that the target is an Advantech platform with at least 10 GB of free space, an English-language Ubuntu interface, and Internet access. Then launch the installer:

sudo ./adv-robotic-suite-installer.run

In the installer menu, use the spacebar to select the required platform components, choose OK, wait for the completion message, and reboot to finish configuring the environment. Package choices can vary by platform and Robotic Suite release; use the options presented for the target system.

First UniCAM configuration

After assigning the connectors for the first time, power the system completely off for 30 seconds, then power it on. For later UniCAM configuration changes, sudo reboot is sufficient.

Open UniCAM​

Use the graphical interface on a system with a desktop, or the text interface on a headless system:

sudo unicam
sudo unicam --tui

In the TUI, use the arrow keys to navigate and press F10 to apply. The GUI contains CAMERA CONNECTION, TIME SYNC, and ROS CONFIGURATION tabs. SAVE & APPLY on any tab saves all three pages.

Map and validate the connected cameras​

On CAMERA CONNECTION, select the camera attached to each CH1–CH8 connector. Select None for an unused connector.

Camera Connection page with channel selectors, detected hardware, validation messages, and action buttons

Figure 2. CAMERA CONNECTION combines channel assignment, hardware detection, and validation.

The page provides these controls and status areas:

  • ADVANCE displays the PHY, VI, lane count, link rate, and virtual-channel mapping for engineering review; it is not edited here.
  • DETECTED HARDWARE reports what the system reads from each connector. Green identifies a detected model. Yellow (not read) means a driver has already claimed the camera, so the page shows the saved configuration rather than a live hardware reading.
  • Auto Apply copies detected results into the channel selectors automatically. RE-SCAN repeats detection.
  • VALIDATION shows blocking errors in red and warnings in yellow. One warning example is declaring more than eight streams on a deserializer.
  • SET ALL TO NONE clears all eight assignments.
  • APPLY DETECTED copies detected results into the selectors but does not save them.
  • SAVE & APPLY validates, saves, generates the configuration, and asks whether to reboot.
Stop active streams before detection

Detection must run while no camera stream is open. If the page reports Not scanned: a stream is open, stop applications using the cameras and check the per-connector ROS services:

sudo unicam-ros status
sudo systemctl stop adv-ros-ch1.service

The service name uses the adv-ros-chN.service format, with one service per connector. Stop each service that owns a camera you need to scan, then select RE-SCAN. If detection does not change the configuration, restart each stopped service with sudo systemctl start <service-name>. If you apply a changed camera configuration, use sudo reboot instead.

Expanded advanced routing view listing PHY, VI, lane, rate, and virtual-channel assignments for g1 and g2

Figure 3. The expanded ADVANCE view exposes generated routing details for the two deserializers, labeled g1 and g2.

Camera names used by the CLI​

GUI namePrimary CLI tokenAccepted aliases
RealSense - D457d457—
Orbbec - Gemini 335Lgg335Lggemini, g300
StereoLabs - ZED Xzedx—
StereoLabs - ZED X Minizedxmini—
StereoLabs - ZED X Nanozedxnano—
StereoLabs - ZED X One (GS)zedxone—
StereoLabs - ZED X One 4Kzedxone4k—
Leopard Imaging - OX03F10li-ox03f10ox03f10, leopard
Leopard Imaging - ISX031li-isx031leopard-isx031
APPRO - AR0234 (ISP module)appro-ar0234—
Sensing World - SG8Aswsensingworld, sgcam, isx031
Nonenone—
ISX031 token

The unqualified isx031 alias selects Sensing World - SG8A. Use li-isx031 for the Leopard Imaging ISX031 camera.

Configure synchronized exposure​

The TIME SYNC tab generates one trigger pulse for every connector on both deserializers. Set Trigger frequency to off, 10, 15, 20, 25, or 30 Hz. Selecting a numeric frequency enables Time Sync; off leaves the cameras free-running. The tab also reports which configured cameras can follow the trigger and any mode requirements.

Time Sync page enabled at 30 Hz with camera compatibility warnings

Figure 4. TIME SYNC is enabled in this example: Trigger frequency is set to 30 Hz, so a shared 30 Hz pulse is sent to both deserializers. The messages below the selector explain which configured cameras follow that pulse and which cameras continue to free-run.

CameraSynchronizesSource-stated requirement
ZED X / ZED X Mini / ZED X NanoYesNo additional setting
Gemini 335LgYesMode fps must exceed trigger frequency; use a 60 fps mode at 30 Hz. ROS sets this automatically.
RealSense D457YesSupports only 15 or 30 Hz; fps equals trigger frequency.
Leopard ISX031YesDriver switches automatically.
Sensing World - SG8AYesSupports synchronization at the requested frequency.
Leopard OX03F10 / APPRO AR0234NoContinues using its own clock.

Time Sync support has not been verified for the ZED X One family, so it is intentionally not listed as synchronized.

For capture procedures and synchronization verification, consult the separately supplied FSYNC-TUTORIAL.zh-TW.pdf. Reboot after changing FSYNC.

Configure ROS 2 startup​

The ROS CONFIGURATION tab requires ROS 2 Jazzy, installed through Robotic Suite. If the page reports ROS 2 Jazzy is not installed, its startup controls remain unavailable. The table has one row per connector and the columns CAMERA MODEL, CHANNEL, START AT BOOT, and IR. Enable START AT BOOT for each connector whose ROS 2 node should start during boot.

The IR control is available only for Gemini and D457 cameras. For Gemini, enable Time Sync before enabling ROS startup.

UniCAM ROS Configuration screenshot showing one row per connector and the Camera Model, Channel, Start at Boot, and IR columns

Figure 5. The ROS CONFIGURATION page. Each connector has its own row; IR controls appear only for supported Gemini and D457 rows.

Some cameras require an external package:

CameraRequirementInstallation behavior
RealSense D457librealsense2 2.58Included; the tool offers installation if missing. It can later be upgraded within 2.58.x.
Leopard OX03F10Argus GStreamer plug-in and gstreamer1.0-plugins-baseunicam-ros install-deps installs the required dependencies; the GStreamer base plug-ins are obtained through APT. Network access may be required.
ZED familyZED SDK 5.4.1Install the JetPack 7.2 release manually from StereoLabs.
Gemini, ISX031, Sensing World, APPRONone statedNo additional package is required by the source.

Save, reboot, and apply​

SAVE & APPLY does not save while VALIDATION contains a red error. When validation passes, the tool stores and generates the configuration, then displays Reboot now? Select Yes to reboot immediately or No to reboot later with sudo reboot.

Save and Apply confirmation followed by the Reboot now prompt

Figure 6. A saved configuration takes effect only after the required reboot or initial full power cycle.

Configure from the command line​

unicam --show
sudo unicam CH1=zedx CH2=g335Lg CH8=d457 FSYNC=30
sudo unicam FSYNC=15
sudo unicam --detect
sudo unicam --apply
sudo reboot
Channel assignments are a complete set

When a command contains any CHn= assignments, connectors omitted from that command become none. Run unicam --show first and include every assignment that must remain enabled. A command that changes only FSYNC preserves channel assignments.

Manage ROS services with:

sudo unicam-ros status
sudo unicam-ros on CH1
sudo unicam-ros off CH1
sudo unicam-ros ir CH2 on
sudo unicam-ros install-deps

The on and off commands can target an individual connector. After you apply a camera configuration, UniCAM updates the corresponding ROS services automatically.

Troubleshooting​

SymptomAction
Configuration appears unchangedReboot after saving. After the first installation, perform a complete 30-second power-off.
VALIDATION reports more than eight streamsEach deserializer has eight video pipes. The profiles may be saved, but no more than eight streams can run simultaneously on that deserializer.
Detection reports Not scanned: a stream is openRun sudo unicam-ros status, stop the affected adv-ros-chN.service, and then run RE-SCAN. Restart stopped services if no settings changed; otherwise reboot after applying the new configuration.
Detection shows (not read)The driver has claimed the camera. To obtain a live reading, set that connector to None, save, reboot, and scan again.
Every camera on one deserializer disappears or drops many framesCheck whether a camera also has USB or external power connected. Disconnect USB and completely remove all power, including external power; sudo reboot does not remove it.
A ZED ROS node does not startInstall ZED SDK 5.4.1 for JetPack 7.2.
ROS services remain off after removing and reinstalling the packageRe-enable the required connector services with unicam-ros. This does not apply to an in-place package upgrade.

Package behavior and supported devices can change; verify compatibility with the target system before deployment.