We added a Microsoft LifeCam HD-3000 to our RoboRIO through USB, but it only works if we run the code from our desktop computer. The code that allowed video feedback while ran on the PC, I built it, ran it as start up, and then deployed it like normal to the RoboRio and then rebooted the robot. When I opened the driver station after the radio finished booting, there was no video being displayed, we had the same options to select the camera. However, no video showed up, and the code just worked while running it on the desktop. I am not sure why the camera gave us video while the code was being run on the desktop computer, but not while being run on the RoboRIO.
Please help.
Before I say anything, I’ll just say most of my knowledge is from C++ and Java, so I don’t know if it applies- although it should still apply, it might not. Are you using any separate vision processing program? Some of those open separate instances of the dashboard, which means you wouldn’t see the camera. Try making sure you only have one instance open, because the camera feed will only go to the first from what I’ve seen. Other than that, make sure that the code is on the RoboRio. Someone who has more LabVIEW experience could help more.
We are using the standard LabView vision code that comes pre-created. We have not changed anything on the DriverStation code with the camera. The code that worked on the desktop is the same code on the RoboRIO, so that should not be the problem. Thanks for the quick reply though.
Here’s the troubleshooting guide I’ve put together for fixing LabVIEW camera issues.
- Make sure Enable Vision is defaulted ON in the front panel of Robot Main and Robot Global Data.
- In either Begin or Vision Processing, wherever you initialize your camera, ensure that it is configured with the correct connection parameters. Since you are using a USB camera, this should just be a matter of selecting the right USB port to be passed into the Camera Begin VI, and (if using Vision Processing) setting the constant T/F into the Select block to the correct value to select USB instead of IP.
- (For IP Cameras only): Ensure that you’re not running into the pesky “.local” issue on the IP address. Depending on whether you’re tethered or over Wifi, the DNS-assigned name of the camera may be either “cameraname: PORT” or “cameraname.local: PORT”.
- (For LifeCam HD-3000 only): Ensure that you have followed the steps for setting up the camera listed on ScreenSteps Live: http://wpilib.screenstepslive.com/s/4485/m/24194/l/288981-using-the-microsoft-lifecam-hd-3000
- (will add more steps as needed)
We only had to follow step 1 and it still is not working. The guide on the website you listed says that you do not need to add any code for this camera for LabView. We created a true constant and replaced the “enable vision” boolean with that constant and then built it, ran it as startup, etc. to run it from the RoboRIO, but still got no camera responding. We got the errors (White text is bold, other errors did not have to do with the camera):
~ERROR 1055 Property Node in WPI_SerialPortGetName.vi->WPI_Seria PortOpen.vi->Begin.vi->RobotMain.viLabVIEW: Object Reference is invalid
~ERROR -44003 FRC: Operation failed due to a communication failure with the camera. WPI_CameraIssue HTTP Request with Authentication.vi
Is there anything else in that checklist that would apply?
The constant change was in Robot Main.vi by the way.
Are you sure you have USB 0 selected in the far left of your Vision Processing.vi block diagram rather than axis-camera.local?
Yes, I still don’t think that would have any affect on the camera, as we still get an image, just only when we run the code when we are tethered, we get no response when we deploy the startup code over WiFi.
It works!!! We found a solution. Website is the second link.
~https://drive.google.com/file/d/0B2aaTMmNdQ2hTmsxRDBHSnd4TFk/view?usp=sharing
~https://forums.ni.com/t5/FIRST-Robotics-Competition/FRC-2017-USB-Camera-not-working-with-LABView/td-p/3571764