Team 226 was a Java beta test team for 2019, and we have put together a summary of the changes in the 2019 Controls System as well as our findings in the following presentation. If you have any questions feel free to post here.
6 Likes
Does the Phoenix tuner need to be connected to plot the motor output and related data or is it stored somewhere and the tuner is able to access it at a later point in time? The CPU you report in your last slide, that is for the roboRio, correct?
Thank you for the information.
The robot needs to have comms with the laptop in order to plot the motor output, and the CPU% was for the RoboRio.
“Update to System Watchdog safety mechanism”
Can you expand on this?
We posted a wpilib changelog earlier today: https://wpilib.screenstepslive.com/s/currentCS/m/getting_started/l/1028812-new-for-2019
The Watchdog class isn’t a safety mechanism in and of itself, but can be used as one. Currently, it just prints warnings about loop overruns in TimedRobot. We tried to make MotorSafety use Watchdog internally, but didn’t have enough time to debug it before kickoff.
1 Like
Excellent, thanks! Poking through that this morning.