Daid

I took a 2nd good look at your photo: This is the side-wall of the highlight you did. The sides are also not connecting up properly, which is an indication that you have a general extrusion issue, not a infill issue. Might be related to some setting, material or machine. But you do not have me convinced that this is a Cura issue. Just to compare, this is, on an UM1, printed yesterday, with the latest Cura default settings, with ColorFabb Orange: http://daid.eu/~daid/IMG_20140429_133454.small.jpg (Material got tangled up at the last 2 layers, so that's where the tiny blobs come from)

You need to press the eject button before pulling out the card. Else data might be missing and you get the above result. As explained above, there is no way to guarantee all data is actually on the card other then safely ejecting it.

And I'm 110% sure it does not. Did you know the layer-view calculates the amount of material back from the E values, and displays the width of the lines depending on that. Making it a great debug tool for issues like this?

Can you try this patch: https://github.com/daid/Cura/commit/fbf92d2b94813df14140236c50e84fb3b55ad388 I just noticed this small mistake.

The UM2 currently cannot show a message on the screen from GCode.

In all honesty, I think we could expect the same sort of post about Ultimaker2 on the Makerbot forums. No printer is flawless. And the printing method isn't flawless. While I would expect a bit better prints from an Ultimaker, I see defects that are just part of DFM printing. So even from an UM2 I would not expect these prints to be perfect. Others problems however however, could be fixed. Some are slicing defects. The letters should have been filled better IMHO. This is a software issue. It's a difficult problem, and Cura does a best effort, but also not get's it perfect. Sadly, with a Makerbot, you are fixed to Makerware. In case Cura does not do your job right on the UM2, you can use other software like Slic3r and KISSlicer. Some are firmware issues. Too high acceleration is a clear cause of some of the banding we've been seeing on the UM2. Expect the same problem is causing issues in these prints on this Replicator 2. From what I've heard, the Replicator2 has some significant play in the gantry. So much, that someone is making extra money by selling 3th party parts to fix it. I can ask around for the supplier if you want. But it sucks if you need after-market 3th party parts to fix a machine that should have been working in the first place. (I cannot listen to the noise right now, on slow internet)

No signup needed. Everyone can just show up. With or without printer (IMHO, does not has to be an Ultimaker. Bring your RepRap or Replicator if you want)

I think faberdashery has the best quality filament. But does not come on a spool and is quite expensive. Next I prefer Ultimaker stuff. Decent consistent quality. (And, for me, quite cheap ) The Colorfabb stuff seems a bit random in my experience. Some rolls are really good. But some print bad. But they have greatly improved over the past year.

No need to PM me, I read the Cura forum section almost every day. I actually have "old OpenGL" backwards compatibility implemented in Cura. But it's hard to test, as my own laptops do support "VertexBuffers" (which is the most important feature to improve rendering speed) But it should fall back to old OpenGL1.1 code if VBOs are not supported. See: https://github.com/daid/Cura/blob/SteamEngine/Cura/gui/util/openglHelpers.py#L130

This. And clicking the open button works. (And a few other things) I have no idea why. It's just crazy. But, I do think I've placed a bit of a workaround in 14.03. (It also only happens on the release version, not on the development version)

The idea is not that far fetched really. And it actually something we do have on our list of possible things to work on. But before that is smarter support material. As you pretty much need good automated support before you want even better automated functions.

The Arduino IDE always defines the TWI interrupt, however the UM2 firmware needs to have this interrupt to it's own use. (For performance reasons) Kevin, I recommend pointing at an Arduino 1.0.1, and the Makefile might be missing bits&pieces. I'm using a Code::Blocks project to build the firmware myself.

Other then some screws vibrating lose, I've never seen much of wear or tear on an Ultimaker.

Not yet, but a fix has been made internally and will be in the next version.

I think you're having a backlash issue. The "indents" of the H do not line up, and the O is oval instead of round, which are both indications of backlash. This is usually a case of too little tensions in the short belts. Which requires unscrewing the motors a bit, pushing them down, and screwing them back tight.

It's an OLED with an SSD1309 controller. It was ridiculously difficult to source in blue. But they are quite common and easy to find in yellow.

Seal it with PVC glue.

Looks like you have an old ribbon cable. This cable is known to cause these problems, we've made an adjustment to it to fix this issue. You should contact support for a free new cable. "Marrit Hoffmans" knows about this problem, so I recommend including her name in the ticket.

We call it "angel fluff", and it can happen on pretty much any machine really.

Good point, I'll have a look at that today. Shouldn't be too difficult to implement the missing M code. (Kinda got lost off my radar)

For some unknown reason, Cura on the Mac somethings thinks the shift key is pressed, causing panning instead of rotating. I do not know of any workaround except for restarting Cura.

Not sure what you're looking for, but it's normal not to model the threads in the 3D model, and note them in the documentation.

I've just uploaded an Cura 14.04-RC1 to: http://software.ultimaker.com/Cura_closed_beta/ This version contains the fix for the external skin quality. An update UM2 firmware to slightly improve the start of the print. Slightly better bridge handling. And best of all, a new improved raft implementation! (And easier support for delta-bots. And support for BFB printers. And some other minor stuff which will make some people happy, but most people won't care about) This new raft was made and tweaked by Gregoire Passault. Known as Gregwar. Known for this "on the head" extruder mod for the UM2: http://umforum.ultimaker.com/index.php?/topic/3261-ultimaker-2-extrusion-problem/&do=findComment&comment=46577 His improved raft implementation puts the raft quality up to the raft of Makerbot. With a clean separation, and a clean bottom surface. We've put in working defaults in the settings for PLA, and, as always, left a lot of tweakable room in the expert settings. I currently do not know how well it works for ABS and Nylon. But I'm sure people will report back on that one. (And there are even more settings to be exposed once I finally get to a working new UI) I hope to move this information forwards toward a better support material implementation. But if that will happen, only the future will tell.

It does, but, the implementation is not perfect. Which is why it crashes at a certain amount of polygons.

Mmm, it indeed moves all the way to the front, I'll make a minor tweak to it so it does not hit the casing. (Not that it will harm anything, it's locked in place due to the motors locking it)