Hi guys-
We have 2 Axis Cameras this year, one connected through the bridge to the cRIO for image processing, and we plan on using the other one for a live stream for driving assistance.
How do we set this up, so even if the cRIO isn’t powered we could still view the stream in the driver station?
Put one camera on 10.17.71.11
The other on 10.17.71.12
Plug both into the DLink.
Devise a way to give both 5v power feeds on the robot.
Create a Dashboard project and change the camera IP address to 10.17.71.12
If you want both cameras displayed on the Dashboard, then you can duplicate the code for the original camera and change that IP address to the 2nd camera.
One camera with the .11 address is all you need to give you all these features. The live stream on your dashboard is independent of the crio.
BTW, you can have a batch script that runs when the classmate logs in that pulls up internet explorer. Then just set the homepage to the webcam that you want to use for drive.
If the cameras are in the same position you are much better off just using one and piping the results back to the driver station after processing, as said in the post above.
Be weary of port rules. There are a couple of threads explaining odd network setups and rules that follow. Also the camera takes up a lot of bandwitdth…
Thanks, I set the IP to be 10.17.71.12, with a default gateway of 255.255.255.0 One other field it asked for was the default router- it was originally 192.168.0.1, so I set it to be 10.17.71.1, would that be correct?
Also, we don’t know LabView very much, (we can open the program and pull up an example), how do you change the value on the camera dashboard?
Thanks!
To modify the dashboard, launch LabVIEW and on the intro screen, choose to make a dashboard from the template. After it opens, you can add any indicators you like including duplicating the vision display and the loop that reads the second camera. You also need to update the IP for the second loop.
Greg McKaskle
Hard to describe if you don’t even know the basics of how to wire in LabVIEW.
[ol]
[li]Create a Dashboard project[/li][li]Open the Dashboard Main.vi block diagram[/li][li]The camera section is in the middle with a vi called Camera-Read MJPG[/li][li]There is a pink wire going into that vi holding the camera address[LIST=1][/li][li]Double-click on the wire and delete it[/li][li]Position your cursor over the vi’s input node for “address”[/li][li]right-click and choose Create -> Constant[/li][li]You should get a box that says 10.te.am.11[/li][li]Change that to 10.17.71.12[/ol][/li][li]Now comes the tricky part creating a new Dashboard[ol][/li][li]Go back to the Project Explorer window[/li][li]At the bottom you’ll see Build Specifications[/li][li]Expand that and you’ll see FRC PC Dashboard[/li][li]Right-click and choose Properties[LIST=1][/li][li]Either remember where the Destination Directory is so you can try out your Dashboard afterwards, or change the path to the default location of the FRC Dashboard.[/li][li]Changing it is a little backwards,[LIST=1][/li][li]Browse to the Dashboard default location on your local disk C:\Program Files\FRC Dashboard (may be Program Files (x86) )[/li][li]You will have to enter an “x” as the file name once you get to the proper folder[/li][li]Back at the Properties screen edit the path directly to remove the x from the directory path[/li][li]Click OK[/ol][/LIST][/li][li]Back at Build Specifications you should be able to right-click and Build[/li][*]Restart your Dashboard to see if you got it[/LIST][/LIST]
Are your cameras pointed in different directions? I assume that is the only reason to have more than 1.
yes one is for tracking one for driving, pointed in different directions. don’t want to load up the c-rio with the driving camera.
A simple way to do this is to just navigate to the IP of the camera (10.17.71.12) in your browser.
Last year, we did this at the last minute for the camera aiming the minibot, and for aiming the minibot launcher, we just stuck a piece of black electrical tape on the computer monitor for aiming.
I’m pretty sure the gateway should be 255.0.0.0. That’s what we set all of our development machines to. Also, which camera did you set to 10.17.71.12? I recommend you use the tracker camera for that IP address because 10.17.71.11 automatically goes to the default dashboard without any configuration. Don’t forget that you need two AxisCamera objects in your code, and that if you’re not using the default IP address for your camera, you need to pass that IP address to the AxisCamera.getInstance or AxisCamera::GetInstance method/function.