Thread: Error -44061
View Single Post
  #6   Spotlight this post!  
Unread 03-11-2012, 18:21
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: Error -44061

I don't have LV 2011 on my computer any longer, but I can show you images of what I was describing.

The first image shows where to get the support code VI.
The second shows that you simply drop it into TeleOp.vi.
If you then open it while running, you can see the time between any given calls. If you call it more than once from the same subVI or want to change the name to be more informative, just wire up your own string to Call Name.

The typical offenders are when teams put length delays or other lengthy code into teleop. Often the amount of the teleop and the pattern of when it misses will remind the programmer of something in their code. They will say -- "0.5 seconds, but that is how long we run our gripper motor", and they will dive into some code and find that they are doing it inline and causing the next teleop to be late, causing the safety config to send the error and shutdown the motors until the code is back in control.

Greg McKaskle
Attached Thumbnails
Click image for larger version

Name:	Clipboard 1.png
Views:	18
Size:	51.8 KB
ID:	13137  Click image for larger version

Name:	Clipboard 2.png
Views:	20
Size:	95.9 KB
ID:	13138  Click image for larger version

Name:	Clipboard 3.png
Views:	19
Size:	182.3 KB
ID:	13139  
Reply With Quote