Thread: Watchdog!?!?!?!
View Single Post
  #17   Spotlight this post!  
Unread 02-03-2009, 01:10
keehun's Avatar
keehun keehun is offline
Team Captain
AKA: Keehun Nam
FRC #2502 (EP Robotics)
Team Role: Leadership
 
Join Date: May 2008
Rookie Year: 2008
Location: Eden Priaire
Posts: 474
keehun has a reputation beyond reputekeehun has a reputation beyond reputekeehun has a reputation beyond reputekeehun has a reputation beyond reputekeehun has a reputation beyond reputekeehun has a reputation beyond reputekeehun has a reputation beyond reputekeehun has a reputation beyond reputekeehun has a reputation beyond reputekeehun has a reputation beyond reputekeehun has a reputation beyond repute
Send a message via AIM to keehun
Re: Watchdog!?!?!?!

Quote:
Originally Posted by Wayne TenBrink View Post
Our programming mentor has about 2 months worth of experience with LabView.
Don't worry, I was the main programmer and that's about what I had, too.

Quote:
Originally Posted by Wayne TenBrink View Post
When you all describe "feeding the watchdog", what actually does that? From your description, I assume that its some built-in, behind the scenes, function of the code that just happens without any special "instruction" from our programmer. And if the code is too busy or gets stuck in a "while" loop, it doesn't feed the watchdog.
Yes. There is a WPI library block which gets input a boolean(?) which I think is tied to some low level vxWorks call. When vxWorks doesn't see it, then it probably stops the .rtexe and decides to tell the DS that the Watchdog has sadly starved to death. (figuratively)

Quote:
Originally Posted by Wayne TenBrink View Post
What would make that happen only intermittently?
I highly doubt it is anything but the code..

Quote:
Originally Posted by Wayne TenBrink View Post
We would like to think it was field/system related, but we really don't know.
This, I highly doubt, especially if it was only your robot with this problem.

Quote:
Originally Posted by Wayne TenBrink View Post
Is there a credible scenario where static electricity could be involved?
What I think is possible is that your battery was low (6~7 volts) and cRio had problems. This "symptom" would be different, so I doubt it.

Quote:
Originally Posted by Wayne TenBrink View Post
What about startup sequencing? I've read where some teams had communication problems when they powered up the robot before the DS. We generally powered up the DS first, but probably not always. I wouldn't think that would necessarily have anything to do with watchdog.
This would be more of an issue with "No Comms" error message, which is worse.

Quote:
Originally Posted by Wayne TenBrink View Post
We generally like the new control system and LabView, but are anxious to find out where the bugs are hiding out and get rid of them.
If you compete in another regional, maybe you can upload your code and we can look it over for any unending loops?

Good luck!
Keehun
Team 2502
__________________
For by grace you have been saved through faith, and that not of yourselves; it is the gift of God, not of works, lest anyone should boast. -- Ephesians 2:8-9
2010: Quarter Finalist (MN 10,000 Lakes)
2010: Website Award (MN 10,000 Lakes)
2009: Quarter Finalist (MN 10,000 Lakes)
2009: GM Industrial Award (MN 10,000 Lakes)
Reply With Quote