Why docking vision is a module brief
Warehouse and factory fleets still solve the last centimetres of charge, load, and station approach with 2D fiducials, AprilTags, ArUco-class markers, QR pads, or printed dock targets. The loop is familiar: approach under nav, lock the marker, estimate pose, crawl into contact. What fails in the field is rarely the detector library. It is motion blur on a rolling shutter, USB UVC latency into a host that already owns the ISP, a FOV that loses the marker at working distance, or a module that cannot be swapped with matching AA and calibration serials when the fleet expands.
Camemake builds that stack as a manufacturer program: OEM and ODM camera modules with in-house SMT, COB or CSP, cleanroom lens work, active alignment (AA), calibration files, and serial tracking.
Est. 2016, 20,000+ m² factory, about 30 million units per month capacity on the public Camemake scale facts. Belgium engineering support, China production, Hong Kong HQ. Interfaces span USB, MIPI CSI-2, DVP/SPI, and GMSL when the cable run leaves the short FPC zone on the chassis.
The buyer question for docking is not megapixel marketing. It is shutter class for motion, latency into the host ISP, FOV versus working distance, trigger discipline when dock and nav share a time base, and a factory path that keeps lot N close to the sample that won the RFQ.
Manufacturer criteria for docking vision
Industry docking coverage often lists finished AGV cameras. For a module OEM, the same problem is a brief checklist. Depth-ToF and iToF stacks belong to a different job (blind spots, overhead obstacles, floor steps). Dock marker alignment is a 2D global-shutter vision problem first.
| Criterion | What docking needs | Why it matters on the vehicle |
|---|---|---|
| Shutter class | Global shutter preferred | Rolling shutter shears marker corners when the base crawls, turns, or vibrates; pose estimators then fight geometry that never existed on the dock |
| Interface | MIPI CSI-2 into the SoC ISP | Raw CSI keeps latency low and leaves demosaic, exposure, and trigger in the host pipeline; USB UVC adds another stack when the dock loop is already tight |
| FOV vs working distance | Marker fills enough pixels from approach through contact | Too wide and the tag is a few blobs; too narrow and you lose the pad before the final crawl |
| Optics | Low-distortion M-size; IR-cut or IR-pass as needed | Warehouse lighting, reflective floors, and IR flood for night docks are ODM filter choices |
| Trigger | External FSYNC / GPIO when dock and nav share one clock | Software-only timestamps do not replace a shared exposure domain |
| Cable | Short FPC for CSI; GMSL when the run is long | Chassis length and motor noise decide the interface early in DFM |
| Calibration pack | Per-serial focus / LSC / WB; extrinsics if multi-cam | Field swaps need files that match the serial on the label |
| Volume path | Samples to production lots on one manufacturer | Dock cams are fleet SKUs; AA yield and long-term supply matter |
Camemake does not invent a finished docking-camera brand SKU here. We engineer the board-level and ODM path: global-shutter MIPI modules sized to the dock envelope, with sensor PN, FPS, baseline, and FOV confirmed per quote so one published number does not lock a single build.
Global shutter for marker lock; MIPI for host latency
Dock approach is motion-critical even when the AGV looks slow. A rolling shutter reads the marker line by line while the chassis still moves. Corners skew, edges smear, and the estimator reports a pose offset that the vehicle then corrects into a miss. Global shutter captures the whole frame at one instant: the shutter class teams ask for when the job is fiducial lock, not casual documentation video.
Interface choice is the second mechanical decision. Closed-loop docking almost always prefers raw MIPI CSI-2 into Jetson Orin-class, Rockchip, Raspberry Pi, or NXP i.MX hosts over USB UVC. Latency stays low, the host owns the ISP, and GPIO or FSYNC can share an exposure time base with nav stereo or aisle cameras when the brief calls for it. Board-level Jetson-ready modules on the 22-pin, 0.5 mm pitch CSI-2 pinout are the production language: sensor, level shifters, and crystal on the FPC, custom cable length, M-size optics.
When the run leaves the length where raw CSI stays clean, Camemake brings GMSL into the same OEM brief: short FPC for the dock face, serializer when compute sits deep in the base. USB stays available for bring-up; the fleet path is usually MIPI once the SoC is locked.
What Camemake puts on a docking RFQ:
- Role. Dock-facing mono for marker pose; optional second FOV or stereo if approach and contact need different working distances.
- Shutter. Global shutter for crawl, vibration, and last-metre turns. Rolling only when motion budget and ISP warp are explicit.
- FOV and working distance. Marker size on the dock, approach standoff, contact Z-height, and pixel budget on the tag.
- Host and CSI budget. Lane count, pinout, FPC length, whether Jetson / Rockchip / i.MX owns the ISP.
- Sync plan. Shared hardware trigger if dock and nav cameras share one control loop.
- Environment. Dust, vibration mounts, IR-cut vs IR-pass, HDR or low-light tuning for aisle lighting.
- Calibration. AA reports, serials, and files the robot software will load on module swap.
How Camemake builds docking modules
CameVision is the published multi-cam ODM family when dock plus nav share one platform: single, double (EGO evaluation), triple, 5-fold, and 9-camera boards. A dock-facing mono is often a single global-shutter MIPI board on that same process language. When the faceplate, connector, or FOV is not in the family, Camemake runs full OEM: PCB, optics, mechanics, firmware, then the same factory lines.
Factory path for a docking program:
- Brief. Marker type and size, working distance, host SoC and CSI budget, cable length, environment, certification markets, mono vs multi-cam sync.
- Configuration. Sensor and shutter class, optics and FOV, MIPI / USB / GMSL, mechanical envelope, quote. Exact PN and FPS confirmed here, not invented in marketing copy.
- Samples. Modules, AA reports, serials, calibration files, host bring-up notes for Jetson or other CSI hosts.
- Production. IQC, SMT, COB or CSP under cleanroom discipline (Class 100 and Class 10,000 on Camemake's public factory story), dust-free lens assembly with optional six-DoF AA (MTF / SFR / CRA / shading), functional and dust inspection, serials into the production database.
- QA and certification support. Optical, electronic, and mechanical inspection with batch QA and serial tracking under ISO9001 process language. CE, FCC, RoHS, and other market paths via Camemake services when the finished robot SKU requires them.
Multi-camera boards that share the dock time base ship with factory extrinsics and a serial. Mono dock modules leave the line with focus lock, shading maps, and a serial so fleet spares match the sample that passed validation.
What OEMs typically ask for in a docking RFQ
- Global-shutter MIPI CSI-2 for motion-blur-free fiducial and marker detect
- FOV and working-distance pair sized to the charge or load station
- External trigger / FSYNC when dock and nav cameras share one robot clock
- Jetson / Rockchip / i.MX pinout and FPC length owned in DFM; GMSL when the chassis run is long
- Per-serial AA and calibration files for field module swaps
- Vibration-aware mounts and filter choices for warehouse lighting and night docks
- Volume path from evaluation MOQs into production lots on one manufacturer
Next step
Send Camemake the docking brief: marker geometry and working distance, shutter and CSI budget, mechanical envelope, target host, and whether the dock cam must share a trigger with nav. We map it to a board-level MIPI OEM design or a CameVision ODM layout, then move from AA samples into serial-tracked volume.
Robotics / CameVision program: https://www.camemake.eu/robotic-solutions
MIPI CSI-2 OEM modules: https://www.camemake.eu/mipi-camera-modules
NVIDIA Jetson MIPI modules: https://www.camemake.eu/nvidia-jetson-camera-modules
Services and certification path: https://www.camemake.eu/services-capabilities
Factory tour: https://www.camemake.eu/inside-the-camemake-factory