New Gcodes not visible on Mini
When I plug my Prusa provided thumb drive into the mini, it recognizes the drive and it can read gcodes that I've made prior to today. However, the new gcode that I just made with the Prusa slicer, in the exact same manner as always. The gcode is viewable in file explorer on the computer and the desktop version of gcode previewer can open it without any problems from the drive. I've double checked and it's the correct file type, though again, I'm not doing anything different than I've done in the past.
Any thoughts or advice? Can I reformat the drive? If so is there something I might need to do for it to then speak to the printer appropriately?
Thanks,
Update
So, in looking for work arounds, I've found that if I save the gcode to the PC and then move it to the flash drive instead of saving directly to the drive the printer recognizes the gcode just fine. This is really puzzling.
Line ending encoding?
So, in looking for work arounds, I've found that if I save the gcode to the PC and then move it to the flash drive instead of saving directly to the drive the printer recognizes the gcode just fine. This is really puzzling.
Potentially something going on with line-endings between MSDOS (CR/LF), UNIX (LF), or something like that?
just random ideas.
Write caching shouldn't be a problem anymore on modern PCs but you can try to see if hitting the eject button in Prusaslicer before you remove the stick helps. It should flush the write cache.
Eject Drive Button
I always do and, in trying to figure it out, I tested both with and without ejecting and got the same result. Older gcodes visible, ones from [yesterday] were not.
RE: New Gcodes not visible on Mini
This did it for me. Eject the drive through the slicer. Thank you!
Write caching shouldn't be a problem anymore on modern PCs but you can try to see if hitting the eject button in Prusaslicer before you remove the stick helps. It should flush the write cache.