Open mminella opened 3 days ago
Hi there, thanks for opening this issue! :)
Could you add 'sample_retract_dist: 5.0' in to your [probe] section? My hunch is that your printer isn't lifting up high enough before probing. I had this problem on my Kobra so I had to add that.
If that resolves the issue please let me know.
Thanks for the quick response! When I try that, I got the following when trying to do a height map: Probe triggered prior to movement
.
When I try homing after that error, I get the following: Endstop z still triggered after retract
. Interesting note is that the extruder goes down, comes up then throws that error. For the record, in that position the light is not active on the level sensor and Mainsail reports that Endstop Z and Probe are both open.
Just to be 100% sure this isn't the issue, I also changed sample_retract_dist
to 20 just to be completely sure that isn't the issue...no difference in results.
On the Kobra both the Z endstop and probe are the same thing, so ultimately what's happening here is that the probe is triggering when it shouldn't. The sample_retract_dist should make the toolhead move up enough that the probe light turns off, can you tell me if that's happening?
A bit of an easier way to test this is to run the PROBE_ACCURACY g-code command after homing, if it works then please move the toolhead to somewhere else on the bed where it fails and run it again.
The probe light does turn off when it is high enough. The light is also not on when the errors trigger.
After homing, I did the PROBE_ACCURACY
command and immediately received the following error: Probe triggered prior to movement
. It was homed and the light was on when I ran the command so that condition makes sense...I'm not sure why that would have thrown an error though.
Ideally the probe should move upwards before probing to counteract this issue, which is what sample_retract_dist should do... Oops! That's not what it does.
You want to put this in your [safe_z_home] section: z_hop: 10
(I just picked 10, try a value bigger if it doesn't work)
No luck. When I put that in, it homed fine but then during the height map, I still get a Probe triggered prior to movement
error. I increased the value to 20 and I got a Endstop z still triggered after retract
during homing. I'm not sure how big you want that value to be...
Could you describe a bit more what the printer is doing? If you could provide a video that would be even better! It's hard to know exactly what's going on by just the errors as they don't show the entire picture.
Nov 16, 2024 01:03:31 Michael Minella @.***>:
No luck. When I put that in, it homed fine but then during the height map, I still get a Probe triggered prior to movement error. I increased the value to 20 and I got a Endstop z still triggered after retract during homing. I'm not sure how big you want that value to be...
— Reply to this email directly, view it on GitHub[https://github.com/printers-for-people/catboat/issues/47#issuecomment-2478919110], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AABNHOYA2MNYGRHAHAUJMPD2AX5LBAVCNFSM6AAAAABRWR6GXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZYHEYTSMJRGA]. You are receiving this because you commented. [Tracking image][https://github.com/notifications/beacon/AABNHO4WHZ7IR7MUMPUCYCL2AX5LBA5CNFSM6AAAAABRWR6GXCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUTYFG4M.gif]
Could you try both z hop and safe min retract distances?
Nov 16, 2024 01:19:50 Jookia @.***>:
Could you describe a bit more what the printer is doing? If you could provide a video that would be even better! It's hard to know exactly what's going on by just the errors as they don't show the entire picture.
Nov 16, 2024 01:03:31 Michael Minella @.***>:
No luck. When I put that in, it homed fine but then during the height map, I still get a Probe triggered prior to movement error. I increased the value to 20 and I got a Endstop z still triggered after retract during homing. I'm not sure how big you want that value to be...
— Reply to this email directly, view it on GitHub[https://github.com/printers-for-people/catboat/issues/47#issuecomment-2478919110], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AABNHOYA2MNYGRHAHAUJMPD2AX5LBAVCNFSM6AAAAABRWR6GXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZYHEYTSMJRGA]. You are receiving this because you commented. [Tracking image][https://github.com/notifications/beacon/AABNHO4WHZ7IR7MUMPUCYCL2AX5LBA5CNFSM6AAAAABRWR6GXCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUTYFG4M.gif]
I have uploaded a video demonstrating the current state of what I'm trying here: https://youtu.be/i-T0G3fVJfU
Sorry, I recorded that video before seeing your last note. Do you know what the field name for safe min retract distance is? I can't find it in the docs. I'll give it a try once you let me know. Thanks again for your help!
I'm on my phone currently so I don't have the exact name but it was the previous setting we tried. You may need both of the settings to have the tool head move out of the way when homing and when probing.
I will check out the video later today, I'm currently in bed on my phone instead of sleeping. But at least that means I can reply to emails. :)
Nov 16, 2024 06:02:21 Michael Minella @.***>:
I have uploaded a video demonstrating the current state of what I'm trying here: https://youtu.be/i-T0G3fVJfU
Sorry, I recorded that video before seeing your last note. Do you know what the field name for safe min retract distance is? I can't find it in the docs. I'll give it a try once you let me know. Thanks again for your help!
— Reply to this email directly, view it on GitHub[https://github.com/printers-for-people/catboat/issues/47#issuecomment-2479731256], or unsubscribe[https://github.com/notifications/unsubscribe-auth/AABNHO5AHETBDIEJG3O5Y2L2AZALPAVCNFSM6AAAAABRWR6GXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINZZG4ZTCMRVGY]. You are receiving this because you commented. [Tracking image][https://github.com/notifications/beacon/AABNHO64ZO5KM7R6M23PYL32AZALPA5CNFSM6AAAAABRWR6GXCWGG33NNVSW45C7OR4XAZNMJFZXG5LFINXW23LFNZ2KUY3PNVWWK3TUL5UWJTUTZWZDQ.gif]
Okay, I had a look at your video, thank you very much for going so in depth.
This is very interesting behaviour. My mental picture of what was happening is that the after homing and probing the printer would go all the way down to the bed then not lift up high enough. Has this happened before? If so, I think the z_hop is the solution for that specific problem.
However in the video it seems like the printer doesn't move down very far at all. Maybe the reason why it is stopping is because the z controller thinks it's hit something, Could you try setting 'driver_SGTHRS: 100' in stepper_z? You might also want to set the run_current to 1 to see if that helps, I'm assuming you have both steppers running off the same controller so it might need a bit extra power.
I have an original Kobra standard. I have upgraded it to a dual z stepper arrangement about a year ago and that was working fine with the original firmware. I am now trying to setup Klipper (using the Catboat fork) and am running into issues related to the Z axis. I have tuned the X and Y motors so they home fine, but I am running into two issues right now with the Z:
Inconsistent homing on the Z axis - When I home the extruder, X and Y perform as expected. Sometimes the Z goes down until the leveling sensor trips (indicated by the red light being on) but some times it does not and just sits above the bed. I have also had one or two "Endstop z still triggered after retract" errors as well during homing.
Inconsistent errors when probing during bed leveling - Seemingly randomly, I'll get "Probe triggered prior to movement" errors during probes on bed leveling. It's important to note that these do not always happen on the first probe of a position so I don't think it's related to the hight of the moves in between probe positions.
I used this method (https://www.klipper3d.org/TMC_Drivers.html#tuning) to tune the X and Y stepper motors but the Z ones basically ignore that (and just goes) which I think is the correct behavior given the leveling sensor. For the record, below is my printer.cfg. What am I missing?