I get an error: printer halted. (kill() called! Any time I home my machine's X or Y axis. I have just installed a 3D touch auto bed level sensor, ironically it works fine. I was using Sprinter firmware but it doesn't support auto bed level, so thus I'm using Marlin. I am using the latest version of Marlin and it gave me nothing but issues, printer wouldn't move or home at all. I used the latest Marlin 1.1.x bug fix edition (1.1.9) and now everything is working correctly except X and Y homing, the machine throws the error: printer halted. (kill() called! on Repetier-Host.

When I use the M119 command all endstops (optical, not mechanical) show as open unless triggered, the endstops are working correctly. When I home the X and or Y it will do as it should and stop when it hits the endstop but that is when the errors pop up and the printer freezes/no longer to gives commands without disconnecting and reconnecting to the printer again.

If I home my Z axis it will deploy the probe and come down and touch the bed 2x and no error code and I can still manually move the printer around with the program movements after homing Z axis. I'm not sure what would cause this to happen only on X and Y but any help would be appreciated.

I use Repetier-Host but I downloaded Printrun just to see what would happen and it shows the exact same effect/errors. I also tried the Marlin bugfix 2.0 and it gave the same errors too.


This question has an open bounty worth +50 reputation from 0scar ending in 19 hours.

This question has not received enough attention.

  • 1
    $\begingroup$ qould you mind telling the verion number of your marlin (the one you downloaded)? "latest version" becomes a wrong information within short weeks often. $\endgroup$ – Trish Jan 8 at 12:57
  • $\begingroup$ Welcome to 3dPrinting.SE, btw! $\endgroup$ – Pᴀᴜʟsᴛᴇʀ2 Jan 8 at 14:08
  • $\begingroup$ @Trish The latest version of the 1.1.x branch will always be 1.1.9 as of sometime last year. X) They abandoned that branch, new developments take place in branch 2. $\endgroup$ – 0scar Jan 8 at 18:31
  • 1
    $\begingroup$ @user3335963 Please add images of the optical endstops and the wiring of the endstops (also wiring to the board). This is e.g. interesting to see whether you have wired it incorrectly and induce a short circuit. $\endgroup$ – 0scar Jan 11 at 12:24
  • 1
    $\begingroup$ also include information if your optical sensors are Normally Open or Normally Closed. $\endgroup$ – Trish Jan 11 at 12:41

Without the images of how you connected the endstops, the best guess for your problem is that the endstops cause a short circuit, once pressed, the microprocessor trips and shuts down. If you provide more information, other people may even add better answers based on your added information.

E.g. how is everything connected at both sides of the cable (board and endstop), does the message occur when you press an endstop, maybe it is even wise to add a link to your configuration files.


Your Answer

By clicking "Post Your Answer", you acknowledge that you have read our updated terms of service, privacy policy and cookie policy, and that your continued use of the website is subject to these policies.

Not the answer you're looking for? Browse other questions tagged or ask your own question.