Jump to content
Ultimaker Community of 3D Printing Experts
Sign in to follow this  
robogrobo

Can't load Netfabb .gcode with pronterface

Recommended Posts

Hi there

I want to test the slicing with Netfabb and try to load the generated .gcode (this) with pronterface but on the commandline I get this error:

0 mm of filament used in this print
the print goes from 5.01 mm to 12.24 mm in X
and is 7.23 mm wide
the print goes from 197.81 mm to 200.0 mm in Y
and is 2.19 mm wide
the print goes from 0.0 mm to 49.93 mm in Z
and is 49.93 mm high
Exception in thread Thread-1:
Traceback (most recent call last):
 File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 530, in __bootstrap_inner
   self.run()
 File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/threading.py", line 483, in run
   self.__target(*self.__args, **self.__kwargs)
 File "./Printrun/pronterface.py", line 1492, in loadviz
 File "/Applications/3D/cura/Printrun/pronsole.py", line 143, in estimate_duration
   moveduration = currenttravel / f
ZeroDivisionError: float division by zero

Any ideas what I did wrong? Thanks.

Dominik

Share this post


Link to post
Share on other sites
looks like NetFabb generated a feedrate of zero somewhere. Could you check if there is an "F0" somewhere in your netfabb generated GCode?

He shouldnt check, you should make sure it will never turns to 0, because that will mean it will freeze the machine :p

I'm pretty sure I do not control the GCode generater in NetFabb ;-)

But it's a bug in PrintRun. It uses 0 as default feedrate when you haven't got a feedrate yet. And you have a "G1 E0" before any feedrate setting in your start code. Which causes a move time calculation with a zero feedrate. I've fixed it for the next version.

Share this post


Link to post
Share on other sites

A quick fix would be indeed to remove the G1 E0, or put an F300 behind it so it has a feed rate.

My next version is ready when it's ready :p I'll announce it on the forums. RC2 is only a week old right now. And has only 2 bugs that I know off (first run wizard problems, first layer of support has too little material). There are a bunch of new features in the work, the project planner being the biggest of them all.

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

  • Our picks

    • Introducing Ultimaker Cura 3.6 | Beta
      Ultimaker Cura 3.6 | Beta is available. It comes with new features, bug fixes, and UX improvements. We would really like to have your feedback on it to make our stable release as good as it can be. As always, you can download the beta for free from our website, for Windows, MacOS, and Linux.
        • Like
      • 95 replies
    • Print Core CC | Red for Ruby
      Q: For some users, abrasive materials may be a new subject matter. Can you explain what it is that makes a material abrasive when you are not sure which print core to use?
      A: Materials which are hard in a solid piece (like metals, ceramics and carbon fibers) will generally also wear down the nozzle. In general one should assume...
        • Like
      • 30 replies
    • "Back To The Future" using Generative Design & Investment Casting
      Designing for light-weight parts is becoming more important, and I’m a firm believer in the need to produce lighter weight, less over-engineered parts for the future. This is for sustainability reasons because we need to be using less raw materials and, in things like transportation, it impacts the energy usage of the product during it’s service life.
        • Like
      • 12 replies
×

Important Information

Welcome to the Ultimaker Community of 3D printing experts. Visit the following links to read more about our Terms of Use or our Privacy Policy. Thank you!