> 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/floorpocket-v2/get-moving/write-cues.md).
# Write Cues
## Add Floorpocket v2 to Show
Add the Floorpocket v2 from the Machine Library.
## Reset Zero
There are two physical locations where you typically set Zero for a lift
1. With the platform all the way down, just before striking the Reverse Limit.
2. With the platform all the way up at Stage Level. You will program in Negative numbers for writing cues.
Either way, To Reset the current position to Zero:
1. Jog the machine to where you want to set Zero
2. Click the position read out in Spikemark
Change the current position to 0.0.
## Set fwd and rev soft limits.
Soft limits should be set just inside of the initial hard limits. Soft Limits prevent you from writing cues beyond these positions.
Important Note: The Floorpocket is still able to be jogged past the soft limits.
## Write Test Cues
Write a slow cue to run up and another to run down.
Write a med cue to run up and another to run down.
Write a fast cue to run up and another to run down.
---
# 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/floorpocket-v2/get-moving/write-cues.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.
