View Single Post
  #7   Spotlight this post!  
Unread 01-03-2012, 15:17
Alan Anderson's Avatar
Alan Anderson Alan Anderson is offline
Software Architect
FRC #0045 (TechnoKats)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2004
Location: Kokomo, Indiana
Posts: 9,112
Alan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond reputeAlan Anderson has a reputation beyond repute
Re: Please Help Compiled info Teleop Periodic Task need verification

Quote:
Originally Posted by mbone206 View Post
I do not see how Globals can be prevented. Teleop will be using set points for periodic task loops, how else can you do it
There are many mechanisms for communicating information from one VI to another (e.g. queues and occurrences), but the default code framework doesn't provide any way to tell both Teleop and Periodic Tasks to use one. Unless you add more input terminals to those predefined VIs, a global variable is a reasonable solution.

There is also a LabVIEW idiom called a "functional global", which might make dataflow purists happier, but I don't think that's an important goal.
Reply With Quote