Re: 2010 Camera and vision problems.
 

Does anyone know if you should be able to ping the camera @ 192.168.0.90 from the driver station. Thanks

Re: 2010 Camera and vision problems.
 

Not from the DS, but rather from a terminal connecting to the cRio. Either through NetConsole, or through Windriver, etc.

The syntax for the VxWorks ping command is

or

for a 10 packet ping.

Re: 2010 Camera and vision problems.
 

Somehow, it still doesn't work for my team. We tried reinstalling the driver station update and the dashboard reverted to the newer update. However, it still refuses to show an image or return data. Is it necessary to change the camera settings through the given program?

Re: 2010 Camera and vision problems.
 

Have you tried using one of the other development environments to see if the issue is with the camera setup or with C++?

We have been unable to get the camera sending the camera information using C++ (seems to hang during the camera initialization) but have it running successfully in both Java and LabVIEW.

Re: 2010 Camera and vision problems.
 

Has anyone gotten the Camera running in LabView?

Re: 2010 Camera and vision problems.
 

364 is having trouble with theirs. Actually, it sounds like an exact repeat of the problems your team was having.

I don't know the details, but basically the ethernet port lights are off. We've tried a few crossover cables, but none of them are working. The camera works connected to a laptop, and the port works when we connect the router to port 2, so neither the camera or the cRio seems to be broken.

I know we've updated the LabView software and the Dashboard software. The Dashboard update didn't work, so we tried it again, and got it to work.

The last thing I know of is that the cRio is not responding to the Dashboard or something anymore. Something about the Watchdog is stopping.

Anyway, don't quote me on the problems as I wasn't the one messing with it, but I wanted to add another team to the list.

I think we tried everything here. I know this thread was up on the projector the whole time while the programming team tried to sort it out.

Re: 2010 Camera and vision problems.
 

I am the chief programmer for 364. We have tried all of the suggestions we could find on this post, but we are still having issues. All of the information that Ryan posted is pretty accurate. I tried uninstalling and reinstalling the DS update, but that still didn't solve anything. We are particularly interested in the fact that it seems that the ethernet port on the cRIO doesn't seem to communicate with the camera at all, but we can still communicate with when the camera is connected strait up to a laptop. The error messages in the diagnostics window say that we are experiencing a "44003" error, and the watchdog is cutting out. We can control motors and get feedback, so I know that the dashboard is communicating with the cRIO.

Re: 2010 Camera and vision problems.
 

We are getting the same error.
I cannot test this till monday, but you might wanna try post 6 of this thread
Hopefully reinstalling the DS update will work, but if it doesnt, this might(post 3)

Re: 2010 Camera and vision problems.
 

I am pleased to report that the out of the box FRC labview code gives us a camera image. Originally, we had two crossover cables in series. :p
when we discovered the problem, the single crossover in series with a normal cable worked just fine. We are painting the target now. By noon tomorrow we hope to have target images.

We have had much experience with setting IP addresses on computers. This is the most likely cause of a system to fail to get an image. I have to threaten students with bodily harm if they try to do wireless before testing with wired LAN. The wireless stuff loves to do its own thing. After we had wired connections successfully, then we did the wireless.

Re: 2010 Camera and vision problems.
 

I am quite excited about the hopefully better camera workings this year. Wether or we get the target tracking working this year is an anserw i won't know until shipping date, but we intend to use it for tele-opp. On the intial testing of the camera, the vetrans were able to get it to work perfectly fine, however there was a slight delay. I wanted to see if anyone found a way to fix the lag, or are we stuck waiting a few seconds to get the images back. - If the lag is un-fixable, I am interested to see how the drive-teams get around that little obstacle.

Re: 2010 Camera and vision problems.
 

We're programming in java and we got the camera hooked up to the cRIO and Dashboard. It recognized the camera by saying "camera running e". However there was no image being fed to the dashboard. The dashboard has already been fixed and the v19 update has already been made. Any suggestions?

Re: 2010 Camera and vision problems.
 

Just a last small update from us, everything seems to be working after trying the uninstall re-install that was recommended. Thank you all for the help!

Re: 2010 Camera and vision problems.
 

I'm a programmer for rookie team 3357 and we are programming in Java.

When ever we initialize the camera (AxisCamera.getInstance();) our code NEVER works. It displays "Watchdog not fed" and "no robot code". It also hangs on that line. We have updated our drivers station to v19 and done all of the other necessary updates.

Any suggestions?

Re: 2010 Camera and vision problems.
 

From above:

Which camera to dashboard program are you using?
The "Camera to Dashboard" example program does not work to my knowledge. Either build the "FRC 2010 Vision Demonstration" program, or add this to your robot's main code:


Could you direct me to the "FRC 2010 Vision Demonstration" program mentioned above? We are having issues getting our camera working as well with C++.

-Ted Dressel, Mentor, Team 1111

2010 Camera and Vision Attempted Setup Summary
 

************************************************** ****************************************
**EDIT: PLEASE DON'T REFER TO THIS. REFER TO POST #68 INSTEAD. THERE IS INCORRECT INFORMATION BELOW!**
************************************************** ****************************************

Hi Guys,

Since there’s a wealth of information located in this thread I’m going to try to summarize the steps for getting a working camera setup for C++ (this may still be helpful for those using the other platforms as well). This summary assumes that code can be loaded on the cRio and run. This is specifically for the 2010 Vision Demonstration example.

1. cRio must be reflashed with v19 image.
2. WindRiver should be intstalled with the WPI Lib update (WorkbenchUpdate20100107.exe). Did anyone have to uninstall WindRiver first?
3. The camera should be set up with IP address 192.168.0.90 (which is the default) and a username and password of “root” and “admin” respectively (admin is NOT the default). I understand there are other valid usernames and password combinations as well.
4. The camera should be connected via CROSSOVER cable to Ethernet port 2 on the cRio and adequate power supplied.
5. The driver’s station update should be installed (DSUpdate1.0for2010.zip). This requires installing BOTH components, uninstalling BOTH components and then reinstalling BOTH components again. Apparently the NI loader has issues. ::ouch::
6. Add the “2010 Vision Demonstration Program” to the current workspace and compile. (In WindRiver click File -> New -> Example… -> VxWorks Downloadable Kernel Module Sample Project -> FRC 2010 Vision Demonstration Program -> Finish.) Be sure to use the correct compiled cRio image path located in the FIRST Downloader Preferences section of “Preferences” (Located under Window).
7. Deploy the code. And watch it work!

From the information I can glean from this thread, this should work (and pan and tilt maybe as well if you hook up some servos – my goal is just to get some images first).

Now at this point, us SPAM guys haven’t been able to get it to work (camera/cable work with a computer, but not the cRio), but we didn’t uninstall BOTH of the driver’s station components last night. I’m thinking of just starting from scratch on all of this, so the above is somewhat speculative. Please feel free to make comments or suggestions for additions to the above steps. I know a many people have been going through the same frustrations and I’m trying to alleviate some of the pain. Hope this helps someone!

- Bryce