Daid

The one in our office didn't seem to do that. But it does have some interesting mechanical features. As well as some "holy shit, those molds for the injection molded parts must have been expensive" (funny what you suddenly look at in other printers) The software they supply has some bugs tough. We managed to lock up the printer a few times without the "open" button working. For slicing they use slic3r.

The velcro changed a few times (different suppliers) I know of at least 3 different shapes, but they all work the same and fit the same.

You could also drill a 3mm hole in the E3D hotend block and then put the PT100 from the UM2 hotend in there. There is some spare power from the powersupply, as it is selected with dual-extrusion in mind. But there isn't a whole lot extra power there. I don't think the 40W for a single nozzle would be an issue. You might run into feeder problems. The feeder is currently one of the weaker parts of the UM2 design. So you might want to replace that with a geared feeder as well.

What you can do, is you slice a file with quickprint, save that GCode. And then switch to full settings mode. In full settings mode, use the "file->load profile from GCode" function to load the settings from the gcode files that you made earlier. This will load the quickprint settings into full settings mode.

A workaround can be, open "c:\program files (x86)\Cura 14.07\Cura\gui\mainWindow.py" in a simple text editor, find the lines that say: #Timer set; used to check if profile is on the clipboard self.timer = wx.Timer(self) self.Bind(wx.EVT_TIMER, self.onTimer) self.timer.Start(1000) self.lastTriedClipboard = profile.getProfileString() (Around line 268) And delete the "self.timer.Start(1000)" line.

Don't think that will work properly for the UM2.

You might have a trademark issue there (trademark law is odd, consult a lawyer in this case, or get written permission from Ultimaker)

I use blue tape on a (unheated) UM2 or UM+ bed quite often for small prints. So you can still use this route on those machines if you want. I like me UMO that I have at home. But mine is upgraded almost to the UMO+ point, except for the heated bed. The UMO+ is already worth it for just the newer electronics.

I always delay the update notification by about a week, in case there are major problems with the release. It's better to have a few people with problems then everyone with problems.

Building Cura for MacOS is a hell. And yes, you should use virtualenv to setup a proper python environment. I'm pretty much glad it works right now. And I do not touch that mac for anything else but building Cura releases. That's how tricky I find that setup.

Your topic has been noticed and we're investigating this. (Nothing but surprise at the R&D department so far)

Cheap servo's have low repeatability. So that will give you problems. It would be better to use a solenoid. Another possible method is using the bed springs as switch: http://ei8htohms.tinyparts.net/?p=1111

There are a few chinees clones of the original. And a Polish clone, but that one stopped selling after tons of complains about quality. And then there are the stolen UM2s. A few have been recovered, but not all of them. As some of these machines where unfinished, they will lack quality control. I have not seen UM2 clones yet. In general, we do not seem to mind about clones, as long as they do not use Ultimaker branding.

As far as I and Ice086 could test, this problem is gone in my latest test version 14.09.1-RC1: http://software.ultimaker.com/Cura_closed_beta/

You can also check if some application installed a global "glut32.dll" in windows/system32, as that should not be there and might be causing a conflict which causes this error in return.

Shouldn't be a huge problom to run it with material inserted. The motor power is lowered during the loading of the filament, so the motor will skip, but that's no problem.

That would only work against the "material buildup" type of Z scar. Which I rarely see these days and is usually solved with proper temperature settings. This scar is actually a sort of gap, and randomizing the start point will only make it visible on the whole skin.

Yes, the settings have become a bit of a mess. Just like most other things in the code. Hench the pink unicorn :-)

Converting STL to a solid is something only Spaceclaim (payed version) can do. Note that this also has a lot of repair&fix tools then, which help in fixing up the STL before conversion. However, here is a workaround, if you first convert the STL to an sketchup model, and then import that in designspark, you should be able to modify it.

Oh, yes, sorry, due to problems with some installations, I moved the preferences files to: C:Users[username].cura14.09 Instead of the older: C:Program Files (x86)Cura_14.07

Z scar is usually where you see small blue up lines.

Plugin error should be logged in the slice engine log (right click on save button)

You are mistaken on this feature. It tries to hide the Z line in "inside" corners. Simple example, on the following object, the Z scar was on the red line: With the new code, it's on the green line, where it's as good as invisible.

That's the total lack of 3D card drivers.

I did? That's special, as I don't recall doing this. But, you should look for CNC milling fonts, or lasercut fonts. That should help you. I know they exists, fonts with just a single line.