Watchdog Problem

[AB Steven]

Yesterday our team updated all of our computers to Labview 2011 and updated our classmate with the FRC flash drive we got. We tried out the sample drive code and our driver station told us that watchdog wasn't being fed. We also tried some of our own code and still were told watchdog wasn't being fed. Does anyone know how to fix this?

[DonRotolo]

Welcome to ChiefDelphi.

I'm not a programmer, but maybe the answer is "Feed the watchdog"?

Use the Search feature in the orange band at the top to find the hundreds of threads on this topic from the last 2 years, surely one of them will have your answer. I recommend doing this.

[AB Steven]

They were supposed to remove watchdog with the 2011 updates. Also, why would the example code that is supposed to run the motors not feed the watchdog if we needed to?

[Mark McLeod]

Try this to narrow down the problem.


Open the block diagram for Begin.vi
Double-click on Drive-Open 2 Motors and open it's block diagram
Change the "enable" input in the center of the screen to "disable"Run that code to see if the Watchdog message goes away.

[Joe Ross]

Yesterday our team updated all of our computers to Labview 2011 and updated our classmate with the FRC flash drive we got. We tried out the sample drive code and our driver station told us that watchdog wasn't being fed. We also tried some of our own code and still were told watchdog wasn't being fed. Does anyone know how to fix this?

After you installed LabVIEW from the DVD and reimaged the classmate with the usb stick, did you install the labview, utilities, and driver station update and reimage the crio?

[jhersh]

Also, make sure you are creating a new robot project after having installed all the needed updates listed above. If you have an old project, then it may be enabling the watchdog.

-Joe

[AB Steven]

Try this to narrow down the problem.


Open the block diagram for Begin.vi
Double-click on Drive-Open 2 Motors and open it's block diagram
Change the "enable" input in the center of the screen to "disable"Run that code to see if the Watchdog message goes away.
We disabled that and it still doesn't work. We also added watchdog blocks in teleop and in Robot main, and still no luck. Any more ideas?

[jhersh]

What exactly is the error message you are seeing now?

[AB Steven]

What exactly is the error message you are seeing now?

http://img34.imageshack.us/img34/2711/36077087.png

Theres a screenshot of our driverstation.

We did what Mark said, tried a brand new default drive code, and it didn't work. We tried reimaging the cRIO, and the cRIO imaging program tells us that the reimage is complete and successful. But, when we restart the robot our old code from before we updated everything to 2011 is there and still works. Could the problem be that the cRIO isn't reimaging correctly?

[jhersh]

We did what Mark said, tried a brand new default drive code, and it didn't work. We tried reimaging the cRIO, and the cRIO imaging program tells us that the reimage is complete and successful. But, when we restart the robot our old code from before we updated everything to 2011 is there and still works. Could the problem be that the cRIO isn't reimaging correctly?

Try this... in Begin, place an open watchdog VI and configure it to be disabled.

[AB Steven]

OK SO our reimagers were keeping the 2010 image instead of defaulting to 2011 now everything is working thanks everyone for posting ideas.

[MaxMax161]

We had the same problem and we fixed it by rewriting all our code in a new robot project. After that we didn't get anymore watchdog errors. If you do end up doing this make sure to find all the .vis in labview again and not copying them from old/other code.

Your only other option is to convert this file to a binary and push it to the crio. http://dogfoodchat.com/wp-content/uploads/2009/03/Dog-Food.jpg