1 Topic by blacky.blackwell

  • blacky.blackwell
  • Member
  • Offline
  • Registered: 2013-10-12
  • Posts: 20

Topic: Homing error

I replaced mt hotend with a E3D. Flashed the firmware to accommodate the thermistor. Now when i manually click home of the X, Y or Z everything homes just fine, but after a print or when i kill a job the limit switch does not stop the axes.
Appeares to be the X switch is the culprit. I tested the X and Y switches and they are making contact. The connectors are seated in the proper places.
The motor will reach the switch then continue its steps until it reaches the 200 max in the firmware.
It didn't do this before i installed the E3D and flashed the firmware. Just installing the E3D i will rule out as just that install should be in no way related to this problem. It has to be in the firmware. I have compared the original firmware to the one i moded and i can spot anything i may have changed to cause this. I didn't change anything with the endstops anyway.
I can post screen shots of the firmware if needed.

Any suggestions.

Thanks

2 Reply by ronsii

  • ronsii
  • Member
  • Offline
  • From: PNW
  • Registered: 2012-10-28
  • Posts: 1,723

Re: Homing error

will it stop if you manually trip the x limit switch by hand after you have done the 'kill job'?

3 Reply by ronsii

  • ronsii
  • Member
  • Offline
  • From: PNW
  • Registered: 2012-10-28
  • Posts: 1,723

Re: Homing error

other possibility is after/during a print it is warmer temp affecting switch mechanics, some SD printers are very 'tight' tolerances with the x limit switch and even though it looks like it is hitting the switch it may need a layer or two of tape or something on the part that actually hits the switch to make it contact soon enough... hope this makes sense smile

4 Reply by blacky.blackwell

  • blacky.blackwell
  • Member
  • Offline
  • Registered: 2013-10-12
  • Posts: 20

Re: Homing error

Figured it out. For some reason my starting and ending G code was blank in Repetier. I replace the G code and everything is fine now. Thanks for replying.