View Single Post
  #3   Spotlight this post!  
Unread 13-01-2016, 06:33
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Camera image and Network Tables

Yes, you don't really want or need to put entire images into network tables.

The dashboard and LV framework code support a number of ways to get images from robot to dashboard.

If using an Axis IP camera, configure it,plug it into the robot radio, and on the dashboard choose IP on the camera selector. The communication is direct between dashboard and camera and the roboRIO isn't even involved.

If using a USB camera, plug it into the roboRIO and choose between the USB SW or USB HW. Both should work, and the primary difference is the configurability and CPU usage tradeoff.

If you then want to process images on the roboRIO, the Vision Processing VI can be modified to also request images from the camera and process them. The resulting data, likely coordinates, distance, etc. are the type of data you'd want to send through network tables.

Greg McKaskle
Reply With Quote