Blog · · 5 min read

CAD models for purchased parts: download, borrow, or build from the datasheet?

Most of a machine is bought: motors, bearings, guides, sometimes a whole robot. Where their CAD models come from, what the terms let you do with them, how to check a downloaded STEP file, and when a model built from the datasheet is the better choice.

Open any machine design and count the parts you actually design yourself: brackets, plates, a frame, maybe a housing. Everything else is bought. Screws, bearings, linear guides, motors, sensors, connectors, sometimes a whole industrial robot. Each of them needs a 3D model, or you can't check whether it fits, collides or can be mounted.

In Go FANUC Go, an open-hardware project on makemachine.ai, the biggest bought part weighs about 560 kg. It is an existing industrial robot that a new mobile base has to carry out of a room, down a ramp and to a new place. The base is designed around the robot, so the robot's model decides almost everything. How that model came about says a lot about bought parts in general.

Three places a part model can come from

The manufacturer or a distributor. Many suppliers offer CAD downloads, usually as STEP files, often behind a login. These are the most accurate models you can get, and they carry the right part number.

A community library. Engineers share huge numbers of models online. The choice is wide and the quality uneven: you may get a mesh instead of a solid, the wrong size from a product family, or a file without any license statement.

Your own model, built from the datasheet. Many parts don't need the original file. A bearing, an aluminium profile, a motor flange or an enclosure can be modeled from the dimensions in the datasheet. You own that model, you can share it, and you know exactly what is in it.

What happened with the robot

When the project needed the robot, a complete, free model of that exact type was only available with an account. So the CAD step first modeled it from the dimension drawings in the manufacturer's manual: seven links with their real housing contours, movable in all six axes. It was drawn slightly larger on purpose, which keeps clearance checks on the safe side.

One version later, a model from a community library was available. It covered two payload variants of the same arm in one file, it had been uploaded years earlier, and its page named no license. The axis distances and the mounting bolt pattern matched the manual exactly, and the side view matched the drawing to 97 %. In its driving pose, the robot on its base came out 1,829 mm high, 71 mm below the door lintel. The self-built model had left 62 mm. Nothing on the base had to change.

Two lessons:

  • A careful model from the datasheet was good enough to design the base. The downloaded model confirmed it rather than replaced it.
  • Without a license statement, the downloaded file is for internal checks only, with credit to its author. It can't travel with the project files.

Licenses matter more than you think

If you want to sell a design, hand it over to a customer or publish it as open hardware, every file in it needs terms that allow that. A community model "without license" doesn't mean free to use. It means nobody has given you permission.

Supplier terms differ from catalog to catalog, so read the ones that apply. A common pattern is that the model may be used to design with that product, and for little else. It comes as-is, without any right to the product itself, and copying the catalog is forbidden. Some catalogs even forbid using their models to train AI. Publishing or handing on the file is a different use, and the terms rarely grant it.

That is why the platform prefers data it may pass on: standard parts, models built from datasheets and libraries with open licenses. A downloaded model is used when it really improves the design, for example an exact outer shape or a mounting interface. It is then listed separately, with source and license, as not transferable.

Check every downloaded model

A file that opens is not yet a file you can trust. Before a downloaded model goes into a design, check:

  • Units. A model in inches read as millimetres comes out 25.4 times too small.
  • Origin and orientation. Where is the zero point, which way is up? Mounting is easier when the origin sits on the mounting face.
  • The exact variant. Sizes in a product family look alike. Compare the part number and two or three key dimensions with the datasheet.
  • Solid or mesh. A mesh shows the shape, but you can't measure edges or cut it cleanly.
  • One body or an assembly. A robot arm needs separate links, or you can't put it in other poses.
  • Level of detail. Modeled threads and lettering make files huge and slow without improving the design.
  • Is it a model at all? Sometimes a "download" is a login page saved under a CAD or PDF file name.

Most of these checks are quick work for AI: reading the units, measuring key dimensions and comparing them with the datasheet. Whether a license fits your plans stays your decision.

Placeholders in real size

Waiting for a model shouldn't stop the design. Until the real file arrives, a placeholder works if it has the right outer dimensions and the right mounting points: flange, hole pattern, shaft. A box in roughly the right place is not enough. A placeholder that is too small hides collisions you will otherwise find on the workbench.

A library that grows with every project

The most wasteful step is searching for the same model twice. Every model and datasheet you download should be stored once, with source, date, part number and a license note. When a supplier sends an updated file, it becomes a new revision, and each project keeps the revision it was designed with until someone moves it on. Files from customer projects stay with that customer.

makemachine.ai works this way. Every part model and datasheet a project downloads goes into a shared parts library, and the CAD step of the next project looks there before it searches online. When the next project needs that robot, it starts with the model and the manuals instead of an empty search.

The short version

  • Most of a machine is bought. Plan where each part model comes from.
  • Prefer models you may pass on: from datasheets, standard parts or openly licensed libraries.
  • No license statement means no permission. Keep such files internal and credit the author.
  • Check units, origin, variant, solid or mesh, and structure before you use a downloaded model.
  • While you wait, use placeholders in real size with real mounting points.
  • Store every download once, with source, license and revisions, so the next project starts ahead.

Follow the real project on the Go FANUC Go project page. For the difference between meshes and real CAD, read AI 3D model or real CAD?, and for keeping invented numbers out of a design, can you trust AI with engineering numbers?

Watch hardware get built by AI. Follow public projects on makemachine.ai, read every result in full and get an email when there is something new.

Get started See the live projects

More from the blog

Open-hardware projects built with AI