Hide Forgot
Version-Release number of selected component: pronterface-2013.10.19-6.fc18 Additional info: reporter: libreport-2.1.9 cmdline: /usr/bin/python /usr/bin/pronterface dso_list: printrun-common-2013.10.19-6.fc18.i686 executable: /usr/bin/pronterface kernel: 3.11.7-100.fc18.i686 runlevel: N 5 type: Python uid: 1000 Truncated backtrace: #1 _create_layers in /usr/lib/python2.7/site-packages/printrun/gcoder.py:306 #2 __init__ in /usr/lib/python2.7/site-packages/printrun/gcoder.py:184 #3 loadfile in /usr/lib/python2.7/site-packages/printrun/pronterface.py:1701
Created attachment 829359 [details] File: backtrace
Created attachment 829360 [details] File: environ
Do you know the steps to reproduce this?
Created attachment 829417 [details] slice and load this file reproduce error. When slicing this file, was the warnings: Dangling edges, will use intersecting circles to get import layer at height -4.71 Slice layer count 19... ... Slice layer count 22... Warning, the triangle mesh slice intersects itself in getLoopsFromCorrectMesh in triangle_mesh. Something will still be printed, but there is no guarantee that it will be the correct shape. Once the gcode is saved, you should check over the layer with a z of: -3.35 ... I can not understand, what is wrong in my design.
Please, insert into gcoder.py lines something alike: [root@localhost printrun]# diff gcoder.py gcoder.old.py 306,307d305 < if self.est_layer_height ==0: < self.est_layer_height = 0.1
That might make sense, but is nto a very clean solution. Can you share the STL/Gcode?
Created attachment 832761 [details] load this file reproduce error STL file was shared 2013-11-26 12:42 EST. Now i share GCode file.
Oh, sorry, I didn't noticed the attached STL. Thanks
Reported upstream: https://github.com/kliment/Printrun/issues/460 In the meantime, let me tell you one thing: When you slice an STL file with Skeinforge it is not automatically put to zero Z coorinates. This could lead to three things: 1) The STL was placed at Z0 by the creator, and everything goes fine (and if the design is yours, it's a good manner to do this) 2) The STL starts on positive Z coordinate and the printer will start print "into the air" (bad print) 3) The STL starts on negative Z coordinate and the printer will print all negative layer to layer no. 1 (bad print) To avoid that, always use Plater and the button **Snap to Z = 0**
Created attachment 833228 [details] this file was snaped to Z=0, but also reproduce error I have made as you wrote, but error return again: I load file into Plater, then snap z=0, then press [Done]. Other my files do not reproduce this error, when started at Z<0.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.