Compatibility Of Realsense SR305 Camera

Short answer: possibly - the Intel RealSense D435i robot skill can work with other RealSense depth cameras (the skill text says it "should also work with other Intel RealSense depth camera models"), but if your SR305 doesn't appear in the skill's device dropdown it’s usually an enumeration/driver/USB or profile issue rather than a hard block in ARC. Below are the most common causes and step-by-step checks to get the SR305 recognized.

Quick links

• Intel Realsense D435i skill: https://synthiam.com/Support/Skills/Navigation/Intel-Realsense-D435i?id=20404
• Recommended librealsense release referenced by the skill docs: https://github.com/IntelRealSense/librealsense/releases/tag/v2.55.1
• ARC downloads & info: https://synthiam.com/Products/ARC

Checklist + troubleshooting steps

1. Make sure RealSense Viewer works and is closed

• Confirm the SR305 appears and streams OK in the Intel RealSense Viewer.
• Close the RealSense Viewer before opening ARC - the viewer can lock the camera so other apps (including the ARC skill) can’t see it.

2. Use a USB 3.0 port and quality cable

• Intel depth cameras must be on a USB 3.0 port (blue USB or marked SuperSpeed). Try another USB3 port or a shorter, better shielded cable if available.

3. Confirm librealsense / drivers are installed & up-to-date

• Install the librealsense runtime/SDK matching what the skill expects (the docs reference v2.55.1). After install, reboot the PC.
• If you updated firmware in the RealSense Viewer, reboot afterwards.

4. Check device visibility by serial number

• The D435i skill lists RealSense devices by serial number. In the RealSense Viewer note the camera serial and then look for that serial in the skill dropdown.
• If the camera shows in Device Manager / librealsense but not in ARC, copy the serial and paste it into your reply.

5. Confirm stream profiles are supported & try auto-size

• The D435i skill expects compatible depth+RGB profiles. In the skill config try setting Width/Height to 0 (auto-size) so the skill doesn't reject unsupported fixed profiles.
• If you manually set resolution/framerate in the skill, make them match what RealSense Viewer shows for the SR305.

6. Run ARC as Administrator (temporarily)

• Try launching ARC as Administrator to rule out permission issues accessing the camera.

7. Check the skill's log panel

• Open the Intel RealSense D435i skill in ARC and press START. Watch the skill log window for errors (driver missing, device not found, permission denied).
• If you see an error, copy/paste the exact log text here and I’ll interpret it.

8. Firmware / device differences

• The SR305 is a short-range model and lacks an IMU. The D435i skill was written for the D435i, but the docs explicitly say it should work with other RealSense models. Still, some skill behaviors or dropdown filtering might expect certain capabilities (IMU, particular profiles). If the skill filters devices by capabilities it needs, it could hide SR305 - the log will usually say why.

9. Conflicts: other apps or services

• Make sure no other app (RealSense Viewer, other robotics SDKs) is holding the camera. Close them all and try again.

10. Final steps if still not visible

• Replug camera, try a different USB3 port, reboot PC.
• Update librealsense and firmware, reboot, then start ARC and the skill.

What I need from you to continue

• OS (Windows 10/11?), ARC version.
• Is the SR305 visible and streaming in the Intel RealSense Viewer right now? If yes, what serial number does the Viewer list?
• What exact entries (if any) appear in the D435i skill dropdown? Any error messages in the D435i skill log when you press START? Copy/paste the log text if present.
• Which USB port (PC built-in USB3, USB hub, USB-C adapter, etc.) and cable type are you using?

If it helps, I can provide the exact ControlCommand() to start/stop the skill or a short checklist you can paste into the skill log area to capture the error. Want me to give the ControlCommand() and a one-line script to get the skill to print debug info?

We will check whether there's an updated driver for that model. In the meantime, can you let us know which RealSense version you were using with that product model? That will help us identify which driver may need updating.