> 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/pushstick/installation.md).

# Installation

When determining how you will mount your Pushstick v2, keep in mind that the v2 has the ability to pull 700lb. Ensure that the structure you are attaching the winch to can resist greater than the force you intend to move plus the additional pre-tension added into your system through the loop of wire rope.

The frame incorporates mounting holes that are compatible with 1-5/8" Unistrut framing and hardware for ease of mounting.

The V2 can be mounted in any orientation except on its head (with the motor and signal connectors towards the floor). However, mounting the Pushstick v2 to match the ‘Bottom’ view allows the use of Creative Conners, Inc deck hardware and the associated pulleys will align with no fleet-angle.

![](https://3040525219-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MhFI6SSKpm8M7EkrYqp%2Fuploads%2Fgit-blob-5dbb833c08fc286c1fb2204bfb89ee1d7d6d02c6%2FPSv2%20Install%20position.png?alt=media)


---

# 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/pushstick/installation.md?ask=<question>&goal=<user_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.