Right after we watched the reveal video on the 9th we went to 179’s field to see what it looked like. When I saw the height of the low bar I looked at one of my team mates and said “There’s no way we’re fitting under that”. I would probably still have the same reaction.
For me, the low bar is an obstacle that I personally knew most teams would design their robot for because “OOOOHHH WE GOTTA DO EVERTHIN’”. So we decided not to. I think we would make that decision again. Even with our #tallbot we still had trouble packaging everything into what we built so kudos to all those low bar robots.
EDIT: I’ve been wanting to say this for a while and I feel like this is an appropriate place to say it:
The low bar is a defence, yes? Yes. So I looked at the problem as would we design our robot to just be able to damage one defence, say the Portcullis. That Portcullis design is essentially your constraint and you can’t remove it, you can’t work around it. It has to stay there. So we decided to not let 1 defence constrain us when there are 8 other ones that are available to take down. (I think that makes sense)
We would definitely take the low bar approach again. We looked at it from a strategy standpoint from district events through worlds. Add to that the design and engineering challenge of getting everything to fit in a tight package. It’s a really good lesson in minimalist design. We opted to not have pneumatics this year to save space, and aren’t regretting that decision at all.
We typically are crossing the other defenses in teleop, but we still wanted to be able to handle that one, as we might be paired with 2 robots who couldn’t do the low bar. From our week 2 event, there were a few times we had to cross the low bar because an alliance partner wasn’t able to complete it for one reason or another.
When we are in tower attack mode, it provides a quick path to go back and forth from the neutral zone and/or secret passage. We used it often (though not always) to make that trip.
Low bar isn’t for everyone, but it provides a fun challenge.
My team totally ditched the low-bar Saturday after bag and tag. We are using our withholding allowance to build a mechanism for Colorado that I believe should be able to change the way defense is played in this game.
Acceleration is a force and therefore would affect the direction of your footprint projection. The footprint is projected in the direction of all forces acting on the robot, I just said gravity because that is always present.
A heavier robot with more rotational inertia is going to tip less than a lighter one because your motors stay there same. I guarantee you I could build a chassis that flips due to its own wheel force, and fix it by adding weight without changing CoM.
This would prevent the tipping because it would reduce the robot acceleration, and rotational acceleration (which means it would have to undergo lateral acceleration for longer before reaching its tipping point) therefore changing the footprint projection, that’s the real reason it wouldn’t tip.
As mentioned above, the cases are the same, you just add another vector for robot acceleration.
Very true, the reactionary force when the robot stops makes it like a pendulum, you want to accelerate out of phase with the robot tipping period to not magnify it.
Counter argument: our design goal was to be able to breach alone, and we picked low bar instead of c class defenses. It means we I ly have to be capable of 7/9 of the defenses instead of 8/9 which would be needed for a solo breaching #tallbot.
I told my students on day two that the game isn’t hard per se, but it is a difficult packaging problem, which is very common in engineering.
We are a tall robot and to be honest I am still alright with that decision. Our biggest problem isn’t the robot wanting to tip over it is that our drivers are afraid of breaking the robot so they keep stopping while going over defenses. This makes us “look” like we will tip. We are using the original AM wheels on our tracks and not so much as a crack (we made hubs to take the abuse).
Without a doubt we would still plan to go under the low bar. We have had multiple matches this year where our ability to do the low bar directly added to our RPs earned in a match (in particular our solo breaching when we are the only robot on our alliance).
Self reliance is something I brought up in the old Low Bar threads and I am very happy to report that it was the right choice for us.
If my team had the experience and the skill to make a fast, accurate high goal shooter, than we might have. However, we have a track record of building functional but not exceptional shooters, and this year, we just decided we didn’t need to shoot high goals.
I am still happy with our decision as it forced us to embrace CAD more in our design process (something the rest of my team had been dragging their feet about) to get everything to fit under that 14" limit. Also, as long as the improvements to our intake we plan on implementing at the Regional work, we should be able to run low goal cycles very quickly, and crossing the Low Bar is critical to that strategy.
Oh, and we inadvertently built a robot that can climb stairs unassisted. That wouldn’t have happened if we had gone tall.
We prioritized breaching and bouldering and that included the low bar. I wouldn’t change a thing. Our robot is a breaching machine and could do 3 - 4 low goals a match at our first regional. The low bar allowed us to keep our center of gravity insanely low which made us able to zip over defenses with no worries of tipping.
Confirmed - we’d still be low-bar capable. The low bar was definitely the easiest defense to breach. The mistakes that held us down at Bayou were mechanical implementation, not strategic decisions. No more 25 chain, at least not for dead-axle drive wheels. We achieved our highest regional seeding yet (18 of 56), and were the highest seeded 5-5 team due to several breaching RP and a capture RP (we scored a few boulders and carried more into the courtyard). Our post season mods will focus on the drive train and tweaking the pickup and launcher.
