nallath

15.1 is not in the works. 15.10 is though. 15.04 supports USB printing, but just like 15.06 and 15.10 it's not really supported for UM2, as the supported way of printing is with the SD card. You can get it to work, but it is a lot more hassle.

Well, i've informed everyone that i've ever heard having extrusion problems about the teflon bit (same goes for pretty much every response that any of the 'regulars' make with regards to extrusion). I believe support does the same. This is actually the reason why new machines are shipped with an extra teflon part.

Short answer; No. Longer answer; There is a lot of heuristics going on in the slicer. If a model is non-manifold, things need to be fixed before they can be printed. If a model has too much small detail (sub micron level) they are 'squashed' in order to prevent duplicates and speed up the process. Depending on the thickness of the part, some lines might not be followed at all (or multiple lines are only followed by one pass, etc).

Python not responding is very common as python is the language Cura is created in. Are there specific actions you took which lead to the lockup? Very large models? Using lay flat? Split into parts? Just loading it and doing nothing?

I don't know how the airwolf performs with USB printing. We obviously never tried (or spent time on) getting Cura to work with non UM printers. If you want ethernet support, you could have a look at octoprint.

I don't believe their precision. It's very, very, very unlikely that they will get below the 100 micron precision. I've made a laser scanner with fairly expensive (industrial grade) computer vision cameras and I wasn't able to even get -near- the 100 micron precision. Let alone what they claim to get. If you look at the 3D models you can clearly see that they don't reach the 100 micron precision. More like 300-400 micron. My first idea for a 3D scanner was actually this, but I scrapped this idea for a number of reasons; 1. If you move your phone (pressing the interface, getting a call, whatever) you need to recalibrate. Laser scanners can take quite a time to calibrate. 2. If you want better scans, you need a phone with better camera / lens. Buying a whole new phone just because you want a better scan? 3. Support -hell- Everyone has a different phone, with different specifications (so they will get different results / issues/ etc). Also note this in buying; Your quality will greatly depend on the quality of your phone! 4. Laser scanners are known for being slow. Very slow. Both because they need a -lot- of images for a proper scan. Their setup makes it even worse because they use a phone. Edge detection (if you don't want a completely naive solution (Something more complicated then thresholding like Canny or Hough)) is a nightmare. Using the naive approach will work, but only in lab-like conditions (and on certain objects). They use a moving laser, which means that for a single snapshot, you will need about 400-500 images. Due to syncing, you can capture about 4-5 frames a second. For a full scan you generaly want about 12 snap shots. This means a full scan will be about 20 (!!) minutes (compared to a projector based setup, that can do the same in 2 minutes). They are also using a color camera, which will impact the quality of the model due to the Bayer filter in the camera. This is also why they use a green laser; Color cameras are twice as good with green light as with other colors. I do have some good things to say about this though; It's cheap for what you get. It's also a step up from regular laser scanners, as the laser can rotate (which increases the number of objects that you can scan).

As far as I'm aware we're not using any scientific papers as a basis for our algorithms. @bagel-orb or @ghostkeeper are the people working on the engine these days, so they will be able to give you a summary if you like.

They seem to happen a lot in topics where I'm the one to post the last reply.

Also, don't use the 15.06 one. Use http://software.ultimaker.com/Cura_closed_beta/15.10/

1. Already implemtend. Its called a support roof. 2. Do you mean top/bottom skin? 3. Different layer height between infill and walls is already possible. Combine infill layers is the setting you are looking for. 4. It's on our to do list, but with a very low priority. 5. It's on our to do list.

Just a general point of warning; When printing with non-standard materials always check what happens to those materials at printing temperatures. There are plastics out there where nasty / toxic components are formed. If you want to know if the not reaching the temp fast enough is the issue, you could try to set it to 270-300-330 in sequence and see where it fails.

The curling usually happens if there isn't enough filament coming from the nozzle to 'beat' the fans & shrinking properties of the material (eg; if enough material is extruded, gravity pulls it down enough).

That manual is old. Depending on what version of the engine you use, a lot of things changed. I'll poke one of the engine devs to give you a full answer.

Check the x-ray view. If there are red areas, your model is non manifold (and thus, wrong)

In 15.06> the setting can be found in the "print sequence" setting in the "special modes" category. Those extra areas that it adds are there to indicate what the size of the head is, as with one at the time you need to take those into account (somewhat).

Don't use print through usb. It's not officially supported. Yeah you can get it to work with some tinkering, but i've never had a lot of succes with it. Sticking to the SD card is a better option imho.

Paul works for Ultimaker these days. Let's just keep it at he's doing great work

There is none that i'm aware of.

If you're doing something wrong, its very easy for us to say what you're doing wrong and closing it. If we never see the issue because you assumed it was your fault, its a much harder thing for us to solve. Also if we're getting a lot of issues where users make a certain 'mistake' it probably means the interface is wrong (in which case our UX people want to know)

What communication log are you referring to?

@mastory; Please create issues on github about the problems that you have. Helps us keep track (and gives you notifications if they are fixed )

15.06.03 did scale automatically, just like the old version. The difference is that it did not -tell- you that it did (our bad!). The newest vesion (the ones IRobbertI linked to) does notify you and gives you an option to disable auto scale.

The old cura should not register any version in the 15.06> range as new updates.