Hey guy’s I’m with a rookie team, 3750, and I’m wondering on some of the in’s and out’s of general FTC design. The team and I don’t wish to copy anyone’s design, but I’ve been wondering what are general strategies people have like different wheel configurations, utilization of motors (HT and Lego) and servos, attaching different electrical components and the battery pack (This is a big one), as well as what types of mechanisms work for different situations, ect. It would be much appreciated if different teams could provide detailed photos of their robots past and present so that I can investigate these different designs. Although I completely understand for any teams that wish to withhold from presenting present robot designs, but past are appreciated as well.
the CAD looks awesome; however i see some possible problems. The wheels wont be stable they need to go through 2 sides of the C channel for it to work otherwise your robot will bend shafts faster and the wheels will be tilted at an angle.
Just my 2 cents about the drive train
Does this work like FRC 148 the Tornado for Lunacy?
Similarly to 148 but we couldn’t match its function using the Tetrix stuff. The CAD isn’t done yet, obviously, as we’re just playing around with stuff for a while now. The shooter is independently driven from the intake and shooter feeder. And I’m not worried at all about the cantilevered shafts bending. If they do, we have more.
FTC 369(FRC 623) has created the king of all zip tie trees. There is no comparison to our 700+ zip tie coated piece of pvc pipe. pictures will be up soon.only downside is color(plain white).
you cant use two foot zipties. only 11 inchers. my interpretation of the rule is that the initial size of the ziptie is what governs if it is legal or not
Swerve drive would be awesome to do, but it is hard.
In the 2009 game, it was important to have a fast robot so it wouldn’t get pinned. Slow Robots in Lunacy were bad.