Re: Hundreds of "Watchdog Expiration: System X" Errors
 

Does anyone know if this solution works?

Re: Hundreds of "Watchdog Expiration: System X" Errors
 

The service is easy to put back to auto if this doesn't improve things. I don't have the problem, so I'm just passing on the results of a search, hoping that it will be helpful. I'd also like confirmation.

Greg McKaksle

Re: Hundreds of "Watchdog Expiration: System X" Errors
 

The most recent update to labview and the DS happened to fix our problem. We barely get any watchdog expirations now. Thanks!

Re: Hundreds of "Watchdog Expiration: System X" Errors
 

I am having the same exact issue. Even after the DS and LV updates, and re-imaging the cRIO with the update as well.

We've been on this for HOURS, maybe 8 in total, because our compressor kept cutting on and off every time we got an error. We blew a fuse and deemed the whole thing unhealthy for the robot. We were getting about an average of 1.3 per second.

We made the odd discovery that it stops when the sidecar is unplugged.. but you can't do much without a sidecar, but if that helps the NI guys pinpoint the issue...

Re: Hundreds of "Watchdog Expiration: System X" Errors
 

Since the issues we knew of and understood were corrected in the latest update, please give a thorough description of any error messages, DS indicators, and error displayed in the diagnostics tab.

Greg McKaksle

Re: Hundreds of "Watchdog Expiration: System X" Errors
 

We were getting brief Watchdog errors last night. With the robot sitting, doing nothing, we'd get spikes and Jaguars flicking to neutral.

We did some packet-sniffing, and it looks like each "spell" of no signal corresponds to the classmate taking too long to send a packet.

Typically, packets are sent from the classmate and from the robot at 50hz. During each spell of watchdog, we saw that the robot would continue sending packets at a steady rate (once every 20ms), but the classmate would hiccup. In the 3 instances we recorded, the classmate's hiccup packet was sent 100, 150, and 200ms since the one that preceded it, rather than the 20ms we expect.

Here's our setup:
ClassMate:
-Wired to router
-Running just the "bottom half" of the driver station (with the diagnostics, setup, IO, etc tabs). The camera feed and other user dashboard code was running on a different PC to minimize load on the classmate.
-This was observed in both developer and driver accounts
-Running most recent driver station

Robot:
-Communicating wirelessly with router about 6ft away.
-Battery was reading 12.6V
-No motors running
-Main watchdog-feeding thread is in a fast loop that just feeds the watchdog. No camera image analysis, no long computations, just checking joystick values and setting motors
-Two PID loops were running. One at 1000hz, one at 100hz, though the 1000hz one was probably Disable()-d at the time.
-PCVideoServer was running on its separate thread, sending data.
-Running the most recent WPILib build (from early feb)
-Running v20 cRio for C++

Last night the robot was fairly well behaved. All night we probably only saw about 10 of these hiccups all night, but on Monday night it was awful, and on Tuesday night it was apparently equally bad.

Hope this helps, and hope I'm not duplicating a post by a 2702 comrade in another thread.

Re: Hundreds of "Watchdog Expiration: System X" Errors
 

This seems alot like what we experienced last night. Our compressor would flick off while not charged, and the solenoids would all get put back to their "off" state, which caused things to move when nobody was touching the controls... also, the top half of the ds (the dashboard part) isnt doing anything. I assume we have to put some sort of call to WPILib for it to start working in our C++ code?