Initializeīegin by opening the devices in Begin.vi, notice that we even skip setting the refnum, and just bundle everything. We gave our results to the people at NI that work on this, and they said the reason was the DevRef get allocated memory every time and they fixed that for the 2017 season (and presumabley onwards).įor that reason, the following moves from being an optimization to reduce lag to being an optimization for the developer (by not causing him/her to type out a case sensitive name multiple and related less than great development methods). In the summer of 2016, we were able to actually do a performance test on this that showed that the following method significantly outperformed the DevRef get/set method. The following optimization has been used by the teams that we are alumni of and mentors of, and none of the teams have had that error since. After speaking with several teams at regionals, we came up with a solution. When the authors of this website first started programming for FRC, we would get the ‘Robot Drive Not Running Fast Enough’ error frequently. FRC LabVIEW Tutorials - Teleop Background
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |