View Single Post
  #5   Spotlight this post!  
Unread 12-02-2016, 12:30
aeastet aeastet is offline
Programming Mentor
AKA: Tim Easterling
FRC #6043 (Allegan Tigers Robotics)
Team Role: Coach
 
Join Date: Jan 2015
Rookie Year: 2011
Location: Holland, MI
Posts: 127
aeastet is an unknown quantity at this point
Re: nagging problem with CPU usage

One of the biggest things that I see that is causing problems is that you have vision on the RoboRio. This is a major resource hog and has nothing to do with LabVIEW.

You should look at moving this vision stuff to the Dashboard. It is not that hard to do. That would help you a lot with your RoboRio resources.

There are many other things that I see that would help with lowering resources. One thing is using global variables. They take a windows call to set priority. This will slow down what you are doing. We use action engines to hold the values that we want to use in other places. Look at our code from last year to see what I am talking about.

I would move all of the dashboard updates to their own loop in the timed tasks. Have one loop that sends and receives values and put them into global variables if you do not have time to lean action engines. Can I edit your code on line? I could try and show you what I am talking about.

Biggest thing you can do is move the vision stuff to the dashboard hands down.