Watchdog Not Fed -- Ghosting
 

When we run the robot we get "Watchdog Not Fed" errors and the robot 'ghosts' every now and then. What do I need to do to fix this problem?

Re: Watchdog Not Fed -- Ghosting
 

we are also having the same problem so if you can figure anything out that would be great, our only guess it that the our vision processing is taking up alot of the memory.

Re: Watchdog Not Fed -- Ghosting
 

We are not using vision processing, we have a very basic setup. Everything in our code at this point is very simple control of drive, and 5 other motors for our robot.

Re: Watchdog Not Fed -- Ghosting
 

Note that we have timed our vision processing code which is based on the 2012 vision sample code, all the filtering takes up between 150 to 200 msec. So if you are calling that code in your main robot task, you need to make appropriate adjustment to your watchdog expiration time.

Re: Watchdog Not Fed -- Ghosting
 

Are you running wireless or with a physical ethernet connection? We had a serious episode of robot glitchiness yesterday that got better when I manually changed the D-Link's WiFi channel to one that didn't have quite so many other networks on it. (I used the inSSIDer program to show me nearby wireless networks.)