Daid

More reports is always better. Test1 and Test2 are equal for these goals (they differ on an point unrelated to Ultimakers)

How does 14.03 compare to 14.03-TEST from http://software.ultimaker.com/Cura_closed_beta/ ? I changed a few things related to this in the TEST.

Github does that on private repositories. For security reasons.

Made it private for a few days so I could upload all the files from our slow work internet connection without people noticing.

Challenge accepted! I'll report back if I can make stuff explode, for fun an profit.

That's crazy.... I love it.

In all honesty, the whole UM 1.5.x board design is crappy. After all, it was designed by a software engineer and a mechanical engineer. BUT, I've never, ever, seen a stepper driver being destroyed by the generator effect. And I've seen LOTS of machines (COM port counter on my machine is over 130). We regularly move heads and extruders while the machines are off. It IS however, possible to damage the stepper drivers by adjusting the power while the machine is on. It does not always happen, which is why some people assume it's possible. But this is generally how people blow up those drivers. Layout wise it makes sense to have the extruder drivers switched. But you're not the first to be caught off-guard by this. (Rotating the steppers 180deg around is a sure way to make them explode) We will be switching to the UM 2.x.x boards in the kits soon. These no longer have the stupid mechanical pots.

Actually, those files are just printed with the default normal profile settings...

This limitation is always there. It will be noticable on very high detailed models.

1.25/.5 = 2.5 You can do math in settings :-)

That's... odd. Can you try: python -c "import wx; print wx.__file__" From a terminal? I get the odd feeling something is wrong in your installation that causes a wrong file to be imported as wx. It should output something like: /python/lib/site-packages/wx-2.8-msw-unicode/wx/__init__.pyc

It's hard to solder these boards yourself. I would not recommend it. However, if you want to do this. We did it by hand by heating up the whole bed with an electric cooking plate. The bed is working as a huge heat-sink making it difficult to impossible to solder otherwise. The "white thing" is the PT100 temperature sensor. so it need to be on the board to properly measure the temperature.

And one warning for the horrible flash site. These are the direct links: http://honda-3d.com/data/fuya-jo.zip http://honda-3d.com/data/fsr_concept.zip http://honda-3d.com/data/kiwami.zip http://honda-3d.com/data/puyo.zip http://honda-3d.com/data/nsx_concept.zip (I'm normally not for deep-linking, but with a site like that, they are asking for it)

619 parts, or 652 if you include the ulticontroller. Good luck :-)

Darn it. We're having super-crappy internet issues at work (reaching wooping speeds of 10kb/s!) might have corrupted the upload, I'm uploading from home right now. Should be up 5 minutes after this post

I doubled-up everything that is yellow in the GCode view ;-) What I did, is, I check for every even layer where there was infill in this, and the layer below it. Then those areas are "doubled up" areas. Then I substracted the "doubled up" areas from the normal infill areas. This means there are no gaps or missing infills where you have slopped areas or the model ending on an odd layer instead of an even layer. Then the doubled-up areas where printed with twice the extrusion. It worked, but the top was really ugly. So I should only do it for sparse infill I think.

Strange, importing wx._core works on my Ubuntu with same wxPython and Python. Can you try the following patch? https://github.com/daid/Cura/commit/435eb90259049bc91428227abc36d18cd1ac97a3 (You can manually edit the file on your system I hope?)

I've uploaded a test version (also to test something completely unrelated) at: http://software.ultimaker.com/Cura_closed_beta/ I think this solves the speed problem, but it would be good to have it verified.

Well, I have lots of ideas. So do not expect everything to make it in a release. I did an experiment with "doubled up" layer thickness for infill. Did not win as much time as had expect. The code was quickly hacked, so didn't commit it. I also did it for both sparse and top/bottom infill. And for top/bottom, "double upping" is a bad idea. Except when it's a bridge. Now, for bridges. The current bridge detection sucks. It's done per layer, which is wrong, and the detection fails a lot of times, and has false-positives. I have a test model testing a lot of cases right now. But I haven't make a proper detection yet.

Actually, the Z change is never done as a single move up, it's done as an X/Y/Z move towards the first point on the perimeter. G1 F2100 X111.76 Y93.37 E80.17075 ;LAYER:3 G0 F9000 X111.90 Y93.10 Z0.75 This also causes less Z blob. Bridging as 0.2mm layers works better then at 0.1mm layers (or thinner). So in some future you might get the option to do bridges at a different thickness. Variable layer-height slicing is something that is in my head. But I also know there is some patent about it. Generic idea is that you look at the angles in the model, at high angles you use thinner layers. Smoothing the changes in layer thickness is also important so get a better consistent look. However, doing this in my current code requires some major changes. But, it is in my head. I know how to do this. It will take significant brain time.

While I see how I can implement idea 1. I do not like the idea of changing the topology of the model (as people already pointed out) Point 2 sounds a bit like the bridging improvements I'm working on.

This helps, but the feeder is also a big noise factor of the UM-Original. And the noisy noisy fan... But. I do have an almost silent modified UM-Original on my desk right now. TMC260 stepper drivers are awesome. But that's something for the far future.

It waits for the buffer to be empty, it does not throw away anything. Other then that, seems you're right. I use the G10, G11 commands in the Ultimaker2, but I did had to fix a few things in there. I think those fixes have made it into the main Marlin branch by now. However, by default, support for them is not enabled! So be warned about that.

He did send me the model and the settings...

Yeah, the model is super-high detail. So it's the perfect test case ;-)