dojan

Alright, so it replicates on that .gcode file, but not on others. Pronterface also seems to behave strangely around that file, so I'm trying to re-slice it now. [Edit - added] So the new .gcode prints fine. Lesson learned, does anyone know what happened? Does anyone want to analyze the faulty file?

So my ultimaker sometimes lags like crazy. This does not seem to have anything to do with model complexity, as other times it works great on very complex models (yoda, voronoid tower) and, as seen in the video, lags alot on even the infill of simpler models like the geared heart. It could have to do with CPU load of the host computer, as I was printing with Pronterface supplied with Cura, and slicing another model at the same time, but it is a dual core CPU, and slicing does not seem to thread very well, and it didn't stop lagging when I either decreased the process-priority if the slice, and increased the priority of Pronterface (all instances I could find), or turned the slicer of and shut Cura down, and waited. Is this the buffer underflow issue I have been seeing floting around? I'm using linux - Ubuntu 10.10, and thus have a baud rate of 115200. Any ideas? (also - dual 60mm fans I hate fan-noise, but also don't want overheating. Now I just have to learn to CAD so I can make a nice fan shroud...)

If you hold the printer head with you hand when the motors are off, does it glide smoothly in both directions? Have you tried reinstalling the firmware to? Is this on every model, even ones that have printed well before? Do you have some known-to-be-good .gcode that also gets this problem? Are the wires of both the motors and the endstops twisted? Just brainstorming a little here, I'm pretty new to this still, so I might easily be missing something...

I have had this a couple of times now, very irritating. As far as I can figure, it's due to power-spikes, ripples or just generally un-clean mains power. I'm considering connecting it behind my UPS which has a stabilizing transformer, but I'm worried that it will introduce power-spikes to my server instead... Anyone who's good with electronics figure this one out?

Sound to me like either the X-motor is skipping steps, or the X-timingbelts are slipping. The motor might skip steps if the axles are not lubricated or if something interferes with the belts, and the belts might slip if the pulleys have come loose. It could also be that the pulleys have become uncalibrated: See step 10 of the extrusion head assembly guide. Anyway, that's what I would check

[Removed]

Thank you for a quick response! That is just the kind of solution I was expecting Trying now... [edit] Yes, that solved it! thank you Btw, thanks for an amazing program; I'm like 3 layers into my third print in total, first with Cura, and I already see an amazing difference... For all you people in the future with the same problem: The Marlyn builder can be found at http://daid.eu/~daid/marlin_build/ (at the time of writing); I entered the baudrate 115200 instead of 250000, and hit "build" at the bottom. After that I clicked "download hexfile", and copy-pasted what comes up into a textfile named "something-or-other.hex", went to Cura, and chose Expert>Install custom firmware in the menu, and chose the .hex file I just created. After that, it at first didn't work, but I went to File>Preferences in the menu and changed the baudrate there as well, and after that everything was just dandy [/edit]

Hi all! Just got my Ultimaker the other day. Assembly went well, and thus begins the learning curve. Tried a few prints with RepG, but decided to skip that and head on to Cura immediately, since it sounds so much better and easier. However. When I first started Cura a First Run wizard pops up. Great! I chose "Ultimaker", and then "Upgrade to Marlin Firmware". Printer gives of a slight humm while it does it's thing, and I click next and "run checks". It says: Connecting to machine... Checking start message... And then nothing. Even some ten minutes later. So I try again, same thing. Clicks "Skip checks", and arrives at the extruder calibration page: Clicks "Heatup for filament removal", but nothing happens. I try to slice some model, everything works perfectly, then try to print it, I get a humm again, and a popup comes up with a few stats, two grayed out buttons and an active "connect" button, which brings about another humm, but nothing more. Pronterface doesn't seem to be able to connect at all. And, of course, RepG doesn't wanna play with Marlin (right?). What to do? Specs: Brand new Ultimaker, with PCB version 1.5.6, carefully assembled, unmodified (so far). Computer: Dell Optiplex 745 with an Intel Core2Duo 6600 and 3 GB of RAM, running Ubuntu 10.10. I have also tried on my main computer with Ubuntu 12.04, but it had some (I believe) unrelated issue with its USB. Before getting Cura to work, I ran this command which I found somewhere around here: sudo apt-get install python python-serial python-wxgtk2.8 python-opengl What I have tried: I tried to reinstall the firmware again, and install the same firmware but from another source (Daids very helpful make-your-own-marlin web-page), but no difference. Rebooting doesn't help either. I have also tried to play around with the baudrate (which is a complete mystery to me by the way). Things I suspect: Something might be up with Ubuntu 10.10, or there might be some dependency I have overlooked. Or the PCB 1.5.6 might be so new that it's incompatible somehow with that version of Marlin (unlikely right?). Other than that, the only thing I can think of is some fault with the PCB itself, but it worked fine with RepG before, so I don't think so. Thanks for any response!