Notifications
Clear all

Problems with Gcode files fron the SD card  

Page 1 / 2
  RSS
Lvet
 Lvet
(@lvet)
Estimable Member
Problems with Gcode files fron the SD card

Hello,

I am trying to print the tree frog model that came with the gcode files on the SD card. The results are pretty terrible.

If instead I slice the tree frog model using the default "Prusa PLA" settings in PrusaSlicer, I get a reasonably decent result.

I would like to understand why. I am assuming that the files on the SD card are optimised for the MK3S and the Prusa PLA filament that came with the printer.

Cheers

Luca

IMG_8658.jpg

This topic was modified 5 years ago by Lvet
Posted : 25/08/2019 4:05 pm
rmm200
(@rmm200)
Noble Member
RE: Problems with Gcode files fron the SD card

Did you try a GCode frog again after the one you sliced?

Just to eliminate the chance of a bad section of filament that got you.

Posted : 25/08/2019 4:40 pm
Lvet
 Lvet
(@lvet)
Estimable Member
Topic starter answered:
RE: Problems with Gcode files fron the SD card

Hi Rmm200,

Yes, I tried several times, with different slicing settings and repeatedly from the SD card gcode. Everything is consistent with the fact that the SD card gcode is leading to mediocre results. It's almost as if it has been sliced for a different type of filament.

Posted : 25/08/2019 4:45 pm
rmm200
(@rmm200)
Noble Member
RE: Problems with Gcode files fron the SD card

You are going to need advice from one who has "seen it all".

I am still new here and can only comment on simple problems. This one is not...

Posted : 25/08/2019 4:50 pm
bobstro
(@bobstro)
Illustrious Member
RE: Problems with Gcode files fron the SD card

You can edit the pre-sliced gcode to extract the "bad" settings and import them into PrusaSlicer. The pre-sliced models have been prepared on older versions of the slicer that lacked some features. The version I have was sliced with Slic3rPE 1.40 back in mid-2018. Is it possible that you printed one meant for a different Prusa printer model?

I wouldn't expect to see results as bad as you're seeing with the frog pre-sliced for your printer, but I also wouldn't worry about it if you're getting good results with the parts you slice yourself. You don't want to slice with those old defaults anyhow.

If you're really interested in pursuing this, zip the gcode file giving you the bad results and upload (attach) it here so we can analyze it.

My notes and disclaimers on 3D printing

and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan

Posted : 25/08/2019 6:24 pm
--
 --
(@)
Illustrious Member
RE: Problems with Gcode files fron the SD card

The non-working frog is 0.05 mm layers: the working frog looks like about 0.15 mm layers.  So it's the low volume printing issue.

I've run across it from time to time with Prusa filament: my opinion is that the Prusa filaments have a lot of solids for pigmentation and these solids hamper small layer height extrusion. 

Make sure you have adequate tension on the filament: nozzle pressures seem to be a lot higher when printing 0.05 mm. And with the extra viscous nature of the Prusa colors like beige and white 0.05 is problematic (the old silver wasn't too bad, unsure what they are shipping today). 

 

Posted : 25/08/2019 6:37 pm
Lvet
 Lvet
(@lvet)
Estimable Member
Topic starter answered:
RE: Problems with Gcode files fron the SD card

Hi Bob,

here is the offending file 🙂 

Attachment removed
Posted : 25/08/2019 7:08 pm
Lvet
 Lvet
(@lvet)
Estimable Member
Topic starter answered:
RE: Problems with Gcode files fron the SD card

Hi Tim,

You are very right. I will try to reslice the model with 0.05mm layers and print it, to see if it shows the same defects.

Posted : 25/08/2019 7:12 pm
bobstro
(@bobstro)
Illustrious Member
RE: Problems with Gcode files fron the SD card
Posted by: luca

here is the offending file 🙂 

I may toss it on this evening to see what happens. Again, though, if you're getting good results slicing yourself, I wouldn't worry about it too much.

My notes and disclaimers on 3D printing

and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan

Posted : 25/08/2019 7:20 pm
bobstro
(@bobstro)
Illustrious Member
RE: Problems with Gcode files fron the SD card

Erm.. I'm printing this thing, and it seems to be twice as large as the treefrogs I printed off the pre-generated folder on my SD card. It also has a huge brim. It doesn't look much like what you showed in your pic.

My notes and disclaimers on 3D printing

and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan

Posted : 25/08/2019 10:11 pm
Dave Avery
(@dave-avery)
Honorable Member
RE: Problems with Gcode files fron the SD card

the pre-sliced one is at 50% scale 🙂

Posted : 25/08/2019 11:11 pm
bobstro
(@bobstro)
Illustrious Member
RE: Problems with Gcode files fron the SD card
Posted by: david.a66

the pre-sliced one is at 50% scale 🙂

Your original post showed what you claimed were results using the pre-sliced gcode off the SD card. I asked you to upload that and you provided a completely different file. I spent 3 hours and 40 minutes printing something unrelated to your issues. What exactly is your intent?

My notes and disclaimers on 3D printing

and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan

Posted : 26/08/2019 2:13 am
--
 --
(@)
Illustrious Member
RE: Problems with Gcode files fron the SD card

My original tree frog STL is about 50 x 50 mm, created 2018-05-28.  

My OEM gcode is:
; generated by Slic3r Prusa Edition 1.40.0+173-win64 on 2018-06-25 at 09:36:09

The uploaded gcode is:
; generated by Slic3r Prusa Edition 1.41.1-beta+win64 on 2018-10-03 at 15:02:40

All the frogs are the same size, and the sample gcodes have a brim.

 

This post was modified 5 years ago by --
Posted : 26/08/2019 2:55 am
--
 --
(@)
Illustrious Member
RE: Problems with Gcode files fron the SD card

Further inspection, I see some differences that aren't making a lot of sense, almost like the uploaded gcode file is corrupt from Prusa.

Luca - try printing this gcode of the frog.

TreeFrog_50um_Sample

This was your file:

//
// File Checksum Integrity Verifier version 2.05.
//
82bf5287e4ee9eb7a96bc66f129ac732 mk3_pla_treefrog_50um_3h_40m (2).gcode

This is my older version of the frog:

//
// File Checksum Integrity Verifier version 2.05.
//
3369b3e04ecb8bdedf8a5f85740edb18 mk3_pla_treefrog_50um_3h_40m.gcode

And to ensure you got the right file without damage:

fciv -add "MK3_PLA_Treefrog_50um_3H_40M.gcode"

Posted : 26/08/2019 3:20 am
bobstro
(@bobstro)
Illustrious Member
RE: Problems with Gcode files fron the SD card

The uploaded gcode and the samples I downloaded have been sliced using very different settings. Off my SD card:

; generated by Slic3r Prusa Edition 1.40.0+173-win64 on 2018-06-25 at 09:36:09
; external perimeters extrusion width = 0.40mm
; perimeters extrusion width = 0.40mm
; infill extrusion width = 0.40mm
; solid infill extrusion width = 0.40mm
; top infill extrusion width = 0.40mm
; first layer extrusion width = 0.40mm

The uploaded sample:

; generated by Slic3r Prusa Edition 1.41.1-beta+win64 on 2018-10-03 at 15:02:40
; external perimeters extrusion width = 0.45mm
; perimeters extrusion width = 0.45mm
; infill extrusion width = 0.45mm
; solid infill extrusion width = 0.45mm
; top infill extrusion width = 0.40mm
; first layer extrusion width = 0.42mm

So I'm really not sure how @luca-vicini expects any resolution of what was wrong with the original gcode sample. This uploaded version prints fine. The sample on my SD card prints fine. No idea what went wrong with your print.

My notes and disclaimers on 3D printing

and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan

Posted : 26/08/2019 4:40 am
--
 --
(@)
Illustrious Member
RE: Problems with Gcode files fron the SD card

The kicker is the print time on the gcode uploaded by Luca does not match the print time in the filename: 

Filename: MK3_PLA_Treefrog_50um_3H_40M.gcode
Print time: ; estimated printing time (normal mode) = 3h 54m 33s

So it's looking like Slicer did NOT create the file.

This post was modified 5 years ago by --
Posted : 26/08/2019 7:49 am
Lvet
 Lvet
(@lvet)
Estimable Member
Topic starter answered:
RE: Problems with Gcode files fron the SD card

Hi Bob,

the frog on the left (in my first picture) is the frog that you printed. I’ve only removed the brim, but it’s exactly the same file. You will notice that there are these strange stripes on the back of the frog.

Last night I have printed the same file with a different PLA filament (from another manufacturer) and these artefacts on the back disappeared. I sliced another time the frog with a 0.05mm resolution, and the artefacts reappeared. 

I will post the pictures.

thank you for the time you took to print the file, but I can assure you it’s the same model on my pic with the brim removed

This post was modified 5 years ago by Lvet
Posted : 26/08/2019 10:48 am
vintagepc
(@vintagepc)
Member
RE: Problems with Gcode files fron the SD card

The diagonal "wave" section is severe underextrusion. Pics here:

https://forum.prusa3d.com/forum/original-prusa-i3-mk3s-mk3-general-discussion-announcements-and-releases/an-accidental-artistic-effect-deliberate-underextrusion/#post-149243

If it went away with another filament temporarily it sounds like you need to do some hot end service. Something is causing it to not extrude properly (blockage, resistance to filament movement, etc)

Posted : 26/08/2019 11:39 am
Lvet
 Lvet
(@lvet)
Estimable Member
Topic starter answered:
RE: Problems with Gcode files fron the SD card

Hello,

here is the pic of two other prints

The black frog on the right is from the file on the SD card but was printed with another PLA filament (the stringing is probably due to the temperature that is too high and outside the filament specs). It has a huge brim (that this time I didn't remove).

The frog on the left is the a print coming from the resliced model with 0.05mm layers. It has the same under extrusion problems of original SD card file. The print stopped in the middle because of the bond tech gears started slipping.

Bob and Tim,

If the file printed correctly in your setup, it's either a problem with my printer or a problem with the PLA spool that came with the printer. I suspect it might be something related to my extruder assembly. I will clean everything thoroughly and continue testing.

The file came with the printer SD card. I purchased the printer about two months ago. I have no idea why the file has these differences in printing times. I will try to print your version of the file.

Attachment removed
This post was modified 5 years ago by Lvet
Posted : 26/08/2019 12:52 pm
bobstro
(@bobstro)
Illustrious Member
RE: Problems with Gcode files fron the SD card

Here are the results I got. The pre-sliced model you uploaded with 0.05mm layers is on the left, another I re-did out of curiosity at 0.02mm layer heights on the right. These were just slap-dash efforts printed with a 0.40mm brass nozzle and some inexpensive Mad Maker filament I had mounted. 3 hours and 40 minutes for the one on the left (roughly, didn't track it closely) and 8 hours 30 minutes on the right.

These aren't amazing results and I certainly didn't put any work into them, but I think these show that:

  1. The pre-sliced files are different than some of us received, but at least this one works.
  2. The Prusa Mk3 has no problem with very fine layer heights. Mine's a stock OG Mk3 with the R2 extruder parts.

The frog printed fine with no brim.

My notes and disclaimers on 3D printing

and miscellaneous other tech projects
He is intelligent, but not experienced. His pattern indicates two dimensional thinking. -- Spock in Star Trek: The Wrath of Khan

Posted : 26/08/2019 2:00 pm
Page 1 / 2
Share: