|
|
|
![]() |
|
|||||||
|
||||||||
![]() |
|
|
Thread Tools | Rate Thread | Display Modes |
|
|
|
#1
|
||||
|
||||
|
Re: getting stuck in autonomous or hybrid on the field
that's a good point. I know we had run practice mode successfully just before Friday, so i think our minds skipped right over that when trying to reproduce the issue, and we did just so happen to have everything we needed for an FMS Lite setup - so it was pretty simple to test that.
But I agree it would have been good to know if it would have had the same issues in practice mode as well. thanks! Jon |
|
#2
|
|||
|
|||
|
Re: getting stuck in autonomous or hybrid on the field
I will bet a cup of coffee that your problem was caused by the fact that your Autonomous VI ended on its own. When your Auton code has finished doing everything it has to do, put it into an infinite loop (containing a 10 or 20 millisecond delay) so that the VI never stops.
I saw this exact problem at a Mid-Atlantic regional event (on somebody else's robot). The problem went away when they added that infinite loop as I outlined above. The problem comes when the robot code tries to stop an Autonomous VI that is already stopped. Looking at the Framework code, I can find no reason why this should be a problem, but nevertheless it appears to be one that only appears when connected to the FMS. |
![]() |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|