Daid

Then you don't have the drivers installed, or the machine not connected, or your computer is not seeing the Arduino.

I'm updating the manual for the next version, with lots more pictures. Small warning with this feature, the nozzle will dive into the printed object with Cura 12.08 because it adds an G1 Z0 at the end!

That would be the best way with Cura 12.08, you don't need to slice the saved result in the project planner.

With Cura? Try configuring a comport and a baudrate, not just a baudrate. The auto-detection in the current release fails on some machines.

Check the toolbar of the project planner, there is a button with is called "all at once", that enables this option.

Flowrate is an old term which we should no longer use because we have step-extruders. If you are seeing "speed related extrusion difference" you could have an extruder drive that is slipping, or you are printing too hot, causing oozing during printing.

It sounds plausible, but an algorithm for that would require a lot of tweaking and configuring. Also, temperature changes take a while, so you would also have to account for that. Maybe, someday in the future we will have this capability.

While not directly related to education, I think it's pretty cool if we have more tools to create objects in an easy way. Designing 3D objects is pretty hard for most people. But if you would have an interface like "pontifex" (game in which you design bridges) to simply make bridges would make more objects possibilities accessible for more people.

Did you level the bed with a cold or hot nozzle? the nozzle slightly expands when heated up, and thus sits lower. This could mean your bed is actually too high which explains the flared bottom layers.

My guess it's the same forces that cause warping. You could reduce the cooling, and increase the temperature a bit so the layers stick better. Or create a heated chamber.

Sounds like a belt tension problem, are your circles round or oval/square?

Already in the next version =)

I recommend adding some soft padding to the feed, so you also have less noise.

For the print itself, it's no problem that it shakes. The printer keeps printing fine, even if you shake it or hold it upside down. (Yes, that was tested by Joris) I haven't seen a machine that wasn't standing stable on a flat surface, but yours could be slightly skewed. Shouldn't be a problem really, if everything moves smoothly then go and print!

I've seen people use ReconstructMe. It's actually the only thing that I've seen being used with results. But it's limited to the resolution of the Kinect. So it can only scan things that are about "human sized" I've never gotten usable results from "photo scanners" like 123 catch. The open source laser line scanner looks nice, but the one I've seen didn't produce any result.

It will eat away your nozzle. You'll have to look in the RepRap blog, but someone managed to do it after a lot of testing and trying: http://blog.reprap.org/

You're welcome. I recommend you report this bug to the creators of Unarchiver. Seems like a nasty one.

I know it has been silent on the TITAN front. But I'm still working on it! As people might have seen, I released the belt tension/connection system on thingiverse: http://www.thingiverse.com/thing:31914 It's pretty simple and small, but works great. I actually managed to almost break the machine by putting to much tension on it. In the design, I've placed all the belts, motors, a Z screw, added feet, added caps for the Z guides. Added all screw holes. The only things missing right now are the extruder drive and electronics. Design pics: Without the front and side panel, so you can see the insides Newer front design, the TITAN text is engraved (it always was, but didn't show like that on the design) and the hole in the front is larger so you can easier access the build area from the front. I need to cut new wooden parts. As my current case is cut from soft wood, and that isn't strong enough. Also, the screw connectors are slightly to short so I lengthen those a bit. I installed the belts for the X/Y system on my test machine, and those work. Need to test the Z mechanism next, if that works then I almost have a working printer. Quick cost estimate: 50 euros on the screws (could be done for a lot less, just got 100 of each length and 1000 nuts) 30 euros rods 52 euros on steppers 20 euros on belts ~20 euros on wood (for the final case) Add about 100 euros for a hotend with all parts from UM (heater, temperature sensor) Using UM electronics would add another 180 euros (but the UM electronics are too large, and pretty expensive) So total raw cost for the machine sits around 450 euros. Excluding the printed parts. Excluding any extra parts I might need for the extruder drive.

There shoudn't be underscores after those filenames... any idea how those got there? They are without underscores in the package. (Should be .py not .py_)

Have you smelled the stuff after it got too hot and melted? I wouldn't want to try to extrude that.

At 0.2mm layers the cellularThing_optimizedForMakerbot.stl seems to slice, but it is using a huge amount of memory, like 800MB. With thinner layers that would get even worse. Slic3r or Kisslicer might do a better job at these models. It's a known problem, and solving it would mean moving to another slicer (Cura is Skeinforge based), but that's no an easy change to make.

(Cura also has a GCode preview, so you could have seen it there) Cura shows those little red lines after slicing, those are actual errors that the slicer sees in the model, could be holes or duplicate faces. Most likely one of those is causing the erroneous infill. You could try running the model trough netfabb cloud, or slicing at a slightly different layer thickness (which could be why the original creator of the model never ran into this problem)

The 32 bit pypy implementation can only use 2GB of memory under windows. So even if you have 10GB of free ram, it will still bug out after using 2GB. Which is a bit of a shame, as the slicing process is currently quite memory hungry. I've never had a model so complex that it would bug out like this, but other people have had the same problem. However, a memory error could also indicate a problem with your RAM. I highly recommend running memtest: http://www.memtest.org/ to be sure that is not it. (This problem is limited to Windows, Mac is always 64 bit, and for linux there is a 64bit pypy to use)

Can you check if you have the directory: /Applications/Cura-12.08/Cura/cura_sf/fabmetheus_utilities/geometry/geometry_utilities/evaluate_elements It tries to find the files in there, and it cannot, that's why it is giving that error.

It's called "layer shifting" and while right now you have it on the first few layers, it could happen on any layer. What you should check is: * Does the Y motor have enough power * Are your pulleys firmly attached to the rods * Are both your long AND short belts tight It could also be that your start height is too low, and that the head moves into the first layers during the print of the next layer, but this usually also results in other problems.