![]() |
Re: Team 254 - 2014 Build Blog + Tech Binder
Quote:
For example, certain teams, especially in eliminations, were able to have a successful catch probability much larger than 10%, but it rarely happened in Qualifications. |
Re: Team 254 - 2014 Build Blog + Tech Binder
Quote:
|
Re: Team 254 - 2014 Build Blog + Tech Binder
Quote:
|
Re: Team 254 - 2014 Build Blog + Tech Binder
Quote:
It was interesting to watch the model evolve over time. We initially severely underestimated pedestal lighting/ball return time, as well as the ability of the average team to acquire assists fairly quickly by inbounding. As a result, on day one, one robot hurdling, self-catching, and scoring was looking pretty tempting. |
Re: Team 254 - 2014 Build Blog + Tech Binder
Looking over your gearbox data/render in both the blog and the technical binder I was wondering why your team chose to orient the CIM motors the way you did. I'm relatively new to gearbox design and I rather like the triangle method that west coast products and AndyMark use. I just wondering what your team's reason was for doing it the way you did.
Is it possible that I could get a look at the .STEP file for the gearbox? |
Re: Team 254 - 2014 Build Blog + Tech Binder
Quote:
It's a cool variant that can be used to save height, and space on one side of the robot. |
Re: Team 254 - 2014 Build Blog + Tech Binder
Quote:
Our cluster gear isn't big enough to get 3 CIMs and a shifting piston around it. |
Re: Team 254 - 2014 Build Blog + Tech Binder
Quote:
|
Re: Team 254 - 2014 Build Blog + Tech Binder
Quote:
|
Re: Team 254 - 2014 Build Blog + Tech Binder
FIRST (:p) of all, thanks for releasing these! The tech binder is just beautifully made! I had some questions though.
1. It's mentioned your drive train was designed for sudden bursts of acceleration, but you're geared for 20 fps+. Why was such a high speed chosen over a lower speed that would have accelerated faster? 2. You had quite a bit of motors and pistons on the robot, how was your battery life? 3.I recall you experimented with alternate material for bumpers this year, how did they hold up? 4. No recipes in the build blog? Has the lack of free corndogs doomed us all? |
Re: Team 254 - 2014 Build Blog + Tech Binder
Quote:
2. The 6 CIMs on the drivetrain were the biggest power draw. The only problems we had were when we tried to push other robots while in low gear, sometimes the breaker would trip. We would obviously replace batteries between every match, and we also purchased some fresh batteries before Champs because the 12 we'd been using for regionals were starting to die. 3. We didn't too much experimentation ourselves with bumper material, but we looked at what 971 and other teams did and tried to improve upon it. We used Cordura bumpers for the first 2 regionals and then switched to Sailcloth bumpers after that. The new bumpers had a coefficient of friction as low as .2 (compared to Cordura's .4 I think). They helped with driving around defense immensely and the material held up pretty well. The biggest problem with the new bumpers was that we ironed on the numbers instead of sewing, and thus sometimes the numbers would bubble up or rub off. 4. I don't recall how many times baked things for the lab, he could answer the questions better than myself. However, one night we did make s'mores using a heat gun. It was awesome! |
Re: Team 254 - 2014 Build Blog + Tech Binder
Quote:
|
Re: Team 254 - 2014 Build Blog + Tech Binder
Sorry for asking this a while after this was released. I've noticed you guys have mentioned you needed to be creative to get tubing on your intakes. How was this actually done on the finished robot?
|
Re: Team 254 - 2014 Build Blog + Tech Binder
Quote:
|
Re: Team 254 - 2014 Build Blog + Tech Binder
We didn't end up needing any lube, just two people and compressed air, it worked pretty well. To expand, these rollers were one of my favorite parts of the robot this year; simple, effective and cheap.
|
| All times are GMT -5. The time now is 13:48. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi