|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Greetings!
I've come across something related to the Axis camera that I thought I'd pass along. First, if you allow the Axis camera to get its IP address via DHCP, the default IP gateway is listed as 192.168.0.1. This gateway doesn't exist. So, camera output via a standard web browser will not be possible. Either fix the DHCP assignment on the cRIO or setup the Axis to use the 192.168.0.3 address of the cRIO as its gateway via a static IP assignment. Next comes the magic. On the cRIO, there is a special variable called "ipforwarding" that controls whether the cRIO forwards packets across the 2 Ethernets. Setting that variable to "1", enables IP forwarding. So from a VxWorks shell or via the cRIO console port: -> ipforwarding=1 will enable the ability to use a standard browser to see and monitor the camera video without the use of the dashboard. To make this permanent, you'll need to either create an application that sets that variable (remember it's an "extern") or add the ipforwarding=1 command to a script of some sort. HTH, Mike |
|
#2
|
||||
|
||||
|
Re: Routing Camera output via the cRIO
we need static routes in the driver station router also?
|
|
#3
|
||||
|
||||
|
Re: Routing Camera output via the cRIO
Yes, you'll need to add a route to the Classmate to be able to get to the Axis camera as well. In WinDoze from a DOS cmd box:
route add 192.168.0.0 mask 255.255.255.0 10.xx.yy.2 metric 3 -p The xx.yy is your team number e.g., Team 116 would be 10.1.16.2. The metric of 3 allows it to go through 3 hops to get to the camera. It's one more than you need, but this allows you to attach a secondary laptop to the Classmate via a USB Ethernet and display the output on the secondary PC. Since the Classmate appears to be having trouble keeping up with the video, this is a good option that is still within the rules. The final "-p" makes this route persistent across reboots. I.e., you won't have to enter this route again on the Classmate. HTH. |
|
#4
|
|||
|
|||
|
Re: Routing Camera output via the cRIO
Interesting - thanks for posting. Is this still valid for the 2015/2016 crio? We have a static IP address on our Axis camera and we would like to be able to connect to the web page of the camera from the driver station laptop while tethered with the USB.
Brent |
|
#5
|
||||
|
||||
|
Re: Routing Camera output via the cRIO
Please clarify if you are discussing the cRIO or the roboRIO as they (as well as the control system surrounding both components) are nothing alike.
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| crio dashboard GPIO output | darkorbit | Programming | 8 | 09-02-2010 15:29 |
| cRIO output problem | alex42 | FRC Control System | 1 | 27-01-2010 22:28 |
| cRIO output files | aoconnor | Programming | 2 | 09-02-2009 17:59 |
| Axis camera without the cRIO | CrazyCarl461 | NI LabVIEW | 12 | 17-01-2009 10:53 |
| moving via camera input | DanDon | Programming | 1 | 20-01-2005 20:12 |