View Single Post
  #7   Spotlight this post!  
Unread 10-04-2010, 11:30
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,751
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Build & Download problems in LabVIEW

I forgot to mention that.

The System Manager tab, the VI one, lets you see the state of the VIs, run additional VIs, and stop VIs that are running. If the system is loaded, it may take ten seconds or so, but it is pretty fast.

The explicit steps are, Open System Manger, flip to the VI tab, Start the monitoring, wait for the list to populate, select Robot Main, and Stop the VI. At that point, the CPU is not loaded, and you can deploy.

Funny that you mention the disabled state being for debugging. I've heard that before, and perhaps it should be more integrated in the framework, and have a way to keep the CPU load down. Hmmm.

Greg McKaskle
Reply With Quote