-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
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
[BUG] PRINTER KILL AFTER HOMING 4 Z MOTOR #26717
Comments
Could you enable This will output a whole lot more debug information on the terminal and maybe help diagnose any issue with the endstops |
Hi, 11:07:52.757 : echo:DEBUG:ECHO,INFO,ERRORS,COMMUNICATION,DETAIL |
Hi, having the same issue. Homing works normal when using only one Z-endstop, all four motors work together, all stop at same time. It works perfect as expected till the last moment when it should simply confirm the Z-homepoint and then function is complete. Instead of finishing, it calls halt. PLEASE HELP, it will be much appreciated. |
I also enabled the #debug_leveling feature as suggested and got the following report; Recv: X:350.0000 Y:150.0000 Z:20.0000 E:0.0000 Count A:28000B:12000 Z:4000 Anyone know what the "P31 B63" received from the printer mean? I am pretty sure this is a bug, the result of homing not knowing how to respond when it received multiple endstop signals. |
Regarding "P31 B63" you have ADVANCED_OK enabled /**
* Send an "ok" message to the host, indicating
* that a command was successfully processed.
*
* If ADVANCED_OK is enabled also include:
* N<int> Line number of the command, if any
* P<int> Planner space remaining
* B<int> Block queue space remaining
*/
This has nothing to do with homing or failing to home. |
A more detailed report. Recv: echo:G91 Recv: <<< do_homing_move X343.0000 Y343.0000 Z30.0000 |
ellensp, thanks, I learned something, much obliged. |
New Revelation...... Send: G28 Z0 |
Found the problem, but not the right solution. In file \Marlin\src\module\endstops.cpp on lines 453 to 459 is the statement that kills the printer if any endstop is not triggered. This need to be altered to ignore if any of Z, Z2, Z3, Z4 is not triggered. It should be ok if only one of the four is triggered. (I think the second bump is a problem as it triggers all four endstops almost simultaneously, resulting in one or more triggers being missed.) If someone with better skills could help out with a alternative solution, it will be great. |
Please download |
Will, let you know shortly..... |
Downloaded the latest bugfix, but same error again. Kill called after validating , the second home bump. Thanks for the suggestion, I hoped it would work, but alas not. |
as a test please disable VALIDATE_HOMING_ENDSTOPS and see if that gets past it |
I already did that test as reported above, disabling VALIDATE_HOMING_ENDSTOPS, terminate normal and correct. Seems when the four steppers is perfectly alighned after the first bump that is the issue, in my unwise opinion. |
added a bunch of debugging to watch hit_state, and set M111 S32 here is the log Note this is on the simulator, so im not sure its fully compatible with multiple Z endstops
It may have raised more questions than answers, the test machine has x,y,z,z2,z3,z4,e0 also found that 2 Z's works fine > 2 and it errors more debugging needed |
Hi, I did the same test with the "S32" debug detail. The resulting output...... It is obvious that KILL is called because one or more endstops, activation was not received. The endstops function 100%, they can be triggered before the validation bump individually, which stops just that stepper correctly. I believe a workaround would be to : In case of multiple steppers and multiple endstops on an axis, to accept correct validation as long as at least one of the multiple endstops are triggered. As for the multiple "home" calls, that is a mystery to me, an indication of other "un-noticed bugs/issues" perhaps? |
That only masks the issue and would defeat the purpose of |
Duplicate of #23227 |
This bug/issue was not resolved. |
#23227 is not closed: |
Did you test the latest
bugfix-2.1.x
code?Yes, and the problem still exists.
Bug Description
Hi everyone,
I'm trying to configure my 3D printer with:
Motors: 2 Y Motors, 4 Z Motors
Endstops: 2 Y Endstops, 4 Z Endstops
I'm encountering an issue during Z-axis homing. The homing sequence starts, touches the endstops, then moves up for a certain ammount of mm (That i dont know how to change), then it come back down and in the instant of the second touch of the endstops, it crashes and triggers the error pictured below.
My Setup:
Marlin 2.1.2.1
Bigtreetech Octopus board with TMC2209 drivers controlled via UART
All motor and endstop pin assignments have been adjusted due to the dual Y and quad Z configuration.
Troubleshooting:
I suspected the pin changes might be causing the problem, but running M119 confirms all endstops are correctly wired and functioning properly.
As a temporary workaround, I comment out //#define Z_MULTI_ENDSTOPS and use only one Z endstop for homing, which avoids the crash and error. However, I'd like to utilize all four endstops for improved accuracy.
How can I configure Marlin to handle 4 Z-axis homing without the crash? Any guidance or insights would be greatly appreciated!
As a possible solution, I also considered modifying the homing procedure to make it happen in a single downward movement, i.e. without the upward and downward movement. I am not sure how to do this, but in Klipper, you can set the value of "homing_retract_dist" to 0 to make it home in a single movement. There is a similar command in marlin ?
Thank you for your time and assistance!
Bug Timeline
No response
Expected behavior
No response
Actual behavior
No response
Steps to Reproduce
No response
Version of Marlin Firmware
2.1
Printer model
No response
Electronics
No response
LCD/Controller
No response
Other add-ons
No response
Bed Leveling
None
Your Slicer
None
Host Software
None
Don't forget to include
Configuration.h
andConfiguration_adv.h
.Additional information & file uploads
CONFIG.zip
The text was updated successfully, but these errors were encountered: