> 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/machinery/spotline/operation.md). # Operation Below is a flow chart for proper Spotline operation. It is important for the end user to understand and recognize the normal sequence of operation to be able to quickly recognize problems.
## Inspection Checklists The following is a checklist to inspect the Spotline prior to rigging. It is necessary to perform the checklists detailed below to ensure all components of the Spotline are operating correctly. If any component fails the test do not use the Spotline and consult Creative Conners Inc. ### Pre-Install The following items should be inspected each time the Spotline is installed. #### Mechanical o Gearmotor Key Engaged o Drum Key Engaged o Brake Key Engaged o Gearmotor Retaining Ring Installed o Brake Retaining Ring Installed o Set Screws on Drum are tight o Chain tension is correct on Limit Switch o Drum Grooves are not damaged or crushed #### Electrical * Spotline runs correctly in Manual Jog mode o Stagehand Pro displays encoder counts while jogging o Counts must increase when jogging FWD * Ultimate FWD, FWD, Ultimate REV, and REV limits operate correctly * Run Brake Test Sequence o LCD displays encoder counts correctly ### Preshow The following items should be checked each day the hoist is in service. o Run brake test sequence o Check Forward Limit o Check Reverse Limit o Ensure encoder is counting correctly o Confirm cable is wrapping onto drum correctly --- # 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/machinery/spotline/operation.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.