Quote:
Originally Posted by mlbernardoni
I don't know what overhead Labview puts on the program. But every student who drives the robot will tell you that there is a big difference, and it was obvious from watching the robot drive.
Same robot, same CRIO, same communications, official 2013 versions of labview and windriver, both very simple programs (1 joystick to 1 motor etc.). The only way to put it, moving the joysick to motor movement on the robot, c++ is much more responsive.
|
Having seen LabVIEW used for very precise control by many teams over many years, I'm not convinced that your experience indicates anything about LabVIEW in general. If you can post your simple programs, I'd like to see if you've done anything that might be causing the LabVIEW one to misbehave. (For example, there could be some simple error in your code which results in a cascade of diagnostic messages to the Driver Station, and those messages are quite capable of interfering with timely communication and control.)