Quote:
Originally Posted by tutkows1
I suggest having a larger video screen, and having a space were messages from the programmer can show up. For example, you are now cocked at position three. Having a pressure gauge is also a good idea.
On a side note: were did you find a gauge that can send the air pressure as an analog signal to the control system?
Edit: More about what we did.
Last year my team didn't use the classmate for the dashboard, we sent it to another computer so we could have a larger screen and it seemed to run the feed better.
|
@tutkows1
Our Robot has an analog pressure sensor on it hooked into one of the analog imputs on cRios. We played around with the data communication and have a guage on our large video screen with the air pressure. I think that the while loop on the dashboard has a slow iteration rate however, because it is quite slow responding, about 1-1.5 seconds per responce, hardly real-time.. But we might consider putting dashboard onto another computer. Did the program run faster on a different laptop than it did on classmate?