Print problems since new firmware and software update
 

Print problems since new firmware and software update  

  RSS
merrill.a
(@merrill-a)
Trusted Member

As posted elsewhere, since I did the most recent firmware and software updates the following problems have developed:

With no stops inserted in slicer 2.0 the printer periodically stops and says to unload and reload filament. The spacing is random.

The printer keeps stopping for a few seconds and the LCD says "heating" but temps show stable. Intervals vary between 1 minute and 15 minutes.

I have reduced fan speed to 175 and then to 150 but no change.

Woke up this morning (20 hour print) and found printer beeping for filament change. Changed filament (pulled out color and replaced with same) and the printer started but kept doing heating stops. So I turned off the filament sensor and now all problems have gone away (so far after 2 hours of printing). I have the new Mk2.5S sensor upgrade but have not installed yet. I will when I get some clear time as I have to take the whole extruder apart and replace/upgrade as that is part of the 2.5S kit. Until I can do this I will leave the filament sensor off as that seems to be the root of the problem. I must also not that the filament I am printing with is opaque and does not shine (as that was problem discussed previously with the sensor), it is light brown (skin) in color.

I have no clue why the sensor would cause the "heating" stop but can understand how it might possibly cause the filament change stop as it may be too sensitive and just sees a filament out condition. Prior to the latest firmware and software updates, I had no problems with sensor except when using silk or translucent/clear filament.

Comments appreciated.

...
Posted : 29/05/2019 3:35 pm
robert.b115
(@robert-b115)
Active Member

I just recently installed my MK3 - MK3S upgrade, and of course, updated my firmware, as well as D/L ing PrusaSlice 2.0. Up until that point, printing with my MK3 was pure joy. Now it is pure hell. Nothing but problems. Failed print after failed print. Even prints that were beautiful before now fail. I can get excellent bed adhesion but often get failed inter layer adhesion, and lots of nasty artifacts. How sad I am that I upgraded. I have messaged Prusa three times with no reply WTF??? Is anyone else experiencing this? I am becoming an expert at changing PTFE tubes etc, Very familiar with aspects of the extruder that I never knew I'd have to know. If I am using exactly the same g-code and same filament (Same roll, not wet etc.) then why are they failing. Is there some bad code in the MK3S software???

Posted : 30/05/2019 6:07 am
david.j21
(@david-j21)
Trusted Member

Any G-code generated for the MK3 will not work on the MK3S. The extruder and sensors have been almost totally redesigned. You will have to regenerate the G-code for the MK3S, from the original STL file, using the latest PrusaSlicer.

Cheers,Dave Jackson"Enthralled Nooby (not so much maybe, ~58 years old)... If 3d printers had been around 40 years ago... "...
Posted : 01/06/2019 7:37 pm
vintagepc
(@vintagepc)
Noble Member
Posted by: david.j21

Any G-code generated for the MK3 will not work on the MK3S. The extruder and sensors have been almost totally redesigned. You will have to regenerate the G-code for the MK3S, from the original STL file, using the latest PrusaSlicer.

That's a pile of hooey. The g-code is agnostic of the sensor or extruder positioning changes. Those are all taken care of by the firmware. Gcode is dumb low-level stuff.

 

But updating firmware/software is a good diagnostic tool to determine whether the problem may be a bug that has been previously resolved.

This post was modified 1 year ago by vintagepc
Posted : 01/06/2019 7:43 pm
Vojtěch liked
Tim
(@tim-m30)
Illustrious Member

Vintage is 100% correct.  I've ran gcode Mk2 users have made on my MK3 while helping then resolve problems. And similarly, I've given people gcode I've created for testing that they have run.  

David's comment is plain superstition without fact based knowledge of how the firmware and gcode interact/interoperate.

As an example: G28 W ... a gcode command.  How is that command in any way printer specific?   Well, for one the W is not a standard Marlin command. It is specific to Prusa FDM printers.  But what happens when the command is not understood by a printer? Like G80 N7 ? The not-understood portions are ignored.  No harm, no foul. 

