ceramichammer

Are you printing 3mm or 1.75 mm filament?

I warn all Ultimaker owners to stay away from this hotend. It has been nothing but a giant headache for months. This unreliable hotend has left our two Ultimakers more or less inoperable since January and chewed up 100+ hours of my time. I've used three of these heads on two different machines. Every single one of them jams. I've polished the interior stainless steel surface to a mirror finish but it did not help. I've increased the size of the heater block and snugged the brass nozzle flange against the face of the heater block to increase heat transfer and nozzle temperature stability. I've tried all kinds of PLA filament and every single one of them ends in a hotend jam. Read this thread for more details. http://forum.seemecnc.com/viewtopic.php?f=54&t=1682&start=560 Plenty of people love this head for ABS but for PLA users, beware.

Ultimaker 1.5.7 shield motor wires are twisted nicely motor wires do run in parallel with thermocouple amp board's power and signal wires I'm still experimenting with other motors' effect

This is a very strange thing. I've been haunted by this issue by an original Ultimaker and an Ultimaker I built myself. I've had some intermittent temperature stability problems. In diagnosing this issue, I have discovered that when the extruder motor (and possibly other motors) is driven even without filament, the temp reading drops ~5C immediately. The temp controller compensates for this artificially low temp and pumps up the power. The instant the extruder motor stops driving, the temp snaps back up ~5C but by then it has overshot. This has happened on multiple Ultimakers with different hardware. I originally diagnosed it as a blown up stepper motor but now I'm not so sure.

It is the Microsoft Visual 2008 (2005?) redistributables. They do bad things.

OK!!!!!!! IT WORKS!!! I uninstalled a bunch of crap including all Windows Updates installed in the last week, adobe flash, Microsoft Visual studio redistributables, Microsoft silverlight, and maybe some other things. I will be a little more methodical with the other computer to determine what screwed it up.

It seems that I can still run Cura 12.12A but every single version from 13.xx and upward hangs at the splash screen.

There isn't a single thing different about these machines that I can think of, except Windows Update. I am teaching a 3D printing class at the library exactly 12 hours from now and I have no way to run these Ultimakers. In a desperate attempt, I'm removing all recent windows updates from one of the machines to see if that fixes it.

Nope. Just an ultrabook with integrated-only graphics.

Whoops, I missed that. Sorry. This is so weird. I have the same problem on a computer with integrated graphics and a computer with discrete graphics.

Do you have automatic updates installed? I have 3 machines and only the machine that isn't updated is still able to run Cura.

14.01 worked fine on my desktop until a few days ago. 13.12 also worked fine until a few days ago.

Both my machines are x64. Yours?

I feel like I'm taking crazy pills. Now my desktop computer is doing the same thing! Could a Windows update have screwed this up? Laptop: Intel HD 4000 Integrated graphics w/ latest drivers Windows 8.1 Desktop: Radeon 7850 w/ latest drivers Windows 8.1 I just tried to copy that glut32.dll and it did not fix the issue.

I just downloaded/updated DirectX and it appears my onboard graphics drivers are current. Any suggestions? Is this comment about python and Windows relevant? http://choorucode.com/2012/04/27/pyopengl-installation-notes-for-windows/ Product Detected Intel® HD Graphics 4000 Current Driver Installed 10.18.10.3412 Your driver is current.

