View my account

Problems using T265 with Pi 4

Follow
Ilya

Dear Realsense support team,

I am seeing a couple issues with my early stage testing of T265 on Pi4 (Raspbian Buster).

 

First issue:

T265 needs to be unplugged and re-plugged after each power cycle of Pi 4. It almost looks like it is not being correctly recognized by the OS at boot.

When running lsusb right after boot, the T265 camera appears like this: "Bus 001 Device 003: ID 03e7:2150 Intel Myriad VPU [Movidius Neural Compute Stick ]". When trying to access the camera in code, an error is thrown: "terminate called after throwing an instance of 'rs2::error'
what(): No device connected".

After un-plugging and re-plugging the T265, it appears like this: Bus 001 Device 006: ID 03e7:2150 Intel Myriad VPU [Movidius Neural Compute Stick]. Then, when code is started, it is able to connect to the camera. After code finished executing, lsusb command gives this output: Bus 002 Device 002: ID 8087:0b37 Intel Corp.

 

Second issue:

The camera would run ok for a few minutes and then throw this error: "terminate called after throwing an instance of 'rs2::error' , what():  Frame didn't arrive within 15000".

 

I tried updating firmware. This did not help.

Please let me know how would you suggest to approach these issue.

Thank you!

 

0

Comments

1 comment

Date Votes
  • MartyG
    • Edited

    RealSense T265 cases are now handled on the RealSense GitHub forum.  To post your question there, please visit the site and click the New Issue button.

    https://github.com/IntelRealSense/librealsense/issues/ 

    Having said that, the issues that you described are known problems on the GitHub.  If you Google about the problems you are having and include the words 'librealsense t265' in each of your searches, you are likely to find relevant search results for the GitHub quickly.  For example:

    librealsense t265 raspian Frame didn't arrive within 15000

    https://github.com/IntelRealSense/librealsense/issues/5101 

     

    Also please note that to update the T265 firmware, all you need to do is install the latest SDK version as the firmware for the T265 is packaged within the SDK.

    0
    Comment actions Permalink

Please sign in to leave a comment.

Didn't find what you were looking for?

New post