> 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/features/scanning.md). # Scanning Cartographer implements a Klipper [probe](https://www.klipper3d.org/Config_Reference.html#probe) interface and exposes functionality similar to what you'd expect from an induction probe, with the benefit of eddy current for accurate measurements. This means that homing, `QUAD_GANTRY_LEVEL` and `Z_TILT_ADJUST`, simply works as expected, but looks slightly different. Cartographer will lower until the trigger point of 2 mm and will then take 20 readings of the frequency to determine the exact distance.\ This means there is on reason to lift the probe and run a probing move again. #### Measure probe accuracy We can check the accuracy of the scan by running `PROBE_ACCURACY`.\ This will run a few probes and output some statistics, like seen below. > probe accuracy results: maximum 2.000898, minimum 1.999665, range 0.001233, average 2.000008, median 1.999758, standard deviation 0.000449 ## Bed mesh calibrate We can make use of the probes ability to take rapid measurements by scanning as we move quickly across the bed. After setting up Cartographer, your `BED_MESH_CALIBRATE` macro will by default do this. To take full advantage, we should increase the density of the mesh. We should be able to move across the bed with a speed of at least 300 mm/s. To fall back to the default Klipper behavior, run `BED_MESH_CALIBRATE METHOD=automatic` . --- # 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/features/scanning.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.