2013 Washington DC Regional

[Robo Hamsters]

Originally Posted by ErikaSosa

Shame 2630's robot stopped working during that 3rd SF game. It was only 6 points at the end, and their robot proved that it could score consistently (they were defended well too, not sure by which robot, but it did a great job).

Thanks for the compliment. The bot that defended against 2630 was our robot. (4466)

[Sam C.]

2415 programmer here in response to why our robot could not compete in the last two matches. I'm trying to figure out the same thing, but here's what we know:

- After our last match we attempted to do a systems check and we noticed that the our robot was communicating (i.e. we could ftp it, and the little light on the driver station that says communication was green), but there was no robot code (the driver station light was red).
> We know that the code was lost between the time of our last match,
> and the next time we turned it on.

- We then tried reimaging the cRIO. It didn't work. We got a spare cRIO from the spare parts table and reimaged that. This time, the code loaded up once and crashed. We were excited because the error we got was IOException, which means there was a file that our code was referencing that we didn't put on it. We loaded our file, rebooted the code, and all of a sudden we couldn't see the code (driver station light was red).
> Now that I think about it, that has to mean that there was an
> issue with our code if it was able to load up once. I'm not sure
> why it worked until now though.

At that point we had to forfeit.

Some other details:

- We use java image version 47.
- We use SmartDashboard. It's been somewhat glitchy, and I've heard
others having issues with it.

If anyone has a clue what could be going on, hit me up. At least writing all of this out helped me think it through.

[Negative 9]

Team 611 actually had a similar problem to 2415 (albeit not right before a finals match). We discovered about 10-15 minutes before our 4th qualification match that the status light on our cRIO would flash twice every few seconds. After having the imaging tool failing to image our cRIO multiple times while we were queuing, we ended up having a dead robot sitting on the field. After the match, Miles, a volunteer at the DC Regional, helped us repair our cRIO. After a little tinkering with the IP settings in MAX, we were able to reimage the cRIO and recompile our code and everything seemed to be working fine.

We still don't have any idea what caused our cRIO to fail between matches when the robot was powered off.

Regardless, it was a great regional and a great season. I'm actually surprisingly sad to see this one end.

[Leah Hirshey]

Hey, a 612 student here,

First off, thank you so much to team 422, It was a delight working with you at VCU and DC, and we hope to see you again next year to continue passing on our friendship block...chunk...thing.

And a huge thank you to everyone who recognized our team in other posts in this thread. We had a challenging season, and the DC Regional was a final accumulation of all our hard work. To see you, our fellow FIRSTers recognizing that means as much to us as any award. Your posts have already been shared around our team, and I cannot say how happy they have made us.

That said, there were so many great teams at DC this year, this is a region to watch. 612 had a great time, and we're sad it's over, but the FIRST spirit is still here.