Week 1 lessons learned: balancing strategy

[D.Allred]

Originally Posted by mwmac

Saw a few teams with 4wd that struggled getting the second pair of wheels on the bridge once it started to tip

Just to be clear about this, 4 wheel robots getting on the bridge second is very dangerous.

[who716]

Originally Posted by GCentola

Speaking of low traction, that seems to be the death of 1 Co-op point. If both alliances are on the C-Bridge, but it isnt balanced, you still get one CP each, but it looks like right after the match ends, the bridge tips to one side and the one on top pushes the other one off accidentally when it slides down.

Yes we thought of this during build session and ended up using a two speed transmission this helps a ton on the bridge because it allows us to make very slow movements while on the bridge and it allows us to stay on the bridge if its tilted or not. the only bad thing is getting it of the bridge after we balanced as its hard to roll.

[Alpha Beta]

Originally Posted by who716

Yes we thought of this during build session and ended up using a two speed transmission this helps a ton on the bridge because it allows us to make very slow movements while on the bridge and it allows us to stay on the bridge if its tilted or not. the only bad thing is getting it of the bridge after we balanced as its hard to roll.

Your post reminded me to go back and watch our 2nd match. It looks like our low gear keeps everyone on the co-op bridge for 5 seconds after the match ends, even though we are not at rest. According to G37, and G41 this should have been worth 1 co-op point to both alliances. It was not awarded, we did not even think to challenge for it at the time, and it does not appear as if the refs are even looking for the 5 second count.

Video (Match 17): http://www.more.net/content/2012-qualification-matches
Match ends at 3:43 on the video, and wheels don't touch carpet until 3:52. At that point the ref gives the all clear signal. Head ref is clearly watching the robot roll off the bridge, but has no reference to the 5 second stipulation from G37.

Lesson Learned: If you have a low enough gear to put yourself in this situation you may want to ask the Head ref how they will determine when 5 seconds has elapsed during the drivers meeting on the Thursday practice day.

PS. What difference would this have made? In hind sight, none. At the time it could have been huge.

[GilaMonsterAlex]

I was really surprised to see that so many teams didn't get the strategy of balancing the bridges (not to say it's easy). I was expecting more team work.

Since the kick off, I was harping to my students about how we should "choo-choo" onto the bridge with another team. It was a major reason why we withheld our bridge manipulator. We weren't sure we needed it.

Now I'm going to make sure to harp about communication with the alliances about our balancing strategy. It will make for a much better competition.

The one thing I'm going to predict is that more and more teams will abandon ball scoring and line up on the bridge balancing. This to me makes the game a bit more boring and takes away the challenge. I wouldn't be surprised to see a rule change where you have to wait til the 30 second mark before you make an attempt to balance the bride (not crossing).

Also, just so I understand this correctly. 148 uses a piston or shaft down to the ground to level out the bridge correct? Do they lift the piston right before the end?

[wireties]

Originally Posted by GilaMonsterAlex

Also, just so I understand this correctly. 148 uses a piston or shaft down to the ground to level out the bridge correct? Do they lift the piston right before the end?

Looked like that to me...

[dj bauch]

Originally Posted by GilaMonsterAlex

Also, just so I understand this correctly. 148 uses a piston or shaft down to the ground to level out the bridge correct? Do they lift the piston right before the end?

Yes, they had a little "foot" they could use to stabilize the bridge. Very clever design. Once the bridge was stable, they would lift the foot back into the robot.