[BUG] (Bugfix 2.0) Homing Failed Printer halted #14489
Comments
|
same problem mks sbase |
|
also bed doesn't heat Bed heating failed printer halted please reset |
|
any update for a fix to this? |
|
Me too. But i can't do anything (homing, move, heat bed....) :-( I think it's a me fault.... but i see i'm not alone. |
|
same problem with SKR 1.3 |
|
Still looking at which commit provoked it |
|
Already reverted with de462f2 |
|
Edit: so using latest source should be ok, right? |
|
Just tried with the last bugfix b6546ea and it does still not work. Even if everything is possible, I doubt that a commit affecting SD EEPROM emulation could provoque this issue... But you never know |
|
There is still posibillity i am not right, however commit under works, also last commit i tryied before the one i mentioned were like 3 up and it want working so.. i dont know now i use older version what i dont mind at all |
|
b6546ea doesnt compile because of broken macros but if I omit only this specific commit, the homing problem went away |
|
cool |
|
The last version: 8916acf (at least) solves the issue for me. No compiling and no homing problems anymore. |
|
Same problem on SKR v1.3 with TMC drivers. Does the newest version fix this? Is there an easy way to update firmware without having to re-enter all of my firmware settings? |
|
@Mbombace
Marlin-Configurator by @akaJes does it nearly auto-magically with a simple drag/drop operation. It will forget some parameters (on my side GRID_MAX_POINTS_X and GRID_MAX_POINTS_Y, so I have to verify with a file comp software (under Windows : WinMerge). https://github.com/akaJes/marlin-config Works for Configuration.h and Configuration_adv.h only. Other files (pins for example) have to be edited by hand). But after some practice, Marlin-Configurator allows the user to upgrade/compile/flash a new commit within less than 5 mn. I don't know of another app doing this. |
Use GIT: create a local branch, commit your setting changes to it and whenever you want to update your firmware, merge the 2.0-bugfix branch into your local branch and let git do the merging magic :D The Github Desktop App is pretty easy to use in this case |
|
I just fixed a 'Printer halted. kill() called!' problem while homing after upgrading my ender 3 pro to a skr v1.4 board. For me, turned out to be the stepper motor driver signals coupling to the endstop switch. The fix for me was to move the wires for stepper motor away from the 2 switch wires in the ribbon cables, and run them separately. Saw the problem on both the X and Y axis. The Z axis already had the wires separated. I expect the new stronger motor TMC2209 driver signals increase the coupling noise, or maybe the skr switch sensors are more sensitive to noise. This problem was exacerbated for my mahine having longer ribbon cables than stock. |
|
Later found that In the marlin configuration.h file there is a ENDSTOP_NOISE_THRESHOLD setting that I probably could have used instead of separating the endstop switch wiring from the stepper motor wiring. I have not tried that yet. |
|
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. |
With the last bugfix : 6a2a10a and when issuing a G28 or using the LCD option to home the printer, I get a Homing Failed / PRINTER HALTED. On pronterface, I get:
SENDING:G28
Error:Printer halted. kill() called!
[ERROR] Error:Printer halted. kill() called!
The printer is unusable.
The previous version I used : a0f8b25 does not have this issue. As there are around 30 commits between the 2 versions, I did not have yet the time to try to narrow down to the one which could be the problem.
Am I alone with this issue?
config.zip
The text was updated successfully, but these errors were encountered: