The header doesn't match the header for tallhex.g found on the MakerGear Wiki page under "sample prints": (http://makergear.wdfiles.com/local--fil ... /tallhex.g). That one was sliced using slic3r. Sounds like this "tallthin" you refer to was sliced using Simplify3D, and is not posted on the Wiki site.3dPrintingMD wrote:Just for learning I opened up the tallthin that was sent to me from MG.
Here are the settings it shows. I assume that these are the only settings to be found in the gcode.
...
I looked at the tallhex.g gcode using Simplify3D as a gcode previewer, and I see that it is thick enough for three outer and three inner perimeters, with additional fill in between. So there is plenty of fill in the model, and it's definitely not a single-wall spiral vase slice.
The only thing that stands out to me is that the fill density is 0.2, and tallhex.g is set to a fill density of 0.2, and they both are set to 3 perimeters. So if one weighs more than the other, it must be extruding more all the time, because all of the other settings look exactly the same. Both claim to be set to an extrusion multiplier of 1 (which is a bit too high, but we're looking for differences between the two gcode setups, and that's not one).Quark wrote:3dprintingMD posted the gcode included in the SD card. Here is the Slic3r ini file that came on the SD card:
The only thing I can suggest is not to use a first layer height of 0.3 and a first layer extrusion width of 200%. I would usually suggest a 0.2mm first layer height and a first layer extrusion width of 100% (or default, which is value 0). Makes me wonder if the extrusion width is somehow not going back to normal after the first layer. You could figure that out from the gcode; it would require a little bit of calculation to determine whether both files are incrementing the E value by the same amount per X-Y movement distance.