|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
|||
|
|||
|
Re: WatchDog Timeout
try using highlight execution to watch what happens with the code. From there, you can make a decision as to where to put the watchdog so the auton doesn't time out.
The way I did it is like the example, but I made subVI's (as I used the same block of code over and over again) and forced a chain through device refrences. You can also try flat sequence structures if you don't want to go through the trouble of the subVI's |
|
#2
|
||||
|
||||
|
Re: WatchDog Timeout
if you have a lot of case structures, and you think ur code is taking too long to run within that particular case, then feed it in that case again (idk if thats allowed tho but it would probably work)
|
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|
Similar Threads
|
||||
| Thread | Thread Starter | Forum | Replies | Last Post |
| Watchdog | darty | NI LabVIEW | 8 | 16-02-2009 09:11 |
| error 5101 : Timeout | Wynlyndd | LabView and Data Acquisition | 3 | 31-01-2006 14:05 |
| Timeout!! | Ricky Q. | Rules/Strategy | 19 | 01-04-2004 22:03 |
| Microsoft Timeout | AJ Quick | Regional Competitions | 12 | 09-03-2003 17:38 |
| Timeout Ruling Discussion | ram | Off-Season Events | 4 | 29-11-2001 13:38 |