Problem with calling the M600 command again #490
Comments
EnableDevice
changed the title
|
Good finding. This might be a bug. I'll take a look. Thanks! |
|
Hello, Oliver. This issue occurred in build "MEGA_S_v1.5.2". I'll attach a photo of what the display should have looked like during a normal pause, and what it actually looked like. Now I have installed TMC drivers, 3DTouch and rebuilt the firmware. I'll see how the printer behaves now.
|
|
I conducted a series of experiments and found out an interesting thing! The M600 command is not just executed once in the code, it is executed once at all! That is, if after flashing the firmware you run the code with this command, it will be executed! The plastic is unloaded, the printer beeps, and the Pause button changes to a Continue button. And you can continue printing. But if you run this code again, the Pause button will not change to a Continue button. At the same time, the plastic is also unloaded, the hotend is parked and the printer beeps. And when you press pause, this is the reaction. Now you can only stop printing. And most importantly, turning off the printer does not produce any results. The M600 command is used only once. :)
|
|
So the M600 command got back to work. :) Some kind of floating problem, I can’t understand the pattern yet. I'm monitoring the terminal to see what's being transmitted... UPD; No, it doesn't work again. I checked it on a test file, everything works as expected. I ran the big print and after three hours everything stopped. :((( At the same time, everything is fine in the logs. ПОЛУЧЕНО: //action:paused
ОТПРАВЛЕНО: M105
ПОЛУЧЕНО: echo:busy: processing
busy: processing
ПОЛУЧЕНО: X:10.00 Y:210.00 Z:20.00 E:-3.92 Count X:800 Y:16800 Z:8000
...
ПОЛУЧЕНО: echo:Insert filament and send M108
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
busy: paused for userThen the heating turned off after a timeout. At the same time, nothing changed on the display. Send M108 to heat nozzle
ПОЛУЧЕНО: //action:prompt_end
ПОЛУЧЕНО: //action:prompt_begin Heater Timeout
ПОЛУЧЕНО: //action:prompt_button Reheat
ПОЛУЧЕНО: //action:prompt_show
ПОЛУЧЕНО: echo:busy: paused for user
busy: paused for user
ПОЛУЧЕНО: echo:busy: paused for userUPD: Let me summarize everything I've done. I have a test file containing two M600 plastic replacements. I launched it, the first command worked (the “Continue” button appeared), but on the second command this button did not appear, the screen remained the same. It was impossible to continue printing. I stopped printing and ran the same file again. Now the first command to change the plastic did not work. I launched it again, and again the plastic was simply unloaded, but the continue button did not appear. I ran it again and now BOTH commands worked! I ran it over and over again, both commands worked! I ran another file, which also had two plastic changes, and again only the first command worked. All the printing went into the trash bin. :( There is no pattern. |
|
While I'm poking around in the code, trying to understand why the printer behaves this way, I need to print. And I found a way where all plastic changes are processed correctly. This is printing via OctoPrint. Yes, it's a crutch, but it works. :)
|
|
Same finding: tried a print with 2 filament changes. Either it does not start at all after it is up to temperature or the pause button does not change to continue when changing the filament or after a continue, it does not start again, heats only 10 degrees too high, then 10 degrees too low, always alternating or the temperature display changes to 0 and it cools down completely. A resume is also not possible, as the target temperature is always 0. |
How did you get the color change working in octoprint? |
|
apmyp1990, just a file launched for printing via OctoPrint normally executes the M600 command. The printing stops, the plastic is unloaded and the “Continue” button appears. After pressing it, printing continues as expected.
|
|
@EnableDevice |
|
@apmyp1990 ; layer 25, Z = 3.650
M600
; feature inner perimeter
G1 Z3.650 F1002
... |
|
Hello, I got exactly the same problem as user EnableDevice describes in detail (sporadic no continue button at M600 at nearly 50% of the print jobs). Today I tried a successfull workaround after occuring the problem. After reading here that octoprints „Continue“ helped I read about Marlin M108. So I printed with active console (Pronterface; other terminal SW should also work; I tried TeraTerm) and there also M108 was mentioned („echo:Insert filament and send M108“). Perhaps it helps to isolate the problem a little bit: Also with sporadic occurence: The display content at the end of print job is also not correct. The end G-code (from wiki here) let the printer beep and normally on display a separate grey summarize window with „ok“ Button cames up with „Printing done took xyz…“. Also in 50% of jobs the mask does no occure after the beeps. If I pressing the STOP button on display and confirm with yes the summarize window occurs. But there seems no dependency if the mentioned M600 problem occured before or not. Also I observed in case of the problem with M600 the nozzle temperature cames from a higer value (210 instead 200 as usual). Another problem (It seems not have any influence): Preheat stops after disconnecting pronterface. If I select preheat via menu after disconnecting the set values came only some seconds and after that they reset to Zero. If I connect pronterface again and select preheat via printer menu it works. If I restart the printer it always works. How can I help to isolate the problem? As revenge to Olivers great work I could spend some time to the issue. For faster way of me we also could exchange private messages in german. Regards |
|
Here I post terminal output in bad and good case of not occured Contiunue button. But it seems not containing enough details. 2) occured continue button at M600 |
|
Test with triggered filament sensor (for easy and fast M600) can provoke the same issue (sometime button occures sometime not). |
|
I found the right define for more verbosity on serial port: ANYCUBIC_TFT_DEBUG I assume that line with action:prompt_button Continue means that normally the button should appear. |
|
After long nights I could understand and fix it.
Thanks again for the great fw (I use the great BL touch functionality). |
|
Wow! @uwetaz thats a great finding! Thank you so much! I think that because I always used the original sources from Anycubic and simply assumed that it worked that way, I never thought of observing the time offset. Great work! I took a quick look at your patch and would implement it as it is, but it would be more elegant and understandable if you made a pull request. That way you will also appear in the contributors :) If you don't want that, I can of course just adopt your change as it is. I leave that up to you ;) |
|
@knutwurst |
Bug Description
Hello.
When using the M600 command, the "Continue" button appears on the screen only on the first call. If there are two plastic changes in the code, then for the second time the “Pause” and “Stop” buttons are present on the screen. And further printing is impossible.
UPD: I experimented. It turned out that it wasn't even a matter of sending the command again. In most cases, the M600 will display “Pause” and “Stop” on the screen when sending. In this case, the plastic is unloaded correctly, it beeps with a buzzer, but does not allow printing to continue, since there is no button "Continue". Only once was it possible to continue printing. And it is unknown why this happened.
Printer: Mega S (first generation with Anycubic 1.0 display).
Additional Information
As I understand it, this is a known problem, since another author found this in releases: "Fixed M600 issue where the screen only showed continue on the first time it was called, not on any further calls".
The text was updated successfully, but these errors were encountered: