LabView Programming - Do we still need Watchdog?

[Mark McLeod]

To fix it, you should analyze your code to really understand if you've got slow code that needs to be sped up. If your code really is laggy then it'll be sluggish in responding to the driver controls even without the Safety vi and it must be fixed.

There's a drop-in tool NI included with the framework this year called Elapsed Times.vi
You'll find it in your project under the Support Code folder.
Just drop it into teleop.vi, Run the project from Robot Main.vi, and bring up the Elapsed Times.vi front panel to watch how long everything takes.

If it's just a coding style that's the problem, then the Safety vi can be turned off.
Inside Open 2/4 Motor (used in Begin.vi) there is an enable/disable.

[Greg McKaskle]

The LV team fully intended to come up with a good replacement for the Delay and Feed VI. Since it never managed to be completed, I'll relate the concept.The idea is to save a copy of Delay and Feed and create a Delay and Update. One step inside the Robot Drive VIs, you'll find a call to Safety Update. You don't need to wire values or anything except the refnum for RobotDrive. Add the appropriate refnums to the connector. If the correct updates are called in place of the Feed of the old VI, I believe the piecewise autonomous will work as before, and I believe that pausing a VI or hitting a breakpoint will typically halt the robot. I say typically because unlike the watchdog, it is possible to pause some of the lower level safety VIs and bypass the safety. This shouldn't happen unless someone is way off the mark in their debugging.

Since I haven't implemented this, and certainly haven't tested it, please test the breakpoint in auto carefully before trusting it.

Greg McKaskle