2006 Davis Sacramento Regional

[NoodleKnight]

Originally Posted by Nuttyman54

Caspar was trying to get a hold of you, but apparently your own 'bot took precedence...sheesh

haha, yeah well, I don't think the team would have been happy if I left the robot in an undrivable state

Sorry for the lack of support, some things just happened that I didn't expect. Oh well, it's part of life.

[Nuttyman54]

Nah, i don't blame you, we had problems too. I think SAC will have a much better setup, being that it's going to be run by the team scouts, not 2 networking guys and a team leader...

[billbo911]

Originally Posted by NoodleKnight

I don't quite understand, it was serving DHCP, there isn't really other common way to run a router, except for ad-hoc (which I'll vouch, wasn't the case).
To get to FSN you had to connect to and IP which had port 80 forwarded. Unless you have two machines set up for DNS hosting along with your server, there isn't a way to access a server within the LAN via easy-to-remember domain name, if that's what you're talking about.
Correct me if I'm wrong, which I think I probably am.

DHCP (Dynamic Host Control Protocol) is the process by which IP addresses are served to devices that connect to a network, unless they already have a static IP assigned to them for that subnet.

DNS (Domain Name Service) is a service that translates Domain Name to IP address. This is used extensively on the INTERNET, but seldom if ever on a small private, or SOHO network, which is the case here. (SOHO stands for Small Office Home Office).

In the case of serving FSN at the regionals, there is no need to use DNS or port forwarding. All you have to do is point a browser to "http://<serverip>" where "<serverip>" is the IP of the server. The web server should automatically serve FSN if it is set up correctly.

Please feel free to come by our pit, I would love to answer any question you might have regarding this.

As far as your router is concerned, I'm not surprised. Lynksys WRT54G's have a nasty habit of locking up at the worst possible time. A simple power cycle or reset usually brings them back to life. What effect your modifications had on it I'm not sure. If we can find some time, maybe we can test it.

[NoodleKnight]

Originally Posted by billbo911

DHCP (Dynamic Host Control Protocol) is the process by which IP addresses are served to devices that connect to a network, unless they already have a static IP assigned to them for that subnet.

DNS (Domain Name Service) is a service that translates Domain Name to IP address. This is used extensively on the INTERNET, but seldom if ever on a small private, or SOHO network, which is the case here. (SOHO stands for Small Office Home Office).

In the case of serving FSN at the regionals, there is no need to use DNS or port forwarding. All you have to do is point a browser to "http://<serverip>" where "<serverip>" is the IP of the server. The web server should automatically serve FSN if it is set up correctly.

Please feel free to come by our pit, I would love to answer any question you might have regarding this.

As far as your router is concerned, I'm not surprised. Lynksys WRT54G's have a nasty habit of locking up at the worst possible time. A simple power cycle or reset usually brings them back to life. What effect your modifications had on it I'm not sure. If we can find some time, maybe we can test it.

Ok, so I wasn't so confused with what you were saying. The router was running DHCP, although I guess it stopped working every time they turned it off (as if it lost it's config settings), but a simple re-logon into the administration panel seemed to fix it. I guess I'll have to look into that later.

[Doug G]

Originally Posted by codeoftherobot

Just as a note, if I recall correctly from the meeting, UC Davis will be allowing the use of their shops for robot repair. Robots will be shuttled back and forth via golf cart/mini trucks to the shop. Can you confirm this Doug? I don't know if any of this has changed or not since the last meeting I attended.

UC Davis is offering the use of their machine shop and machinists for the three days. There'll be a shuttle (truck) that will transport parts/robots/participants back and forth.

[blue_crew]

Originally Posted by Doug G

UC Davis is offering the use of their machine shop and machinists for the three days. There'll be a shuttle (truck) that will transport parts/robots/participants back and forth.

Thats great! I cant wait to see a robot on the back of a golf cart driving through the uc davis campus.

[Mike Hendricks]

