paper: Calculating for Requirements: a Systems Engineer's Mechanical Calculator

[JesseK]

Thread created automatically to discuss a document in CD-Media.

Calculating for Requirements: a Systems Engineer's Mechanical Calculator by JesseK

[ahollenbach]

whew. That's downright impressive. Good work! Not only does it look good, but that is a phenomenal system you developed.
One thing (cosmetic only) - some pages you forgot to change the title...but it doesn't take away a single bit from the awesomeness!

[JesseK]

Updated to reflect a proper analysis using Wolfram Alpha with Ether's equations to solve for Time as a function of distance to goal, gearing, mass, and radius. The new file size is reduced by 80%!

The goal for this new revision is to get the final #'s within 10% of what's seen on the field while also exposing designs that may burn a motor out over the duration of a competition. It will also serve as the foundation of an extension to Karthik's strategy presentation for DC-area teams.

Note -- the product log function winds up being so negligible in good designs that I don't bother with Newton's method to calculate it. It does expose bad designs, yet there are also other indicators of 'bad design' that will become apparent in the graphs.

John, here's your proverbial idiot button

[badtkee]

Wow this is amazing!!

I just had 1 quick (and hopefully easy) question. How long is a match?

[JesseK]

Originally Posted by badtkee

How long is a match?

Typically tele-operated period is 120 seconds. Autonomous varies from year to year (15-30s).

[badtkee]

so if i say it does the objective 10 times in a match, the calculator does it 10 times in 120 seconds? I'm trying to use the calculator to see how much battery I need. I need my robot to run for 45 min