> 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/stagehand/stagehand-apprentice-2/stagehand-apprentice-2-features.md).
# Stagehand Apprentice 2: Features
Let’s talk about all the Capabilities and Features you can expect from this powerhouse motion controller:
## New Features
### Split Acceleration and Deceleration
Write more complex cues with different ramp up and ramp down times
### Large Graphical OLED Display
See more information at a glance rather than cycling through all the fault codes
### L21-30 Power Input
The Stagehand Apprentice now comes with a more easily attainable input power connector to connect to more attainable power distributions, including the option to custom order it with our traditional L15-30 Power Input Connector.
### VFD Parameter Library
Change VFD Parameter Set from Spikemark (5.5.2 or later) and not a VFD keypad
## Existing Features Still Here
* Onboard controls for jogging manually
* Spikemark connectivity with dead-simple addressing and plain ethernet networking
* Limit Override Buttons
* Discreet Interlock Circuits
* Position Feedback with PID Error Correction - in conjunction with an Encoder
* Circuit Protection
* 3 circuit breakers and two (2) time delay fuses protecting the controls and encoder
* All of this is packed in a 6U Rack Enclosure
## Capabilities
* 5 HP max motor
* 3 Phase 200VAC-240VAC Input Power
* 230VAC 3 phase motor output
* 200VAC brake circuit
* 60Hz Speed \*can be overspeed to 120Hz at half capacity.
---
# 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/stagehand/stagehand-apprentice-2/stagehand-apprentice-2-features.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.