Repository navigation
Replies: 5 comments 5 replies
|
Hi @ntsarb Thanks so much for your work in modernizing the RealSense SDK's T265 support to bring it to working condition in the latest version! There are no plans for RealSense to resume official support for T265. The camera is no longer manufactured and the RealSense product range's present and future is now focused solely on the stereo depth cameras. I'm certain that you will find a lot of interest from current T265 owners though if you maintain your T265-enabled custom version of the SDK as a separate GitHub fork. You could make your repository easier for T265 users to find by creating a video on YouTube that demonstrates your T265-enabled 2.59.1. Technical and development support for T265 ceased in 2020, so it is not possible for RealSense to alter the T265's firmware driver, unfortunately. Also, T265 was produced when RealSense was a division of Intel, and since 2025 RealSense has become a separate company (RealSense, Inc) that is no longer part of Intel. Thanks again for your work in support of RealSense! |
|
The old Intel licence terms documentation is no longer available but the terms of the current RealSense, Inc End User Licence Agreement document (whose terms cover the use of firmware drivers) should be applicable. https://www.realsenseai.com/realense-inc-end-user-license-agreement/ RealSense firmware drivers have always been closed-source, so by the End-User Licence terms it is not permitted to decompile and reverse-engineer them, remove or alter any proprietary notices, or distribute them to third parties. |
|
The firmware for T265 did not have an archive where users could download the firmware themselves. Instead, the firmware was bundled within the SDK. When the camera was plugged into the USB port, it would check the firmware version and automatically install a newer firmware than the currently installed one if a newer version was bundled in the SDK. My research indicates though that saying the firmware files are "bundled in the SDK" does not mean that they are stored locally in the SDK's file structure but instead were downloaded from an Amazon S3 web address when the update process was activated, as described at #5979 Intel removed their RealSense web files when RealSense transitioned to the spun-off company RealSense, Inc. If one had a T265 firmware file then it is conceivable that the download address in the SDK could be changed to check a different web address for the file, such as a path set up for your own project. That would probably be a violation of the End User Licence though if it was changing the distribution of the firmware from its original Intel path. |
|
If ownership of the T265 technology remained with Intel when RealSense was spun out into the RealSense, Inc company then there may be nothing that can be done by RealSense, Inc. I will highlight your firmware distribution permissions proposal to my RealSense colleagues to seek their advice. |
|
After discussion with my RealSense colleagues, I have opened a formal internal query to our R&D department to get their opinion of your proposal. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
Hi,
I spent some time today to assess whether it is possible to cleanly add support back for the RealSense Tracking Camera T265 to the latest RealSense v2.59.1 and I was successful (more details below).
Nikos
What has been successfully tested
A fork of the latest RealSense v2.59.1 with T265 support. The T265 firmware is fetched at build time (the CMake configure step) from the conda-forge librealsense-2.53.1 package (librealsense-2.53.1-h8386552_6_cpu.conda), cached in .fw-cache/, and embedded into librealsense2.so.2.59.1 via .incbin. After the library is built, the firmware travels inside the library itself — no network access at install or runtime. (The camera's own on-device firmware is separate; this blob is what the SDK carries for T265 boot/verification.)
What changes were made (summary)
All reactions