Jump to content


  • Content Count

  • Joined

  • Last visited

Community Reputation


About Banjo

  • Rank
    LAVA groupie

LabVIEW Information

  • Version
    LabVIEW 2012
  • Since
  1. I see that you have already done the strip chart shifting action. I just didn't watch it long enough. Thanks again.
  2. Thanks for the examples. I cranked up the speed in your example by a factor of 20, and it does not appear to hit the CPU all that hard. I would have to figure out how to drop older points off the left side, but that can be viewed as an interesting challenge. Given the low rate of update in my VI I might be able to get away with updating the X-Y with every data point and see what that does to the resources. That would simplify the code somewhat. Testing this idea inside my GUI environment will take a bit of time. Thanks for the ideas.
  3. Thanks for the replies. I am still stuck with LabVIEW 2012. Don't even have 2012 SP1 installed yet. I do not know whether the VI's are re-entrant or not. I inherited this infrastructure. I will see if I can find out. I have read on the forum that X-Y graphs are CPU hogs. I have not tried them myself, so that is only rumor for me. This is not a show stopper problem for this project. If push comes to shove I will drop the chart or live with it kike it is. But it would be nice to make it work properly. Thanks again.
  4. I have a GUI that allows the user to display one of three front panels by swapping the front panels of three asynchronous VI's into a subpanel in the main front panel. All three VI's are launched asynchronously at startup and continue to run in the background. On one of three VI's there is a strip chart that updates at about 1 Hz. It has a history length of 1024 and is showing 200 points. It works as expected on first display. When I swap into the subpanel one of the other VI's, the first one continues to update in the background, i.e. the data points continue to tick up. However, when
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.