Skip to content
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

Closed
phcoetzee opened this issue Apr 25, 2018 · 3 comments
Closed

Problems after updating to v1.3.3 #35

phcoetzee opened this issue Apr 25, 2018 · 3 comments
Labels
type: bug Something isn't working

Comments

@phcoetzee
Copy link

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.

@OllisGit OllisGit added the type: bug Something isn't working label Apr 25, 2018
OllisGit pushed a commit that referenced this issue Apr 25, 2018
@OllisGit OllisGit added the status: waitingForFeedback Wating for Customers feedback label Apr 25, 2018
@OllisGit
Copy link
Owner

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

OllisGit pushed a commit that referenced this issue Apr 25, 2018
@phcoetzee
Copy link
Author

phcoetzee commented Apr 25, 2018 via email

@phcoetzee
Copy link
Author

Hi Olli,

Looks like the bug has been fixed now with v1.3.4

Thank you very much

Pieter Coetzee

@OllisGit OllisGit removed the status: waitingForFeedback Wating for Customers feedback label Apr 27, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants