T265: Old issue: Frame didn't arrived within 5000 #5101
Description
| Required Info | |
|---|---|
| Camera Model | T265 |
| Firmware Version | 0.1.0.279 |
| Operating System & Version | Raspbian Buster, Ubiquity - all the same |
| Kernel Version (Linux Only) | |
| Platform | Raspberry PI |
| SDK Version | 2.2.9.0 |
| Language | |
| Segment | others |
Issue Description
I know, this issue has already been discussed (but no solution so far). I can easily reproduce it by letting the T265 starr to a white wall w/o features or covering it with a towel or letting it run in a dark room.
Most the time the T265 recovers from that by reverting the initiating situation. But this helps not all the time. If it doesn't recover, it starts to deploy NaN coordinates at 200 Hz and there is no way to convince the cam to be in "save" areas again :)
What would be the suggested procedure then? Not even restart of the script seems to help. Only unplug/re-plug of USB, which is a little problem IMHO for robots :)