I've seen reports in the past of other devices on NUCs needing to be unplugged and replugged to get them to work (mice, keyboards, external drives, etc). I couldn't find a definitive solution to the issue. A Microsoft tech support person who was asked about this issue by a NUC owner thought it may be related to outdated or incompatible device drivers.
Thanks for your reply. I did assume that the issue could be with NUC. But I noticed something strange. On running cpp-capture, I was able to get the IR/RGB/Depth streams which meant that the USB driver is not entirely malfunctioning. So I tried analyzing the process of launching the ros nodelets using gdb and find problematic areas in the nodelets. I narrowed to down to an issue related to getting data from the IMU and fisheye camera. By commenting out the following lines:
I was able to get all the data, except from IMU and Fisheye. I will need these data streams too in the future though, so I do not consider this "hack" to be a permanent solution. Please, can someone more knowledgeable about the driver code look for a complete solution?
I'm glad you were able to find a workaround. Good luck with the IMU and fisheye!
This message was posted on behalf of Intel Corporation
Thanks for your interest in the Intel® Realsense™ Platform.
Unfortunately, the ZR300 has only been validated to work with this hardware and software System Requirements for the Intel® RealSense™ Development Kit... . This might be the reason why you can't get data from the IMU or the fisheye.
We apologize for any inconvenience that this may cause.
Thanks for clarifying that. But I feel that this issue can be solved. I urge Realsense's developers to put in some time to investigate and debug this issue, and confirm whether the problem is on realsense's side or NUC's side. Meanwhile I will raise an issue in NUC forums and see if they can help me out somehow.