![]() |
GRIP with USB Camera
I am trying to use GRIP with my USB camera. I know the camera works and is configured correctly but, with my input set to webcam 0 it says it can not find the camera.
What source must I use to access my USB camera? |
Re: GRIP with USB Camera
What's the exact error message that happens when you create a camera source?
|
Re: GRIP with USB Camera
This is the part that I believe you are looking for.
Code:
WARNING: Failed to initialize CameraSourceCode:
Loading Dependency Injection Framework |
Re: GRIP with USB Camera
What model camera is it?
Just to make sure, it's plugged into the roboRIO, right? |
Re: GRIP with USB Camera
The model is not on it and the box is long gone. It is a logitech webcam of some type.
Putting the camera on the dashboard works fine, yes it is plugged into the RoboRio. |
Re: GRIP with USB Camera
I updated to Grip 1.1.1 unfortunately I am still unable to create my camera source.
When I plug the webcam into the labtop it works, so I know the camera is compatible and works. I can output the camera to the dashboard, therefore the camera is operation when plugged into the roboRio. Code:
VIDEOIO ERROR: V4L: index 0 is not correct!Do I need to be using a different source when it is plugged into the RIO? |
Re: GRIP with USB Camera
I found my own problem. I should have read the error more carefully.
Code:
INFO: Loading file /home/lvuser/project.grip |
Re: GRIP with USB Camera
Quote:
|
Re: GRIP with USB Camera
I am also trying to get my Microsoft LifeCam 3000-HD to work, but using RoboRealm. After using the FRC_CameraClient module, I get the error "Invalid Jpeg Format". It works fine when connecting directly to the PC. The only other discussion I have found about this is in this (http://www.roborealm.com/forum/index.php?thread_id=5472) RoboRealm thread:
"It seems that they are using jpeg images but with a couple bytes at the beginning of the stream that indicate size, fps, etc. Its not a standard stream format so we'll have to create something specific to handle these kinds of streams." Perhaps the RoboRio is formatting USB Webcam images specifically for the dashboard? Even if not, it seems to be an issue with the RoboRio, since other webcams are having this same issue. Later in that thread, however, the guy who was having issues said he was able to successfully get the image to come in right, but he doesn't really explain how. Edit: This (http://www.chiefdelphi.com/forums/sh...d.php?t=134404) thread details how the RoboRio handles USB Webcams. According to it, the images extracted from the webcam is missing a part of the normal JPEG header. While his modified camera viewer may not be useful, he also explains that the Intermediate Vision template will re-encode the images locally. |
Re: GRIP with USB Camera
This defiantly seems to be the problem.
It seems to get closer if you don't start the camera in the code. It can at least find the camera this way but, it has extraneous data. Code:
VIDEOIO ERROR: V4L/V4L2: VIDIOC_S_CROP |
Re: GRIP with USB Camera
Just got RoboRealm to pick up the USB Webcam image using the Intermediate Vision example program.
|
Re: GRIP with USB Camera
GRIP has loads of potential to be a very powerful tool, I'd like to see if we (being the users of chief delphi) can get it working.
|
Re: GRIP with USB Camera
Just curious if anyone has gotten GRIP to work on the RoboRIO using a USB camera. We have it running with the Axis IP camera, but the two MS lifecams we tried both throw that same error.
|
Re: GRIP with USB Camera
GRIP on the roboRIO with our USB Lifecam 3000-HD works without camera error but an old Logitech USB camera from the junk box throws those same errors of a bad couple of bytes in each frame. An Axis M1011 IP camera with GRIP running on the driver station PC runs for about a minute then the image freezes. We might guess the setup of the camera isn't right but the documentation on how to set it up is sparse and there aren't really very many choices to be made anyway.
We are having severe startup problems but if GRIP can make it past the first few seconds after starting on the roboRIO it runs fine albeit a little slow. |
Re: GRIP with USB Camera
Quote:
We're using a Logitech C920 USB, and were initially unable to get it directly working with GRIP running on a RPi2. Not too surprising, since that platform isn't not officially supported by GRIP. However, there's an awesome thread on Github with a lot of great community activity getting GRIP onto RPi2. With the info in that thread we were able to get that USB camera's feed published as an IP camera using mjpeg-streamer, which GRIP was then able to find and use on the RPi2, running Linux Arm. Might be something to try on the RoboRio? We haven't yet verified GRIP is publishing stuff to NetworkTables, we hope to verify that tonight. |
Re: GRIP with USB Camera
Quote:
Do I still initialize the camera server when trying to use it with grip? Code:
CameraServer server = CameraServer.getInstance(); |
Re: GRIP with USB Camera
If you initialize the cameraserver in your robot program GRIP probably won't be able to access it. Usually only one application can access a camera at a time on Linux.
To get similar functionality as CameraServer, you can use the "Publish Video" operation in GRIP. |
Re: GRIP with USB Camera
I think we are really close to getting this working!
What is setting property #16? We are getting this error on our deploy: Code:
Jan 27, 2016 1:53:36 AM edu.wpi.grip.core.Main start |
Re: GRIP with USB Camera
Quote:
This is completely harmless. Since we don't do anything to manually configure camera settings in GRIP, any properties that get set are just by OpenCV trying to set up some defaults. Is the project working otherwise? I noticed you have a SUCCESS message and no exceptions. |
Re: GRIP with USB Camera
Yes! Everything appears to be working. I saw the error an I guess I panicked.
Everything appears to be operational, network tables and all. Should I be concerned about this error? Everything seems to still work but, maybe. Code:
Loading Dependency Injection Framework |
Re: GRIP with USB Camera
While the project is loading, the steps start running before the camera is ready. This isn't really concerning, and it should be fixed in the next release.
|
Re: GRIP with USB Camera
Hi Thomas I am still not able to get my camera (Microsoft 3000 USB) to be found in version 1.1.1. Every time I enter 0 the error pops up "A problem occurred trying to start the frame grabber for Webcam 0". I know this camera works do testing it on the robot and on other computers that have the older version of Grip on them.
Sincerely, Joe |
Re: GRIP with USB Camera
Can you try it on the other computers with a newer GRIP? AFAIK nothing has changed with USB cameras between the last few versions of GRIP, so it may be a driver issue.
|
Re: GRIP with USB Camera
Quote:
Also, we have code that uses the NI camera support to switch the DS feed between multiple USB cameras...but we can't use it if GRIP is running. Is there some way or could a way be added for the robot code to feed images to GRIP instead of GRIP commandeering the camera? We are interested in GRIP but do not want to give up our existing camera server code. |
Re: GRIP with USB Camera
Figured it out that the drivers of the camera had not been fully downloaded. Thanks for your help.
|
Re: GRIP with USB Camera
Hey, so we are having some issues with getting the network tables to work. I was wondering if you guys who got it working could elaborate on how you got that side of things working? We're using C++.
Thanks! |
Re: GRIP with USB Camera
Hi, all.
My problem is similar to others in the thread, but not quite the same. I can get GRIP 1.2.0 running just fine on my laptop, using the MS Lifecam 3000 USB. it publishes to NetworkTables on the RIO, and then the DS is able to act upon it to control the robot as expected. So far, so good. But when trying to deploy the GRIP to the robot (so it can run headless on the RIO), I get this error: Code:
/usr/local/frc/JRE//bin/java -Xmx50m -XX:-OmitStackTraceInFastThrow -XX:+HeapDumpOnOutOfMemoryError -jar '/home/lvuser/grip.jar' '/home/lvuser/project.grip'I do start GRIP from RobotInit as specified: Code:
/* Run GRIP in a new process */I also made sure the CameraServer is not running. I'm GUESSING that the camera isn't sending any images to the first pipeline stage (resize)... but there's insufficient debug info in the log to tell me what might be wrong. I checked that the GRIP file is using device 0, and this matches what is in the RIO dashboard (which says "cam0"). Thoughts? -Scott |
Re: GRIP with USB Camera
Quote:
One this I would recommend trying out is the v1.3 release candidate 1. The only thing it changes about cameras is that they now try to restart if they don't work the first time. The problem might be as simple as cameras not connecting the first time because they're initializing or something weird. Let me know if this helps. |
Re: GRIP with USB Camera
Quote:
|
Re: GRIP with USB Camera
Thanks, Tom! I'll try installing that tonight.
BTW, we are finishing our build season in the WPI pits (since we don't have access to Burncoat HS during winter vacation)... so we will be on campus tonight from 6-10 if you happen to be around and want to see an instance of this issue "live". My email is s-taylor@att.net if you want to contact me outside of this thread. |
Re: GRIP with USB Camera
Dumb question, but the only pre-built releases for 1.3.rc1 are x86_64b. What do I need to do differently on my laptop in order to deploy it to the RIO and its ARM processor? (32-bit/arm flags, for example)? or other special compile flags?
|
Re: GRIP with USB Camera
Quote:
|
| All times are GMT -5. The time now is 01:31. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi