-
Notifications
You must be signed in to change notification settings - Fork 5
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
M117 (Set LCD Message) not handled correctly #10
Comments
I'll take a look when I get a chance. Probably Saturday at the earliest. |
Thanks for your quick response! From what I can see, these lines are probably responsible for capitalizing the string. It looks like there's a blacklist this command may be missing from? |
Weird. I copied that function right from OctoPrint, since it isn't public: |
Oh, that's interesting. I should have a look at what OctoPrint does when you directly submit the whole command in the terminal. Maybe it's an OP bug. |
Well, OctoPrint only expects one command at a time so multiple may throw an error or produce some weird output. |
Try 0.1.6 (your code works for me now) |
I’ll have a look at it this evening 😃
|
Sorry, I didn't get around to checking this, yet. Probably this evening. |
Yup! Works like a charm! Thanks for the quick fix! Especially command like:
For Auto home / ABL (G28 / G29), the last command executes before the system finished the operation, but I assume that's an OctoPrint limitation. |
The terminal commands aren't playing nicely with
M117
.When
M117
is the first command, like this:M117 Reporting setting; M503
Then the commands after that aren't executed.
When
M117
appears at the end of a chain of commands:M503; M117 Reporting setting
Then the string passed to
M117
is capitalized.This means that command like these won't work:
M117 Auto Homing; G28; M117 Auto Homing Done;
M117 Centering; G90; G0 Z5; G0 X117.5 Y117.5; G0 Z0; M117 Centered;
The text was updated successfully, but these errors were encountered: