[BUG] 1.5.0 file and folder parsing issues + pause/resume workaround #447
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?
I have a Mega M with a Trigorilla V1.1 Board (+ Blue/White Display, two endstops on Z-Axis) and i have problems to access the SD-Card with Firmware V 1.5.0-b3. As long the SD card is removed, i can access the Setup-Menu, but when the SD-Card is inserted, i see the additional "Backslash"-Folder, but the Machine doesn´t respond any longer to any input=hangs. Sending M20 via Pronterface gives me a File list, M21 tells me "SD Card ok".
What could be wrong?
Edit: Doesn´t happen on 1.4.4.
Also having trouble with Filament change on 1.4.4 during SD-Card-Print. Nozzle parks, releases the filament, Status on LCD goes to "paused" after pressing "continue" the filament is fed in as supposed, but after that the printer stalls. Sending M118/M24 or whatever via Cura wont resume the print. the same happens during printing directly via USB. I suppose the buffer is being filled up and no other external command is accepted.
Ok, the Filament change won´t resume because of this:
echo:busy: processing
//action:paused
//action:prompt_end
//action:prompt_begin Pause
//action:prompt_button Dismiss
//action:prompt_show
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:Insert filament and send M108
//action:prompt_end
//action:prompt_begin Nozzle Parked
//action:prompt_button Continue
//action:prompt_show
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
echo:busy: processing
echo:busy: processing
echo:busy: processing
echo:busy: processing
//action:prompt_end
//action:prompt_begin Paused
//action:prompt_button PurgeMore
//action:prompt_button Continue
//action:prompt_show
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
echo:busy: paused for user
Because the display cannot show "Purge more" and "Continue", it stalls in a "pause for user-loop", which i cannot break by sending various commands via serial. It wants TFT UI input to continue, no matter what command comes in via serial.
SD works. The cause was that the SD-Card contained two Directories (Anycubic factory written with spaces and some Chinese Characters), which presumably cannot be handled by either Marlin 2.1.2 and Long File Format (since 8:3 though M20 worked)- or the Display got a Char which it did misunderstood and locked up. For whatever reason. Anyway, no issue for V1.4.4.
Got Filament Change also working. After issuing M108 (pr pressing "Continue" on the Display) and Filament being fed in, i also have to issue also M876 S1 through the Emergency Parser to overcome the "purge More" and "Continue"-Message, which are not shown on Display.
Hi, sorry for the late reply!
The information is very valuable and thank you so much for sharing it. :)
I'll take a look!
Kein Problem / no problem :-)
Hallo Ich habe ich habe Anycubic Mega S habe ein Problem wen ich beim Drucken Pause setze kann ich nicht mehr fortsetzen mit Version 1.1.9 ging gut mit 2.0 nicht mehr
Already fixed in
4d6715761d
.You can use 1.5.0 Beta 4 to get everything you need :)
Sorry for the late reply, thanks for the Fix, i will try it as soon as i can (currently the Printer is being heavily used). About the Filament issue - any chance to add M876 S1 after the Filament is being fed in or modify pause.cpp, Line 283 ff - or does a modification conflict with the Filament Menu?
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.