'No Frames Received!' for T265 streams after a minute or two #7178
Comments
|
@RealSense-Customer-Engineering @RealSenseCustomerSupport Can you take a look into this? Past 'No Frames Received!' issues seems to be related to firmware or SDK versions, but as far as I understand this is the most recent release. |
|
Hi @dorodnic @ev-mp @RealSenseSupport any ideas? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Issue Description
I flashed an SD card using the pre-built image provided by this RealSense doc, but realized it doesn't install
realsense-viewer. So I went ahead and did thelibuvc-backendinstallation as instructed here.When that was complete, I plugged in the T265, and started
realsense-viewer. I was able to see images from the fisheye lenses and also observed that it was able to track motionfor about 1-2 minutes. Afterwards, it stopped broadcasting data (see image below). Restarting the viewer has no effect on the issue, and these are the only error messages that appeared:There is however an interesting behavior that I noted. When I turn the stream off and on again (when all streams has the 'No Frames Received!' error), the fisheye streams still have the 'No Frames Received!' error, but the Accel, Gyro and Pose streams seems to be working. It isn't until a minute or two later that all streams have the 'No Frames Received!' error (as shown in the image above).
This goes away when unplugging and replugging the T265 into the Pi 4, but the issue recurs after awhile.
I noticed in #6943 that the patch-based build method is more stable than the
libuvc-backendmethod, but there's not really a mention on how to do that on the Pi 4. Could that be the reason, and if so, is it possible to do the patch-based build on the Pi 4?The text was updated successfully, but these errors were encountered: