> 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/showstopper-node-editor.md).
# Showstopper Node Editor
Configuring Showstopper Nodes and Groups
After you have set your [Node ID's](/docs/spikemark/ip-address-and-network-connection/setting-showstopper-node-id.md) and [IP Addresses](/docs/spikemark/ip-address-and-network-connection/setting-showstopper-ip-address.md) for your Showstopper devices, you will want to configure them in Spikemark to easily see which E-Stop in your system is triggered.
{% hint style="danger" %}
Showstopper Status and Node configurations is only available in Spikemark 5 with Showstopper 4 Hardware.
{% endhint %}
Simply, **Open** the **Showstopper Node Editor**
**Enter** a **name** for each Node ID on the Network and **Click** to **Check Box** to make it **Visible** in the **Showstopper Status Window**
**Organize** your E-Stops into **groups** or groups of groups to provide organization for all the E-stop's in your system.
To Create a Group of Showstopper Nodes, **open** the **Showstopper Group Node Editor**
After assigning names to Node IDs and organizing them by groups, see your E-stop Statuses in the Showstopper Status Window.
* **Grey Circle:** Not Connected
* **Green Circle:** E-Stop Released
* **Red Circle:** E-Stop Engaged
---
# 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/showstopper-node-editor.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.
