Go to Post Geez, now I'm like some all-knowing all-seeing FIRST sage who lives in the moutains waiting for students to venture upwards to my home to ask me if there will ever be a water game....:rolleyes: - Koko Ed [more]
Home
Go Back   Chief Delphi > Technical > Technical Discussion
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
View Poll Results: Do you ever lose control of your robot?
Never- our controls are always 100% with no sluggishness nor dropouts 26 37.14%
we started paying careful attention to radio placement and never had another problem 17 24.29%
Yes we sometimes have sluggishness and dropouts: We always just blame it on our software. 26 37.14%
We thought sluggishness was a requirement listed in the rule book 9 12.86%
Multiple Choice Poll. Voters: 70. You may not vote on this poll

 
 
Thread Tools Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #24   Spotlight this post!  
Unread 18-03-2011, 09:20
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,763
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: Robots not under driver control- does it happen- do you determine why?

A comment on the difference between Run as Startup and pressing the run button using LV.

Running LV with only the run button is quite similar to running as startup, but because the panel(s) are open, the cRIO and development computer are both working a bit harder communicating info back and forth about panel values.

This protocol is typically lightweight, just sending binary values, usually from robot to dev computer. If you change a panel value such as a PID gain, the dev sends a small packet to the robot. Obviously, the more windows you have open, the more traffic. The more probes you add to your VI, the more traffic. Vision is a case that is not lightweight. It is extremely useful to be able to probe and view panels with camera data on them, but to get the data to the laptop, the image has to be compressed by the cRIO and transmitted as part of the protocol. This only happens if the image is visible on a probe or panel. Scrolling the image offscreen won't help, and I doubt that minimizing helps. To lighten the load, you close the panel with images when you aren't using them.

I develop with the run button all the time, but then again, I like debuggers. Also, I usually don't run the dev stuff and DS on the same computer, and almost never run both on a Classmate. Hopefully this helps explain why panels can indeed cause dropouts, but it doesn't have to force the Startup approach too early.

Greg McKaskle
 


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 17:04.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi