Camera not Sending to Dashboard

[DjMaddius]

Originally Posted by RufflesRidge

I just re-read your first post an saw Crossover cable. I'm not sure if the robot radio has auto sensing ports (allowing a crossover to work), but you theoretically should be using a patch cable, not a crossover.

What I would try is set up the camera with the tool, and leave it plugged into the PC. Change your PC IP to 10.xx.yy.5, open a browser and go to 10.xx.yy.11 Username: FRC Password: FRC. This is the configuration the Dashboard is expecting. If that works, then try moving it over to the switch.

We can get to this. Once power is removed and put back on it no longer works :/

[Greg McKaskle]

To review, there are multiple ways to configure and use the camera.

By default, the dashboard expects the camera at 10.te.am.11. To change the IP to something else, rebuild the dashboard from source. This configuration supports reading the camera form both dashboard and robot. This is the recommended configuration.

If you prefer and have an 8 slot, you can use the setup above, or you can use port 2 on the cRIO. If using port 2, set the camera IP address to 192.168.0.90, set the camera IP in Begin or in the constructor, and change the dashboard to use the retransmitted image server.

Greg McKaskle

[DjMaddius]

Alrighty well we have gotten down to the point where everytime I plug it into my desktop I can connect to its web server just fine and it displays the image. But labview and the crio don't see the image.

I have setup two accounts on it. user root password admin and user FRC password FRC. Is there anything else I should be doing?

[ebarker]

Originally Posted by DjMaddius

We can get to this. Once power is removed and put back on it no longer works :/

This is precisely the problem we are having. We have gone through two cameras. We can configure them and then connect to the dashboard fine.

We we remove power and turn the camera back on again, the camera has lost the IP address.

???

[RufflesRidge]

Originally Posted by ebarker

This is precisely the problem we are having. We have gone through two cameras. We can configure them and then connect to the dashboard fine.

We we remove power and turn the camera back on again, the camera has lost the IP address.

???

Is this an Axis 206 or M1011?

[DjMaddius]

Ours is the 206
EDIT::
Tomorrow morning I will pull up last years manual configuration guide and go through it. If that work's then we will have found a solution.

EDIT2::
http://minus.com/mbwXSo0OH#1

Here is a copy of the PDF for configuring it last year in case anyone would like to do the same as me.

EDIT3::
I think the difference from this years configuration and last years is the FRC user. I didn't have it added last year. Just the root user. Possibly that's the reason I'm having issues. I'll try removing the FRC user tomorrow and see if then it works. Possibly trying both accounts and causing an issue somewhere. Hmm.

[Greg McKaskle]

The FRC FRC account shouldn't hurt anything, and in fact, it is the credentials that LV uses first. I don't know the details for C++ or Java. If you delete it, LV and possibly the others will fail the connection several times before succeeding.

Please describe the camera IP, cRIO IP, and DS/development computer IP and how they are networked (what ports, etc).

I typically use a 4 slot, but if I use an 8, I connect port 1 to the dlink. Port 2 is unused. Then I connect everything else into the dlink using standard patch cables. I can then run the DS & DB and it work. I can run Vision Assistant if I want, and I can run LV examples on the computer or the cRIO and they work.

Greg McKaskle

[DjMaddius]

Alright, We had finally got it working. What we had done to get it to work is created a new dashboard in LabVIEW. I added a cameraIP output (like the robot IP output) and then it worked. Yet, the default dashboard still doesn't work. Here is a copy of the dashboard I built:
http://minus.com/mR2lE91ir#1
Sources are also on that page.


EDIT::
Also, I manually configured the camera to its static ip 10.xx.yy.11 like the config software should. Not sure if this made a difference or not. Made the default gateway 10.xx.yy.1