Jump to content

Diagnosing Setup Error on UM3


sharonana

Recommended Posts

Posted · Diagnosing Setup Error on UM3

I have a UM3 that has been reset.  When I turn it on, it enters the initial setup flow.  But I get stuck each time with ER15 for slot A.

 

I don't have an extra AA 0.4, and I don't need one for what I print, so I'd really rather not buy an extra just for setup.  Is there a way to do the setup with an alternate core?

 

If not, how can I figure out if the problem is the core, or something else?

 

If not, is there a way to see the logs or get to the diagnostic menu before completing the setup process?  I tried connecting via pronterface on USB, but couldn't get any readings.

 

Thank you!!

  • Link to post
    Share on other sites

    Posted · Diagnosing Setup Error on UM3

    I'd just swap the cores to see if the error moves or not.  

     

    If the problem moves when you swap cores left/right then it's a core.  You can't use the printer unless both cores are able to heat up because that is required for active leveling.  I suppose maybe you can skip the active leveling with the tweaker tool.  Every um3 comes with 3 cores: 2 AA 0.4 and one  BB 0.4.

     

    If the problem *doesn't* move then I'd suspect the cable going into the top of the print head.  It's common for the cable to pull too hard.  If you remove the rear two screws in the head then the rear half of the head pops off and you can see a connector.  Push that back down hard.  Also when putting together use some paper as a shim to hold the cable so it doesn't pull on the connector.

     

    You can get to the log file with ssh.  If you are comfortable with ssh.  But you first have to put the printer in "developer" mode which just lets you ssh into the printer.  username/password  root/ultimaker.  When printer is in dev mode it shows the ip address on the display at the top. You probably can't get into dev mode until you fix this problem unfortunately.  Once your printer is in dev mode, leave it there forever in case you get problems like this one again.

     

    Use journalctl to dump the log file (google it).  For example to see everything logged since the most recent boot do:

    journalctl -b

     

     

     

  • 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
    • Our picks

      • UltiMaker Cura 5.8 Stable released 🎉
        In the Cura 5.8 stable release, everyone can now tune their Z seams to look better than ever. Method series users get access to new material profiles, and the base Method model now has a printer profile, meaning the whole Method series is now supported in Cura!
        • 4 replies
      • Introducing the UltiMaker Factor 4
        We are happy to announce the next evolution in the UltiMaker 3D printer lineup: the UltiMaker Factor 4 industrial-grade 3D printer, designed to take manufacturing to new levels of efficiency and reliability. Factor 4 is an end-to-end 3D printing solution for light industrial applications
          • Thanks
          • Like
        • 3 replies
    ×
    ×
    • Create New...