I swear that this worked a few days ago and I'm not sure what changed. Here is the output.txt. # Generating comtypes.gen._683BF642_E9CA_4124_BE43_67065B2FA653_0_1_0 # Generating comtypes.gen.TaskbarLib Traceback (most recent call last): File "C:\Program Files (x86)\Cura_14.01\python\lib\site-packages\wx-2.8-msw-unicode\wx\_core.py", line 14660, in <lambda> lambda event: event.callable(*event.args, **event.kw) ) File "Cura\gui\splashScreen.py", line 16, in DoCallback self.callback() File "Cura\gui\app.py", line 75, in afterSplashCallback from Cura.gui import mainWindow File "Cura\gui\mainWindow.py", line 16, in <module> from Cura.gui import sceneView File "Cura\gui\sceneView.py", line 30, in <module> from Cura.gui.util import previewTools File "Cura\gui\util\previewTools.py", line 13, in <module> from Cura.gui.util import opengl File "Cura\gui\util\opengl.py", line 21, in <module> glutInit() File "C:\Program Files (x86)\Cura_14.01\python\lib\OpenGL\GLUT\special.py", line 323, in glutInit _base_glutInit( ctypes.byref(count), holder ) TypeError: 'NoneType' object is not callable Traceback (most recent call last): File "C:\Program Files (x86)\Cura_14.01\python\lib\site-packages\wx-2.8-msw-unicode\wx\_core.py", line 14660, in <lambda> lambda event: event.callable(*event.args, **event.kw) ) File "Cura\gui\splashScreen.py", line 16, in DoCallback self.callback() File "Cura\gui\app.py", line 75, in afterSplashCallback from Cura.gui import mainWindow File "Cura\gui\mainWindow.py", line 16, in <module> from Cura.gui import sceneView File "Cura\gui\sceneView.py", line 30, in <module> from Cura.gui.util import previewTools File "Cura\gui\util\previewTools.py", line 13, in <module> from Cura.gui.util import opengl File "Cura\gui\util\opengl.py", line 21, in <module> glutInit() File "C:\Program Files (x86)\Cura_14.01\python\lib\OpenGL\GLUT\special.py", line 323, in glutInit _base_glutInit( ctypes.byref(count), holder ) TypeError: 'NoneType' object is not callable Traceback (most recent call last): File "C:\Program Files (x86)\Cura_14.01\python\lib\site-packages\wx-2.8-msw-unicode\wx\_core.py", line 14660, in <lambda> lambda event: event.callable(*event.args, **event.kw) ) File "Cura\gui\splashScreen.py", line 16, in DoCallback self.callback() File "Cura\gui\app.py", line 75, in afterSplashCallback from Cura.gui import mainWindow File "Cura\gui\mainWindow.py", line 16, in <module> from Cura.gui import sceneView File "Cura\gui\sceneView.py", line 30, in <module> from Cura.gui.util import previewTools File "Cura\gui\util\previewTools.py", line 13, in <module> from Cura.gui.util import opengl File "Cura\gui\util\opengl.py", line 21, in <module> glutInit() File "C:\Program Files (x86)\Cura_14.01\python\lib\OpenGL\GLUT\special.py", line 323, in glutInit _base_glutInit( ctypes.byref(count), holder ) TypeError: 'NoneType' object is not callable Traceback (most recent call last): File "C:\Program Files (x86)\Cura_14.01\python\lib\site-packages\wx-2.8-msw-unicode\wx\_core.py", line 14660, in <lambda> lambda event: event.callable(*event.args, **event.kw) ) File "Cura\gui\splashScreen.py", line 16, in DoCallback self.callback() File "Cura\gui\app.py", line 75, in afterSplashCallback from Cura.gui import mainWindow File "Cura\gui\mainWindow.py", line 16, in <module> from Cura.gui import sceneView File "Cura\gui\sceneView.py", line 30, in <module> from Cura.gui.util import previewTools File "Cura\gui\util\previewTools.py", line 13, in <module> from Cura.gui.util import opengl File "Cura\gui\util\opengl.py", line 21, in <module> glutInit() File "C:\Program Files (x86)\Cura_14.01\python\lib\OpenGL\GLUT\special.py", line 323, in glutInit _base_glutInit( ctypes.byref(count), holder ) TypeError: 'NoneType' object is not callable Traceback (most recent call last): File "C:\Program Files (x86)\Cura_14.01\python\lib\site-packages\wx-2.8-msw-unicode\wx\_core.py", line 14660, in <lambda> lambda event: event.callable(*event.args, **event.kw) ) File "Cura\gui\splashScreen.py", line 16, in DoCallback self.callback() File "Cura\gui\app.py", line 75, in afterSplashCallback from Cura.gui import mainWindow File "Cura\gui\mainWindow.py", line 16, in <module> from Cura.gui import sceneView File "Cura\gui\sceneView.py", line 30, in <module> from Cura.gui.util import previewTools File "Cura\gui\util\previewTools.py", line 13, in <module> from Cura.gui.util import opengl File "Cura\gui\util\opengl.py", line 21, in <module> glutInit() File "C:\Program Files (x86)\Cura_14.01\python\lib\OpenGL\GLUT\special.py", line 323, in glutInit _base_glutInit( ctypes.byref(count), holder ) TypeError: 'NoneType' object is not callable

Please, please, please post a whole bunch of pictures of the bed, the leveling screws, and the z-axis carriage! They said they won't be releasing any schematics for months. I'm about to build a new one and I would love to Incorporate the new bed style into our printer.

What is the maximum move speed? How has moving the extra mass of the extruder to the print head affect things? How much heaver is the print head vs the original? Are the linear motion components basically the same?

After a solid year of printing with the V1 hotend and nozzle, I finally destroyed the nozzle during disassembly. Because I'm in the USA and a cheapskate, I ordered nozzles from MakerGear. I purchased a .35mm and a .75mm nozzle. On their description page, it says the 0.35mm nozzle actually extrudes at 0.43mm. It says nothing about the 0.75mm nozzle. I know that this is influenced by die swell but what parameter is the "nozzle width" setting is Cura actually expecting?

I'm trying to fine-tune my steps/mm and retraction settings. I'm using Repetier to do the calibration because it gives much better manual control. I'm just trying to get the settings correct. I am confused about the units that Cura lists for retraction. It says mm/s. Is that mm/s of filament? Below is my interpretation of units. Can someone sanity check this? Cura print speed (mm/s): linear speed of the hotend Cura retraction speed (mm/s): linear speed of 3mm filament through the drive gear Repetier speed (mm/min): linear speed of 3mm filament through the drive gear.

I have full confidence someone at our space will try to do both at once so I will report back with the results.

Sorry for the simple question but I couldn't find it on the product page or in the Wiki. Obviously the Ulticontroller gives you the ability to print off of an SD card but do you lose the ability to print directly from a computer? At our hackerspace we want to give people the option to do both but if installing the Ulticontroller keeps us from doing it the old fashioned way, I don't want to shell out $140 for it. Does anybody know?

I just upgraded from 13.01 and loving the new interface and all the sweet options. I printing a simple adapter for a vacuum cleaner with 3 walls and no infill. While printing the vertical part of the cylinder, everything was fine. However, once it got to a 45 degree outward taper, things got really weird. The head was jerking 10-15 times per loop. It looks like the stutter step (knit line) that is made every time it changes z-height but obvious much more frequently than once a layer. I've never seen this jerky motion before. There is nothing obviously wrong in the visual representation of the tool path.

7.5mb file. I will double check that this wasn't just a hiccup.

Daid, you're the man. I was using 13.01 beta for a while so I'm stoked for 13.03. Here are some things that are acting funny: I sliced a large file. Before printing the large file, I downloaded, sliced, and printed some belt tensioners. I closed the print window. In the Cura main window, I clicked "Show result" of the slicing results for the large file not yet printed. It displays the "Layers" view as expected but the print button is greyed out. I then loaded the STL file again. In previous versions of Cura, you could click "print" and it would look to see if there was an existing .gcode file for the model file. This was unavailable. My last attempt was clicking "File....Load profile from G-code" which still left the print button greyed out. In previous versions of cura, you could cycle through each layer in "Layer" view with the up and down buttons, the up and down keyboard keys, or jump to a particular layer by typing it. In 13.03, I don't see a field to type in a number (which isn't that big of a deal) but I can't seem to cycle through with the keyboard keys which is a real bummer. This was a very useful feature for a G-code sanity check. This last one may not be a bug but it sure is a pain and I don't see a setting to change it back. In previous Cura versions, canceling a print in the print window but leaving the print window open would keep the head at temperature. This was great because there always seems to be a couple false starts getting the bed level, PLA to stick, etc. Now when you click cancel, it powers down the hotend, requiring it to ramp back up to temperature before a re-print can be attempted. Thanks again. You do awesome stuff.