Go to Post The weight sounds about right, too. If you need more than 65 pounds for your manipulator, then the drivetrain isn't the part you should be redesigning... - s_forbes [more]
Home
Go Back   Chief Delphi > Competition > Rules/Strategy
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
Thread Tools Rate Thread Display Modes
  #16   Spotlight this post!  
Unread 08-02-2013, 09:38
B Dot's Avatar
B Dot B Dot is offline
Play, Rest, Repeat
AKA: Bryan
FRC #1706 (Ratchet Rockers)
Team Role: Driver
 
Join Date: Jan 2013
Rookie Year: 2011
Location: Wentzville, MO
Posts: 27
B Dot is an unknown quantity at this point
Re: Rule G05 and Autonomous

Quote:
This question seems like it would fit this thread, would a tape measure be allowed on the field?
When you said tape measure i instantly thought of a range finder, like what bow hunters and even golfers use to measure distances. It would be fairly quick and discrete and there would be less factors for human error
  #17   Spotlight this post!  
Unread 08-02-2013, 09:39
FrankJ's Avatar
FrankJ FrankJ is offline
Robot Mentor
FRC #2974 (WALT)
Team Role: Mentor
 
Join Date: Feb 2011
Rookie Year: 2009
Location: Marietta GA
Posts: 1,944
FrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond reputeFrankJ has a reputation beyond repute
Re: Rule G05 and Autonomous

Your proposal is not inherently against the rules.

My understanding is the disable just disables the outputs. The program in the crio is still running. So you can have code that monitors the encoders, you just have to stick it the right place so it runs during disable. You could input the start point from the smart dashboard. You can even put a push button on one of the inputs on the robot to mark the zero point of where you start reading your encoders from. Nothing in G05 prevents this.

The only issue would be G07 if you take too much time. A little practice would prevent this.
  #18   Spotlight this post!  
Unread 08-02-2013, 10:51
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,862
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Rule G05 and Autonomous

There are a lot of problems with the "move it after it's on" approach, and we can't be doing it.

The field will not wait for your robot to boot, then allow extra time for you to move your robot around.
That goes for positioning by encoders/cameras/gyro or anything that demands you wait for the robot to finish booting and connecting with the field before getting on with life.
The goal is to start the match the moment all robots are connected to the field.
Taking one minute more than absolutely necessary adds an hour to the length of a single event day.

We will be told when we can power-up/power-down our robots, we do not get to choose.
We are always told to start the robot after it's been placed on the field for safety reasons.
Occasionally, the FTA has the discretion to direct us to start the robot before coming onto the field, but that's for FTA reasons, not team reasons.

