Overview
This page is laid out to “sell” to technical buyers without marketing fluff: quick positioning + credible engineering claims, then deeper specs, block diagrams, and integration documents.
A robotics-focused imaging PCB integrating two camera paths: visible and NIR (Near-Infrared). Designed to support deterministic capture via hardware trigger, coherent timestamping, and a clean host interface for low-latency perception pipelines.
Acronyms: NIR = Near-Infrared.
Specifications
Use a compact table: it’s skimmable and forces you to state measurable numbers. Replace “TBD” with verified values.
| Spectral bands | Visible (RGB) + NIR (Near-Infrared), e.g. 850–940 nm (TBD) |
|---|---|
| Resolution / frame rate | e.g. 1920×1080 @ 60 fps per channel (TBD) |
| Shutter type | Global shutter preferred for robotics (TBD) |
| Synchronization | Hardware trigger input, shared clocking, frame counters (TBD) |
| Timestamping | Host-visible timestamps; PTP (Precision Time Protocol) option if Ethernet (TBD) |
| Host interface | USB 3.x / MIPI CSI-2 / GigE (Gigabit Ethernet) (choose) |
| Power input | e.g. 9–24 V DC (Direct Current) with onboard regulation (TBD) |
| Typical power | e.g. 3.5 W @ nominal capture (TBD) |
| Operating temperature | e.g. −20 to +70 °C (board) (TBD) |
| EMI/EMC | Designed with ground/return integrity and shielding options (TBD) |
Acronyms: fps = frames per second. PTP = Precision Time Protocol. EMI/EMC = Electromagnetic Interference / Compatibility.
Electrical interface notes ⌄
- Trigger: 3.3 V logic input, configurable edge, debounce/filtering optional (TBD).
- GPIO: status pins for frame-valid, sync, error state (TBD).
- Power: reverse polarity and inrush handling recommended for robotics harnesses.
- Grounding: star-ground strategy into chassis + controlled return paths for high-speed lanes.
Optical considerations ⌄
- IR illumination: 850 nm offers sensitivity; 940 nm reduces red-glow visibility (TBD).
- Filters: band-pass filters reduce cross-talk between visible and NIR paths.
- Calibration: intrinsic/extrinsic calibration for dual-path alignment (factory or user workflow).
Latency & determinism ⌄
- Capture-to-host: quantify camera exposure + readout + transport + host copy.
- Timestamp point: define whether timestamp is at trigger edge, exposure start, or frame-valid.
- Jitter budget: publish worst-case timing jitter under load (engineers care).
Block schematic diagram
For the website, a clean block diagram is usually better than dumping full schematics inline. Link the full schematics PDF above.
- Trigger semantics: specify what the trigger edge means (exposure start vs frame latch).
- Timebase: define how timestamps are generated and how to align with robot clock.
- IR illumination: specify supported wavelength(s), strobe support, and safety constraints.
- Calibration: publish a repeatable workflow for visible↔NIR alignment.
- Thermals: provide heat paths, derating, and enclosure guidance.
Use-cases
Keep use-cases concrete. Tie each to a measurable benefit (lighting robustness, timing determinism, failure handling).
Evaluation kit & support (example)
This is where you state what the customer gets and what you support. Keep it crisp and testable.
- Vision PCB + lens/sensor modules (as configured)
- Harness + trigger cable
- Reference host capture utility + SDK examples
- Calibration target + procedure
Keep claims consistent with what you can actually ship/support.
Replace with real addresses/forms. Avoid putting personal email addresses on public pages if possible.