Decoding the gcode?
My mk3 has been working great since I assembled it. I have one print now that refuses to stick. Thought at first that I needed to clean the bed better but first I tried to print a known good file and it printed fine. So I'm thinking I did something wrong in the slicer that has this one file messed up. I switch back and forth between the .4 and the .25 nozzle. I'm thinking I might have failed to set the nozzle to .4 for this file. I used Brackets to view the g code but I didn't see anything that would be obvious to a noob like me as to which nozzle this file was set to use. Can anyone tell me what I should be looking for in the code to figure out if that's what I did? TIA
Re: Decoding the gcode?
[...] Can anyone tell me what I should be looking for in the code to figure out if that's what I did? TIA
Your best bet would be to study the preview in your slicer. Using Slic3rPE, save the gcode file, then click the Preview button at the bottom. You can view each layer for problems. One common mistake is to not have the model flat on the bed. Look carefully at the 1st layer to make sure there's good contact between the model being printed and the bed. I've had some models with bumps or ridges on the 1st layer that provided minimal actual bed contact, even though it looked flat.
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
Re: Decoding the gcode?
If you're using Slic3r PE with mostly default settings, it should insert the settings used at the end of the file, like this:
; nozzle_diameter = 0.4
You can open the gcode file with a regular text editor.
Re: Decoding the gcode?
notepad++ is free and works!
Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
Re: Decoding the gcode?
[...] Can anyone tell me what I should be looking for in the code to figure out if that's what I did? TIA
Your best bet would be to study the preview in your slicer. Using Slic3rPE, save the gcode file, then click the Preview button at the bottom. You can view each layer for problems. One common mistake is to not have the model flat on the bed. Look carefully at the 1st layer to make sure there's good contact between the model being printed and the bed. I've had some models with bumps or ridges on the 1st layer that provided minimal actual bed contact, even though it looked flat.
I'm thinking that Slic3r places the model on the bed by default? If not, then I have the check box enabled. I've never had to move a model to the bed. Model is approx. 45mm x 80mm rectangle with a flat bottom so I should be ok there? The intro line appears to be normal, I notice a problem as soon as it goes to lay the skirt line. Acts just like the live z is too high but only this model is giving me the trouble. I already resliced the model and made sure I had the settings correct before I left for work, I'll try printing the new file tonight. I just wanted to diagnose what I did wrong in case I see this problem again.
I never tried it and I'm not at home to look, but is there a way to reload this g code back into Slic3r and view it like I can do in PrusaControl?
Re: Decoding the gcode?
If you're using Slic3r PE with mostly default settings, it should insert the settings used at the end of the file, like this:
; nozzle_diameter = 0.4
You can open the gcode file with a regular text editor.
Hmmm, so it should be that obvious, eh? LOL. I'll hafta take another look. Thanks!
Re: Decoding the gcode?
notepad++ is free and works!
Joan
Cool! Free is good! I see it says notepad++ supports tabbed editing so if the new file works I can open them side by side to compare. I don't think I can do that in Brackets.
Thanks Joan!
Re: Decoding the gcode?
If you're using Slic3r PE with mostly default settings, it should insert the settings used at the end of the file, like this:
; nozzle_diameter = 0.4
You can open the gcode file with a regular text editor.
Hmmm, so it should be that obvious, eh? LOL. I'll hafta take another look. Thanks!
OK, so I didn't mess up the nozzle diameter setting. Both the old and the new file showed it set to 0.4mm. I went ahead and kicked off the new file tonight and it layed down a normal intro, skirt line, and first layer without changing anything but the file. It's still printing but it looks good so far.
I did open both files side by side in Notepad++ and the only thing that stood out was that the old file was almost 400 lines larger than the new. But the difference was nearly 40000 lines in, which I assume is much too far in to have affected the start of the print?
So now I think I might be the victim of temperature compensation of the PINDA probe? Normally I just wipe the bed, preheat, and go but I had to change the nozzle first this time and load the filament so maybe the probe warmed up enough to raise the Z axis to where the print wouldn't stick? I have the Z raised to nearly the top of it's travel when I swap nozzles so bed heating isn't too much of an issue but does the hot end heat the PINDA too? One way to find out I guess, after this print finishes I'll let the printer set overnight and try printing the old file in the morning from a cold start?
Re: Decoding the gcode?
Yes the pinda temperature can change the live z height. The MK3 pinda is supposed to compensate, but it may not be perfect. In this thread some people (myself included) posted some start gcodes that will warm (and cool) the pinda probe to a set temperature, with the hopes of achieving consistent results: https://shop.prusa3d.com/forum/assembly-and-first-prints-troubleshooting-f62/material-going-out-of-nozzle-while-heating-up-or-o-t23665.html#p101627
Re: Decoding the gcode?
[...] Can anyone tell me what I should be looking for in the code to figure out if that's what I did? TIA
Your best bet would be to study the preview in your slicer. Using Slic3rPE, save the gcode file, then click the Preview button at the bottom. You can view each layer for problems. One common mistake is to not have the model flat on the bed. Look carefully at the 1st layer to make sure there's good contact between the model being printed and the bed. I've had some models with bumps or ridges on the 1st layer that provided minimal actual bed contact, even though it looked flat.
I see what you mean now. I drew a different model with a flat base but tilted a few degrees from level in the XY plane. Slic3r did not set the base flat on the platform even though the base itself was indeed flat. Not the problem with this file but I'll need to watch for that in the future. Thanks!