> 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/strict-timing-mode.md).

# Strict Timing Mode

Strict Timing mode insists that the motor moves accurately and achieves the cue position within the theoretical time allowed for that movement based on the programmed distance, speed, and acceleration. If the motor cannot achieve the target in the computed time, it will be turned off, regardless of its current position, once the calculated cue time has passed.

{% hint style="info" %}
For shows that have tight timing requirements, this option may be useful. However, it has mostly been included in Spikemark since it was the only mode available in earlier versions of Spikemark. When using this mode, you have to be diligent about [tuning](/docs/spikemark/position-scale/motor-tuning.md) your motors well. Sloppy tuning will result in motors abruptly stopping in mid-move.
{% endhint %}

To ignore your Target Tolerance, and switch into Strict Timing Mode:

1. Select the machine you want in Strict Timing Mode
2. Go to the Advanced Pane
3. Click the check box for Strict Timing Mode

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-35c74e31d21b3bff0e036bc0e04dc3e80363c890%2FStrictTimingMode.gif?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/strict-timing-mode.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.