Quote:
Originally Posted by RufflesRidge
Using the Practice mode on the Driver Station in your pits and turning on Highlight Execution (the little lightbulb) while running the code from LabVIEW you may be able to see what VI may be getting stuck (unfortunately it's possible that the issue won't crop up with highlight execution enabled).
You should also check the Diagnostics tab and NetConsole to make sure no errors are being reported.
|
To follow up with what's been said already...
We tried this, but unfortunately we could only reproduce the problem with built code (as opposed to just deployed). We added user messages to almost every bit of our code, which actually made the problem a little bit better, happening about half the time. When it did happen though, it was inconsistent as to where in the code it happened.
We ended up rewriting our whole teleop and autonomous code on Thursday night before our Qualification matches, and it preformed reasonably well (with a lot of between-matches scrum). By our second match in Qualifications we had gotten it back up to almost where it was.
The whole building issue is key here, as it could most likely be a bug that's been lurking in our codebase for a long time, as we never really tested our build code with a practice match. This lack of testing is something we have noticed and are taking steps to improve.