Introduction - I have a motor that speed is controled by the throttle. I have it hooked up to a global vartiable and i tired to add it in to the dashboard, but it just reads 0. I made sure im reading and writing them correctly.
Question - Is there a extra step that needs to be taken?
The robot and the Dashboard are separate programs running on separate computers. In order for the Dashboard to display a value from the robot, you will need to send that value from the robot through the “high priority” dashboard data stream, and retrieve it in the Dashboard.
Instructions for doing this are in Tutorial 7—Integrating Examples into Robot Code.
Steve, I hope you are Ok if add to your question…
I did the tutorial Alan suggest, worked fine. I would like to eliminate some info/controls not to dash, TCP error night mares in past…
When I delete Analog/ Digital on dash, of course get errors in code, need clean up.
Alan - others
Can I just delete control and try and eliminate errors in VI until they are gone,
or is there a better method? Do not want to create problems by trying to prevent them, want limited info sent back if not needed.
thanx
mark
To limit info sent back if not needed, you will have to modify the Dashboard Data Type Def on both the send (cRIO) and receive (dashboard) side. Plus all the code now that does not match (errors) just to save a dozen or so bytes.
NOT worth the time and head ache and possible data mis-match you are sure to introduce.
It is only a total of 97 bytes. Even if you make it smaller, it most likely will still be sent in the data packet of the same size with most of the packet made up of zeros.
Hi Omar
2 years ago had a lot of TCP errors during match, most teams said they had to modify the dashboard code to send nothing back to eliminate these errors?
Also, need more room on dashboard for other indicators for drivers, can hide controls to make more room? having trouble increasing size of dash, not using class mate as driver station, have a bigger screen laptop
thanx
Mark
One of the first modifications our programming team made to the Dashboard was to add a large tab control to the right and put all the existing “debug” indicators in a tab named “raw info”. All the really useful custom indicators are in the tab named “game info”. Everything that was there in the default dashboard is tucked neatly out of sight, but is only a mouse click away when necessary.
I have found an excellent tutorial, http://www.thesciencedude.com/teaching/1208/Resources/Programming%20in%20LabVIEW/Dashboard%20Tutorial.pdf
I have found a tutorial on exactly what i wanted thanks.
I have never seen or had a report filed about dashboard not working on the field. There tends to be lots of helpful advice about deleting code or working around the field. I find that most of it is well-intentioned, but misleading. For example, – “I’ve heard that having your driver stand with their legs crossed will speed up the communication between the robot and the field – something to do with their body acting as an antennae and crossing the legs working like a twisted pair cable … anyway, everybody is doing it!”. Feel free to try it, but pay attention to the source, and when possible, test the statements for yourself.
Greg McKaskle