AirBronto
-
Posts
30 -
Joined
-
Last visited
Content Type
Forums
Events
3D Prints
Posts posted by AirBronto
-
-
4 hours ago, ahoeben said:
Thanks for looking in to it. Could you try http://files.fieldofview.com/temp/OctoPrintPlugin.curaplugin ?
You can safely remove the log file every now and then, otherwise it will just keep growing and growing.
Absolutely! Thanks for the quick response. I'll test it when I get home from work and I'll let you know the outcome.
-
4 hours ago, ahoeben said:
I need logs to see what is going wrong. Go to help->show configuration folder, and locate cura.log. Please post that file somewhere and share a link.
Network printing (to UM3) has been totally rewritten in Cura 3.3, and as a result the OctoPrint plugin also needed a fairly major rewrite. The 3.2 version of the plugin will not work with Cura 3.3, and vice versa. The new version has not had as much testing as I would have liked, but I was busy with the setting visibility presets and the support blocker... Testing is much appreciated.
These are the lines that get generated when I print to OctoPrint that seem to include the error. I can try to post the entire log file but it's pretty big:
2018-03-28 17:22:41,306 - DEBUG - [MainThread] UFPWriter.UFPWriter._createSnapshot [25]: Creating thumbnail image... 2018-03-28 17:22:41,306 - INFO - [Thread-8] SliceInfoPlugin.SliceInfoJob.run [29]: Sending anonymous slice info to [https://stats.ultimaker.com/api/cura]... 2018-03-28 17:22:41,309 - DEBUG - [MainThread] UM.View.GL.ShaderProgram.load [55]: Loading shader file [C:\Program Files\Ultimaker Cura 3.3\resources\shaders\overhang.shader]... 2018-03-28 17:22:41,890 - DEBUG - [Thread-5] USBPrinting.AutoDetectBaudJob.run [37]: Checking COM5 if baud rate 38400 works 2018-03-28 17:22:42,705 - ERROR - [MainThread] UM.Logger.logException [81]: Exception: Unable to write to file CFDMP_Turntable_Top_v2: 'BuildPlateModel' object has no attribute 'activeBuildPlate' 2018-03-28 17:22:42,706 - ERROR - [MainThread] UM.Logger.logException [85]: Traceback (most recent call last): 2018-03-28 17:22:42,707 - ERROR - [MainThread] UM.Logger.logException [85]: File "X:\3.3\build\inst\lib\python3.5\site-packages\UM\Qt\Bindings\OutputDeviceManagerProxy.py", line 122, in _writeToDevice 2018-03-28 17:22:42,708 - ERROR - [MainThread] UM.Logger.logException [85]: File "C:\Users\Chris\AppData\Roaming\cura\3.3\plugins\OctoPrintPlugin\OctoPrintPlugin\OctoPrintOutputDevice.py", line 302, in requestWrite 2018-03-28 17:22:42,709 - ERROR - [MainThread] UM.Logger.logException [85]: active_build_plate = Application.getInstance().getBuildPlateModel().activeBuildPlate 2018-03-28 17:22:42,710 - ERROR - [MainThread] UM.Logger.logException [85]: AttributeError: 'BuildPlateModel' object has no attribute 'activeBuildPlate' 2018-03-28 17:22:42,993 - INFO - [Thread-8] SliceInfoPlugin.SliceInfoJob.run [33]: Sent anonymous slice info.
It looks like the Application.getInstance().getbuildPlateModel().activateBuildPlace function is looking for an attribute that doesn't exist. This is with a brand new version of Cura 3.3 with a brand new version of the Octoprint plugin installed through the plugin manager.
Let me know if you need more information.
-
This update is amazing! The bridging settings are really useful and the support blocker is invaluable. Great work Cura team!
Has anyone been able to get the Octoprint plugin working? I can install it from the manager, but the 'Print with Octoprint' button doesn't do anything. I believe this problem happened when Cura 3.2 was released as well, and manually copying the Octoprint files from github worked. Unfortunately, that doesn't seem to work with 3.3. I also tried to copy over the working plugin files from 3.2 to 3.3, but when I do this I get a Python error and Cura 3.3 won't start. I can delete the plugin and Cura will start again, but then the plugin doesn't work.
Introducing Ultimaker Cura 3.3 | Beta
in UltiMaker Cura
Posted
Update: It worked perfectly! Whatever you did took care of it, I could send my print job directly to Octoprint and it picked it up and started printing immediately. Thanks for the super-quick turnaround!