> 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/legacy-manuals/deck-chief/getting-started.md).
# Getting Started
The Deck Chief is simple motor controller designed for theatre. For applications where ease-of-use is paramount, the Deck Chief provides intuitive push-button operation with variable speed, soft-start, limit switch inputs, and an optional remote control pendant. For traveler curtains, roll-down screens, display turntables, simple slip stages, or many other motorized devices found on stage the Deck Chief is ideal.
This manual will guide you through:
* Unpacking
* Installation
* Powering up
* Operation
If you need help along the way contact us on our website ([creativeconners.com](https://www.google.com/url?q=http://www.creativeconners.com\&sa=D\&source=editors\&ust=1661263884714038\&usg=AOvVaw30dEyss7eApwQKhPXvefG6)), via email (), or by phone (401-289-2942 x2)
## What’s in the box?
Inside the box you should find:
* Deck Chief motor controller
* 12-pin remote pendant terminator plug
If any of these items are missing, please contact us immediately for a replacement.
If you purchased any power cables, limit switches, or other accessories, those items are packaged separately.
## Deck Chief Features
The Deck Chief was created to satisfy the need for simple and safe variable-speed operation of motorized curtains, turntables, projection screens and other effects in theatrical facilities and live event venues. It features:
Front Panel Features
Electrical and Control Connections
---
# 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/legacy-manuals/deck-chief/getting-started.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.
