-
Notifications
You must be signed in to change notification settings - Fork 24
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
Problems after updating to v1.3.3 #35
Comments
I had the opertunity to test the plugin with a different printer and found out the reason for this strange behaviour: Remove the colon (replace by =) or update to a the new releasee V1.3.4. Please test it |
Hi Olli,
Thank you for the reply, I will give it a try again.
Have a nice evening
Pieter Coetzee
…On Wed, Apr 25, 2018 at 6:12 PM, OllisGit ***@***.***> wrote:
I had the opertunity to test the plugin with a different printer and found
out the reason for this strange behaviour:
The problem is the new default printer-message. There is a : (colon) in
the message.
After sending this faulty command the printer run into a kind of endless
loop, see terminal tab.
Remove the colon (replace by =) or update to a the new releasee V1.3.4.
Please test it
Olli
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#35 (comment)>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/Ak7eX8maGZdq8Qwdld6VTANXMnOfKAbRks5tsKBlgaJpZM4TjRuH>
.
|
Hi Olli, Looks like the bug has been fixed now with v1.3.4 Thank you very much Pieter Coetzee |
After updating plugin from v1.3.0 to 1.3.3 my octoprint becomes unresponsive. When I click on a gcode to start printing, nothing happens. No rise in bed temp or nozzle temp and even if I want to cancel the print, nothing happens. I have to reboot my octoprint. If I disable the plugin, everything works fine. With v1.3.0 everything was also working fine. Running octoprint v 1.3.8.
The text was updated successfully, but these errors were encountered: