View Single Post
  #2   Spotlight this post!  
Unread 11-02-2015, 23:34
Chris_Elston's Avatar
Chris_Elston Chris_Elston is offline
Controls Engineer
AKA: chakorules
FRC #1501 (Team THRUST)
Team Role: Engineer
 
Join Date: Feb 2004
Rookie Year: 2001
Location: Huntington, Indiana
Posts: 750
Chris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond reputeChris_Elston has a reputation beyond repute
Re: Best Practice for adding custom VI to Robot Main?

Quote:
Originally Posted by RufflesRidge View Post
Personally I think the VI is fine to help keep things organized. I would stick it in Periodic Tasks as is, outside the pre-populated loops in there.

If you do want to leave it in Robot Main, you need to get have it be a fork off the error chain like Periodic Tasks is, what you have now will prevent the main Scheduling Loop section from running until your subVI completes which it sounds like it may never do.

So something like this is best practice?
Attached Thumbnails
Click image for larger version

Name:	timed.jpg
Views:	22
Size:	130.4 KB
ID:	18293  
__________________
Team T.H.R.U.S.T. 1501
Download all of our past robot's source code here:Repository

Favorite CD quote:
"That can't be their 'bot. not nearly enough (if any) rivets to be a 1501 machine." ~RogerR: Team #1369
Reply With Quote