Quote:
Originally Posted by apalrd
In LV, I've seen this issue when the WPIlib spits out errors. It seems that, if any individual thread gets a VI or two spitting constant errors, then the processor load of logging and transmitting all of these errors to the DS bogs it down enough for the thread to become unhappy (which usually trips one of the 100ms watchpuppies, which then sends more errors, and then everything dies).
I'd see if there are any errors being spit out.
|
If it weren't for that last sentence, I'd have almost no idea what you were saying.
