Thread: cRIO networking
View Single Post
  #2   Spotlight this post!  
Unread 10-05-2010, 15:30
apalrd's Avatar
apalrd apalrd is offline
More Torque!
AKA: Andrew Palardy (Most people call me Palardy)
VRC #3333
Team Role: College Student
 
Join Date: Mar 2009
Rookie Year: 2009
Location: Auburn Hills, MI
Posts: 1,347
apalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond reputeapalrd has a reputation beyond repute
Re: cRIO networking

Port 1 is 10.xx.yy.2. You cannot change that
Port 2 is 192.168.1.1? You cannot change that either.

You can run a proxy.
If you are using the network cam, its IP is 192.168.1.90 so the cRio's port2 address makes sense.
Are you trying to forward camera images to the dashboard without overloading the cRio?
Are you using LabVIEW? If you open the ethernet cam in LV, set framerate and size and other options you want, and then stop (don't even save a refnum), and delete all vision code, it wont make a big impact on CPU speed (not any less then proxying the camera).
__________________
Kettering University - Computer Engineering
Kettering Motorsports
Williams International - Commercial Engines - Controls and Accessories
FRC 33 - The Killer Bees - 2009-2012 Student, 2013-2014 Advisor
VEX IQ 3333 - The Bumble Bees - 2014+ Mentor

"Sometimes, the elegant implementation is a function. Not a method. Not a class. Not a framework. Just a function." ~ John Carmack