I want to plug my Logitech C270 USB Webcam into sbRIO-9607 to do simple image capture. However, the camera is not recognized by sbRIO-9607. Actually, sbRIO OS does not find any new USB device plugged in when I plug in the camera. Anything wrong with the sbRIO USB port design?
I've also done the following things to make sure that the camera itself is good.
1. It works well when I plug it to a MyRIO USB port.
2. If I connect the sbRIO to a USB 3.0 hub and connect the camera to the hub, it works.
I'm wondering whether any design fault on sbRIO-9607 USB port. Or any limitation?
The main compatibility requirement for the camera is that it conforms to the UVC standard and is USB 2.0. From what I'm seeing online, that model seems to meet those requirements. From a software compatibility perspective I think you'll need to have the "USB Webcam Support" feature installed. This software component is packaged in IMAQdx and you should be able to install it to the target by doing a custom software installation (rather than selecting the Recommended Software Set) in MAX. Could you confirm in MAX that the right support is installed?
If you already have support installed and its still not working could you clarify these points:
Thanks for your quick guide and reply. Here are the answers.
First of all, Yes, the "USB Webcam Support" is installed properly. Otherwise, the camera won't work even I have the USB hub inserted.
Let me summarize two scenarios here.
I suspect that this could be a kernel issue rather than a hardware issue. What version of LabVIEW RT and the cRIO drivers are you using on the sbRIO and on the mRIO? Also, could you execute the "uname -a" command on both myRIO and sbRIO targets to get the kernel version?
The MyRIO is using RT 2016 and NI-RIO 16.0. The sbRIO is using RT 2016 with NI-RIO 17.6 (to work around another issue). To run "uname -a", I'm getting the following results. Seems that they are using a same kernel. Actually, the reason why I suspect the HW is that a USB Hub without power supply can make things work well.
Linux NI-myRIO-1900-03073d19 4.1.15-rt17-ni-4.0.0f1 #1 SMP PREEMPT RT Fri May 27 10:41:15 CDT 2016 armv7l GNU/Linux
Linux NI-sbRIO-9607-01bbebaa 4.1.15-rt17-ni-4.0.0f1 #1 SMP PREEMPT RT Fri May 27 10:41:15 CDT 2016 armv7l GNU/Linux
Thanks for the info. I was suspecting a kernel issue because there are a lot of older bug reports surrounding similar behavior:
This issue was supposed to be fixed in 3.5, but it seems like some people still experienced issues after that proposed fix. Additional, I think the problem originally came about as a regression. Given that, it's still possible that what you're seeing is related and a similar regression has occurred recently.
Even though there is a difference between myRIO and sbRIO, that can still be kernel related since I believe the root problem in reported bugs was dependent on timing at bootup and enumeration. Slight timing differences between hardware models could produce the different behavior. This may also explain why some the addition of a hub fixes the issue since a hub would influence timing.
A telltale sign that we're running into the same thing would be "cannot set freq 16000 to ep 0x86" entries in /var/log/kern.log. Could you check this log? Also, readout from "lsusb -v" may prove helpful.
Sorry for replying late.
I did observe that this had been a long time kernel issue before I started this topic. But I was expecting that NI has done enough tests so that I started this topic.
In my case, if I run "lsusb", I don't get the device ID 046d:0825 shown in the list. If I run "lsusb -v", sometimes, I'm getting messages as below when the camera does not work.
Can't get device qualifier: Resource temporarily unavailable
Can't get debug descriptor: Resource temporarily unavailable
I don't see /var/log/kern.log. But I find /var/local/natinst/log/ker.log, which does not contain ""cannot set freq 16000 to ep 0x86"".
Besides, I've tried to upgrade the firmware to 6.0.0f1 and driver to 18.0 but found no use.
I wanted to give you a quick update on this. We've been looking into this behavior on our end and have attempted to replicate the issue on a 9627 and 9637 with the 2016 SW stack. Unfortunately, neither of these setups have shown the problem. However, each included a fairly stripped down software set with just System Configuration and NI-IMAQdx components. In the interest of leaving no stone un-turned I'm curious to know all the software you have installed so that I can mirror it. Can you generate a MAX Technical Support Report for me?
Thanks for keeping looking into it. Please check out the attached file.
BTW, based on my experience, I'm not sure whether you can easily find one camera to reproduce the issue. I have one at my hand, which does not work with several sbRIO-9607s, maybe all. I can send it to NI China if you can give me some contacts, or maybe together with my sbRIO. This will save you much time, I think.