# Paper: AMB Design Spreadsheet v3

With kickoff quickly approaching, I feel this is a good time to share the updated version of my design calculator spreadsheet. It features calculations that are very helpful for designing the mechanical, electrical, and pneumatic aspects of your robot.

Please note that you need to enable macros for the Sprint Distance Calculator to work.

Changes since the last version:

• Added Pneumatics Calculator, which allows you to predict air volume usage based onthe number and size of cylinders, tanks, compressors, etc.
• Added reverse shifting Sprint Distance Calculator
• Fixed bugs with Sprint Distance time calculation
• Fixed bug with Ratio & Distance Calculator
• Miscellaneous bug fixes
• Minor UI changes

As always, if you have any questions on how to use the spreadsheet or find any problems with the calculations, please donâ€™t hesitate to reach out either in this thread topic or by PM.

10 Likes

We seem to be getting errors on the Sprint Distance tab for time to distanceâ€¦

Interesting. Did you enable macros? I downloaded it fresh on a new computer and it seemed to be working fine. Can you send a screenshot so I can see what inputs youâ€™re using and what error youâ€™re getting

1 Like

I think itâ€™s because weâ€™re using Google docs and not Excel

Oh yeah, that would definitely do it. The Sprint Distance Calculator uses VBA code to run the timing simulations, so copying over to Google Docs wouldnâ€™t bring that code along too

Could you put a note somewhere on the sprint distance calculator tab explaining what the different â€śxâ€ť, â€śvâ€ť, â€śaâ€ť, and â€śslipâ€ť values on the chart mean? Charts/formulas that donâ€™t define their variables (in plain english) are one of my biggest pet peeves.

Otherwise great calculator.

Iâ€™m assuming that itâ€™s the following:
x - distance traveled
v - velocity
a - acceleration

1 Like

Sean is right. I assumed those were pretty standard variable names, but I guess some people might not pick up on that right away. Slip shows when the wheels are slipping (i.e. the robot breaks traction). I included a key explaining these terms for whenever I post the next release.

Thanks for the compliment

1 Like

# AMB Design Spreadsheet v3_2.xlsm (165.4 KB)

Version 3.2 - A few more bugfixes and improvements:

• Fixed incorrect NEO motor data
• Redesigned imperial metric selection to be more intuitive
• Updated COTS sprocket and belt sizes; removed inaccurate pulley and gear sizes
• Chain/Belt C-C Calculator now includes the suggested C-C addition and also automatically populates the correct pitch based on the chain/belt type selected
• Can now use stall voltage as an input for the Mechanism Calculator
• Added key for Sprint Distance Calculator graph

# AMB Design Spreadsheet v3_3.xlsm (169.3 KB)

Version 3.3 - Fixed bugs created in v3.2

• Corrected calculation mistake for stall voltage input in Mechanism Calculator
• Fixed bug with imperial/metric selection on all calculators

The sprint time always return as a error, only my problem?

I just downloaded a fresh copy and it didnâ€™t give me any errors. Make sure you enabled macros, otherwise you will certainly get errors (specifically #NAME errors). If thatâ€™s not the problem, can you send me a screenshot of the sheet (either posted here or by PM).

# AMB Design Spreadsheet v3_4.xlsm (165.9 KB)

Version 3.4 - Bug fixes

• Fixed stall voltage calculation for multiple-motor mechanisms
• Fixed erroneous motor data
1 Like

How do we input actuation times or how many times it will be used during the match for the pneumatics tab?

There are three inputs for that for each action. Time Per Cycle defines how much time between each cycle start (i.e. from extension to extension, or period). Start Time and End Time are pretty much exactly what they sound like: what time does the first action happen and when does the last happen. So for example, if your action starts after autonomous and ends at the start of the endgame you should put 15 for Start Time and 130 for End Time (20s before the 150s match ends).

The model makes a few assumptions. The â€śsimulatorâ€ť has a resolution of 1 second. Any action that fires less than once per second shows both extension and retraction at the beginning of the cycle (worst case scenario). An action that happens more than once a second happens that number of times per second, every second. You wonâ€™t see the sawtooth shape on the graph because itâ€™s interpolating between second marks, but in reality it will be there.

As Iâ€™m writing this, I found a bug in the calculation that makes it not work for non-whole number periods greater than 1. Iâ€™ll be pushing an update to fix that soon. In the meanwhile, you can use multiple of the same actions with different periods to emulate the same thing.

Iâ€™m trying out a new method for hosting my spreadsheet that will allow me to push updates so the most recent version is at the top of the page rather than having to find the most recent version in the middle of the thread. Iâ€™m hosting the Excel document on GitHub, and using GitHub Pages to make an auto-download page. If this works well, Iâ€™ll be using this to host future versions of my spreadsheet (and possible other white papers I post that I plan on updating in the future).