Jump to content
Ultimaker Community of 3D Printing Experts

Ultimaker 3 - recurrent Gcode error

Recommended Posts

Posted (edited) · Ultimaker 3 - recurrent Gcode error

Hello. Could you help me with this problem?


We are facing a recurrent problem with our Ultimaker 3 extended

The prints stop with the same error message: 'An error occurred while

processing this print job. Line nr = ...' (see pic attached).

The gcode is generated with Cura 2.5 downloaded on Ultimaker website,

and this error keeps happening more than 50% of the time, with different


Resetting the firmware and updating it didn't help.

Could it be a problem with the usb stick?

We are not able to find helpful information online regarding this

problem, could you please help us?

Thanks a lot.


Edited by Guest
  • Link to post
    Share on other sites
    Posted · Ultimaker 3 - recurrent Gcode error

    I have never seen this. I recommend also asking your reseller. But yes I would immediately change the usb stick to another brand. Get the smallest you can (I think I use a 4GB one right now but not sure).

    Does it get this part way through the print?

    It's possible to continue a failed print if you keep the bed hot or part will pop off. You have to know right where it failed (Z value) and then you mostly just edit the gcode removing everything up to that spot but keeping the very first bits. But I'm worried the gantry will knock over your very tall print when it goes to prime the nozzle. I dont' know how to disable the nozzle priming on the UM3. I've never continued a large print on UM3. Only UM2.

  • Link to post
    Share on other sites
    Posted (edited) · Ultimaker 3 - recurrent Gcode error

    For whoever else has the same problem...

    This error can have 3 causes:


    1. Broken usb stick. this happens, try printing via network?
    2. You did not eject the USB drive properly after copying files to it?
    3. There is a communication error in the serial connection inside the printer and the motion controller(marlin) receives the gcode garbled.


    The last one is only really visible since a testing version 3.6.90 but has been possible for ever (never saw it before that version though, mind you I've seen point 1 and 2 happen occasionally before then).

    If you have ruled out the top 2 possibilities and you are using 3.6.90 installed please downgrade to a stable release.

    Edited by Guest
    • Like 1
    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

      • Talking additive | The 3D printing podcast
        Why should we be the only ones asking questions? Join us and ask Jabil all your questions on September 22nd 5pm CET
          • Like
        • 3 replies
      • Ultimaker masterclass: Optimizing your Ultimaker Cura workflow
        Save your seat for either broadcast on September 23.
        What will you learn?
        · Best practices for iterative print preparation and every lesson you should learn from each print
        · The right way to use per-object settings and when they are most useful
        · Easy-to-use resources for anyone who wants to develop their own printer definitions, plugins, or print profiles
        · How to optimize print profile settings and whether to “keep” or “discard” changes
        · When is the right time to export your drawing from CAD? (Based on Ultimaker Cura’s surprising power as 3D control software)
        · And a whole lot more tips and tricks!
        How can I join?
        This free masterclass will take place twice:
        1. 11am CEST (5pm SGT, 5am EDT)
        2. 5pm CEST (11am EDT, 8am PDT, 11pm SGT)
          • Like
        • 0 replies
      • Do you use 3D printing at work? Let us know
        It doesn't matter if you are using 1 Ultimaker or 10, there is inspiration in everything. We're looking for ...
        • 1 reply
    • Create New...