> For the complete documentation index, see [llms.txt](https://help.besmart.software/t4i/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.besmart.software/t4i/commands-overview/annotations/diameter-h7.md).

# Diameter H7

## Command Description

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FYMadrcQe4mhA6yEoxJT3%2Fimage.png?alt=media&amp;token=34d9e281-4eae-4572-bd43-a6302cb14ee9" alt=""><figcaption></figcaption></figure>

This command adds the diameter symbol before the dimension text and the fits symbol (or just the tolerance for the hole or shaft) after the dimension text. Fits symbols can be adjusted in Holixa T4I settings.

## Command Location

* Drawing environment

## Command Settings

`Be.Smart T41 ribbon -> Be.Smart T4I -> Edit settings -> Other tools tab -> Diameter H7`.

<figure><img src="https://4060565498-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FL8qMZuBhZUXGRVospdct%2Fuploads%2FeWfB2P8HeKQF7w30XfO1%2Fimage.png?alt=media&amp;token=5600c76f-726f-4d65-be3e-7d807c04447d" alt=""><figcaption></figcaption></figure>

The values of the fit can be changed to the most often used, or any of the fields can be left empty.

## Workflow Overview

1. Run the command.
2. Select the dimension.

{% hint style="info" %}
The command can also be used in reverse order (first select the dimension (multiple dimensions) and then run the command).
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://help.besmart.software/t4i/commands-overview/annotations/diameter-h7.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.