> For the complete documentation index, see [llms.txt](https://docs.creativeconners.com/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.creativeconners.com/docs/spikemark/position-scale/position-scale/manually-calculate-position-scale.md).

# Manually Calculate Position Scale

Confirm that the current Position Scale field is set to “1” in the Position section of the Stagehand Properties Panel.

{% hint style="success" %}
This will make sure Spikemark is reading 1 encoder count per actual encoder count (cts/ct)
{% endhint %}

[Reset your position](/docs/spikemark/position-scale/reset-position.md) to 0

In the Local Controls section of the Jog Workspace, run the motor forward or reverse as far as you safely can. Record the Travel Distance

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-ce8c3ad24109c1effadb101e5fa9fcc8d86db075%2FJoggin.gif?alt=media)

At the top of the Stagehand Properties Panel, note the number of encoder counts that are traveled.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-cff7cadc919e0c394500575cc5671d3b494369ba%2FCts.png?alt=media)

$$Position Scale = EncoderCounts/TravelDistance$$

{% hint style="info" %}
For example: 1,245,012 encoder counts / 125.5 inches = 9,920.41 encoder counts per inch.
{% endhint %}

Enter the result from the previous step into the Position Scale field and then select the appropriate units from the Position Units drop-down menu.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-5648a027232ee5f7106d332a7f488c976841f969%2FCalculatedScale.png?alt=media)


---

# 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://docs.creativeconners.com/docs/spikemark/position-scale/position-scale/manually-calculate-position-scale.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.