Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Programming (http://www.chiefdelphi.com/forums/forumdisplay.php?f=51)
-   -   2006 Autonomous Disappointment (http://www.chiefdelphi.com/forums/showthread.php?t=41567)

Venkatesh 12-01-2006 08:45

Re: 2006 Autonomous Disappointment
 
Even greater than the holy grail: Your robot has one button, Win.

Cyber Punk 234 12-01-2006 09:02

Re: 2006 Autonomous Disappointment
 
I think less time is better really. It makes teams have to perfect and work harder to make sure it works right.

Chriszuma 12-01-2006 13:52

Re: 2006 Autonomous Disappointment
 
Quote:

Originally Posted by Astronouth7303
The holy grail: Your board has one switch, "Fire".

Actually, I was toying with the idea of doing something like that; i would have a turret continuously track the target so the driver can just hit a fire button to shoot them into the goal wherever he is on the field (assuming he's in range). Of course, it wouldn't be quite the holy grail, it would the holy grail plus two joysticks, and a switch to pick up balls.

TimCraig 13-01-2006 01:26

Re: 2006 Autonomous Disappointment
 
Quote:

Originally Posted by Donut
Lastly, it adds a new challenge; will you have enough time to shoot all 10 balls?

Exactly.

TimCraig 13-01-2006 01:29

Re: 2006 Autonomous Disappointment
 
Quote:

Originally Posted by MichaelGoldfarb
If FIRST were to leave the autonomous operation period any longer it would make the process of scoring a large amount of points that much easier.

And everyone would have the opportunity to score some points during autonomous. There would be a wider range of scores during autonomous. And it would me that teams OTHER than the top teams could hope to score meaningfully.

TimCraig 13-01-2006 01:37

Re: 2006 Autonomous Disappointment
 
Quote:

Originally Posted by Dave Flowerday
I'd guess that since autonomous was introduced in 2003, less than 10% of the teams I've seen used more than 10 seconds worth of the autonomous period. In fact, in many cases the real autonomous action was over in 5 seconds or so. .

Granted in the games of the past and Stack Attack was with the old BASIC Stamp processor. But have you run the numbers for this game? At 12 M/sec from any reasonable distance, the balls are in the air for a good fraction of a second. If you're a team that doesn't have a strong autonomous, it takes a few seconds to just get to the center of the field and line up.

TimCraig 13-01-2006 01:49

Re: 2006 Autonomous Disappointment
 
Quote:

Originally Posted by cbolin
Hi,
Consider this aspect...Software assist during the 120 second drive time.

I was specifically thinking of the actual autonomous phase vs the other control aspects of the robot during the teleoperation phase.

TimCraig 13-01-2006 01:58

Re: 2006 Autonomous Disappointment
 
Quote:

Originally Posted by Joohoo
Just because Auton mode is shortened That doesn't mean you can't have a task done autonomously in the other 2 minutes

Two separate issues. If you don't walk away with the 10 point autonomy bonus, the rest is just robot control.

TimCraig 13-01-2006 02:01

Re: 2006 Autonomous Disappointment
 
Quote:

Originally Posted by phrontist
90 seconds in autonomus? Psssh. Lame! Our driver will just try to amuse the crowd while the robot does it's thing... :D

I've seen your drivers. They're not that amusing. :D

Donut 13-01-2006 07:57

Re: 2006 Autonomous Disappointment
 
Quote:

Originally Posted by Chriszuma
Actually, I was toying with the idea of doing something like that; i would have a turret continuously track the target so the driver can just hit a fire button to shoot them into the goal wherever he is on the field (assuming he's in range). Of course, it wouldn't be quite the holy grail, it would the holy grail plus two joysticks, and a switch to pick up balls.

Our team wants a fire button as well, I suggested giving the shooter operator joysticks "just in case" the camera stops working or something weird. I think might put on a switch to toggle between auto fire (firing using the camera to aim) and manual fire (just giving control to the shooter operator), that way if the camera is pointed at the wrong goal or we're on defense and want to save energy by not having the turret move, we can just set it to manual.

Oh, lastly, we'd like one big Easy button right in the middle between the 2 drivers. Must light up, must be big and red.

SoftwareBug2.0 13-01-2006 17:27

Re: 2006 Autonomous Disappointment
 
Quote:

Originally Posted by Astronouth7303
The holy grail: Your board has one switch, "Fire".

Our team wants to have one switch: don't fire.

binary_sandman 14-01-2006 21:01

Re: 2006 Autonomous Disappointment
 
i am mad that aucton is cut to 10 seconds but challenges are good.
it is still Enough to make a ball in the top goal.
{
1388
}

KenWittlief 14-01-2006 21:04

Re: 2006 Autonomous Disappointment
 
only one button? "Launch" or "shoot" would be good.

"Fire" on a robot is usually a bad thing - or do you mean to trigger the Halon system?

BTW: over the years I have seen robots catch fire during a match. Sometimes a motor does a pyrotechnic show billowing smoke. A few times wires have shorted and circuit breakers where not where they should be and stuff caught fire.

If this happens quickly look in the bleachers. You can actually see all the team scouts, crossing that team number off their list of potential alliance partners :^)

Eldarion 14-01-2006 22:31

Re: 2006 Autonomous Disappointment
 
Quote:

Originally Posted by KenWittlief
only one button? "Launch" or "shoot" would be good.

Why do we need a button? The joysticks have triggers, right? :D

Sagar_Indurkhya 14-01-2006 22:43

Re: 2006 Autonomous Disappointment
 
Quote:

Originally Posted by Eldarion
Why do we need a button? The joysticks have triggers, right? :D

Because pushing a big red button is classic.


All times are GMT -5. The time now is 07:34.

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