MK3S+ sees all gcode models on card except for one model
I have exhausted all my ideas what this issue is. Using Prusa Slicer 2.9.2. MK3S+ has latest firmware 3.14.1-8237. I have never had an issue where I can slice one model where the MK3S+ detects it on the SD card just fine and then slice another model, roughly of the same size and the MK3S+ will not detect that file for nothing. These models are not complex at all. My wife wanted some buttons to use with her sewing craft. One is 0.875"⌀ and the other is roughly the same except it is shaped like an animal head with ears. The animal button is the one that the printer will not detect on the SD card. I did get a pop-up after slicing the animal button that said "looks like a logo or a sign" and I just ignored it. Later I found the option in preferences to disable automatic color change but that made no difference. No errors with either slice.
So to clarify a bit, if I slice and export the normal round button to the SD card, the MK3S+ sees it just fine and I can print. If I slice and export the animal button to the same SD card, the MK3S+ does not detect that gcode file. Any suggestions?
RE: MK3S+ sees all gcode models on card except for one model
It is a longshot seeing as how you had success with one file already, but be certain that the "printer supports binary g-code" option is unchecked in the "Printers" tab. Note that you must have Prusaslicer in "Expert" mode to see this option. To the best of my knowledge the MK3 printers cannot decode binary g-code and therefore likely will not "see" a file with a .bgcode extension.
Regards,
Steve
RE: MK3S+ sees all gcode models on card except for one model
Could it simply have to do with the file names? Name too long, containing a character the printer can't handle, or something along those lines?
RE: MK3S+ sees all gcode models on card except for one model
It is a longshot seeing as how you had success with one file already, but be certain that the "printer supports binary g-code" option is unchecked in the "Printers" tab. Note that you must have Prusaslicer in "Expert" mode to see this option. To the best of my knowledge the MK3 printers cannot decode binary g-code and therefore likely will not "see" a file with a .bgcode extension.
Regards,
Steve
That option is and has been unchecked. It is the strangest thing.
I can add the model of the standard button, slice and print without fail. While Prusa slicer is still up, I can go back, remove standard button model, insert animal button, slice and printer just does not see the file. I can close slicer, re-open and create a new print job with animal button, slice and printer still does not detect it. I can then remove the animal button model and insert standard button model, slice and printer see it without fail all while slicer is still open and not closed after removing the animal button. Arrggg...
RE: MK3S+ sees all gcode models on card except for one model
Could it simply have to do with the file names? Name too long, containing a character the printer can't handle, or something along those lines?
Yep that was it. It wasn't the length but rather I paid no attention to the beginning of the file. I named the standard button beginning with the diameter like this "0.875_button.stl". I missed the leading "0" at the beginning and it was ".875_animal_button.stl". Wow such simple very things can really snowball sometimes.
I thank you for waking me up.
Slice the project as usual but save the project, ( Files > Save as ) then Zip the resulting .3MF and post it here for us to analyse. It will contain both the part and your settings for us to analyse.
Cheerio,
RE: MK3S+ sees all gcode models on card except for one model
Slice the project as usual but save the project, ( Files > Save as ) then Zip the resulting .3MF and post it here for us to analyse. It will contain both the part and your settings for us to analyse.
Cheerio,
I do not think uploading anything will help you. The solution was simple and pointed out by @jurgen-7. His solution caused me to take a look closer at my blunder only to discover that I named the file wrong. I initially saved the .stl model with a "." at the beginning of the file name. The file name was ( .0875_Animal_Button.stl ). The file name was to be named (0.875_Animal_Button.stl). The MK3S+ did not like the dot at the beginning and saw the file as a foreign extension, thus causing the MK3S+ to not detect the file on the SD card. While typing, I had all the characters there, but in the wrong order. When I added this model to Prusa Slicer, Prusa Slicer did not detect the dot at the beginning of the file and sliced the model as (.0875_Animal_Button.gcode) anyway and exported to my SD card and I did not catch this mistake. Perhaps Prusa slicer should have caught this issue ahead. I am not saying Prusa Slicer is bad, but rather Prusa Slicer should perhaps have this feature built-in in order to head off any issues like the one I created.