|
Re: Which programming language does your team use?
That is the point, the programs were very simple and as close to identical as we could possibly program using Labview and C++ FRC required libraries.
We use Victors, all classes in the labview program are based upon the victor motor control block and all classes in C++ are based on the Victor base class in the WPI C++ library. (The victors on the robot go all the way from Red to Green, full power range with each program.)
The CRIO speed is what is set in the WPI base classes. We did not program for that with either C++ or Labview. (As I said, very simple programs using the foundations supplied by FRC and WPI.)
We used the same iterations per second in our C++ code as Labview uses.
Labview was completely compiled and downloaded to the CRIO, no extra communications. And we did not see any errors while running these simple programs.
We did not measure the CPU load, but I find it hard to believe the CPU was pegged with such a simple program.
But I agree with your objection, it comes down to the compiled code on the CPU. I do not know what overhead Labview adds (or for that mater the WPI library), but it is very noticeable on our robot.
We had 2 very very simple programs using the FRC required foundation for C++ and Labview.
As for teams not noticing any lag. Neither did we for the past 5 years. We are not saying that there is any error in Labview. We have successfully used Labview for years. And I will say we have had very complex programs that functioned very well.
|