> 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/showstopper/legacy/showstopper-consolette/making-the-connections/multiple-consolettes.md).

# Multiple Consolettes

In most systems, a single Showstopper 4 Consolette is all that is required to run your show. However, if you need to create separate areas of responsibility for different operators, or automation zones, you can layout your system to have multiple Spikemark computers and matching Consolettes. Probably the most common reason to do this is to split Deck automation and Overhead automation. For some shows, it makes sense to have one operator for all deck pieces, and a second operator to run all flying machinery.

In such a system, you **use one Showstopper Base**, two Showstopper Consolettes, and two Spikemark computers, as shown below. By powering both Consolettes from the same Base, you guarantee that pressing any Emergency Stop button will stop all motion. However, you can arrange your network address scheme so that each Spikemark instance only connects to the relevant Consolette to keep cue control and jogging control isolated between deck & flies.

![](/files/-MhJQuVjuCPW43OqP8Ns)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.creativeconners.com/docs/showstopper/legacy/showstopper-consolette/making-the-connections/multiple-consolettes.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.