Working code in Windows shows 'Watchdog Not Fed' once deployed

[Ether]

Originally Posted by Mark McLeod

Get Competition Mode waits for a DS Occurrence, which I assume to be the arrival of a new packet. It's got a drop-dead timer of 1 second associated with it, i.e., no packet = mode goes to finish and terminates the user program.

Does anyone know what the timeout value is for the User Watchdog, and for the System Watchdog ?


~

[kamocat]

User watchdog is .5 seconds, or 500ms.
System watchdog uses a TCP connection between the DS and the cRIO. (I don't know what the timeout period is, but when it times out, your DS will say there's no robot connection)

[Ether]

Originally Posted by kamocat

User watchdog is .5 seconds, or 500ms.

Much longer than I expected. Can you provide a link to where this is documented?

Thanks.

[Alan Anderson]

Originally Posted by Ether

Much longer than I expected. Can you provide a link to where this is documented?

As with almost everything in LabVIEW, it's documented right where you would use it. In this case, that's the Watchdog Open vi. With "hover help" active, you'll see the default "Expiration (0.5s)" shown. The "Detailed help" link explains it completely.

[Ether]

Originally Posted by Alan Anderson

As with almost everything in LabVIEW, it's documented right where you would use it. In this case, that's the Watchdog Open vi. With "hover help" active, you'll see the default "Expiration (0.5s)" shown. The "Detailed help" link explains it completely.

Thank you.

I'll ask a LabVIEW programmer to show this to me next week at the next team meeting.


~