Why outdoor AMRs need GMSL cameras, and how the Gemini 335Lg delivers

USB has been the default interface for stereo depth cameras since the category existed, and it works fine on a robot that stays indoors on smooth floors within a few meters of its compute box. Push that same robot outdoors, onto a longer chassis, or into a route with vibration and electromagnetic noise, and USB starts to show its limits. That gap is exactly what the Orbbec Gemini 335Lg GMSL stereo camera was built to close, and it's worth walking through why GMSL matters before looking at what the camera itself does with it.

What USB gets wrong for robots in motion

USB 3 cable runs top out around 3 meters before signal integrity becomes a problem, which is a real constraint on AMRs where the camera sits at the front of the chassis and compute lives further back, or where a sensor mast needs distance from a vibrating drivetrain. USB connectors also aren't locking connectors. On a robot that's accelerating, braking, and crossing uneven terrain all day, a connector that can work loose under vibration is a maintenance problem waiting to happen, and an intermittent camera disconnect mid-route is a worse failure mode than a camera that never worked at all. Add electromagnetic interference from motor controllers and battery systems, common on outdoor and industrial AMRs, and USB's shielding starts to strain against loads it wasn't designed for.

What GMSL2 and FAKRA change

GMSL2, or Gigabit Multimedia Serial Link 2, is a serial protocol built for exactly this kind of high-speed, long-run, electrically noisy application, which is why it's common in automotive camera systems before it made its way into robotics. Paired with a FAKRA connector, it supports cable runs up to 15 meters without an extension, against roughly 3 meters for USB, and moves data at up to 6Gbps, more bandwidth than mainstream GigE cameras offer. The FAKRA connector locks in place, which is the more practical benefit for a systems integrator: it holds through vibration and repeated motion instead of relying on friction fit. None of this changes what the sensor sees. It changes whether the data reliably gets from the sensor to the compute stack on a robot that's actually moving, which is the condition USB was never built around.

The environmental and latency stack outdoor navigation adds

Outdoor AMR navigation compounds these connectivity issues with its own environmental demands. Temperature swings between a cold morning and a sun-exposed afternoon stress both the imaging hardware and the cabling. Direct sunlight can wash out projected IR patterns unless the stereo system is tuned to hold up across lighting extremes. And navigation latency has a hard ceiling: a robot moving at speed needs depth data delivered and processed fast enough to plan around a moving obstacle before it's already too close, which puts a premium on the sensor's own compute rather than only on the transport layer.

How the Gemini 335Lg is built for this

The Gemini 335Lg is the GMSL2/FAKRA version of the Gemini 335L, sharing its 95mm baseline and running active and passive stereo simultaneously to hold depth accuracy across lighting conditions rather than switching between modes. Spatial precision is rated at 0.8 percent at 2 meters and 1.6 percent at 4 meters, measured during factory calibration, with a working depth range from 0.17 meters out to 20 meters and beyond. Depth processing happens on Orbbec's MX6800 ASIC, the same depth engine used across the Gemini 330 series, which keeps depth-to-color alignment and depth computation off the host processor.

Robust design

The camera carries an IP65 rating for water and dust ingress, provided IP65-compliant cabling is used during power-on operation, and is rated for 3.8Grms of vibration across 5 to 2000Hz. It's compliant with EN61000-6-2 and EN61000-6-4 for electromagnetic immunity and emissions, and runs across an ambient temperature range of -10°C to 50°C at 15fps, narrowing to -10°C to 45°C at 30 and 60fps. Multiple Gemini 335Lg units can be hardware-synchronized on a single host for applications needing coverage from more than one viewpoint.

On the integration side, the 335Lg is pre-integrated with NVIDIA Jetson AGX Orin and Jetson Thor, and ships with out-of-box support through partner hardware including the Advantech MIC-733-AO, Axiomtek AIE510-ONX, and Connect Tech's Anvil embedded system, all built around GMSL2 camera inputs. The camera runs on the same open-source Orbbec SDK as the rest of the Gemini line, with native ROS1, ROS2, and NVIDIA Isaac ROS support, so a team that's already validated an application on the USB-based Gemini 335L can move to the 335Lg for production deployment without rewriting the perception stack.

FAQ

Does the Gemini 335Lg sacrifice depth accuracy for the GMSL2 interface? No. The 335Lg shares its imaging hardware, baseline, and depth accuracy figures with the Gemini 335L. GMSL2 and FAKRA change how the depth and RGB streams get to the host, not what the stereo engine measures.

Can a team prototype on USB and deploy on GMSL2 without redoing their software? Yes, since both cameras run on the same Orbbec SDK, a team can develop and validate against the USB-based Gemini 335L on a bench and move to the GMSL2/FAKRA Gemini 335Lg for the production robot without rebuilding the perception pipeline.

Is GMSL2 only useful for outdoor robots? Longer cable runs and vibration resistance matter for any AMR or robotic arm dealing with distance between camera and compute or exposure to motion and electrical noise, indoors or out. Outdoor deployments tend to stack more of these stressors at once, which is why the interface shows up most often in that context.