> 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/machinery/pushstick/making-the-connections.md).
# Making the Connections
Once you have your Pushstick v2 mounted, you will need to plug it into a Stagehand controller. The Pushstick v2 is manufactured to be compatible with either the Stagehand Pro or the Stagehand Apprentice, but not both.
## PRO MOTOR
Power input for both the motor and brake have been combined into a single IRC - (24B) 4P/8P Male Pins connector. The motor and brake connectors are available from several manufacturers and suppliers. Refer to the following diagram for details.
?alt=media)
## APPRENTICE MOTOR
Power input for both the motor and brake have been combined into a single IRC - 44mm X 27mm (6B) 6P 16A Male Pins connector. The motor and brake connectors are available from several manufacturers and suppliers. The 5HP, 208VAC three phase Stagehand Apprentice power cord will output 220VAC across pins 5 & 6. Refer to the following diagram for details. The pins for the motor cables are Han E style, with the motor input (pins 1-3) being 12AWG and the brake input (pins 4-6) being 16AWG.
## SIGNAL
Connecting the Encoder, Forward/Reverse/Ultimate limits is accomplished through a single locking connector (IRC - 44mm X 27mm (6B) 24P 10A).
The limit switch inputs are used to protect against the motor traveling too far in any direction. This prevents damage to the machine and scenery and can prevent injury. When running in a cue, this is one of the safety features that guards against encoder failure. When jogging manually, this keeps you from accidentally traveling too far.
The encoder connected to the machine uses a quadrature differential line driver encoder to give incremental position feedback to Spikemark.
?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/machinery/pushstick/making-the-connections.md?ask=&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.