01-31-2011 03:14 PM
Last year there were a lot of problems with running robot using the camera, lag and TCP errors. I know teams created new dash boards to eliminate some controls. I read the dash board tutorials, I still need a little assistance.
If I want to just use camera for image feedback, no processing, and some large digital input Boolean LEDs, what will I have to do to have minimal data fed back that will cause lag or errors? In main code, do I need to eliminate any code if I am feeding back on image for students display, no image processing.
The tutorial indicated an alternate way to send data to dash board is modifying the DashboardEnalbles.ctl. Is this the better way to minimize data flow from Robot? I assume this is the front panel? I do not see this control in project window.
I had a reply do just start deleting controls and dash board code, run test each time. I believe there should be a better way.
To add large Boolean LEDs, do I run code similar to gyro dash exercise.
There must be more documentation and support, the tutorials did not explain how to create a dashboard executable.
Your help will be greatly appreciated
02-01-2011 03:21 PM
Have you had a chance to look at the Tutorials linked to the LabVIEW Getting Started window? Tutorials 6 and 7 will help you modify your Dashboard project. If you want to eliminate image processing, you would do that in the code you deploy and run on the robot. The image data is not processed in the Dashboard. The rest of the data (non-image data) comes from the Driver Station.
As for building the executable, from the Dashboard LabVIEW project, look to the bottom for Build Specifications. Expand that section, right-click FRC PC Dashboard and select Build.
Let me know if you need more information on this.
Take care!
Tanya V