-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
resolves #1377 + cleanup #1379
resolves #1377 + cleanup #1379
Conversation
The repair works. |
@radek8 Still have the problem even with this fix :-( |
The previous code was restored and is working properly now. You probably missed something. Retry please |
resolves bigtreetech#1363
This does not fix #1363. I had to remove this line (around line 20) in ProbeOffsetControl.c:
The nozzle has just homed (line 15) and I don't see the sense in moving it beyond this point. The P_PROBE_OFFSET values are ( in my case) beyond the physical capability of the nozzle, these offsets are used to calculate the distance from the probe to the nozzle. Trying to move the nozzle to the probe position is not a good idea and it will cause these horrible grinding noises. |
@Octet-nl |
As you mentioned correctly in #1363 the problem was not on the Z axis but on X and Y. At first it looked like a Z axis problem because it was caused by enabling Z offset. When I had my BL-touch connected to the Z-endstop connector, it made sense to enable Z_SAFE_HOMING. Now I have the original Z-endstop connected, and the BL-touch is connected to the PROBE connector on the BTT SKR mini E3. This is working great and I don't want to change this. As a wise Marlin person once said: A probe is not an endstop and an endstop is not a probe. (Reason for this is that the BLtouch once failed as an endstop so the nozzle drilled a 1 sq mm hole in the middle of the build plate. So for me no more homing there, it is not safe :p ) Apart from that, I don't see a reason for the movement of the nozzle to an area that can't be reached. I removed the offending statement and now everything works as expected. Is there any reason why I should not do this? |
As an experiment I removed the complete contents of probeOffsetEnable and probeOffsetDisable, except for the statements |
Understood your setup and the problem you had on the bed. The better solution is to make XY offset configurable based on preference/need. However, an HW setup forcing to use a probing point that is never reachable and far to be a good probing point for z offset is quite useless for me and I would tried a different setup |
XY offset is now measured with respect to the probe position as per Marlin config instructions. |
try PR #1415. It should solve your problem (set the new parameter on config.ini to 0) |
BUG FIXES:
PR STATE: