-
-
Notifications
You must be signed in to change notification settings - Fork 19.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
M190 and M109 may lead to zombie state #4198
Comments
|
Commands that go into a loop, such as We have a request (#3611) to add a new (un-blockable) GCode to break out of some of these blocking loops, but this will require adding a more low-level check for the given command. And there is still no guarantee that a command can be received and processed while the queue is blocked, because we have to respect a full serial character buffer also. See that thread for the issues raised. For now, until we can look at some redesign of the foundations of our command processing (preserving compatibility with host software), this is how it will have to work. I realize that |
A patch for now is to send it a temp command that is lower then the actual temp from LCD( I dont know if this works from host), faster is the reset switch :) |
@maukcc That works because commands sent from the LCD bypass the command queue. |
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. |
After I send "M190 S60" to Marlin from Printrun, I cannot cancel the order util the temperature of hotbed reach 60.If I don't want to wait, I have to press the RESET button on RAMPS.
If someone want to contral printer with APP in mobile phone, after "M190" or "M109" sended, he/shi cannot pause the printing task at once.Sometimes It's troublesome。
So I suggest: Marlin can deal new "M190" commond when dealing "M190". The same as "M109"
From looming
The text was updated successfully, but these errors were encountered: