Go to Post A coin flip is a wonderful thing. Not because it makes the decision for you, but because when the coin is in the air, you realize what you really want. - rtfgnow [more]
Home
Go Back   Chief Delphi > Technical > Programming > NI LabVIEW
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
 
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 20-03-2010, 20:19
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,731
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Autonomous independent-watchdog errors

Quote:
Originally Posted by ewoodring View Post
I get error messages in the message window in the Diagnostics tab on the Driver Station that say "Watchdog expired: system #, user #." Is there anything in code I have to change to fix this?
It depends.
A few of these messages are normal and may not affect your robot operation.
The # is a count of how many of each have occurred and of which type of Watchdog (system vs. user).
  • You'll usually see momentary system Watchdogs at mode transistions, e.g., Disabled -> Auto -> Teleop -> Disabled. Those are nothing to worry about.
  • User Watchdogs are common when your autonomous code finishes and exits, but seeing them in Teleop or while Auto is supposed to be running is a problem in your code.
In the lower left of the Driver Station screen are you seeing a persistent message of "Watchdog not Fed?"

That message will occur if you are not currently running any autonomous code at all, for instance, if it has already completed and exited or if you have bypassed all auto code. The default Autonomous Independent will generate this Watchdog, since after it completes it's assignment it just exits and the Watchdog goes unfed.
The Watchdog message is not a problem if no code is supposed to be running.
In this case, when Teleop code begins to execute, it will resume feeding the Watchdog and the message will go away.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 20-03-2010 at 20:30.
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump

Similar Threads
Thread Thread Starter Forum Replies Last Post
periodic tasks in autonomous independent Ether NI LabVIEW 19 31-03-2010 07:15
global variables and autonomous independent Team1824 NI LabVIEW 10 19-02-2010 23:00
Autonomous Mode, Independent, Iterative (?) FRC2669_Valery General Forum 4 18-02-2010 09:50
Autonomous Independent Code Issue Watchdog not fed pilum40 FRC Control System 0 11-02-2010 12:00
Using Sensors in Autonomous Independent Felipe Sagui NI LabVIEW 2 27-01-2009 17:25


All times are GMT -5. The time now is 04:45.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi