Octopi / Octoprint
Posted: Wed Feb 11, 2015 7:48 am
I'm hoping one of you using Octopi version of Octoprint knows if there's a fix for this.
After the last release of Octopi package it hasn't been working properly for me on Internet Explorer or Firefox. I've looked around on their Wiki and version pages but haven't been able to find anything on it.
They added a feature now that lets you specify multiple hotends. I have it set for one hotend. The software loads up properly on the browser initially and I am able to start a print. The problem is that after the print starts on the left side of the browser were the printer status is displayed it goes into this script that start listing non-existent hotends and seems to get caught up in a loop that makes the browser show the non-responsive script error pop-up. So at this point the software becomes unusable. The print does continue to print normally. The problem seems to be just with the web-server end.
Anyone know of a current workaround for the problem until it gets fixed? I'm thinking also maybe in this new version there is something I was supposed to manually add to the config file, but haven't found any documentation that mentions anything.
After the last release of Octopi package it hasn't been working properly for me on Internet Explorer or Firefox. I've looked around on their Wiki and version pages but haven't been able to find anything on it.
They added a feature now that lets you specify multiple hotends. I have it set for one hotend. The software loads up properly on the browser initially and I am able to start a print. The problem is that after the print starts on the left side of the browser were the printer status is displayed it goes into this script that start listing non-existent hotends and seems to get caught up in a loop that makes the browser show the non-responsive script error pop-up. So at this point the software becomes unusable. The print does continue to print normally. The problem seems to be just with the web-server end.
Anyone know of a current workaround for the problem until it gets fixed? I'm thinking also maybe in this new version there is something I was supposed to manually add to the config file, but haven't found any documentation that mentions anything.