Go to Post Side effect include: Hearing loss, splinters, blisters, extreme sprit, uncontrollable urges to scream "GO MOE", and bright green fashion sense - The Lucas [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

 
Closed Thread
 
Thread Tools Rating: Thread Rating: 3 votes, 5.00 average. Display Modes
  #1   Spotlight this post!  
Unread 11-01-2015, 18:25
IronicDeadBird's Avatar
IronicDeadBird IronicDeadBird is offline
Theory Crafting Fo days...
AKA: Charles Ives "M" Waldo IV
FRC #1339 (Angelbots)
Team Role: Tactician
 
Join Date: Feb 2014
Rookie Year: 2005
Location: Colorado
Posts: 958
IronicDeadBird has a reputation beyond reputeIronicDeadBird has a reputation beyond reputeIronicDeadBird has a reputation beyond reputeIronicDeadBird has a reputation beyond reputeIronicDeadBird has a reputation beyond reputeIronicDeadBird has a reputation beyond reputeIronicDeadBird has a reputation beyond reputeIronicDeadBird has a reputation beyond reputeIronicDeadBird has a reputation beyond reputeIronicDeadBird has a reputation beyond reputeIronicDeadBird has a reputation beyond repute
Re: [Request] Robot speed rules of thumb

Speed is an interesting factor this year considering per rules given there is no reason why a robot without a drive base couldn't score. If you are using these "rules" to determine what speed your robot should go I would suggest you consider otherwise because speed (in my mind) isn't a really important factor this year.
I'll try to make this simple but its hard for me to explain its just something that I observed nobody taught me this so I couldn't dig up a lesson plan.
In this kind of game "speed" isn't as important of a measurement as "idle time" you want all mechanisms working together to make sure your robot is always performing an action that would contribute to scoring. Wasted time is wasted scoring potential in that regards getting to a point on the field quickly isn't as ideal as getting to a point on the field when you are ready. If you zoom over to where you need to be but you aren't quite ready to off load a stack I would refer to the time spent fidgeting as "idle time". What sucks about "idle time" is that time isn't enough to increase your scoring potential. Its enough time that you lose scoring potential but not enough time that you can do anything meaningful to make up for it. The speed of your robot and the mechanisms on it need to work together to minimize this sort of idle time.
Hope that makes sense! If not I'll try and rephrase it as a Haiku...
__________________
HERO 俺を讃える声や 喝采なんて 欲しくはないさ
I liked my team more before they stole my jacket.
Play is for kids this is serious...
  #2   Spotlight this post!  
Unread 11-01-2015, 19:54
smclean1969 smclean1969 is offline
Registered User
FRC #3512
 
Join Date: Oct 2010
Location: Orcutt, CA
Posts: 37
smclean1969 is an unknown quantity at this point
Re: [Request] Robot speed rules of thumb

The "right" speed is difficult to provide a universal answer for. In general, if your robot is an offensive based robot, it needs to be faster. The right speed should be fast enough that you're able to control both the robot as well as any field elements. We've traditionally had a top speed around 15 fps. For ultimate ascent we had a top speed of 12 fps with increased control. While the better control was nice, we were limited to two runs whereas the faster robots were getting three in. Last year, we had a top speed up around 18 fps and we routinely lost control of the ball because we were so fast in driving so we actually drove at speeds that were less than optimal.

For the low end, that's key for defense or for high control/high torque scenarios, such as the bridges in Rebound Rumble. I don't see the need for a low gear this year. For those defensive push matches 4 to 6 fps should be sufficient.

I agree that this year will be about deliberate control and effective pacing more than incredible speed. That said, the robots that will be top seeds at St Louis will be incredibly fast but they also don't need this blog for inputs. We all tend to follow their lead.
__________________
Scott McLean
FIRST Team 3512, the Spartatroniks
Team role: mentor


2011: Highest Rookie Seed and Rookie Inspiration Award Long Beach Competition
2012: Winner Los Angeles Regional -- w/ Team 987 and Team 1717
2013: Finalist Los Angeles Regional -- w/ Team 599 and Team 981; Engineering Excellence
2015: Entrepreneurship Award - Ventura Regional
Closed Thread


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 00:46.

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