Updated: Mar 27
In pursuit of creating assembly instructions for the drone landing platform our team ran into issues creating a concise BOM (bill of materials). In Fusion 360 when a component is mirrored it will be saved under a new name. This naming scheme has been discussed previously on the Fusion 360 blog here. You can see the naming scheme effecting the total quantities in the BOM in the drawing below:
In modeling the drone landing platform we mirrored many component to avoid having to import every bracket on every connection.
The easy fix to avoid the conflict in the naming scheme would be to not use the mirror function to populate the model with components. We needed iterated quickly in CAD and importing every component in would take too long.
Initially the team used google sheets to take the csv output form the BOM in Fusion 360 to sum up the quantiles of equivalent parts. However user error could effect the output of the part quantities as users had to ensure that the correct cells were selected to sum up.
By creating a script we would eliminate these extra steps.
There were a couple of requirements
1) account for both 8020 part numbers and McMaster-Carr part numbers
a) 8020 part numbers are 4 numbers + letters (appending)
b) McMaster-Carr part numbers are 7-8 characters of numbers and letters
2) account for miscellaneous named components unique to the team and without part numbers
3) output as csv format for easy copy paste back into Fusion 360 drawings
The low level flow of the script:
1)opens up csv
2)line by line check if name is 8020 or McMaster
3)check if name is a miscellaneous part
4) remove extra bits of naming on the part and isolate part numbers
5) document part number and quantities in dictionaries
6) combine all dictionaries of part number and quantities
7) output as csv format
When all was said and done this script replaced about 20 minutes of potentially inaccurate work into a couple of seconds.
Find the script on GitHub here
1) include table of both 8020 and McMaster-Carr part numbers to output both
2) consider having screw count included in how many screws is needed for each bracket to get estimates of hardware purchasing
3) integrate it into Fusion 360 as a script accessible within the UI
4) model each component individually in to bypass need for the script