The end of week 3

It's a few days until week 3 of our 6 week build season ends. How's your team doing? Are you ahead? Behind? On time? Do you have your robot all designed and being built, or are you still deciding on what kind of robot to build? Anything you want to share?

There's only 3 weeks left. Will you make it?

[JohnSchneider]

Due to a CAD error were a little behind...we should be back on route at the end of week 4 though...*knocks on wood*

[Akash Rastogi]

We're farther behind than we would like and farther behind than our collaboration teams. But I think we can still finish strong. Trying to perfect some CAD with only 2 people has been a struggle. Here's a sneak peak though.

http://www.atomicrobotics.com/2012/0...-cad-complete/

[davidthefat]

We are really behind. So essentially, our design has many flaws on multiple levels. I have low expectations this year. We do not even have a proper design yet; neither do we have a drive built. Really bad position we are in right now.

[Akash Rastogi]

Originally Posted by davidthefat

We are really behind. So essentially, our design has many flaws on multiple levels. I have low expectations this year. We do not even have a proper design yet; neither do we have a drive built. Really bad position we are in right now.

That's the spir.....wait...umm.....


Be more optimistic, be more focused, and try to bring some positive energy to your team during these last few weeks.

[davidthefat]

Originally Posted by Akash Rastogi

That's the spir.....wait...umm.....


Be more optimistic, be more focused, and try to bring some positive energy to your team during these last few weeks.

I am a realist. The team has been ignoring my warnings. My hope is that we get something that moves to competition.

[Ankit S.]

We're behind, but hey, that's the fun of build season right? Assembling that robot during that last caffeine powered weekend...

We have not started building the actual robot yet, due to machine problems and finals. We are expecting some parts in a few days and we will be working our butts off to catch up!

[MichaelBick]

We also have not started actually building. Our CAD team is small also, and so we are very behind, but I am confident we will be able to get at least everything up to a perfect shooter, in the bag.

[Gray Adams]

We're behind, but we're all behind where we'd like to be starting on day 1.

If only we could have Week 6 urgency every week.

[GRT808]

Found ourselves in a bit of a crisis earlier thesis week when our chassis was milled wrong due to some miscommunication. We no longer had access to manual mills to complete the long job but found a clever solution to our problem by rearranging some structural elements. A one person CAD team with continual input from members is a good way to keep motivated and possible (although having two people or more prevents miscommunication errors). All in all I think we are on time and the team continues to bond and endure with the resources we have.

256 is in the middle. We're on good form for week 3, although we've been spending way too long on our drive train (chain :|), we will start constructing our shooter/ball elevator thingy either this Saturday or next Tuesday, depending in how much we get done Saturday (We're gonna drive the robot! [We've said that 8 times, BTW...]) But we will drive for sure Saturday.

I may even post a video of us collecting balls. It won't give too much information on our robot, but it'll be interesting to see, at least.

[CalTran]

Boy can I relate to the noncompetitiveness of a team...our team is usually good, and we're going to get a decent 'bot out there at KC, but at the same time, I wish that the team would strive to compete up there alongside Bomb Squad and Team Titanium and Winnovation.
It made me really sad when I told someone on our team about something 1717 does, only to recieve back "Are we Team 1717? No, we're 2410." I know that we're not d'Penguineers, but that still doesn't mean we can't emulate what an award winning team does. (The reference in question was how d'Penguineers tweak their practice bot, and fabricate their competition bot only when they're absolutely sure about what works and what doesnt. -Reference from The New Cool- because our team rushed through prototyping and straight to metal fabrication. This arised because I asked our shooter team if they had tested everything and they said "No, but our metal shooter will be modular so we can continue testing.)

[MichaelBick]

Originally Posted by CalTran

Boy can I relate to the noncompetitiveness of a team...our team is usually good, and we're going to get a decent 'bot out there at KC, but at the same time, I wish that the team would strive to compete up there alongside Bomb Squad and Team Titanium and Winnovation.
It made me really sad when I told someone on our team about something 1717 does, only to recieve back "Are we Team 1717? No, we're 2410." I know that we're not d'Penguineers, but that still doesn't mean we can't emulate what an award winning team does. (The reference in question was how d'Penguineers tweak their practice bot, and fabricate their competition bot only when they're absolutely sure about what works and what doesnt. -Reference from The New Cool- because our team rushed through prototyping and straight to metal fabrication. This arised because I asked our shooter team if they had tested everything and they said "No, but our metal shooter will be modular so we can continue testing.)

I say the same thing to my team, and get the same response. As the CADder, I try to integrate some their ideas into our design process, but I believe that the best team to emulate is 254. They always have an effective simple(r) design, that I believe should be all team's way of thinking when they're designing, unless they have the resources of teams like 1717.

[Alpha Beta]

Originally Posted by CalTran

our team is usually good, and we're going to get a decent 'bot out there at KC, but at the same time, I wish that the team would strive to compete up there alongside Bomb Squad and Team Titanium and Winnovation.

2410 is always on our preseason watch list of excellent teams in the KC area.

While I'd love to say we designed it in the first 3 days and have been moving towards the polished product ever since... We've had our set backs with rule reinterpretations, misalligned parts, enginneering break throughs that require major redesigns, and inoportune illnesses from key members. One subsystems hasn't made it to CAD yet, and a second one is still looking for the right design concept. These things are not totally unexpected, so no panic just the constant pressure to fail faster. We'll be fine.

The drive base is built, finished wiring it last night, and should be driving it around today after school. Parts are mostly in house for the ball intake and delivery system. Prototypes all appear to function within our design perameters.

Software team found last year's robot to have a lot of similar functionality to this year's requirements and have turned it into a test bed for working out the kinks in code. We'll see how it translates to the smaller (faster) CRIO.

We're on schedule, but we wanted to be ahead, so it feels like we are behind.

[Otto.KARS]

[quote=CalTran;1114520]Boy can I relate to the noncompetitiveness of a team...our team is usually good, and we're going to get a decent 'bot out there at KC, but at the same time, I wish that the team would strive to compete up there alongside Bomb Squad and Team Titanium and Winnovation.

I know what you mean. Team 2345 has been striving for the same competitiveness. Usually our team creates a simple, yet effective, robot. This year we have upped the complexity. Overall, the team is on schedule. The build team is a little behind (we just finished our full frame). Programmers have several "pilot" codes for every function on the robot, and we are currently working towards target tracking.

I cannot wait to meet you guys (Metal Mustangs and Titanium) at KC.