It's
  1. get the robot on the field
  2. turn it on
  3. position it (if you have a gyro you have to position, then turn on, so it's especially important for teams with gyros to be able to position quicker than anyone else)
  4. load frisbees
  5. get off the field
All should be accomplished BEFORE the robot completes booting.

If there is a problem getting all the robots to connect with the field, then robots will be turned off and back on again, and you do NOT get extra time to re-position your robot to re-prepare your encoders.

Last year our drivers wanted to use the camera feedback to position our robot, but it really didn't work out.
The camera doesn't boot all that quickly, and when there was any issue that caused us to connect slowly or be restarted, then the camera image only appeared after we were all off the field and behind the lexan. The match typically started a moment after we saw the camera image on our driver station.
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 08-02-2013 at 22:54.
  #19   Spotlight this post!  
Unread 08-02-2013, 14:18
philso philso is offline
Mentor
FRC #2587
 
Join Date: Jan 2011
Rookie Year: 2011
Location: Houston, Tx
Posts: 940
philso has a reputation beyond reputephilso has a reputation beyond reputephilso has a reputation beyond reputephilso has a reputation beyond reputephilso has a reputation beyond reputephilso has a reputation beyond reputephilso has a reputation beyond reputephilso has a reputation beyond reputephilso has a reputation beyond reputephilso has a reputation beyond reputephilso has a reputation beyond repute
Re: Rule G05 and Autonomous

Quote:
Originally Posted by JesseK View Post
There's a better way: find a known point to always set down on, then go a known distance in autonomous. If you can't even do this, then your team will be in trouble if you're ever asked to move your starting position in order to accommodate another team's autonomous (e.g. you both shoot 3 from the same spot -- who moves?).
The GDC has given us a number of navigational aids in the form of retro-reflective tape around the goals, a wall and a pyramid. You may want to find an FLL team in your area that knows how to use sensors and how to exploit the field elements and the robot's physical atributes (i.e. one that can do a large number of the tasks on the half of the field away from Base). They may be able to give you a fresh perspective on how to develop an autonomous mode strategy.

Last edited by philso : 08-02-2013 at 14:25.
  #20   Spotlight this post!  
Unread 08-02-2013, 14:30
Doug G's Avatar
Doug G Doug G is offline
Coach / Teacher
FRC #0701 (Robovikes)
Team Role: Coach
 
Join Date: Dec 2002
Rookie Year: 2001
Location: Fairfield, CA
Posts: 880
Doug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond reputeDoug G has a reputation beyond repute
Re: Rule G05 and Autonomous

Quote:
Originally Posted by MARS_James View Post
Starting configurations definition says nothing about height and considering starting in your own Auto Zone you can be the max height of 84in
Off topic I know but I think a lot of team's missed this rule change for this year....
__________________
Work Hard, Have Fun, Make a Difference!

  #21   Spotlight this post!  
Unread 08-02-2013, 22:38
piguy123 piguy123 is offline
Registered User
FRC #4751
Team Role: Programmer
 
Join Date: Nov 2012
Rookie Year: 2012
Location: Canada
Posts: 6
piguy123 is an unknown quantity at this point
Re: Rule G05 and Autonomous

Can we set any parameters at the start of the autonomous period? Or are we just allowed to change the mode from teleop to autonomous? We were thinking about setting up a few pre-programmed instructions based on our position around the pyramid. Actually, could someone clarify how exactly we're placed? I was under the impression that we had to be perpendicular to one side of the pyramid. Can we really place however we want as long as we're touching the pyramid?

Thanks
  #22   Spotlight this post!  
Unread 08-02-2013, 22:43
EricH's Avatar
EricH EricH is offline
New year, new team
FRC #1197 (Torbots)
Team Role: Engineer
 
Join Date: Jan 2005
Rookie Year: 2003
Location: SoCal
Posts: 19,817
EricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond reputeEricH has a reputation beyond repute
Re: Rule G05 and Autonomous

Quote:
Originally Posted by piguy123 View Post
Can we set any parameters at the start of the autonomous period? Or are we just allowed to change the mode from teleop to autonomous? We were thinking about setting up a few pre-programmed instructions based on our position around the pyramid. Actually, could someone clarify how exactly we're placed? I was under the impression that we had to be perpendicular to one side of the pyramid. Can we really place however we want as long as we're touching the pyramid?

Thanks
Clarification on exact placement: G05 says touching the pyramid. That is the only positional requirement.

You don't change the mode; FMS (the field system) takes care of that. There are ways to select between autonomous modes; I would suspect parameters can be changed as well.
__________________
Past teams:
2003-2007: FRC0330 BeachBots
2008: FRC1135 Shmoebotics
2012: FRC4046 Schroedinger's Dragons

"Rockets are tricky..."--Elon Musk

  #23   Spotlight this post!  
Unread 09-02-2013, 00:21
Kevin Sevcik's Avatar
Kevin Sevcik Kevin Sevcik is offline
(Insert witty comment here)
FRC #0057 (The Leopards)
Team Role: Mentor
 
Join Date: Jun 2001
Rookie Year: 1998
Location: Houston, Texas
Posts: 3,730
Kevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond reputeKevin Sevcik has a reputation beyond repute
Send a message via AIM to Kevin Sevcik Send a message via Yahoo to Kevin Sevcik
Re: Rule G05 and Autonomous

Quote:
Originally Posted by Mark McLeod View Post
We will be told when we can power-up/power-down our robots, we do not get to choose.
We are always told to start the robot after it's been placed on the field for safety reasons.
Occasionally, the FTA has the discretion to direct us to start the robot before coming onto the field, but that's for FTA reasons, not team reasons.
Really? I've heard FTAs recommending teams turn bots on at the end of the previous match, but I've never heard one insisting we leave a bot off till it's on the field. We've always turned our bot on well before we even step on the field to get the booting started so the radio is already booted and ready when we're on the field. It makes things run lots smoother and quicker, since the radio is the entire reason for the huge delay involved in a robot reboot. The radio takes a good 45-60 seconds to come up. The cRIO is usually up in 15-20 or so. Atleast that's about how long I estimate waiting whenever I warm boot the cRIO for programming purposes.

Anyways, I've never heard of FTAs requiring robots to be off, and I'm curious under what authority they'd do so. Is it the generic "Anything the FTA says goes" reasoning, or is there something in writing to back this up?
__________________
The difficult we do today; the impossible we do tomorrow. Miracles by appointment only.

Lone Star Regional Troubleshooter
  #24   Spotlight this post!  
Unread 09-02-2013, 14:29
piguy123 piguy123 is offline
Registered User
FRC #4751
Team Role: Programmer
 
Join Date: Nov 2012
Rookie Year: 2012
Location: Canada
Posts: 6
piguy123 is an unknown quantity at this point
Re: Rule G05 and Autonomous

Quote:
Originally Posted by EricH View Post
Clarification on exact placement: G05 says touching the pyramid. That is the only positional requirement.

You don't change the mode; FMS (the field system) takes care of that. There are ways to select between autonomous modes; I would suspect parameters can be changed as well.
So I guess there's no way to set any initial parameters to direct our robot during autonomous? I guess the only control we get is what direction the robot faces. Do we also get to choose which position?
  #25   Spotlight this post!  
Unread 09-02-2013, 14:43
PVCpirate's Avatar
PVCpirate PVCpirate is offline
FRC Data Nerd
AKA: Anthony Jennings
FRC #1058 (PVC Pirates)
Team Role: Alumni
 
Join Date: May 2010
Rookie Year: 2009
Location: Londonderry NH
Posts: 669
PVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud ofPVCpirate has much to be proud of
Re: Rule G05 and Autonomous

Quote:
Originally Posted by piguy123 View Post
So I guess there's no way to set any initial parameters to direct our robot during autonomous? I guess the only control we get is what direction the robot faces. Do we also get to choose which position?
You and your alliance get to determine where your robot is placed and which direction it faces, just as long as it is touching your pyramid.
__________________
My accomplishments with 1058:
2010 - Granite State Regoinal Winners, Galileo quarterfinalists, IRI quarterfinalists
2012 - GSR Chairman's Award winners
An incredible four years I will never forget
  #26   Spotlight this post!  
Unread 10-02-2013, 01:04
Jaxom Jaxom is offline
Registered User
AKA: Michael Hartwig
FRC #1986 (Team Titanium)
Team Role: Mentor
 
Join Date: Apr 2010
Rookie Year: 2008
Location: Lee's Summit, MO
Posts: 379
Jaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant futureJaxom has a brilliant future
Re: Rule G05 and Autonomous

Quote:
Originally Posted by piguy123 View Post
So I guess there's no way to set any initial parameters to direct our robot during autonomous? I guess the only control we get is what direction the robot faces. Do we also get to choose which position?
You can set up config parms via your driver's station and/or by inputs (switches, whatever) on your robot. Manipulate the devices during set up, before you step back from your DS and/or as you're placing your robot on the field (or even before). Have your auto code read them first thing & act appropriately.
__________________


Mentor http://www.teamtitanium.org/
  #27   Spotlight this post!  
Unread 10-02-2013, 12:48
Mark McLeod's Avatar
Mark McLeod Mark McLeod is offline
Just Itinerant
AKA: Hey dad...Father...MARK
FRC #0358 (Robotic Eagles)
Team Role: Engineer
 
Join Date: Mar 2003
Rookie Year: 2002
Location: Hauppauge, Long Island, NY
Posts: 8,862
Mark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond reputeMark McLeod has a reputation beyond repute
Re: Rule G05 and Autonomous

The general reasoning is that it's safest to be unpowered while physically carrying the robot around, the same reason we power off before removing our robots from the field, so that falls under the safe operation practices and procedures.

FTA's usually only make requests like these when trying to investigate or address a problem, so that doesn't mean we can't power up in queue to pre-charge our pneumatics, drop in new code, or verify that things are working.
The field personnel may request robot's be turned on early, if matches are really falling behind, to get things moving.
I know as CSA I occasionally request that a particular team be allowed to remove their robot from the field while still powered up, so I can inspect the bridge logs that are lost in a power down. But I ask the FTA first. Things like that are their call.

A memorable past instance of one field request to Not turn robots on before coming onto the field was 2010 when the recommended replacement for the old black bridge caused all the black bridges to be thrown off the field network. There was a particular startup sequence that had to be followed.
Last year robots were running with unrestricted video feeds, sometimes pulling 15Mb/s. Robots had to be turned on in sequence so the culprits could be identified.



Quote:
Originally Posted by Kevin Sevcik View Post
Really? I've heard FTAs recommending teams turn bots on at the end of the previous match, but I've never heard one insisting we leave a bot off till it's on the field. We've always turned our bot on well before we even step on the field to get the booting started so the radio is already booted and ready when we're on the field. It makes things run lots smoother and quicker, since the radio is the entire reason for the huge delay involved in a robot reboot. The radio takes a good 45-60 seconds to come up. The cRIO is usually up in 15-20 or so. At least that's about how long I estimate waiting whenever I warm boot the cRIO for programming purposes.

Anyways, I've never heard of FTAs requiring robots to be off, and I'm curious under what authority they'd do so. Is it the generic "Anything the FTA says goes" reasoning, or is there something in writing to back this up?
__________________
"Rationality is our distinguishing characteristic - it's what sets us apart from the beasts." - Aristotle

Last edited by Mark McLeod : 10-02-2013 at 13:35.
  #28   Spotlight this post!  
Unread 10-02-2013, 14:27
pmangels17's Avatar
pmangels17 pmangels17 is offline
Mechanical Marauders - Alumnus
AKA: Paul Mangels
FRC #0271 (Mechanical Marauders)
Team Role: Mechanical
 
Join Date: Jan 2012
Rookie Year: 2011
Location: Bay Shore, NY
Posts: 405
pmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond reputepmangels17 has a reputation beyond repute
Re: Rule G05 and Autonomous

You could technically use a potentiometer, but the turn limit would mean it isn't applicable on the drivetrain. Unless you had a retractable wheel with the potentiometer on it, that then retracted when it was moved into optimal position.
__________________
Junior at the University of Notre Dame, Mechanical Engineering

Got questions (about Notre Dame, robots, college, etc), don't hesitate to ask.

**Bang Boom Pop!** "Was that the robot?" "I don't know, do it again"
**BANG BOOM POP** "Oh, now it's on fire."
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 17:23.

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