Between Prusa printers, there "might be" specific gcode command unique to each, e.g., a MK3 with an MMU gets a few different commands than a MK3 without an MMU.  Changing filament is one.  But I'd not be afraid to run a gcode created for an MMU bearing MK2 on my non-MMU Mk3.  The printers are simply tolerant of these sorts of errors.  

Can gcode damage a printer? Sure, but not because of a model number difference within a family of printers.  The command M104 S500 would be one of those commands I'd hate to encounter.  But then that is't the issue here and setting the nozzle to 500c would break most stock printers.

 

As for failed prints after upgrading MK3 to MK3S ... the major changes that can affect print quality are the print cooling fan shroud and the extruder idler assembly.

The print cooling fan affects thermal properties: running the Nozzle PID calibration can help reduce the differences of the new shroud.

The idler tension also needs to be a bit higher than on the MK3.  One spring is now doing the work of two. Add a few turns to the idler adjustment screw.

Beyond this, the same 40w heater, block, thermistor, nozzle are being used. As are the same X, Y, and Z motors, belts, beds, frames, etc. The only tangible difference is how the filament sensor works. Both types having shortcomings. A glitchy ball bearing in the MK3S can cause load/unload hell (usually an assembly issue). But usually won't cause bad prints. 

If I had to guess what the issue is here, and without a photo that shows the artifacts being described I am guessing, I'd go with PID calibration first. Easy to fix, too. 

This post was modified 1 year ago 2 times by Tim
It is always wise to get more than one opinion......
Posted : 01/06/2019 8:12 pm
jbinfl
(@jbinfl)
Reputable Member

My suggestion is to ensure the correct firmware was downloaded and installed.  I would even go so far as to download it and install it again.  the stopping and unload/load is the wrong firmware being installed.   That is not a Prusa Slicer issue, but a firmware issue.  Same for the heating item...  Once you verifiy that is the issue, then other suggestions can be of assistance.

"With no stops inserted in slicer 2.0 the printer periodically stops and says to unload and reload filament. The spacing is random. The printer keeps stopping for a few seconds and the LCD says "heating" but temps show stable. Intervals vary between 1 minute and 15 minutes."

Strange women, laying in ponds, distributing swords, is hardly a basis for a system of governance!...
Posted : 01/06/2019 11:08 pm
Tim
(@tim-m30)
Illustrious Member

The filament sensor is a known weakness in the Prusa firmware.  The best way to deal with it is to disable the filament sensor.  This has been ongoing since the MK3 was released.  Flaky code in the sensor interrupt handler.   That said, the optical sensor and the IR sensor both can cause false filament detections.   A false detection often causes other problems to assert.  Again, disabling the sensor is a good debug method. 

 

It is always wise to get more than one opinion......
Posted : 02/06/2019 12:42 am
edward.c6
(@edward-c6)
Reputable Member

I'm with Tim-m30.  I had very similar issues to what your having, load unload filament and heating stops, both were from the filament sensor.  A down and dirty check would be to disable it via menu when the issue starts occurring and if it goes away you have your answer.  I have a MK3 but the fix for me when it starts happening is to pull out the sensor and very gently wipe it with the corner of a wet type lens wipe, then reinstall, this usually gets me back up and running for a couple of months.  That being said it happened a couple of months ago and I never got around to cleaning the sensor so it remains disabled.

 

Posted : 02/06/2019 3:24 am
jbinfl
(@jbinfl)
Reputable Member

Yep, the filament sensor is most likely it.  Upon rereading the post, I see now that it might just be a coincidence that it happened after the software update...

It is easy to get confused on the download page now that the MK 3 is not the top link, but has been moved down 😊 .  I have downloaded the wrong software before, so it is always good to double check.

Strange women, laying in ponds, distributing swords, is hardly a basis for a system of governance!...
Posted : 02/06/2019 1:31 pm
prusa3d.com-6
(@prusa3d-com-6)
New Member

Hi, is this purely a firmware issue (and hence can be fixed)? Or is it a hardware issue (problematic design / sensor, etc.)?

If it is the former, is a firmware fix in sight?

Posted : 11/08/2020 6:18 pm
Share:

Please Login or Register