Announcement: Introducing the RealSense Tracking Camera T265

[MartyG-RealSense]

Hi everyone,

A new RealSense camera product called the RealSense Tracking Camera T265 is now listed for pre-prder on Intel's online Click store, with pre-orders due to ship in the week of March 4 2019.

"Intel RealSense Tracking Camera T265 is a new class of stand-alone Simultaneous Localization and Mapping device, for use in robotics, drones and more".

https://click.intel.com/order-intel-realsense-tracking-camera-t265.html

[barnjamin]

Thanks, Specifications table is a little light on details. Any chance for some numbers like fps and depth accuracy?

[dorodnic]

Thanks @MartyG-RealSense

• Learn More @ realsense.intel.com
• Intel Announces New Class of RealSense Stand-Alone Inside-Out Tracking Camera (Newsroom)

Also, I'll try to answer some of the questions here.

FAQ

1. Is this a Depth-Camera?
   No, the T265 does not offer any Depth information. It can provide IMU (Accel and Gyro), two monochrome fisheye streams, and 6-DOF pose data.

2. Can I use it together with a Depth-Camera?
   Yes, this device can be used with RealSense (and most likely any 3rd-party) depth cameras. It is passive and comes with an IR-cut filter.

3. What platforms are going to be supported?
   At launch the T265 will be supported via librealsense on Windows and Linux, and via ros-realsense.
   Mac-OS and Android support is planned but not scheduled yet, as well as OpenVR integration.

4. What are the system requirements?
   Any board with USB2 capable of polling 6-DOF packets 260 times a second should be sufficient. The device was validated on Intel NUC platform.

5. Will the same SLAM be available for the D435i as a software package?
   We are still looking into it, please stay tuned.

[sam598]

@dorodnic Will the pose timestamps be able to sync with realsense depth cameras? Or will there be some method of synchronizing the pose data with other hardware?

[dorodnic]

@sam598 - As far as I know there is no hardware-sync, but you could query T265 and D400 clocks with ~2-4ms accuracy each.

[dorodnic]

Fairly short (24sec) recording of T265 data:

Accelerometer and Gyro + Dual Fisheye + POSE data

3D View showing device trajectory

Download sample *.bag file (1GB) and open with Intel RealSense Viewer 2.18+
(click Add Source > From File... to load the ROS-bag recording)

[JBBee]

This product looks amazing. Does it provide any support for persistence? Ideally, a way to fetch and save the map on a host and then restore it and re-localize to that map?

Thanks.

[dorodnic]

@JBBee - right now save/load_relocalization_map is still not part of librealsense API, but it is part of device capabilities and we are planning to support it at product launch next month.

[nominator]

@dorodnic

@JBBee - right now save/load_relocalization_map is still not part of librealsense API, but it is part of device capabilities and we are planning to support it at product launch next month.

I would like to do +100 likes on it if I could. Have been waiting so long for a proper tracking solution from Realsense. After reading initial info. on T265, first question in my mind was, whether it will allow persistence? AND IT WILL :) so cool!!

Other nice to have features could be
1- Occlusion (virtual objects occluded by physical geometry) in AR
2- Plane detection (walls, floors, angled surfaces) for placing virtual objects,
3- Ray-casts to detect touch targets in 3D space etc

Thanks

[dorodnic]

Appreciate the feedback.
Since this device is based on Myriad VPU, we might be able to add more CV functionality in the future.
However, right now we are focusing on the V-SLAM aspect.

[nominator]

@dorodnic That will be awesome. Until then, is it possible for 3rd party developers to use the raw streams of data from camera to implement these CV features on the host? Just want to make sure there is nothing to keep from it in the SDK or the device