Camera IP doesn't stick

[ehlochbr]

I've been having problems with the camera and thought I had fixed it tonight, but I'm not quite there and could use advice.

I used the 2012 setup program for the camera and set it up so that the camera gets plugged into the radio instead of the cRIO. After doing this it looks like it works (I can see an image on the dashboard). But when I do a hard reset on the robot the camera goes away and never comes back. In order to get an image again on the dashboard I have to go through the whole setup process again with the setup program.

If I use the setup program to set up the camera so that it plugs into the cRIO, it never works.

Any ideas? Thanks.

[SuperS_5]

You are going to have to list the steps that you go through.
A forgetful cRIO is not a new problem, but more details will help.

About the second Ethernet port:
The first thing I can think of is the Boolean on the BD of the Begin.vi. It controls the IP address where to look for the camera. I believe true is to use the bridge, and false is to use the older method of the second port. Of course the camera would have to be set to that IP address if you chose to use the second port.

[Mark McLeod]

In addition to the cRIO program modification Mike mentioned, if you move the camera to the 2nd cRIO port it still won't be visible on the default Dashboard. Default is programmed to assume the camera is connected to the bridge at a particular IP address.

To see the camera image on the Dashboard while the camera is connected directly to the cRIO it's necessary to create a new Dashboard project and change how the camera image is retrieved.

For the other problem, where the camera image never comes back after cycling the power on the robot:
= Is the light ring on the camera green?
= I'd see if you could web browser to the camera at either of the two potential IP addresses just to see where it's at
= See if cycling just the camera power causes the camera to drop out, too. That would isolate interaction with the bridge as a potential cause.

[RufflesRidge]

Have you tried restarting the Dashboard after resetting the robot to see if the image shows up then?

[ehlochbr]

Yes, I have tried to restart the dashboard after cycling the robot and it doesn't help.

After power cycling the robot the camera comes back with orange light ring around the lens (it was green before cycling while it was working).

What do you mean by the BD in the begin.vi? Thanks

[ehlochbr]

After more digging, the problem is a communication problem. For some reason, in the HTTP Authentication.vi (which is about 8 or 9 levels down)an error gets generated by the TCP/IP.vi. I just don't know why i only get an error when I reboot the robot. If I resetup the camera it works until the robot is power cycled.

[SuperS_5]

BD= block diagram

[Cjdowney]

I'm having the same issue here, was able to ping 10.te.am.11 (not sure if that helps), but not able to bring up a webpage connected to it. If I reset it and start over it will work fine until a hard reset is done.

[Greg McKaskle]

You don't mention an error code, but this sounds a bit like an issue I've seen when I swapped cameras that had the same IP address, but certainly different MAC addresses. I don't remember the error code, but ran across it when testing the exact restart situations you seem to be seeing.

I just tested cycling power to various components using the installed DS and cannot reproduce the issue with the 206 camera. My setup is that I have the camera and computer plugged into the switch, and I've cycled the camera alone, the switch alone, and both simultaneously, and after the camera LEDs turn green, my image returns each time.

Can you describe any difference that I'm not testing?

Greg McKaskle

[RufflesRidge]

Originally Posted by Greg McKaskle

Can you describe any difference that I'm not testing?

Greg McKaskle

Was your camera set up with the automated tool? I won't be with a team that uses the 206 until Monday, but base don the posts here on CD I'm worried the tool is setting something up incorrectly.

[Cjdowney]

I'm not getting the problem anymore (or at least not at the moment). What I did was manually set the ip rather than using the labview tool. Maybe give that a try and see if it fixes it for you also.

[Greg McKaskle]

I believe it was. I'll reset it and test again.

OK. I reset and ran the tool on the 206. When I power cycle the camera, it never turns the LEDs green. I suspect this means it factory reset on power up. My normal advice would be to make sure the mounting of the camera doesn't hit the reset button, but since it is my advice, ...

Anyway, I agree that something seems rotten with the new camera config utility. I'll see if I have the source. In the meantime, if you are seeing this issue, I'd recommend hand configuring

1. Factory reset the camera.
2. Set computer IP to 192.168.0.xx where xx is not 90.
3. Launch web browser and enter 192.168.0.90 into the URL.
4. The camera will ask you to set the root password. Use admin or whatever you like.
5. It will ask you to log into the camera (root:admin).
6. Click on the Setup tab.
7. Click on the Users link on the left.
8. Add (FRC:FRC) as an administrator.
9. Switch to the TCP link and set the IP to manual 10.te.am.11 and I set the router to 10.te.am.01.
10. Change computer IP back to 10.te.am.xx and go about your way.

Thanks for the specifics in reproducing this. I'll look into it a bit or get the author to look into it on Monday.

Greg McKaskle

[RufflesRidge]

Thanks for checking that out Greg! That should save me some time on Monday, I'll jump right to doing the config manually.

[ehlochbr]

Thanks for the tips!!!

I'll try this out this afternoon and post the results. This has been really helpful. I'm excited to try it!