|
|
|
 We don't do battle bots, but we play hard. - Gdeaver [more] |
 |
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
| We don't do battle bots, but we play hard. - Gdeaver [more] |
|
|
|||||||
|
||||||||
|
|
Thread Tools | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Problem with System Watchdog
I'm having a problem with the system watchdog timing out whenever I click on one of the tabs in the driver station window. We loaded the unedited default code into our test bed and the problem was still there, so as far as I can tell it has nothing to do with any of the changes we have made.
I also tried to edit the timeout length of the system watchdog by using the Watchdog Configure VI (not sure if it is a standard VI or not), but then the code wouldn't load. Is anyone else having the same problem, and does anyone know of a fix? EDIT: I disabled the user watchdog and the error still occurred, so I am almost certain it is a problem with the system watchdog. Last edited by JSonntag : 14-01-2010 at 16:37. 
|
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Problem Getting Victors to run with the new control system | Boommaster713 | Programming | 11 | 15-02-2010 15:29 |
| cRIO system watchdog | kamocat | NI LabVIEW | 2 | 30-10-2009 23:53 |
| System: Watchdog problems | dboisvert | C/C++ | 7 | 16-02-2009 02:36 |
| System: Watchdog problems | dboisvert | C/C++ | 1 | 15-02-2009 20:12 |
| [FTC]: Problem with Code or Problem with Bluetooth? | VeedotJaydot | FIRST Tech Challenge | 3 | 27-01-2009 18:22 |
Threaded Mode