Hi!

I have been using the output of /camera/odom/sample within my SLAM package and I have been consistently facing this issue : whenever there is a halt in robot motion after continuous usage, the output of the above mentioned topic turns to NaNs and my SLAM node crashes, but the realsense node does not, it continues to spit out NaNs. This happens when you stop moving after a while even in a feature rich environment. I am not sure whether this has something to do with how the transform tree is set up. This issue is usually resolved by me unplugging the T265 from the USB, plugging it again and starting the node. Sometimes it goes away with some additional motion. Is this happening to other people as well? This issue seems to be related to #695