James Kuszmaul 687e2c6711 [artf3709] Fixed PIDController loop timing.
For C++: The PIDController loop had been changed to run an infinite loop
with a Wait(period) rather than using the Notifier class to schedule
exact runs of the CallCalculate command. Essentially a revert to bb50f4b134,
accounting for more recent changes.

For Java: A similar problem had developed; essentially, a TimerTask used
to be used and at some point was changed to a Runnable. The Runnable had
an infinite loop with a Wait; TimerTask actually schedules things reasonably
(although it is not strictly real-time). Also, there were some
Thread-safety issues which I fixed.

Although Java and C++ had similar issues, they seem to have developed
these issues independently.

Changes have been tested on the GearsBot in both C++ and Java (and it
    works).

Change-Id: I478cb8bfd77cd2d031f8e343d0b8193b602dcc2a
2014-10-31 17:01:44 -04:00
2014-05-12 15:33:54 -04:00
2014-04-01 11:18:29 -04:00
2014-10-21 16:41:24 -04:00
2014-03-03 11:30:55 -05:00
2014-06-02 15:36:18 -04:00
Description
WPILib - FRC Robotics Library
467 MiB
Languages
C++ 53.8%
Java 32.7%
Python 6.6%
C 2.6%
Jinja 1.7%
Other 2.5%