-
Notifications
You must be signed in to change notification settings - Fork 8
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
TILT_ADJUST printers calculate wrong offset #2
Comments
@EightFinger I'm so sorry your bed got scratched! I have a v2.4, so I had only tested it on printers using QUAD_GANTRY_LEVEL. Printers that use TILT_ADJUST need different math to calculate the z-offset. Someone on Discord posted a similar issue, and I resolved it the best I could with their info. Could you update the repo, run AUTO_TAP again, and share a screenshot of the console output? Let me know if the new version fixes it. Thank you for trying this out, and for your time! |
Thanks again for the fast reply. Sadly I´m currently on vacation, so I can´t test the update now. I´ll get back to you, as soon as I can. Probably end of next week. One different question, I think the "FORCE" command would overwrite the previously calculated offset value, right? For me it added the new calculated value to the old one, like first run -0.110, second run with FORCE=1, was -0.110 again, but it set the z-offset to -0.220, so I didn´t use the FORCE command. I will check this with this new update when I get back. |
That does look odd, and is a different result from the other person's TILT_ADJUST results. phazil's results I will look into this soon and make a fix that works for both of those results. Thanks for responding so quickly, and sharing your issue! If run run AUTO_TAP twice, the first time it will calculate it, and the second time it will set z-offset to the last calculated result. If you run FORCE=1 it won't use the last calculated value, and will do it again. I'm not sure why your offset seemed to double when you ran it again - a fix will be implemented soon |
I used the most recent update. I am finding that autotap reports and sets the z-offset to 0.06 as the z-offset, but I need to run a z-offset of 0.562, or else the nozzle runs into the bed. Before autotap my z-offset in klipper was z_offset = -0.570 To remedy this I have done the following in my start macro |
@The-Original-Reth are you using a printer that uses QUAD_GANTRY_LEVEL, or TILT_ADJUST? |
@The-Original-Reth I've never heard of a Trident using QGL, how do you have that configured? |
I guess I was confused. Screw tilt I associate with V0. I will change it and see what happens |
[auto_tap] 9:25 PM After changing it and running a print. I still had to add a 0.5 z-offset. In order to get a good first layer. |
Might've found a different bug. It zeros the already input z-offset, but your homed z0 (with the offset) may still have an impact on the probe/measure results? I have another module I'm working on and will port some things from that into this, like automatic homing, which should fix that issue. Maybe then the TILT_ADJUST issue will be more clear Thank you for screenshots and detailed information! |
@phazil, you were correct, the saved z-offset was impacting the results (using STA method since it also used the probe/measure instead of just the travel). It should no longer care about your previous z-offset as of this commit Currently working on fixing issue 5, then the TILT_ADJUST issue should be easier to solve. The hunt continues... |
Just reran auto_tap with your newest update. Auto TAP Results These results are about 0.5 to large |
I am now getting this error on the newest revision of auto_tap 7:17 PM my previous z-offset was -1.2 |
My auto-tap is constantly 0.4 higher than what should be used. So I just decrease by that amount. Hopefully it can get sorted out. |
So I´m back from vacation now and tried the newst update with my printer and read trough all the comments. The calculated offset is too high. My normal working offset is -0.865 How can i help you to improve this script even further? This is my console output: 13:55 |
So I did some further testing. I used a probe and lift speed of 0.5 (really slow). This way I got very consistend and accurte measurements. Which are similiar to my hand measured value from above. Auto TAP Results on VITALII_CNC using 'rev hop' method |
@EightFinger Awesome! Thanks for all the info, and for doing some tests of your own. Be careful with the negative offset. Hand measured (saved offsets) are inverted from "live offsets" like Auto TAP measures (at least that I've seen) Last "probe method" I can think of to try is to get the measurement, and move back to z0 to check if it's still triggered. I'll take everyone's results and generate some graphs with the data to see if it makes things more clear, but honestly I'm not hopeful besides it being tuned on individual printers, which kind of defeats the whole purpose. I appreciate you, and everyone who have contributed time, and I hope there's some breakthrough that fixes these issues. |
@Anonoei Thanks for the answer. Your are right with the saved offsets are inverting upon saving. I changed my multiple back to a positive and to 21.5 to be more close to my value. So now it shoes 0.859 but saves to -0.859. This way it is correct. Your idea on how to get min/max values could work. I´m not the most knowledgble, because I just start tinkering with this stuff, but I really like to try out new stuff. I had an idea to get the nozzle touching bed value by conecting wires to the holding magnets and screws in TAP. This way we would probably know excactly the Z value when the nozzle touches the bed and the magnets disconnect. Maybe I´ll try this in the future. |
Since the original problem is sovled and with more people found the right multiple for Vitalii Tap, I´m gonna close this issue. Thank you very much. |
First I really like your idea, but I think it doesn´t seem to work with a trident at the moment.
Today I installed your updated version trough moonraker, thanks for that!
I reverted my z_offset back to 0 and heated my chamber and did homing, plus z-tilt.
Then i did AUTO_TAP command with the following settings.
I calculated a offset of 0.110 which when saved translates to [probe_z_offset: -0.110].
My hand self measured z_offset for a nice first layer is: -0.865, which is far away from the AUTO_TAP one.
Never the less, I tried to make a test print, to fine tune the first layer, but the nozzle far too close to the bed, it is even dragging on the bed a little bit. This way the extruder can´t push any filament through the nozzle and my printer stops.
Chaning back to my old z_offset, it prints without any problems.
Am I doing something wrong?
Picture of bed with scratches:
Printer Setup:
Voron Trident 300x300x250
Stealthburner with Rapido Hotend
Vitalii3D MetalTap with 2.4.1 OptoTap PCB at 24V
The text was updated successfully, but these errors were encountered: