> For the complete documentation index, see [llms.txt](https://manual-1-3.karamba3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://manual-1-3.karamba3d.com/3-in-depth-component-reference/3.1-model/3.1.11-point-mass.md).

# 3.1.11: Point-Mass

Karamba3D is capable of calculating the natural vibration modes and frequencies of structures (see section [3.5.7](/3-in-depth-component-reference/3.5-algorithms/3.5.7-natural-vibrations.md)). For results to match reality the inertia properties of a structure need to be modelled correctly. Masses of elements (e.g. beams, trusses, shells) are automatically taken care of. All other items need to be included via point-masses.

{% hint style="info" %}
Be aware of the fact that masses defined with the **“Point-Mass”**-component do not have a weight but inertia only! However they add to the mass of a model as output at the **"Assemble"**-component.
{% endhint %}

Thus they effect only the calculation of natural frequencies. The “Point-Mass” component expects a mass in kilogram at its input-plug **“Mass”** (see fig. 3.1.11.1). Nodes where masses shall sit can be identified by supplying node indexes or positions (just like for point-loads). Point masses get displayed as green spheres. Their diameters result from the volume calculated as mass divided by density. The latter defaults to $$7850kg/m^3$$ (steel) and can be provided at the input-plug-**“rho”**.

![Fig. 3.1.11.1: Vibration mode of beam with point mass in the middle](/files/-M9XuT_i4asTdz_npyJW)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://manual-1-3.karamba3d.com/3-in-depth-component-reference/3.1-model/3.1.11-point-mass.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.