Supported Cameras
RealSense D435i
Depth Camera with IMU
- Dual infrared stereo cameras
- Active depth sensor
- Built-in IMU (accel + gyro)
- 640x480 @ 30Hz
- USB 3.0 connection
RealSense T265
Tracking Camera
- Dual fisheye cameras
- Built-in IMU
- 848x800 @ 30Hz
- Purpose-built for SLAM
- USB 2.0/3.0 connection
Prerequisites
Verify installation
Check that your camera is detected:You should see your camera listed with its serial number and firmware version.
RealSense D435i Examples
The D435i provides stereo infrared cameras and RGB-D depth.Stereo-Inertial Mode (Recommended)
Use infrared stereo cameras with IMU for best performance:From the README.md:110-111, this is the recommended way to use the D435i with ORB-SLAM3.
What Happens Internally
The example (stereo_inertial_realsense_D435i.cc:162-165) configures streams:- Infrared cameras: Better for SLAM (no RGB distraction, consistent lighting)
- IMU synchronization: Accelerometer data interpolated to gyro timestamps
- Auto-exposure: Automatically enabled for varying lighting
- Emitter disabled: IR projector turned off (stereo_inertial_realsense_D435i.cc:143)
RGB-D Mode
Use the depth sensor with RGB camera:- Indoor environments
- Objects at close range (less than 10m)
- Dense reconstruction needs
Monocular and Stereo Modes
Also available but less commonly used:- Monocular
- Stereo
- Monocular-Inertial
RealSense T265 Examples
The T265 is specifically designed for tracking and SLAM with fisheye cameras.Stereo-Inertial Mode
Configuration
The T265 example (stereo_inertial_realsense_t265.cc:89-94) uses fisheye streams:- Wide field of view (170°)
- Optimized for tracking
- Low latency
- Works in low light
Monocular-Inertial Mode
Comparison: T265 vs D435i
| Feature | T265 | D435i |
|---|---|---|
| Camera Type | Fisheye | Infrared Stereo |
| FOV | 170° | ~85° |
| Best For | Tracking, Motion | Depth, Mapping |
| Depth Sensor | No | Yes |
| Outdoor Use | Excellent | Good |
| Indoor Use | Excellent | Excellent |
| Price | Higher | Lower |
Camera Configuration
RealSense cameras are automatically configured with optimal settings.D435i Auto-Configuration
The examples automatically set (stereo_inertial_realsense_D435i.cc:141-154):Custom Configuration
To modify camera settings, edit the YAML file:Running Real-Time SLAM
Initialize
Move the camera slowly with visible features in view.
Wait for initialization to complete (status shown in viewer).
Operate
Move the camera through your environment.
The system tracks in real-time and builds a 3D map.
Visualizer Controls
The Pangolin viewer shows:- Main View
- Current Frame
- Controls
- 3D map points (small dots)
- Keyframes (camera frustums)
- Current pose (red/green frustum)
- Trajectory (line trail)
Troubleshooting
Camera Not Detected
Camera Not Detected
Solutions:
- Check USB 3.0 connection (blue port)
- Try different USB port
- Verify with
rs-enumerate-devices - Update firmware:
rs-fw-update - Check permissions:
sudo chmod a+rw /dev/bus/usb/*/*
Initialization Failed
Initialization Failed
Tips:
- Move camera slowly
- Ensure good lighting
- Point at textured surfaces
- Wait for auto-exposure to stabilize
- Check IMU is working:
rs-enumerate-devices -c
Dropped Frames
Dropped Frames
If seeing “dropped frames” messages:
- Check USB bandwidth (disconnect other devices)
- Verify USB 3.0 connection
- Close realsense-viewer if running
- Reduce resolution if needed
Tracking Lost
Tracking Lost
Recovery:
- System will attempt relocalization
- Move to area with good features
- Return to previously mapped area
- Restart if necessary
IMU Synchronization Issues
IMU Synchronization Issues
The examples handle IMU synchronization automatically.
If issues persist:
- Check
IMU.Frequencyin YAML (should be 200) - Verify motion correction disabled
- Ensure librealsense2 version >= 2.40
Performance Optimization
- Reduce Resolution
- Fewer Features
- Disable Viewer
For faster processing, modify the example:Update YAML accordingly.
Saving Trajectory
Trajectories are automatically saved when stopping:Custom Output Name
Specify output filename:f_my_trajectory.txtkf_my_trajectory.txt
Advanced: ROS Integration
For ROS integration with RealSense: See ROS Examples for more details.Comparison with Dataset Examples
| Aspect | Live Camera | Datasets |
|---|---|---|
| Setup | Plug & play | Download required |
| Timing | Real-time | Can replay slower |
| Debugging | Harder | Easier (repeatable) |
| Ground Truth | No | Yes |
| Use Case | Deployment | Development |
Develop and tune your system on datasets (EuRoC, TUM-VI) before testing with live cameras.
Next Steps
Camera Calibration
Calibrate your own RealSense setup
IMU Configuration
Fine-tune IMU parameters
ROS Integration
Use ORB-SLAM3 with ROS
System Tuning
Optimize for your application