> For the complete documentation index, see [llms.txt](https://docs.dietrichs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.dietrichs.com/dc-statics-en/faq-dc-statik/positionsarten/dacher/knaggen.md).

# Knaggen

In DC-Statik können für den Fußpunkt neben normalen Fußpfetten vier unterschiedliche Knaggentypen ausgewählt werden. Abhängig vom Knaggentyp ist der Kragarmquerschnitt reduziert oder hat den vollen Querschnitt. Der Knaggentyp 1 unterscheidet sich durch den Lastabtrag von den Typen 2-4:

**Knagge 1:**\
Der Lastabtrag findet aufgrund von Sonderdübeln statt, die zwischen Knagge und Sparren angeordnet werden. Zur Lagesicherung werden die Bauteile mit Gewindestangen miteinander verbunden.

**Knaggen 2-4:**\
Bei diesen Knaggentypen findet der Lastabtrag über die Kontaktpressung statt. Die Knagge ist in den Sparren eingelassen. Zur Lagesicherung werden die Bauteile ebenfalls mit Gewindestangen verbunden.

<figure><img src="/files/ZkI59Yr2vslxSYvPoJxk" alt=""><figcaption><p>Knaggen-Typen</p></figcaption></figure>


---

# 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://docs.dietrichs.com/dc-statics-en/faq-dc-statik/positionsarten/dacher/knaggen.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.