Quote:
Originally Posted by Jared
Switching would likely fix the problem, but it's not a good solution.
The motion code I had is copy pasted from a project that ran perfectly on the cRIO - except I used Vectors instead of ArrayLists. There were no timing issues ever.
It's ironic that the fancy dual-core ARM controller running realtime linux and a newer version of Java has less accurate timing than a very outdated version of Java running on a system an order of magnitude less powerful.
|
The robot code does not run as a real time process. Nor does the standard JRE have real time support.
(That being said, I don't think C/C++ programs run as real time processes by default either.)
So perhaps those that are so eager to complain might realize that if they spent a little less time complaining and a little more time analyzing the problem and developing solutions, then they might have a little less to complain about. - dlavery [more] 
Threaded Mode