Jump to content

Last layer issue


Karras

Recommended Posts

Posted · Last layer issue

Hi

I've recently reset printer to factory values, adjusted feeder pressure due to some underextrusion problems and solved uneven belt tension. Overall quality of print increased, but there's a new problem with he last layer. It seems like an overextrusion just in the very last point of the last layer. Usin an ultimaker 2 with PLA and firmware is updated.

Is there any value to adjust?
Thanks

IMG_20180117_104302.jpg

  • Link to post
    Share on other sites

    • 3 months later...
    Posted · Last layer issue

    Hello,

     

    Did you ever figure out this problem?  My machine just started this same issue today on a UM2Go and can't figure out what changed.  I've been trying to print the "stock" code that came with the printer on the SD card, so it should be the same as previous prints, but every print from the card now has this bugger on the last layer when the print has all but finished the print.  It occurs just before the head moves back to home.  It seems to try to spit out a lot of filament at once, very fast, and in turn, it grinds out the filament in the feeder at the spot where it meets the feeder motor.  Since it grinds down that spot, it now can not advance the filament and I have to clear the jam every time.

     

    I have not updated any firmware or done any resets that I know of, but I did connect it via OctoPrint.  That shouldn't have any affect, since I'm not using OctoPrint to actually slide my files.  I actually haven't sliced anything.  I'm using gcode that came with the printer as a baseline.  Once I open up the gcode from the card, I'll find the last few commands sent before it goes to home.

     

    Anyone else have any ideas?

     

    TIA

     

     

     

  • Link to post
    Share on other sites

    Posted · Last layer issue

    This is a recent known bug.  3 things have to happen together for this to happen.  If you fix ANY of the 3 things this bug will go away.  Hundreds of people had this problem.  You can either:

     

    1) Go to the latest version of cura or the version before from a few weeks ago (I think version 3.2.0 or newer).

    2) Add lots of large comments at the end of every gcode file (latest curas will do this).  About 20 lines of 80 characters is plenty.

    3) Update to the latest um2go firmware

     

    Any of these 3 things will fix the problem.  

     

  • Link to post
    Share on other sites

    Posted · Last layer issue

    whoops....  

    1st,  I mean *effect, not affect.  ....was typing too fast & didn't catch my mistake because I didn't proofread.?

    2nd, I've seen some other posts about "blobs" and firmware.  Could this be a firmware update issue?  I didn't do a firmware update, but I have 2.6.2.

    3rd, What is the initial  firmware for UM2Go?

     

  • Link to post
    Share on other sites

    Posted (edited) · Last layer issue
    1 minute ago, gr5 said:

    This is a recent known bug.  3 things have to happen together for this to happen.  If you fix ANY of the 3 things this bug will go away.  Hundreds of people had this problem.  You can either:

     

    1) Go to the latest version of cura or the version before from a few weeks ago (I think version 3.2.0 or newer).

    2) Add lots of large comments at the end of every gcode file (latest curas will do this).  About 20 lines of 80 characters is plenty.

    3) Update to the latest um2go firmware

     

    Any of these 3 things will fix the problem.  

     

     

     

    Great.  Thank you for the fast response.  I did just find some other posts mentioning this blob.  I must have been typing my 2nd post as you were replying.

     

    However, I did not to a firmware update so that part is a bit weird that it started happening all of sudden.

     

    I am on 2.6.2 now, so will go get the updates.

     

    Thanks again

    Edited by adsparkme
  • Link to post
    Share on other sites

    Posted · Last layer issue

    The bug was in about 2 years of firmwares but it didn't show up until you had all 3 bugs working together.

  • Link to post
    Share on other sites

    Posted · Last layer issue
    14 hours ago, gr5 said:

    ...

    2) Add lots of large comments at the end of every gcode file (latest curas will do this).  About 20 lines of 80 characters is plenty.

    ...

    Out of curiosity, what is the technical background reason for this?

     

  • Link to post
    Share on other sites

    Posted · Last layer issue
    2 hours ago, geert_2 said:

    Out of curiosity, what is the technical background reason for this?

     

     

    Paragraph (2.) on this comment:

    https://community.ultimaker.com/topic/21651-um2-huge-blob-grinding-at-end-of-print/?do=findComment&comment=202235

  • Link to post
    Share on other sites

    Posted · Last layer issue
    21 minutes ago, tinkergnome said:

     

    Thanks. I hadn't read that 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
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 16 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
          • Like
        • 0 replies
    ×
    ×
    • Create New...