Chief Delphi

Chief Delphi (http://www.chiefdelphi.com/forums/index.php)
-   Chit-Chat (http://www.chiefdelphi.com/forums/forumdisplay.php?f=14)
-   -   Oh god did our robot just run into the driver station auto club (http://www.chiefdelphi.com/forums/showthread.php?t=146159)

IronicDeadBird 23-03-2016 15:16

Oh god did our robot just run into the driver station auto club
 
And no the one that went flying out of the field doesn't count.

Our robot at least twice at Arizona North decided it would love tap the driver station opposite of the low bar. Turns out motion profiling is easier to spell then it is to implement.

GreyingJay 23-03-2016 15:25

Re: Oh god did our robot just run into the driver station auto club
 
I'm fully expecting ours to accidentally do that at some point during our matches in North Bay this weekend. I'll be mortified, of course, given my vocal stance against this "strategy". But irony is what it is... If it happens, we'll fix it.

Our students agree that "run and gun" is NOT a viable auto strategy on our team. We have code that we think will do the job.

yonip 23-03-2016 15:28

Oh god did our robot just run into the driver station auto club
 
Well one time our robot just rammed the wall repeatedly for ~10 seconds. Next match (I think) it hit the driver station wall again... and then ran away :0 (both during CHS Greater DC, and that was all the castle crashing we've done)
We totally forgot that velocity PID is sticky so we never stopped the bot when it went far enough...

GreyingJay 29-03-2016 14:05

Re: Oh god did our robot just run into the driver station auto club
 
As expected, we had a few unexpected crashes at North Bay. Our most egregious happened when an encoder was ripped clean off the gearbox in a previous match, and nobody noticed... :ahh:

We fabbed up a skid plate after that!

Nyxyxylyth 29-03-2016 14:18

Re: Oh god did our robot just run into the driver station auto club
 
Yeah, nobody noticed the encoder wire had fallen out.

We've since put in a timeout, just in case.

EmileH 29-03-2016 14:28

Re: Oh god did our robot just run into the driver station auto club
 
1786 at Granite State, every single match ;)

messer5740 29-03-2016 14:56

Re: Oh god did our robot just run into the driver station auto club
 
Ours did that at the Buckeye Regional once... We increased the time and speed to get over some of the ground defenses and on our first run, we went over the rough terrain and went full force into the opposite driver station. Our drive team was mortified because this had happened to us multiple times in our previous regional and vowed to never intentionally do so. We changed the time slightly to avoid that happening again. We make up for a lack of aggressive auto by playing great tele opp!:D

Tim Sharp 29-03-2016 15:09

Re: Oh god did our robot just run into the driver station auto club
 
Quote:

Originally Posted by Nyxyxylyth (Post 1564733)
Yeah, nobody noticed the encoder wire had fallen out.

We've since put in a timeout, just in case.

Encoders seem to be the cause of a lot of that. We struggled with a similar issue at Rocket City. The encoders turned out to be counting down instead of up.

Ari423 29-03-2016 15:53

Re: Oh god did our robot just run into the driver station auto club
 
423 did that in almost every eliminations match at Springside Chestnut Hill, but just barely so. During quals we always stopped before we crashed. Between quals and elims we upped the power from 50% to 85%, but forgot to change the timing. Now the robot would stop almost exactly 1/2 second after it crashed, consistently. Sadly because of quick turn-around time and LabVIEW's slow and inconsistent deploys, we weren't able (or willing to risk) reloading the code to stop a second earlier. I'd like to officially apologize to any team we may have hit and let you know that we've fixed that problem for Westtown this weekend by adding an ultrasonic rangefinder to auto-stop when we get close to the wall.

jkoritzinsky 29-03-2016 21:52

Re: Oh god did our robot just run into the driver station auto club
 
I never thought I'd say this, but open loop timed auto FTW!

GreyingJay 29-03-2016 22:32

Re: Oh god did our robot just run into the driver station auto club
 
Quote:

Originally Posted by Nyxyxylyth (Post 1564733)
Yeah, nobody noticed the encoder wire had fallen out.

We've since put in a timeout, just in case.

Holy cow your robot goes over that moat fast.

plurp911 29-03-2016 23:29

Re: Oh god did our robot just run into the driver station auto club
 
Our robot did this for many matches, and after asking software to make auton end a bit sooner, they decided to go by the motto "if it ain't broke, don't fix it"

Tom Line 30-03-2016 01:04

Re: Oh god did our robot just run into the driver station auto club
 
Quote:

Originally Posted by Ari423 (Post 1564790)
423 did that in almost every eliminations match at Springside Chestnut Hill, but just barely so. During quals we always stopped before we crashed. Between quals and elims we upped the power from 50% to 85%, but forgot to change the timing. Now the robot would stop almost exactly 1/2 second after it crashed, consistently. Sadly because of quick turn-around time and LabVIEW's slow and inconsistent deploys, we weren't able (or willing to risk) reloading the code to stop a second earlier. I'd like to officially apologize to any team we may have hit and let you know that we've fixed that problem for Westtown this weekend by adding an ultrasonic rangefinder to auto-stop when we get close to the wall.

This is the primary reason we took a year working on implementing a simple text file system where everything is read in from text files that we FTP to the robot. Deploying labVIEW in a competitive environment is nearly impossible. Just FTPing new constant and auto text files takes a matter of a second.

tcjinaz 30-03-2016 01:38

Re: Oh god did our robot just run into the driver station auto club
 
Quote:

Originally Posted by Nyxyxylyth (Post 1564733)
Yeah, nobody noticed the encoder wire had fallen out.

We've since put in a timeout, just in case.

Yeah, verily.

Is anyone else watching gravity to see if they're on a defense or not?

tcjinaz 30-03-2016 01:42

Re: Oh god did our robot just run into the driver station auto club
 
Quote:

Originally Posted by Nyxyxylyth (Post 1564733)
Yeah, nobody noticed the encoder wire had fallen out.

We've since put in a timeout, just in case.

And the LORD spake, saying, "First shalt thou take out the Holy Pin, then shalt thou count to three, no more, no less. Three shall be the number thou shalt count, and the number of the counting shall be three. Four shalt thou not count, neither count thou two, excepting that thou then proceed to three. Five is right out. Once the number three, being the third number, be reached, then lobbest thou thy Holy Hand Grenade of Antioch towards thy foe, who being naughty in My sight, shall snuff it."[

epylko 30-03-2016 05:37

Re: Oh god did our robot just run into the driver station auto club
 
Quote:

Originally Posted by EmileH (Post 1564741)
1786 at Granite State, every single match ;)

I saw a robot do something like that at the Pittsburgh regional this year. It hit so hard the driver station and joysticks flew off and hit the ground.

Everyone added velcro to their driver station and joysticks after that.

Sperkowsky 30-03-2016 07:30

Re: Oh god did our robot just run into the driver station auto club
 
Our hard crashes came in practice matches but we definitely deserve to be a part of this club.

https://www.thebluealliance.com/match/2016nyny_qm36

or

https://www.thebluealliance.com/match/2016nyny_qm74

SuperSVGA 30-03-2016 12:13

Re: Oh god did our robot just run into the driver station auto club
 
I can't remember what match number it was, but I think our robot hit the wall hard once and knocked the other teams driver station down. And I think the other team got a yellow card, but not us...

rich2202 30-03-2016 12:59

Re: Oh god did our robot just run into the driver station auto club
 
Our team's robot hit the wall, and the wheels kept spinning. The Ref e-stopped our robot to keep it from digging up the carpet.

IndieWaves 30-03-2016 18:26

Re: Oh god did our robot just run into the driver station auto club
 
Quote:

Originally Posted by SuperSVGA (Post 1565274)
I can't remember what match number it was, but I think our robot hit the wall hard once and knocked the other teams driver station down. And I think the other team got a yellow card, but not us...

There's not necessarily a penalty for knocking an opponents driver station off, as they have tried to encourage teams to use the hook-and-loop tape to secure it down. The opposing alliance may have done something completely different during the match to earn a Yellow Card.

SuperSVGA 31-03-2016 02:02

Re: Oh god did our robot just run into the driver station auto club
 
Quote:

Originally Posted by IndieWaves (Post 1565462)
The opposing alliance may have done something completely different during the match to earn a Yellow Card.

I think the yellow card was probably for them trying to save it as it dangled by the cords.

EricH 31-03-2016 02:10

Re: Oh god did our robot just run into the driver station auto club
 
Quote:

Originally Posted by SuperSVGA (Post 1565626)
I think the yellow card was probably for them trying to save it as it dangled by the cords.

Operator console safety is NOT a yellow card. It's right there in the rule, as the exception.

Means that any yellows were for something else. What, I don't care to speculate.

Road Rash 31-03-2016 06:06

Re: Oh god did our robot just run into the driver station auto club
 
Quote:

Originally Posted by epylko (Post 1565089)
I saw a robot do something like that at the Pittsburgh regional this year. It hit so hard the driver station and joysticks flew off and hit the ground.

I saw the same thing at the 2016 Wisconsin Regional during qualifications. One robot hit the wall so hard the entire driver station flew right off the shelf. :yikes:


All times are GMT -5. The time now is 02:15.

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