2010 Camera and vision problems.

[1jbinder]

Reinstalling worked for us!!!!
Thanks guys,
Julian

[ranc]

Originally Posted by 1jbinder

Reinstalling worked for us!!!!
Thanks guys,
Julian

Did you reinstall Windriver? or the driver station update?

[Bigcheese]

I finally got camera output + target data on the dashboard. The problem was indeed the drivers station update.

Here's how to fix it:

1. Download the drivers station update: http://joule.ni.com/nidu/cds/view/p/lang/en/id/1535
2. Run the drivers station update and install.
3. Run the drivers station update and select remove for both components.
4. Run the drivers station update and install.

This fixes it. NI needs to fix the installer.

[DanDon]

Originally Posted by Bigcheese

I finally got camera output + target data on the dashboard. The problem was indeed the drivers station update.

Here's how to fix it:

1. Download the drivers station update: http://joule.ni.com/nidu/cds/view/p/lang/en/id/1535
2. Run the drivers station update and install.
3. Run the drivers station update and select remove for both components.
4. Run the drivers station update and install.

This fixes it. NI needs to fix the installer.

I was just about to post this. Exactly what I had to do to fix the problem.

I also have the camera tracking the target on a pan/tilt assembly .

[tekman1001]

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

[DanDon]

Originally Posted by tekman1001

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

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

ping "host address",numPackets

or

ping "192.168.0.90",10

for a 10 packet ping.

[dag0620]

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.

[TPNigl]

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?

[s133p]

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!

[mobilegamer999]

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?

[ranc]

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?

[Michael DiRamio]

Originally Posted by ranc

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?

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.

[umangv620]

Has anyone gotten the Camera running in LabView?

[jerry w]

Originally Posted by umangv620

Has anyone gotten the Camera running in LabView?

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.
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.