[BUG] Not possible to print file "ender.gcode" #327
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Have you read all Wiki articles in cluding the FAQ? Yes
https://github.com/knutwurst/Marlin-2-0-x-Anycubic-i3-MEGA-S/wiki
A little problem (or a late Easter egg) with an Anycubic I3 Mega S and your current firmware version:
I tried to print a part for an Ender printer.
The filename started with "ender", The print should be done from the SD card.
Problem: The filename just doesn't show up in the printer's selection menu. All *.gcode files that start with "ender" are invisible ...
Only after renaming the file to "11ender.gcode" only, printing was possible.
Is this a bug, an undocumented option or I'm too stupid? ;)
Greetings from the river Rhine
Ralf
Translated with www.DeepL.com/Translator (free version)
Interesting thing.
Just tested myself, confirmed (Mega P). Apparently it's not "ender", but the keyword "end". "end.gcode", "end123.gcode", etc. all cause the same issue.
"END" is the command sequence to - who would have thought - end the file list. Seems there is no need to issue ENTER afterwards.
FIles alphabetically before "end" are still shown, enything afterwards is not. Only the TFT outpus is affected, Octoprint shows the files on SD card.
This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.
But that only applies to the blue-yellow dgus clone tft, right?
My findings are from a DGUS-clone, right (don’t have a different one to test)
There should be some more or less trivial solutions, if it’s a TFT bug (rewrite the filename, add some prefix, or similar), but I think we should check the original FW/sources first for any hints on that.
I have the problem with the white / blue display, the old version of the Anycubic Mega. The effect also occurs with the firmware 1.4.4 on the motherboard.
This issue is stale because it has been open 30 days with no activity. Remove stale label / comment or this will be closed in 5 days.
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.