Quote:
Originally Posted by Tom Bottiglieri
The real answer is probably to use C/C++.
:-/
|
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.