<p>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.</p>

<p>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. </p>

CC BY-SA 4.0
2019-01-12T11:43:09.607Z
2019-01-14T13:45:27.350Z
2019-01-14T13:45:27.350Z
0scar
<p>I apologize I should have got back with you guys sooner. I downloaded a fresh copy of the Marlin firmware again and pulled up the Sprinter config.H folder. Since the firmwares are very similar I was able to just glance at my Sprinter firmware and noticed certain endstops for my optical endstops required "pull ups" to correctly work. I thought I had tried this before but either I did some thing wrong the first time or I didn't save the changes, who knows. Thanks to every one trying to help.</p>

CC BY-SA 4.0
2019-01-26T05:14:12.683Z
2019-01-26T07:26:07.743Z
2019-01-26T07:26:07.743Z
user3335963
<p>I get an <code>error: printer halted. (kill() called!</code> 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 <code>error: printer halted. (kill() called!</code> on Repetier-Host.</p>

<p>When I use the <code>M119</code> 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.</p>

<p>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.</p>

<p>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.</p>

CC BY-SA 4.0
2019-01-08T12:57:38.100Z
qould you mind telling the verion number of your marlin (the one you downloaded)? "latest version" becomes a wrong information within short weeks often.
Trish
CC BY-SA 4.0
2019-01-08T18:31:22.363Z
@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.
0scar
CC BY-SA 4.0
2019-01-08T19:41:03.490Z
all of the versions i used were downlaoded with in the last 3 days, I've tried all the verisons they have listed.
user3335963
CC BY-SA 4.0
2019-01-08T21:40:47.160Z
Also, the board I'm using is a ramps 1.4 all of the electronics I use are the most basic 3D printing stuff you can find online. I also tried removing the auto bed level and its settings to test and see if it was the Z probe causing the issue and it did not change any thing. I'm assuming its some sort of homing setting or maybe possibly a endstop setting but the end stops seem to work correctly.
user3335963
CC BY-SA 4.0
2019-01-08T22:11:38.160Z
I also did forget to mention I am using optical endstops not mechanical.
user3335963
CC BY-SA 4.0
2019-01-08T22:29:11.153Z
I made a small amount of progress. When I turn on pull ups for X and Y min I can now home the printer with out error codes, but If i try to print some thing I get the error code again.

theres a catch though, If I home the Y axis first it will give me the error code, if I home X thenY no error code unless I try to print.
user3335963
CC BY-SA 4.0
2019-01-11T10:50:39.357Z
@user3335963 I've added a bounty to attract more people to help you out. In the mean time, please update the question by [edit]; comments are not really meant for prolonged information addition and storage or discussion. The better. more complete the question, the more chance you get an appropriate answer.
0scar
CC BY-SA 4.0
2019-01-11T12:24:37.850Z
@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.
0scar
CC BY-SA 4.0
2019-01-11T12:41:39.220Z
also include information if your optical sensors are Normally Open or Normally Closed.
Trish
CC BY-SA 4.0
2019-01-14T09:37:59.297Z
Please help us help you! Please add the requested data into your question by [edit] and ping Trish or 0scar by leaving a comment where you put the @ in front of the user name to give him a notification! This does not sound as a configuration problem, but a hardware problem. You may also add a link to your configuration.h file if you want us to check it for you.
0scar
CC BY-SA 4.0
2019-01-14T13:53:58.790Z
at least give us a wiring diagram, labeling which input/output is wired to which sensor input/output and where your optical sensors get their power from. Also, the specs of the optical sensors (working voltage) would be a necessary information
Trish
<marlin><firmware><y-axis><x-axis><homing>
X and Y homing issues
user3335963
# X and Y homing issues

(Asked by: username_0 on 2019-01-08)

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.

**Tags:** marlin, firmware, y-axis, x-axis, homing
> **Comments:**
> **username_1**: qould you mind telling the verion number of your marlin (the one you downloaded)? "latest version" becomes a wrong information within short weeks often.  
> **username_2**: @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.  
> **username_0**: all of the versions i used were downlaoded with in the last 3 days, I've tried all the verisons they have listed.  
> **username_0**: Also, the board I'm using is a ramps 1.4 all of the electronics I use are the most basic 3D printing stuff you can find online. I also tried removing the auto bed level and its settings to test and see if it was the Z probe causing the issue and it did not change any thing. I'm assuming its some sort of homing setting or maybe possibly a endstop setting but the end stops seem to work correctly.  
> **username_0**: I also did forget to mention I am using optical endstops not mechanical.  
> **username_0**: I made a small amount of progress. When I turn on pull ups for X and Y min I can now home the printer with out error codes, but If i try to print some thing I get the error code again.  theres a catch though, If I home the Y axis first it will give me the error code, if I home X thenY no error code unless I try to print.  
> **username_2**: @user3335963 I've added a bounty to attract more people to help you out. In the mean time, please update the question by [edit]; comments are not really meant for prolonged information addition and storage or discussion. The better. more complete the question, the more chance you get an appropriate answer.  
> **username_2**: @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.  
> **username_1**: also include information if your optical sensors are Normally Open or Normally Closed.  
> **username_2**: Please help us help you! Please add the requested data into your question by [edit] and ping Trish or 0scar by leaving a comment where you put the @ in front of the user name to give him a notification! This does not sound as a configuration problem, but a hardware problem. You may also add a link to your configuration.h file if you want us to check it for you.  
> **username_1**: at least give us a wiring diagram, labeling which input/output is wired to which sensor input/output and where your optical sensors get their power from. Also, the specs of the optical sensors (working voltage) would be a necessary information  

---

## 2 answers

### Answer by username_2 on 2019-01-12. Score: 1

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.


---

### Answer by username_0 on 2019-01-26. Score: 1

I apologize I should have got back with you guys sooner. I downloaded a fresh copy of the Marlin firmware again and pulled up the Sprinter config.H folder. Since the firmwares are very similar I was able to just glance at my Sprinter firmware and noticed certain endstops for my optical endstops required "pull ups" to correctly work. I thought I had tried this before but either I did some thing wrong the first time or I didn't save the changes, who knows. Thanks to every one trying to help.


---

