# Out of range after the relocation of CR touch

**URL:** <https://klipper.discourse.group/t/out-of-range-after-the-relocation-of-cr-touch/15269>\
**Category:** General Discussion\
**Created:** [March 28, 2024, 1:13am UTC](https://klipper.discourse.group/t/out-of-range-after-the-relocation-of-cr-touch/15269 "2024-03-28T01:13:01Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![jmdutil](https://avatars.discourse-cdn.com/v4/letter/j/b4bc9f/32.png) [@jmdutil](https://klipper.discourse.group/u/jmdutil)\
**Post date:** [March 28, 2024, 1:13am UTC](https://klipper.discourse.group/t/out-of-range-after-the-relocation-of-cr-touch/15269/1 "2024-03-28T01:13:01Z")

</div>

### Basic Information:

out of range after the relocation of CR touch  
 Printer Model: Ender 3 s1 with sonic pad.

[klippy.log](https://klipper.discourse.group/uploads/short-url/bsCG8TTa5nGZK9IaJ0kR3HIcpNN.log) (3.0 KB)

I have relocated my CR touch on mt 3nder 3 s1.  
I have to update my X/Y offset for my CR touch to:  
x\_offset: -46.8  
y\_offset: 0

I went to the config file and updated these parameters.  
When I send a bed level, the probe is very close to the bed (2-3mm) and @ the 7/8 measurement I receive the error message that I am out of range (246.80 xxxxx)

I have read the other discussion regarding the same issue as mine. However, I still can’t make my bed level go as it was.

This is the file I have printed

> **[Ender 3 S1 Zero Offset CR Touch Mount by JHenley01 | Download free STL model...](https://www.printables.com/model/257460-ender-3-s1-zero-offset-cr-touch-mount)**

regards,

---

<div class="post-metadata">

**Author:** ![EddyMI3D](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/eddymi3d/32/1981_2.png) [@EddyMI3D](https://klipper.discourse.group/u/EddyMI3D)\
**Post date:** [March 28, 2024, 6:34am UTC](https://klipper.discourse.group/t/out-of-range-after-the-relocation-of-cr-touch/15269/2 "2024-03-28T06:34:12Z")

</div>

> [@jmdutil](#):
>
> Printer Model: Ender 3 s1 with sonic pad.

You may read this:

> [@Creality Sonic Pad and Alternatives](https://klipper.discourse.group/t/creality-sonic-pad-and-alternatives/6324/1):
>
> Creality Sonic Padexclamation Update Since July 11, 2023, Creality seems to have [released a firmware](https://www.creality.com/pages/download-creality-sonic-pad?spm=..page_1934481.products_display_1.1&spm_prev=..product_afecb672-1369-4c48-ba2d-f0cd762126a6.header_1.1) with a newer Klipper version. Again, they have not released the sources for this and the other components as required by the GPL license. Again, they are violating the OSS license and making money off the work of others. Background The Creality Sonic Pad is intended to be a “one-stop” solution for Klipper. A SBC running Klipper along with Moonraker, Fluidd, Mainsail and KlipperScreen A …

The Sonic Pad does not produce a usable klippy.log.  
There is no chance to find out why what is gong wrong.

---

<div class="post-metadata">

**Author:** ![jmdutil](https://avatars.discourse-cdn.com/v4/letter/j/b4bc9f/32.png) [@jmdutil](https://klipper.discourse.group/u/jmdutil)\
**Post date:** [March 28, 2024, 11:18am UTC](https://klipper.discourse.group/t/out-of-range-after-the-relocation-of-cr-touch/15269/3 "2024-03-28T11:18:54Z")

</div>

So the out of range error is generated because of this?

---

<div class="post-metadata">

**Author:** ![jmdutil](https://avatars.discourse-cdn.com/v4/letter/j/b4bc9f/32.png) [@jmdutil](https://klipper.discourse.group/u/jmdutil)\
**Post date:** [March 28, 2024, 11:19am UTC](https://klipper.discourse.group/t/out-of-range-after-the-relocation-of-cr-touch/15269/4 "2024-03-28T11:19:45Z")

</div>

![20240328_000701](https://global.discourse-cdn.com/free1/uploads/klipper/original/2X/d/d22c3361fbe35b3769236064700feb01340ae58b.jpeg)

---

<div class="post-metadata">

**Author:** ![Sineos](https://yyz2.discourse-cdn.com/free1/user_avatar/klipper.discourse.group/sineos/32/18_2.png) [@Sineos](https://klipper.discourse.group/u/Sineos)\
**Post date:** [March 28, 2024, 11:35am UTC](https://klipper.discourse.group/t/out-of-range-after-the-relocation-of-cr-touch/15269/5 "2024-03-28T11:35:57Z")

</div>

> [@jmdutil](#):
>
> x\_offset: -46.8  
> y\_offset: 0

Since you adapted the offsets, you need to adapt the limits of your bed mesh as well as it is relative to the probe coordinates. See [Understanding X and Y Axes Limits and Homing](https://klipper.discourse.group/t/understanding-x-and-y-axes-limits-and-homing/10779#mesh-coordinates-vs-nozzle-coordinates-6)

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/free1/uploads/klipper/original/1X/64419bf2aac6639e6ef5cef200dcd456b0a01ac3.png) [@system](https://klipper.discourse.group/u/system)\
**Post date:** [May 27, 2024, 11:36am UTC](https://klipper.discourse.group/t/out-of-range-after-the-relocation-of-cr-touch/15269/6 "2024-05-27T11:36:33Z")

</div>

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.
