Jump to content
Ultimaker Community of 3D Printing Experts
Sign in to follow this  
variador

Hit endstop z

Recommended Posts

Hit endstop Z seems fairly easy to understand if it means what it says on the UltiControler.

However,

This error occurs during the second layer of the print that is going over exactly the first layer of the print. The print never gets anything but taller and only 6 mm at that.

Once the error occurs the extruder head starts out of line by shifting Y towards the front of the printer.

Haven't tried printing it straight from Cura yet. It is a rather large print but well within the boundaries and smaller than others printed before.

Has happened twice in what seemed to be the same place.

Second time was after deleting the first file from the card and slicing it again in Cura.

The Ulticontroller is a week old and has had no problems.

Anyone have an idea of what's happening?

Thanks

Share this post


Link to post
Share on other sites

Perhaps you have a loose wire on one of the z endstops and a certain movement shakes the ultimaker enough to trigger the problem?

What would be nice is a utility that shows the state of all 6 endstops so you can shake the ultimaker and jiggle all the wires and move the head around and see if something will trip one of the endstops.

I would consider disconnecting the *bottom* z endstop - you probably don't need it anyway - just to see if that helps. Could it be though that it's the Y endstop that is triggered and it's just the message that is wrong?

 

Share this post


Link to post
Share on other sites

Thanks for the reply Gr5,

Corrupted firmware was the culprit.

Nothing worked after many failed attempts using a different setup every time. Tried a much smaller piece after tightened everything up (nothing loose). It went bad at the same spot on a smaller piece ( after first layer fan starts, outline goes good and then bam! It goes all out of whack.

Slowed the print speed way down since this is the second layer when everything speeds up.

Same problem.

This problem occurred once before because of a firmware problem.

After trying different methods, the firmware finally reset and once again everything is fine.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×

Important Information

Terms of Use Privacy Policy