> 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/drive-communication/drive-communication-compatibility.md).

# Drive Communication: Compatibility

## Compatibility

{% hint style="warning" %}
Stagehands manufactured before 12/06/2021 need to [update parameters](/docs/spikemark/drive-communication/drive-communication-setting-vfd-parameters.md)
{% endhint %}

Drive communication is included with Spikemark 4.0.0 or later and is only available with the Stagehand Apprentice and Stagehand Pro controllers.

The Stagehand Servo, Smart Machines (Pushstick Mini, Spotline Mini, and Spotline Practical) and Stagehand AC Classics do not have the ability to communicate with their drives.

The Stagehand Mini^2 supports this feature as well, though as of this writing, VFD compatibility is limited to Mitsubishi A700/800 and D700 series VFD’s.

Every Stagehand Apprentice and any Stagehand Pro produced after 3/1/2018 ships from the factory with these features enabled.

Stagehand Pro’s built prior to 3/1/2018 require the [RS-485 upgrade](/docs/spikemark/drive-communication/rs-485-upgrade.md) to enable this functionality.


---

# 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/drive-communication/drive-communication-compatibility.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.