Still no camera feed

[cappielloa]

So, after a week and a half, I have still been unable to get any response from the camera on the robot. I have been meticulously following the "2010 Camera and vision problems" thread, but to no avail. I am using Windriver to program.

First off, I'll let you know everything that I have done. Initially, I tried to incorporate the camera code into an existing program, but now I'm just trying to get "2010imagedemo" to work. I have installed all of the updates and I am sure that the driver station has updated. I have updated the cRIO image and run the camera setup tool, verifying that the FRC account is there and that I can get a feed while connected directly to the computer. All of this has been done from both the classmate PC and our old programming laptop (even running it as the driver station). And to clear up any other confusion, it is connected to port 2 with a crossover cable and gray button on the driver station to enabled the camera feed is ticked.

The code builds fine and loads onto the robot. I then get the "watchdog not fed" message along with an error in the 'Diagnostics' tab:
"Fatal error "Task error: Task already deleted." in HandleError() in C:/Windriver/workspace/WPILib/Task.cpp at line 188"
Note that no such file exists. Everything sits unresponsive for about a minute, then the watchdog error goes away and I can resume teleoperated, just with no camera feed.

Thanks for any help.

[Mr. Lim]

Cappielloa,

We've run into the same issue here as well. Pretty much the exact error, when attempting to use the 2010 demonstration code. We applied all the updates, including uninstalling and installing the Driver Update.

[Mr. Lim]

Can you verify that your console is showing a "s_errno_EHOSTUNREACH" error?

We've logged into the cRIO using the Console Shell, and attempted to ping 192.168.0.90 using the following command:

ping "192.168.0.90",4

The pings were NOT successful.

Shouldn't we be able to ping the camera through the cRIO Console Shell?

[Mr. Lim]

We "fixed" our problem tonight after experiencing the exact same issues as the OP.

It turns out, all our prior attempts to update the cRIO image to v19 failed, and we were running and older image on the cRIO.

After reimaging the cRIO with v19, we were able to get the DriverStation to view the camera feed, and our WatchDog not fed errors disappeared. We were only able to do this after DOWNLOADING the code however. We still have not been successful in getting camera frames in debug mode. It also takes a long time for the camera feed to start after powering on the robot, and one has to be patient enough to not enable the robot while the camera feed is being established.

[cappielloa]

Thanks for the suggestions. I'll try updating the cRIO again. The DS reports v19, but the imaging tool was giving me a lot of trouble and I had to restart it a few times. If that doesn't work, we're planning on testing another cRIO with it. It may be a few days, but I'll post again if I make any progress.

[Mr. Lim]

Originally Posted by cappielloa

Thanks for the suggestions. I'll try updating the cRIO again. The DS reports v19, but the imaging tool was giving me a lot of trouble and I had to restart it a few times. If that doesn't work, we're planning on testing another cRIO with it. It may be a few days, but I'll post again if I make any progress.

We had problems with the imaging tool as well. Ultimately, we ended up using the CLASSMATE the reimage the cRIO by directly connecting the two with the orange crossover cable from the camera. For some reason the reimaging tool kept throwing either a UDP communications error during cRIO reboot, or could not set the cRIO's IP address.

Also, although it's obvious, don't forget to check-off "format controller" and select the v19 image when you reimage.

Lastly, I would be really interested in knowing if BEFORE you reimage, if you can open a Target Tools -> Console SHELL in Wind River, and try a ping "192.168.0.90",4

If you had the same problem as us, those pings should fail.

However, the moment you successfully re-image, before you load any code, if you ping again, it should work.

[cappielloa]

Thanks. I'm pretty optimistic that reimaging will work. I'll let you know presumably on Monday how everything turns out.

Did your DS report v19 before you fixed it?

[Rolland0]

We're having the same problem over here. I'll let you guys know if we make any progress.

[ideasrule]

I was saying on another thread that I had to go to C:\Program Files and manually delete the folder with the driver station software, then reinstall the software, before the feed worked. Just uninstalling and reinstalling the update didn't work.

[Rolland0]

OK, our feed is working. I'm not really sure what did it but here's what we did:
1. deleted our current project and made a new 2010 Image Demo project
2. added an FRC account to the camera
3. ran the camera setup utility
4. reformatted the cRIO
After that, it was all good. If anyone has any ideas why this worked, I'd be glad to hear it.

[Mark McLeod]

If you never had an FRC/FRC account on the camera before, then the cRIO would have been refused login rights...