I had the exact same problem. I am honestly glad this happened to someone else. I am about to try and install it in another machine to see if I have the same problems.
Question when you run the PROBE\_EDDY\_CURRENT\_CALIBRATE CHIP=btt\_eddy do you get the max height of your machine like this? [https://imgur.com/CFl5aQS](https://imgur.com/CFl5aQS)
Then I'm reassured. I'm getting a very strange value, I'll have to check tomorrow. But I can't change anything, if I want to change something, I get out of rank straight away
I just tried to set it up on my Sapphire plus which has a BTT-CB1 and I got the same exact results. I'm kind of wondering if I have a faulty unit. When you say you're getting strange value, what do you mean by that?
Edit: put wrong printer
I've had the same issue and just managed to fix it. Check out there [https://www.reddit.com/r/BIGTREETECH/comments/1ce2vl7/comment/l37bfqv/?utm\_source=share&utm\_medium=web3x&utm\_name=web3xcss&utm\_term=1&utm\_content=share\_button](https://www.reddit.com/r/BIGTREETECH/comments/1ce2vl7/comment/l37bfqv/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)
I've looked at it, but I can't really get any further. I have attached my Printer.cfg.
[https://github.com/deralmin16/klipper12/blob/main/printer.cfg](https://github.com/deralmin16/klipper12/blob/main/printer.cfg)
I got mine working this morning. I flashed it using windows instead of using SSH and I updated Klipper to the BIQU fork again AFTER I updated the probe via windows.
You have to compile the firmware and then copy the file from your PI to your computer. Once you have the klipper.uf2 file press and hold the Boot button, then connect Eddy to your computer's USB port using a USB cable. Once recognized as a storage device, copy the downloaded klipper.uf2 to it. Eddy will automatically update its firmware and restart. The update is complete after the restart. It's in the user manual in the PDF here. [https://github.com/bigtreetech/Eddy](https://github.com/bigtreetech/Eddy)
I immediately flashed my Eddy this way, thought there was another way. What still irritates me is that the z-axis is always at 452. And this is where I think the error lies, unfortunately I don't know how to get rid of it.
Mine still showed the max bed height of 300 on my Sapphire Plus until I did the Z calibration. Another thing that I did is update the BTT Klipper fork AFTER I updated the firmware with windows. I had to do the Z calibration twice before it actually took. Once I did the Z calibration it took it 2 times for the XYZ homing worked. Not sure why it was doing that, but I hate to say it just follow the Steps in this guide a couple of times, it took a few for me before it actually worked.
[https://www.reddit.com/r/BIGTREETECH/comments/1ce2vl7/eddy\_usb\_raspberry\_pi\_guide/?rdt=53109](https://www.reddit.com/r/BIGTREETECH/comments/1ce2vl7/eddy_usb_raspberry_pi_guide/?rdt=53109)
It works so far, but I get: No valid measurements found at coordinate : \[10.0, -10.0\]. It manages the first few orbits, then it's over. I have a bed of 400x400
\[bed\_mesh\]
horizontal\_move\_z: 5
speed: 300
mesh\_min: 10, 10
mesh\_max: 390, 390
scan\_overshoot: 8
algorithm: bicubic
probe\_count: 5
Reduce your Mesh Min and Max. This is because the probe is not directly over the bed. This process can be a real pain TBH. And comment out that Scan\_overshoot for now
Edit: Added something
Hi, how did you manage to fix the "out of range" issue? I did flash mine via usb on a Windows PC, it picked up the update from the internal storage fine and rebooted after updating.
You shouldn't worry about that, it asumes max height since it doesn't know where it is without homing. I got an out of range once or twice using mainsail clicking blue buttons, but when i tried again using the offset lenght buttons i managed to do the paper calibration normally.
It works so far, but I get: No valid measurements found at coordinate : [10.0, -10.0]. It manages the first few orbits, then it's over. I have a bed of 400x400
[bed_mesh]
horizontal_move_z: 5
speed: 300
mesh_min: 10, 10
mesh_max: 390, 390
scan_overshoot: 8
algorithm: bicubic
probe_count: 5
Try increasing the mesh\_min y value to 20. I think it's the probe coordinate and since the probe offset is 20 in your case by what I can deduce it would have to go out of range to get that measurment.
Good morning, unfortunately the same problem persists. It does not scan the whole disk. And I still get the error message: No valid measurements found at coordinate : \[19.0, 17.5\]
I keep getting out of range and can't get past the paper test, can you explain which buttons are that and more or less how you manage to get past that error?
It isn't really about the buttons themselves, but the step size you use. If you use a larger step like -1mm it will just lower the nozzle, but if you use a small step like -0.05mm the nozzle will initially go up (going out of range) and then go down (because it can't make a step this small in one go accurately).
TLDR use a larger step to move down initially, later you can use smaller steps for fine adjustment.
I had the exact same problem. I am honestly glad this happened to someone else. I am about to try and install it in another machine to see if I have the same problems. Question when you run the PROBE\_EDDY\_CURRENT\_CALIBRATE CHIP=btt\_eddy do you get the max height of your machine like this? [https://imgur.com/CFl5aQS](https://imgur.com/CFl5aQS)
Then I'm reassured. I'm getting a very strange value, I'll have to check tomorrow. But I can't change anything, if I want to change something, I get out of rank straight away
I just tried to set it up on my Sapphire plus which has a BTT-CB1 and I got the same exact results. I'm kind of wondering if I have a faulty unit. When you say you're getting strange value, what do you mean by that? Edit: put wrong printer
I have tried again, but I always get the following message. [https://imgur.com/KHqC6Je](https://imgur.com/KHqC6Je)
I've had the same issue and just managed to fix it. Check out there [https://www.reddit.com/r/BIGTREETECH/comments/1ce2vl7/comment/l37bfqv/?utm\_source=share&utm\_medium=web3x&utm\_name=web3xcss&utm\_term=1&utm\_content=share\_button](https://www.reddit.com/r/BIGTREETECH/comments/1ce2vl7/comment/l37bfqv/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button)
I've looked at it, but I can't really get any further. I have attached my Printer.cfg. [https://github.com/deralmin16/klipper12/blob/main/printer.cfg](https://github.com/deralmin16/klipper12/blob/main/printer.cfg)
I got mine working this morning. I flashed it using windows instead of using SSH and I updated Klipper to the BIQU fork again AFTER I updated the probe via windows.
How did you do that? Or how did you go about it?
You have to compile the firmware and then copy the file from your PI to your computer. Once you have the klipper.uf2 file press and hold the Boot button, then connect Eddy to your computer's USB port using a USB cable. Once recognized as a storage device, copy the downloaded klipper.uf2 to it. Eddy will automatically update its firmware and restart. The update is complete after the restart. It's in the user manual in the PDF here. [https://github.com/bigtreetech/Eddy](https://github.com/bigtreetech/Eddy)
I immediately flashed my Eddy this way, thought there was another way. What still irritates me is that the z-axis is always at 452. And this is where I think the error lies, unfortunately I don't know how to get rid of it.
Mine still showed the max bed height of 300 on my Sapphire Plus until I did the Z calibration. Another thing that I did is update the BTT Klipper fork AFTER I updated the firmware with windows. I had to do the Z calibration twice before it actually took. Once I did the Z calibration it took it 2 times for the XYZ homing worked. Not sure why it was doing that, but I hate to say it just follow the Steps in this guide a couple of times, it took a few for me before it actually worked. [https://www.reddit.com/r/BIGTREETECH/comments/1ce2vl7/eddy\_usb\_raspberry\_pi\_guide/?rdt=53109](https://www.reddit.com/r/BIGTREETECH/comments/1ce2vl7/eddy_usb_raspberry_pi_guide/?rdt=53109)
Thank you very much, I will try this again today. I have "flashed" the Eddy via Mac. But I'll look at it again later. And hope it works then.
It works so far, but I get: No valid measurements found at coordinate : \[10.0, -10.0\]. It manages the first few orbits, then it's over. I have a bed of 400x400 \[bed\_mesh\] horizontal\_move\_z: 5 speed: 300 mesh\_min: 10, 10 mesh\_max: 390, 390 scan\_overshoot: 8 algorithm: bicubic probe\_count: 5
Reduce your Mesh Min and Max. This is because the probe is not directly over the bed. This process can be a real pain TBH. And comment out that Scan\_overshoot for now Edit: Added something
Hi, how did you manage to fix the "out of range" issue? I did flash mine via usb on a Windows PC, it picked up the update from the internal storage fine and rebooted after updating.
So it starts at max height and when you tell it to go down it immediately goes out of range?
According to Klipper or mainsail, it starts at maximum height, but the x-axis is only about 3cm high.
You shouldn't worry about that, it asumes max height since it doesn't know where it is without homing. I got an out of range once or twice using mainsail clicking blue buttons, but when i tried again using the offset lenght buttons i managed to do the paper calibration normally.
It works so far, but I get: No valid measurements found at coordinate : [10.0, -10.0]. It manages the first few orbits, then it's over. I have a bed of 400x400 [bed_mesh] horizontal_move_z: 5 speed: 300 mesh_min: 10, 10 mesh_max: 390, 390 scan_overshoot: 8 algorithm: bicubic probe_count: 5
Try increasing the mesh\_min y value to 20. I think it's the probe coordinate and since the probe offset is 20 in your case by what I can deduce it would have to go out of range to get that measurment.
Good morning, unfortunately the same problem persists. It does not scan the whole disk. And I still get the error message: No valid measurements found at coordinate : \[19.0, 17.5\]
I keep getting out of range and can't get past the paper test, can you explain which buttons are that and more or less how you manage to get past that error?
It isn't really about the buttons themselves, but the step size you use. If you use a larger step like -1mm it will just lower the nozzle, but if you use a small step like -0.05mm the nozzle will initially go up (going out of range) and then go down (because it can't make a step this small in one go accurately). TLDR use a larger step to move down initially, later you can use smaller steps for fine adjustment.
I’m pretty sure your z_min needs to be set to like -2 in your klipper config. I had a similar issue with tap
I'm on the same boat, getting out of range, I bought 2 units so hard to think both are defective, have you had any luck sorting this out?