View Single Post
  #8   Spotlight this post!  
Unread 23-01-2013, 14:47
Orion.DeYoe Orion.DeYoe is offline
Registered User
FRC #5413 (Stellar Robotics)
Team Role: Mentor
 
Join Date: Feb 2012
Rookie Year: 2011
Location: North Fairfield, OH
Posts: 206
Orion.DeYoe is a splendid one to beholdOrion.DeYoe is a splendid one to beholdOrion.DeYoe is a splendid one to beholdOrion.DeYoe is a splendid one to beholdOrion.DeYoe is a splendid one to beholdOrion.DeYoe is a splendid one to beholdOrion.DeYoe is a splendid one to beholdOrion.DeYoe is a splendid one to behold
Re: Image processing

Quote:
Originally Posted by matthewgkerr View Post
I have had a look through the forums on the image processing topic trying to work out if we should process images on or off the cRIO. For starters, I would be looking at processing the images on the driver station; probably on an upgraded laptop from the one that comes with the rookie kit. As a rookie team, would the veteran teams recommend one direction over the other. My current thinking is removing the image processing from the cRIO will make for simpler robot code. Any thoughts or suggestions would be appreciated.
In the past vision processing has mostly been done completely on the robot. Last year doing the tracking on the driver station laptop became really popular. Our team did our tracking on the driver station last year and this year we've made improvements and are tracking on the laptop again. It's driving the robot and working 10 times better than when we tracked on the robot.
One thing we had trouble with was getting the "target data" array to the robot. We ended up using a DCP port (port 1130) to send the array to the cRio. I have attached the two VIs we used (I downloaded them from another thread). You'll use the "DCP Send.vi" in the dashboard program, and you'll use "DCP Receive.vi" on the robot.

I hope this helps!
Attached Files
File Type: vi UDP Receive.vi (6.7 KB, 6 views)
File Type: vi UDP Send.vi (6.9 KB, 4 views)