Jump to content
Ultimaker Community of 3D Printing Experts

UM5 random XYZ shift, then fails.


Recommended Posts

Posted · UM5 random XYZ shift, then fails.

Hello,

 

For the third consecutive time (even after fw update, cura update, and reseting the parameters), the UM5 goes at a random position:

 

 

 

I tried to "pause" the printing, immediately resulting in the following error:

 

image.thumb.jpeg.9a5fcde9323b862b033efb2f6e95de27.jpeg

 

As already said in another post, I'm trying to print this part since march and this is the nth time the UM5 fails. I've tried all firmwares available since January.

 

 

  • Link to post
    Share on other sites

    Posted · UM5 random XYZ shift, then fails.

    Have you tried printing it via cloud or using another USB-drive? My UM2 back then did similar things a few times because of a bad SD-card. 

  • Link to post
    Share on other sites

    Posted (edited) · UM5 random XYZ shift, then fails.

    My company's IT security rules prohibit me from connecting the printer to the network.

     

    I assume the USB drive is fine since :

    - I hope the file is copied on the linux BEFORE starting the print. 

    - If it's note the case, I would think that the prints will fails, instead of continuing with a constant shift on all axis. If some sectors of the disk were bad (assuming that the flash controller inside the drive did not do its job - very improbable), it's absolutely unlikely that the printer went into the same error with different consecutive prints, while the USB-drive has been formatted between prints.

    Googling the bug just reveal me that the bug was already know 5 years ago on UM3 :

    https://community.ultimaker.com/topic/17713-detected-move-outside-of-normal-printer-volume/

     

     

    Quote

    We (very rarely) had that a printer would slam the printhead repeatedly to the side of the printer, and added this protection to prevent this. We have actually found the root cause, but the cause was found late in the 3.6 firmware development process. So we only added the error detection, and not yet the proper fix to prevent this. As this touches a core component of the firmware.

     

    Edited by bonelli
  • 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
     Share

    • Our picks

      • New here? Get ahead with a free onboarding course
        Hi,
         
        Often getting started is the most difficult part of any process. A good start sets you up for success and saves you time and energy that could be spent elsewhere. That is why we have a onboarding course ready for
        Ultimaker S5 Pro Bundle, Ultimaker S5, Ultimaker S3 Ultimaker 2+ Connect.   
        They're ready for you on the Ultimaker Academy platform. All you need to do to gain access is to register your product to gain free access. 
        Ready? Register your product here in just 60 seconds.
          • Like
        • 13 replies
    ×
    ×
    • Create New...