nallath

You can check the github for specs of the bowden. It should be there.

Print one at the time does nothing if the objects are too high. This is indeed not communicated as well as it could to the user.

Hmm, next time we should post pictures faster. Most of R&D has been telling that dual extrusion is hard, but pictures do tend to get the point across a lot better.

Yeah the UMO can handle it. It has quite a bit more power to force material through the nozzle.

It's normal that the computer thinks an UMO is an arduino mega. What you describe sounds like some sort of short circuit in the power of the upper board (eg; the shield that sits on top of the arduino mega). It's a hardware failure, so you'd have to contact support for that.

As far as I can tell, it's both. But it's not my project, so I'm not 100% up to date.

These are usually caused by backlash. Check the tension of your belts & tighten your pulleys.

The backend of the site was changed, which caused this problem. Your data is not lost. If you contact support, they can help you with getting your data back.

In the ideal case the higher firmware will be better. But sometimes fixingin something messes up something else, so the latest version isn't always the best. You can see how old your firmware is by checking the version number, we use a pretty simple system of year.month.version (eg 14.12.1 means that we released 2 versions for this month already, the 14.12.0 and the 14.12.1) We start at .0, because we software engineers are silly like that.

oh and iefbr13; The plastic bolts are only for the controller, but that could be a bit more specific in the manual.

'I am sorry for the delay, we are doing everything as possible to fix this' Well, consider it said now All jokes aside, we recently almost doubled our support team (+3 people). We -are- working on this.

I don't know what process we use, I'm part of R&D, not production / logistics. We should fix this, I totally agree. I simply want to share that most people seem to think that these problems are very easy to solve when they are actually very complex problems. They aren't simple problems. All of the 'solutions' posted here are already in place in so far I'm aware (We do weighing, we have random dubble checking, etc.). So yeah, Its not an excuse, but it aint a completely bad reason either. And we're still growing, so if anyone believe they are up to the challenge please send your resume

Well the main reason it's not there yet, because it just doesn't print well. Slapping an extra extruder on it isn't hard. Getting it to print on par with the first head, that's the really really hard part. I think that a lot of people have a far to high expectation of how good the quality of dual color prints are.

How kits can be shipped with missing parts is quite easy; mistakes happen. There is a huge number of parts in them, so if you have a certain chance that it goes wrong for each part, the odds are it will go wrong (This is a reason, not an excuse). You wouldn't need to go to the hardware store, we are supposed to ship you the parts we forgot. The law is quite protective of consumers in this regard.

This is pretty much why we did the refactoring. We now actually have *drumrolls* documentation! But it would cost us more time to have community people involved, because we're still doing much of the groundwork and you need to communicate quickly (and preferably face to face)

We might have at some point had a printer 'accidently' drop down from the first floor two times in a row. It did survive the first time relatively unscathed. The second try not so much. But really, we've been leaving printers on overnight for the past year at the office. Generally speaking we've got a few handfull running at night. We haven't had any problems with it. You can also transport the machine quite easily, we also do that quite regulary. If you don't mind scratches, this shouldn't prove a problem.

You are not ignored. Just because we don't implement your function does not mean we ignore it. It simply means we don't have the resources to implement every single feature request (we would need triple the number of software engineers to even get started). Daid is generally quite blunt and straitforward in his response to feature requests, which i can imagine is ofputting. This is mostly due to dutch culture (eg; honesty / being straightforward is seen as something good) and him being an engineer (which tend to be more direct anyway). Combine that with a very large amount of people writing very poor (no details, no 'why do you want this function', or 'what is your problem in the first place) requests, you get these kind of responses. I'd also like to add that just because a change removes a problem, it does not always solves the problem. Nor does it mean is is the best way to do it. We're currently trying to fix the big pile of code that our software has become (partially because we kept adding 'fixes' to problems, making it a huge load of "but in this case you need to solve it differently".

Yup. We retrofitted the beds of the um2 to the umo (plus).

The value going red is just a warning. Cura will still do it's very best to work with whatever (weird) values you give it.

Theoretically it should be possible, but I think you would need to make custom firmware (eg; um2 firmware with umo settings for steps / end switches)

Try printing with PET. I've found that it's superior to both PLA & ABS.

And the length of the heated area in the nozzle is shorter, which should help with printing of very fine detail (or so i've been told). I haven't printed up to a resolution where I was able to notice a difference.

And the heated bed is a problem. We're already pushing the current power supply to its limit. Bigger bed means more required power.

This is exaaactly why we call it pluggable unicorn. No risk of production names reaching release

If im correct, the files for the UMO are specified with a thickness.