Thread: Routing Camera output via the cRIO
View Single Post
  #1   Spotlight this post!  
Unread 02-10-2010, 01:16 PM
taichichuan's Avatar
taichichuan taichichuan is offline
Software Mentor
AKA: Mike Anderson
FRC #0116 (Epsilon Delta)
Team Role: Mentor
  
Join Date: Feb 2010
Rookie Year: 2010
Location: Herndon, VA
Posts: 328
taichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud oftaichichuan has much to be proud of
Send a message via AIM to taichichuan
Exclamation Routing Camera output via the cRIO
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
Reply With Quote