View Single Post
  #3   Spotlight this post!  
Unread 25-09-2013, 08:50
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: Dual Cameras - Dual Purposes

Sending the image to the cRIO every 100ms is step one, displaying on on dashboard is step two, correct?

To send any data you like from any processor on the robot to the cRIO, I'd open up a socket, or use TCP or UDP. It sounds like this is already underway.

To send data from any processor on the robot to the DS is pretty much the same, but you need to ensure that you used ports compatible with FMS setup. The FMS blocks most ports and a select few are left open for exactly this sort of communication. Again, use TCP or sockets. The modification to the Dashboard will be very similar to the code on the robot. Read the image from the correct port and IP. Depending on the format of the image, I'd probably try to convert it to an IMAQ image. The WPI functions do this internally for JPEGs, and it is possible to hand over an array of pixel data and IMAQ will use it for the image data. Then you use the normal dashboard image control and write to the terminal. I've done three camera images at once before, and it works fine as long as the laptop can keep up with the decompression overhead.

I don't think language choice has much to do with this, and if you have more detailed questions, please ask. Or get the programmer to ask directly.

Greg McKaskle
Reply With Quote