When pressing Calibrate X(/Y/Z) in Delta Calibration printer starts to shake printhead in direction of corresponding tower and reboots after few seconds.
Configuration files: Configuration.zip
Hardware: Anycubic Kossel Linear Plus with Bigtreetech SKR v1.3 board
Expected behavior: Printer starts to calibrate corresponding axis (not sure though, using this features for the first time and can't find any info)
Actual behavior: Printer starts to violently shake printhead in direction of corresponding tower and reboots after few seconds
Marlin is downloaded today (26th of November) from bugfix-2.0.x branch.
Here is a video I recorded: https://www.youtube.com/watch?v=qgJ1AZSIq4c (there is a probe attached, without a probe behaviour is the same)
I was able to reproduce this even with code prior to my recent delta probing changes (b904ba0f291cdcb9759464f064f85ba066b778ce).
The center
Something very strange is happening with this. I added some serial prints to the code, and I see the prints from the command attempting to execute multiple times, even though it was only selected once. I then see "cold extrusion prevented" before the controller resets.
_goto_tower_x
goto_tower @ 210.00
tower_vec (coefficients) = { -0.87, -0.50, }
_man_probe_pt = { -87.47, -50.50, }
do_blocking_move_to_xy_z = { -87.47, -50.50, 5.00} fr_mm_s=0.00
_goto_tower_x
goto_tower @ 210.00
tower_vec (coefficients) = { -0.87, -0.50, }
_man_probe_pt = { -87.47, -50.50, }
do_blocking_move_to_xy_z = { -87.47, -50.50, 5.00} fr_mm_s=0.00
_goto_tower_x
goto_tower @ 210.00
tower_vec (coefficients) = { -0.87, -0.50, }
_man_probe_pt = { -87.47, -50.50, }
do_blocking_move_to_xy_z = { -87.47, -50.50, 5.00} fr_mm_s=0.00
_goto_tower_x
goto_tower @ 210.00
tower_vec (coefficients) = { -0.87, -0.50, }
_man_probe_pt = { -87.47, -50.50, }
do_blocking_move_to_xy_z = { -87.47, -50.50, 5.00} fr_mm_s=0.00
_goto_tower_x
goto_tower @ 210.00
tower_vec (coefficients) = { -0.87, -0.50, }
_man_probe_pt = { -87.47, -50.50, }
do_blocking_move_to_xy_z = { -87.47, -50.50, 5.00} fr_mm_s=0.00
_goto_tower_x
goto_tower @ 210.00
tower_vec (coefficients) = { -0.87, -0.50, }
_man_probe_pt = { -87.47, -50.50, }
do_blocking_move_to_xy_z = { -87.47, -50.50, 5.00} fr_mm_s=0.00
_goto_tower_x
goto_tower @ 210.00
tower_vec (coefficients) = { -0.87, -0.50, }
_man_probe_pt = { -87.47, -50.50, }
do_blocking_move_to_xy_z = { -87.47, -50.50, 5.00} fr_mm_s=0.00
echo: cold extrusion prevented
Almost the same problem on delta (FLSUN QQ-S) with MKS Robin Mini board. Press Calibrate X(/Y/Z) - printer just hangs and to not respond to touchscreen.
I have the same problem,
Anycubic Kossel Linear Plus + SKR V1.3 + TMC2130 +2004 LCD.
Allso i have problem with delta calibration, G33
everytime the same result: Correct delta settings with M665 and M666
I have no ideea that the problem is....
Could we modify the firmware for more detailed error? (over serial) just a thought.
Can anyone responding to this echoing the same problem explain whether these options are actually useful? I am not sure if they are needed, or if they are completely replaced by G33 delta calibration.
I don鈥檛 have time to look any further into this right now. I don鈥檛 actually use these options, so I wouldn鈥檛 even notice if they were gone.
who knows the last working version?
@vijexa since 2.0 was just released a few days ago has this changed this issue at all?
Hi.
I can confirm, that build from 1.12.2019 still has this issue.
This is happening because the planning buffer fills up and _man_probe_pt (in menu_delta_calibrate.cpp) is called recursively when the menu update is refreshed.
I've tested a hacked in fix that uses a static local to track whether _man_probe_pt is already in progress, and simply returns when called recursively.
This doesn't seem like the right fix, but I'm having trouble figuring out how to avoid recursive callbacks from the menu when idle() is called (deep inside _man_probe_pt).
@thinkyhead, do you have a suggestion for this, or know who I could talk to for a recommendation?
@thinkyhead, do you have a suggestion for this, or know who I could talk to for a recommendation?
@InsanityAutomation andbi have been talking about this a bit. The problem is that he doesn鈥檛 have a delta and I don鈥檛 presently have time.
We are currently considering whether these are completely obsolete. They have probably been broken for a long time, and if you use G33 I don鈥檛 think you shouldn鈥檛 need them. Even if you do need to manually calibrate, these don鈥檛 actually store any settings, they simply let you manually probe a height through the LCD, so they really are not that great of a solution.
One option is to simply delete them. This will prevent people who don鈥檛 actually need them from reporting issues. Nobody replied to my question on this issue asking whether this capability actually matters. If people complain that they are still important, they could be replaced with something more useful that actually does something, such as a G33 P3 to probe the tower heights.
@vijexa when you get time please have a retest
and as bugfix 2.0.x is updated daily please retest say every 14 days or so
My pull request mentioned above has not been merged yet. They are welcome to test with the changes in my PR, but I can guarantee it is still broken in bugfix-2.0.x.
@vijexa @KosVas91 @istyszy @nivaman
This fix was just merged into bugfix-2.0.x. Could one of you try it out and verify that it fixes the issue for you?
@vijexa @KosVas91 @istyszy @nivaman
as @sjasonsmith just asked could one of you try it out and verify that it fixes the issue for you?
@boelle I think you can go ahead and close it. They've had a week, so we'll just need to depend on my testing when I created the fix.
oki, just ping me if we need to reopen, i just have a rule of thumb not to close verified ones
I apologize if this is not aloved, but just for info - I have loaded firmware from end of January and can confirm that Delta calibration is now working.
@nivaman definitely allowed and appreciated! Thanks for the confirmation :)
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.