Quote:
Originally Posted by Greg McKaskle
That dashboard with the overlays was probably the default one written in LV.
|
I am not sure I get what you said. Did you say the default Dashboard written in LabView does or does not support overlay? In other words, can we use that Dashboard unmodified or do we need to crack the LabView code and modify it to support rectangular target overlay? I hope we don't have to modify it because we don't really know LabView that well and we don't even have LabView installed. The credit card USB memory thingy disappeared after passing around between the programming students, and everyone denied they have it
.
Quote:
Originally Posted by Greg McKaskle
The Rectangular Target Processing example has some annotation code you can place into your dashboard. It is in the RT code, but turned off, and it defaults to being on for the My Computer version of the code.
It takes in the bounding box, scores, and other values, but you can easily strip out numbers and other code if you wish.
|
Where can I find this Rectangular Target Processing example? I looked at the VisionSample2012 project and that's not it.
Quote:
Originally Posted by Greg McKaskle
The key will be getting the data needed for the overlay from the robot back to the dashboard. The WPI libraries contain tools for this. And you will then need to extract the data in the dashboard and hook it to the overlay functions. If you look at the dashboard code from a couple years ago, this was done the same way, just in the default code.
|
My understanding is that Dashboard Packer code in the WPI library is packaging data to send to the Dashboard. So the key is to understand if the Dashboard has code to expect array of target data and what format should the data be in? When you say "extract the data in the dashboard and hook it to the overlay functions", it sounds like this is modifying the LV code in the Dashboard, right?