> For the complete documentation index, see [llms.txt](https://docs.cartographer3d.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cartographer3d.com/cartographer-probe/need-assistance.md). # Need Assistance? If you're struggling with the setup, configuration or another cartographer issue, we're available on [discord](https://discord.gg/yzazQMEGS2) to help you. If you're having issues within klipper/mainsail, please create a thread in the [Help & Support ](https://discord.com/channels/1165274913624572014/1229798364514750596)section on discord and PLEASE include the following. * Printer.cfg * Klippy.log * Screenshots of the issue if available. * A detailed description of what you were doing at the time of this issue. ### Using Touch? Heres a quick check list of things to check prior to asking for assistance if youre having inconsistent touch results or failures. * [ ] Is cartographer mounted approx within a range of 2.6-3mm **ABOVE** the nozzle tip? [(Tool Here)](/cartographer-probe/installation-and-setup/probe-installation.md#mount-cartographer) * [ ] Is your toolhead completely rigid? * [ ] Checked toolhead for loose screws? * [ ] Checked toolhead for bad wiring? * [ ] Checked A/B or X/Y and Z belt tension? * [ ] Checked lead screws? * [ ] Is your nozzle clean? * [ ] Have you tried turning off crowsnest, adaptive mesh or led\_effects? (Note) --- # 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.cartographer3d.com/cartographer-probe/need-assistance.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.