Dim3nsioneer

Strange. I just checked the registry. No USBSER there except the entries from software installation (I guess, I'm not a registry expert), but not where you indicated. It's not possible Cura finds some other USBSER key? COM3 is actually the port my UM gets if connected. I see two possible origins of the issue: - I recently installed the Arduino tool, connected it and uploaded a custom Marlin version to my UM. Maybe this changed something else in the registry... :???: - Windows update... no further comment needed I guess... :rolleyes: btw: It's Win8.0...

I mean execute a print job for at least 10 minutes. Then abort the print, home the printer and start the same print job again...

What happens if you run the printer for a while (with the erratic behavior, maybe without filament), stop it and immediately restart it? Does it behave again or does it stay erratic?

Three options: - print with COM3 - Save GCode... :eek: - Slice engine log... So, it's a feature? It will stay like that? No automatic button change anymore?

@dubtec: Do you have the same effect if you just move the object a tiny bit to provoke a new-slicing? @Daid: I still have the print button instead of the save button in RC7 without printer connected...

Sounds to me as if you could improve your bed leveling. Maybe your head is just a bit too close to the bed? If you have an UM1 or a UM2 with flavor RepRap you may also add an offset to your start.gcode for correction. I usually also adjust the flow for the first layer (to something like 90%) and get a very nice first layer.

@mastory: You convinced me. There are multiple issues opened for Marlin which deal with that topic. But there seems to be no consensus up to know how to solve the problem...might take some more time... :sad:

No need if you have identical extruders (same version!) which is the case with the Ultimaker Dual Extrusion Kit and a not too old UM Original. filament diameter: strongly agree! (Daid is most probably hating my guts as I might have mentioned diameter2 once or twice before... :shock: ) flow multiplier: must to have until Cura gets a proper implementation of diameter2 (oops, I did it again... ), from that point on: nice to have nozzle size: agree temp: already implemented steps per mm: see above I have an idea how to implement individual flow multipliers directly in Marlin (see http://umforum.ultimaker.com/index.php?/topic/3580-flow-rate-adjustment-ulticontroller/&do=findComment&comment=40780)... I hope I can realise a first version soon.

I guess you know Murphy's law... It will destroy any least-buggy-marketing... btw: what about the save/print icon (http://umforum.ultimaker.com/index.php?/topic/4487-bring-me-your-bugs-cura-1402-rc2-ready-for-testing/page-8&do=findComment&comment=41143) and the diameter2-issue? Any chance we get a bugfix for those in 134.03?

Are you refering to the missing diameter2 in Cura (http://umforum.ultimaker.com/index.php?/topic/3580-flow-rate-adjustment-ulticontroller/)?

Congratulations on your self-fix! You might want to give Ultimaker some short feedback as they probably will be interested to check why quality control of this board failed.

Finally you should swap the drivers of the x and the z axis in addition to the swaped motors and end switches. Skip it if you swaped exactly these two drivers before. If the result is still the same, time has come to submit a ticket with this information to Ultimaker...unless someone else has a mind blowing idea... I think, the problem may be something like a bad solder point on one of the boards...

Here is another new idea :wink: : Connect your z motor with the x-axis on the Ultimaker Arduino shield. Make sure the z stage is somewhere in the middle of the two end switches. Then try to move the motor in both directions, e.g. G91 (for relative positioning) G1 F9000 X15 G1 X0 If the motor skips reduce the speed (e.g. F4500 or even less). If this tests works (means the z stage drives in both directions) then its a broken DIR bit for the z axis (as gr5 said). Make sure, you switch the z motor back to the z axis afterwards before something really bad happens...

So ein 'Skript' gibt es in Cura. Die Option nennt sich 'Cool Head Lift' und findet sich in den 'expert settings'. Wenn Du gleichzeitig die Minimalgeschwindigkeit auf sagen wir mal 20mm/s oder so hochstellst, bekommst Du genau das, was Du möchtest. Allerdings dürften diese Optionen normalerweise nicht bei einem UM2 in Cura angezeigt werden. Du müsstest unter den 'machine settings' den 'flavor' auf 'RepRap' umstellen und darum einige Einstellungen, die Du Dir gewohnt bist, am Drucker selbst zu machen, in Cura vornehmen. EDIT: Wenn Du den flavor umstellst, kannst Du auch gleich das Flowthermostat-Plugin benutzen. Dieses stellt die Temperatur nach der 'aktuellen' Geschwindigkeit (im GCODE) ein.

Is it a bug or a feature that I get the 'print via USB' button in Cura 14.03RC6 instead of the 'save file' button when my UM1 is not connected to the computer?

Quite a strange behaviour... a video indeed might help to get a better understanding. However, you already did some important checks. Sounds as if mechanics (motor and end switches) are fine. Which slicer did you use for gcode generation? Do you use the default firmware or a custom version? As a shot in the dark, it sounds to me as some strange gcode problem with a missing z-coordinate for the first print command.

Oh, sure... the stl is here. Please feel free to include it in your published set on Thingiverse if you like it. I think there is not much sense in opening a new set on Thingiverse for such a minor modification.

First of all, thanks drayson for adapting IRobertI's cable chain for the UM1! I implemented it with my new heated bed using 10 chain segments: However I had to modify the bed end part (yellow). With the original design, the radius for the chain segments was too small. Thus, I added 10mm on the bed end part and also moved the screw bore by these 10mm in order to get a larger radius for the chain segments. It works nice this way...

It's some time ago... :wink: Such an implementation is possible in Marlin. I would suggest it that way: - keep the current multiplicator as it is (to keep things compatible) - add an additional multiplicator per extruder - extend gcode M221 - M221 Sxxx sets the overall multiplicator - M221 Ty Sxxx sets the extruder-specific multiplicator for extruder 'y' What do you think?

Just for reference: http://umforum.ultimaker.com/index.php?/topic/3651-bigger-wipe-prime-tower/&do=findComment&comment=28360

Just be aware that the filament diameter of the second extruder is (still) not properly implemented in Cura. The slicing engine just takes diameter 1 for diameter 2 independent of what you put into that 'diameter2' box on the GUI... :sad:

The change is instantly. I use http://gcode.ws for checking print speeds on individual layers. Sometimes a speed change is not completely obvious. It can e.g. be due to a different acceleration situation which needs more or less time than the layer before... a radical change is from solid infill of the bottom closed layers to the infill with less than 100%. If you have your fan(s) on 100%, a layer time of 5-7 seconds is usually sufficient if you print PLA.

It's not a question of the firmware but of the order the M109 and the M190 GCODE commands are placed by Cura. In newer versions of Cura, there are two commented lines a the top of the start.gcode which just have to be uncommented: ;M190 S{print_bed_temperature} ;Uncomment to add your own bed temperature line ;M109 S{print_temperature} ;Uncomment to add your own temperature line

Most probably it's a feature. I guess your print is small. If your nominal speed does not match the minimum layer time set in Cura, print speed is reduced to match the minimum layer time. But you can also set a minimum velocity. See the 'Cool' sections in both the advanced and the expert settings in Cura.

Crude yes, but it works... @Eli: Successful bridging depends on more than just the speed. You e.g. want to have the print temperature as low as possible and the fans on full throttle. Acceleration and flow also play their part... But I agree that bridging is something Cura might become better in. Maybe one day... but not too soon, I guess, as Daid and Nallath are currently working on a complete redesign of the GUI. I don't know if any improvements of the slicing engine are planned for Cura 14.x (x>3).