View Single Post
  #14   Spotlight this post!  
Unread Yesterday, 15:04
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,766
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: Teleop Pausing Itself

Just to pile on, ... err ... , I mean clarify, LabVIEW debugging involves running the VI interactively by pressing the run button

Each VI's compiled code is downloaded to memory, connections are established so that you can see panels, probe, breakpoint, change some values on panels, etc.

Once the code is working well, you build an exe and deploy it. There happens to be a way to compile debugging into an exe, but that is not used as often as the interactive case.

Greg McKaskle
Reply With Quote