Quote:
Originally Posted by Ether
I'm not a LabVIEW guru, but I was under the impression that "getting stuck in autonomous" is not an issue with the FRC LabVIEW framework, because it automatically shuts down autonomous at the end of the autonomous period.
Could a knowledgeable LabVIEW person please comment?
|
From my reading of the LabVIEW framework, this is right. LabVIEW starts the Autonomous VI as a separate task, and then kills it when autonomous mode ends. This is possible with C++/Python/Java too, but most teams opt to avoid the confusion of threading and just stick with single-threaded code. In fact, my team had an issue with LabVIEW last year that we traced to a race condition happening around the transition into autonomous.