1388 will be there (we're currently sitting down in the hotel eating breakfast as we speak). If you guys need any tools or help, come see us. We've also managed to squeeze the famous vise and drillpress under the bus (people on 1072 should remember that) and hopefully we'll manage to get them inside the ARC again

Ahh .. only a couple hours to go

[Team1726Nerds]

hi....thanks again for the use of your vise! it's a life saver. good luck tomorrow

[Mike Hendricks]

Originally Posted by Team1726Nerds

hi....thanks again for the use of your vise! it's a life saver. good luck tomorrow

No problem, we're glad to let anyone use it who needs to, regardless if they think it's overkill.

We're just glad Jason didn't stop us at the door when we bought it in (we were actually concerned if the letter of the no floor standing tools rule would be enforced, but because the lack of machine shop within walking distance we figured it'd be ok), the same goes for the drill press. Either way, MANY teams used that vise this year, and last year .. and we're just glad to have it.

Good luck to everyone tomorrow .. If anyone needs some help, just come over to 1388's pit and ask for Mike

[MrForbes]

I put up the first batch of pits pics from Thursday morning, hope you like them!

if I misidentified a team please let me know and I'll fix it. Also I hope to get pics of the rest of the teams by Friday night.

http://www.selectric.org/nerds/2006ca/index.html

[MrForbes]

updated Friday night with new pics of all robots

http://www.selectric.org/nerds/2006ca/index.html

[thecheatdx]

I'm going to try and get all the alliances for the finals when they come up and edit this post when it's all said and done.

EDIT: HERE IT IS!

Alliance #1:
Team 1351
Team 649
Team 100

Alliance #2:
Team 766
Team 568
Team 835

Alliance #3:
Team 1726
Team 852
Team 1662

Alliance #4:
Team 114
Team 1834
Team 245

Alliance #5:
Team 955
Team 701
Team 753

Alliance #6:
Team 1678
Team 34
Team 1388 (XD YAY!)

Alliance #7:
Team 1458
Team 115
Team 368

Alliance #8:
Team 1960
Team 1318
Team 956

LOLZ FP ON T3H ALLIANCES FTW!!11oneone

Davis/Sac Rocked.

Lots of upsets, lots of matches going to three for the finals. Good to see so many old FIRST friends, and make new ones. I have one beef. The sportsmanship award should definitely gone to Team 34 from Huntsville.
Because of a shipping mishap, their robot didn't arrive until 7pm on Thursday.
They had it uncrated and passed through inspection by 7:15.

Instead of complaining and hanging out, they adopted a rookie team and helped them all Thursday afternoon. Ed Sparks (mentor) was a volunteer inspector and helped make the inspections a breeze for me and everyone else.

So Hat's off 34, you guys are a class act. The South shall rise again!

(I don't count Florida as part of the South

Dr. Bot, Lead Inspector San Jose, Davis.

[Team1726Nerds]

Agreed this was a great regional. Thank you to everyone for being help to us when we needed it, and thank you for all who we were alliances with. And I especially thank team 852 and 1662, our bots complimented one another perfectly, and I don't think we could have picked a better alliance. Also congrats to 245 on the chairmans (and woody flowers) award, and 753 on the inspiration award. We know that you both stood out to us in your helpfulness.

1726 also says hats off to 34. We were right next to you in the pits, and saw all the help you gave to 1974 and anyone else who needed, despite your bot not showing up Friday.

So we will be seeing some of you in Atlanta, and we hope to see others over the years!

[sciguy125]

This regional was a little upsetting for 1351. We fought hard and made it to first seed. Then, about 20 mins before our quarter final match, we had a speed controller fry. We didn't have enough time to fix it and went in with the left drive dead.

The really disappointing part was that we have two motors per side and only one died. We might have been alright had the second motor worked. However, it looks like we accidentally unplugged/dislodged/otherwise caused to fail the signal cable from the other speed controller while we were trying to replace the dead one. There were other problems associated with our hasty swap job, but those mentioned were the direct causes of the failure.

We lost both of the quarter final matches and were out. Thanks to 649 and 100 for sticking through it with us anyway.

FOR THE RECORD:
It seems that we had 4 separate teams come to our pit and comment on our robot's remarkable similarity to 254's. We did not work with them, ours was developed completely independently. We didn't see their design until they released pictures from the Portland regional, so we didn't have time to copy it either. I was actually pretty shocked when I noticed that we pretty much have the same robot, functionally anyway. And as for copying their strategy too, we had the idea on kick off day. The robot was designed with the "shoot from the platform" attack in mind. The reason we didn't impliment it at Silicon Valley is that we were having some drivetrain issues that made it hard to get up the ramp. Again, we are not a cheap knockoff of 254. We independently designed a similar, but shoddy version of their robot.