Skip to Content

CameVision EGO: a stereo SOM Camemake builds for egocentric robotics

12 September 2026 by
CameVision EGO: a stereo SOM Camemake builds for egocentric robotics
CVHAI
| No comments yet

CameVision EGO: a stereo SOM Camemake builds for egocentric robotics

Brand: Camemake
SKU:CV-EGO01-OS
Module program: CameVision (ODM PCBs and ODM finished products; OEM when the family does not fit)
Product: https://www.camemake.eu/shop/cv-ego01-os-camevision-ego-dual-global-shutter-ai-stereo-camera-2414
Program overview: https://www.camemake.eu/robotic-solutions

Why this module exists

Egocentric robotics needs first-person stereo that can leave the lab without a host PC on a trolley. USB stereo sticks still assume a laptop, a Jetson backpack, or a workstation. When the interesting frames happen on a moving body (mobile manipulator, head-worn rig, handheld teaching pass), the camera has to carry sync, inertial sense, compute, radio, and local storage with it.

CameVision EGO is Camemake’s evaluation double-PCB in that class: a commercial stereo system-on-module you put in a housing, not a UVC webcam you hope the host will keep up with.

What Camemake ships on CV-EGO01-OS

Published board facts from Camemake’s CameVision page and shop listing:

ItemValue
SKU

CV-EGO01-OS

Cameras2 × 2.3MP global shutter, hardware-synchronized stereo
IMU2 × IMU, one per camera (camera-frame VIO cues)
ProcessorRockchip RV1126B with integrated NPU
Memory1 GB RAM
Storage16 GB eMMC + microSD
WiredUSB 3 / USB-C
WirelessWi-Fi 6 + BLE (u.FL antenna)
PowerBattery pads and USB-C
SoftwareOpen-source demo on GitHub
Evaluation priceUSD 199 (MOQ 10) · USD 160 (MOQ 1000)

Baseline, exact sensor part numbers, FPS, and FOV are set per ODM/OEM configuration. Camemake confirms those on the quote rather than publishing one number that only fits a single build.

Manufacturer story: one platform, many camera counts

EGO is the double-camera evaluation unit in a wider CameVision module program Camemake designs and manufactures:

  • Single: monocular PCB for documentation, wrist/tool views, or monocular VIO
  • Double (EGO): hardware-synced stereo + dual IMU (default for SLAM, VIO, egocentric stereo)
  • Triple: stereo plus a context camera on one time base
  • 5-fold: timed array for backpack wearables
  • 9-camera: near-surround workplace capture with array-level calibration

All five PCB counts are available as ODM (Camemake platform, your brand, your housing, your volume). Finished goods on the same family (stereo headset, cap, PPE helmet, 5-fold array + backpack, handheld teaching gripper) are also ODM. When nothing in the family fits, Camemake runs OEM: full PCB, optics, mechanics, and firmware, then production on the same lines.

That is the Camemake angle: direct manufacturer with Belgium engineering support, China production, Hong Kong HQ. Design, assembly, optical alignment, and QA live in-house, with serial tracking, factory extrinsics for stereo and multi-camera boards, and volume paths from evaluation MOQ 10 up through production MOQs.

Factory and OEM path

Camemake’s stated process for this class of work:

  1. Brief: camera count, baseline, host, cable length, environment, certification needs
  2. Configuration: sensor, shutter, optics, interface (CSI / USB / GMSL), mechanical envelope, quote
  3. Samples: boards and housing if needed, calibration files with serials
  4. Production: SMT / COB / CSP on Camemake lines, QA, serials, volume

For funded camera startups, Camemake Lens (Shenzhen R&D center) adds lab, cleanroom, and on-site engineers with 0% equity; when you ship, you produce on Camemake’s line.

What teams use it for

Typical Camemake-facing jobs for EGO and the CameVision family:

  • Handheld teaching passes so a manipulator learns from first-person stereo (UMI-style gripper ODM on the same platform)
  • Mobile-base SLAM / VIO without a companion PC
  • Wearable logging for policy learning and imitation (hours of first-person stereo plus IMU, stored locally)
  • ODM wearables (headset, cap, helmet, backpack array) when the product is already designed and needs brand + volume
Share this post
Archive
Sign in to leave a comment
Connecting factory MIPI modules to Jetson, Raspberry Pi, and Rockchip
Kits do not give the rails and MCLK a factory module expects. That gap is the adapter problem.