> 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/spikemark-vantis/6-motor-and-group-details.md). # Motor and Group Details ### **Groups** A Motor Group is a collection of two or more motors that operate together while continuously monitoring each other's status. If a fault occurs on any motor within the group, all motors in the group stop to help protect the load and maintain safe operation. {% hint style="info" %} Locked Motor Groups offer synchronized motion with fault monitoring. Unlocked Motor Groups allow unsynchronized motion to different positions, but still fault monitor across the group. {% endhint %} Motors within an Unlocked Motor Group do not need to share the same target position or travel speed. This flexibility allows multiple motors to work together while executing independent movements. For example, two motors lifting a truss can be programmed to raise and lower the truss while simultaneously tilting it by assigning different target positions or speeds to each motor. ![Stagehand Card](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-1b8289d5a8872749a538e46c8c0aa019bf50936e%2FSpikemark-Vantis-Stagehand-Card-Labeled-2.png?alt=media) 1. The **Lock Icon** is displayed only for grouped machines and indicates the current Motor Group configuration:\ a) A **Locked Group** links all motors together, allowing them to move as a single unit. All motors will respond together and share fault conditions.\ b) An **Unlocked Group** allows each motor within the group to move independently while still sharing fault status. A fault on any motor within the group will be communicated to the entire group. 2. The **Position Delta** displays the difference in position between motors within the group by identifying the current positions of the motors with the minimum and maximum travel positions.\ a) **Min Position** – Displays the motor with the smallest current position within the group, along with its current position value.\ b) **Max Position** – Displays the motor with the greatest current position within the group, along with its current position value. To learn more about how groups work within Spikemark, refer to [Groups](https://github.com/creativeconners/PublicDocumentation/tree/main/spikemark/groups.md). ### **Group Details** To find out more information about a group including what individual axis are controlled within it, simply double tap the group's **Stagehand Card** to access **Group Details**. ![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-69208f1c03a91d4a04858a85b4b822becaff2a55%2FSpikemark-Vantis-Group-Details-2.png?alt=media) From this menu you see and access the following: 1. Make the group **Active** or **Inactive**. NOTE: An Inactive group will not be able to move until Reactivated. 2. **Position Delta**\ NOTE: Adjustments can only be made at the Spikemark PC. 3. **Reset Drives** within the group should you experience a fault during operation. 4. **Connect All** or **Disconnect All** Stagehands from Spikemark NOTE: Disconnected Stagehands will not allow movement of their respective machines within a group 5. **Activate All** or **Deactivate All** machines within the group.\ NOTE: Deactivated machines will not run within the group until reactivated. This is perfect should you need to take a faulted or broken machine temporarily out of a group. 6. Activate or Deactivate individual machines by tapping them in the **Axis/Stagehand List** 7. Add or move the group to a **Spike** or a one time **Move to Position** ### **Motor Details** Similar to **Group Details**, you need only double tap a single **Stagehand Card** to access its **Motor Details**. ![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-c6fb08f2c31404780d04502ef74cc25b5dca2a11%2FSpikemark-Vantis-Motor-Details-Page-3.png?alt=media) You'll notice a very similar screen that allows a lot of the same accessibility as the **Group Details** menu with a few extras. You can now also: 1. Turn **Load Alarms** On/Off 2. **Reset Position** if you notice one of your axis is off from what is displayed. 3. Access **Motor Status** which gives you a lot more incite into why a motor is faulted or is not able to move. NOTE: Green means go! If you notice one of your parameters is showing red, try reseting the drive. 4. Access **Motor Properties** where you can adjust a variety of things such as: a) **Max Fdw/Rev Position** to further limit the travel of a motor b) **Max/Min Jog Percent** to adjust the sensitivety of the **Jog Paddle** c) **Default Speed, Accel and Decel** to adjust how fast your machines move when moving to a **Spike** or **Move to Position**. --- # 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/spikemark-vantis/6-motor-and-group-details.md?ask=&goal= ``` `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.