> 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/show-control/osc/osc-input-tirgger/motor-commands.md).

# Motor Commands

### Motor Position

#### /motor/{motor\_name}/position \[number]

If **number** is present then Spikemark will attempt to reset **motor\_name**'s position to **number**. If **number** is not set then Spikemark will send a data message back with **motor\_name**'s current position.

### Motors Spike Position

#### /motor/{motor\_name}/spike/{spike\_name}/position \[number]

If **number** is present then Spikemark will attempt to set the position of **motor\_name**'s spike with the name **spike\_name**. If **number** is not set then Spikemark will send a data message back with the position of **moto\_name**'s spike with the name **spike\_name**.

{% hint style="warning" %}
This will update a spikes position which will affect every cue that uses the spike.
{% endhint %}

### Motors Spike Factor

#### /motor/{motor\_name}/spike/{spike\_name}/factor \[number]

If **number** is present then Spikemark will attempt to set the factor of **motor\_name**'s spike with the name **spike\_name**. If **number** is not set then Spikemark will send a data message back with the factor of **moto\_name**'s spike with the name **spike\_name**.

{% hint style="warning" %}
This will update a spikes factor which will affect every cue that uses the spike.
{% endhint %}

### Motors Spike Offset

#### /motor/{motor\_name}/spike/{spike\_name}/offset \[number]

If **number** is present then Spikemark will attempt to set the offset of **motor\_name**'s spike with the name **spike\_name**. If **number** is not set then Spikemark will send a data message back with the offset of **moto\_name**'s spike with the name **spike\_name**.

{% hint style="warning" %}
This will update a spikes offset which will affect every cue that uses the spike.
{% 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://docs.creativeconners.com/docs/spikemark/show-control/osc/osc-input-tirgger/motor-commands.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.