ROBOTBAY / DEVELOPER NOTES / 001

Start with your first depth frames.

Read the developer resources, choose for your task, then leave a reproducible record for the next person.

RobotBay task selection note · editorial guidance distinguished from official sources

01 / DOCUMENTATION

Check the integration requirements

Task: connect one depth camera and acquire depth frames on a host. If color is needed, verify the model’s supported color streams separately. Use a static tabletop object; no robot motion is required.

These are existing document-review records, dated on each product page. None of these candidates has completed a RobotBay hardware test for this task. Compatibility remains unverified.

02 / TASK SELECTION

Define the task before choosing a camera

This is a decision path, not a performance ranking. Start with equipment you already own. Without distance and field-of-view requirements, we do not recommend a particular model.

Your requirementCheck firstNext step
Close tabletop / small objectsMinimum operating distance, field of view and mounting; compare official model data with target size.Include D405 for review; verify its range and color-stream capabilities before substituting it for another model.
A more distant viewpointActual distance, material and lighting; maximum range does not establish task accuracy.Compare D455 and Gemini 335 model documentation, then test in the same scene.
The application uses ROS 2Match OS, architecture, ROS distribution, wrapper, SDK and firmware.Verify capture with the vendor SDK first, then check ROS images, camera_info and timestamps.

Integration checkpoints: leave evidence at each step

  1. Identify the device

    Record model, firmware, host OS and architecture; confirm device enumeration in the official tool.

  2. Pin the software

    Save SDK/wrapper tags or commits, installation method and dependencies; do not write only “latest”.

  3. Capture a frame

    Use the official example for that version; save dimensions, format, units and raw timestamps. An image alone does not establish depth accuracy.

  4. Observe a short run

    Suggested: capture 60 seconds of logs, requested profiles, frame counts, interruptions and errors. This is a contribution observation window, not a product acceptance standard.

  5. Enable a second run

    Include steps, commands, failures and recovery; state which conditions remain untested.

Sources and limits of this note

Editorial date: 2026-11-08. The decision path and checkpoints are RobotBay suggestions, not manufacturer performance findings. Check model specifications in the official sources linked on each product page.

RealSense SDK ↗
RealSense ROS wrapper ↗
Orbbec ROS 2 wrapper ↗
03 / OPEN INTEGRATION CALL · RB-INT-001

Open call: document your first depth frames

Looking for developers who already own one of these cameras and can document a real integration. Other models are welcome; include sources and versions without assuming compatibility.

Hardware contributor

Connect the device and document environment, steps, data and failures.

Reproducer

Repeat another contributor’s steps and flag missing prerequisites. Record different hardware separately.

Documentation contributor

Check versions and improve bilingual instructions. No device needed; documentation work is not hardware testing.

Volunteer for this integration → Submit an existing run →

Participation is free and voluntary. Hardware, funding and mentor support are not currently promised. RobotBay organizes issues, reviews evidence and credits contributors with permission.

Combination records: awaiting the first real run

No reviewed integration result exists for this task yet. Failed and partial runs are welcome. Reviewed records will identify device, host, software, task, result and limitations, with links back to product pages.

Review and credit policy →