tinkergnome

Is this the top side (on your picture), or the bottom of the part? It's hard to see, but to me it looks like the printed object came (partially) loose from the buildplate and the softened material was just dragged around a bit in this area. The visible surface seems to be not flat and a bit "smeary"?

The explanations in the manual are pretty much complete (as far as i can see). Do you miss a setting there? Can you show pictures of the model (solid-, x-ray- and layer view)?

CAD programs can create a solid by specifying a series of cross sections. This would be the easiest way. Usually this function is called "loft" or "sweep". I don't know, if blender or OpenScad provide such a function, but it's easy done with FreeCAD.

Hi Gary, here are some suggestions that may be useful: https://ultimaker.com/en/community/8374-temperature-sensor-stuck-um2#reply-69983 https://ultimaker.com/en/community/8374-temperature-sensor-stuck-um2#reply-108902

...oder die Support-Seite von 3DVerkstan, dort sind reichlich Bilder, auf denen man sieht, wo alles hingehört. Disassembly of the Ultimaker 2+ feeder

So etwas deutet normalerweise auf eine fehlerhafte (bzw. nicht für 3D-Druck geeignete) STL-Datei hin (hast Du dich bei HMax angesteckt...? ). Die "X-Ray"-Ansicht in Cura könnte da schon (visuelle) Hinweise geben. Den Inspector von Meshmixer könnte ich auch noch empfehlen (nur für den Fall, das Du eine Zweitmeinung einholen möchtest...)

My screenshot is Cura 2.7, Ultimaker 3. Looks like a single extruder machine in your case, or the visibility of this setting is disabled (you can check the latter by a click on the small gear icon). If you're in need for a dual extruder machine definition for Cura 2.7 / UM2+ you can start with the Mark2 definition. You probably have to adapt the start script, but apart from that it should be pretty close to your needs. Don't expect great prints with your setup (i think you already know the problems with heat transfer and inactive nozzles scratching the surface...) - but you asked for Cura, not for the hardware setup...

Hi Graeme, it seems like you already have a working (DIY) printer definition with two extruders, right? I would use the search bar in Cura to search for "support" This shows up all related settings, including support speed and support extruder.

Welcome @Vespyr! Cura always uses absolute coordinates for the extruder axis (at least i see no option to change this). I assume, an M82 at the end of your start script would be a good idea...

It's Ultimaker 2+ There's no need to build a new firmware. The steps/mm are stored in EEPROM anyway. Basically follow the instruction in this old post and double the value for the z-axis (or better: to the correct value according to the pitch of the lead screw... ). You would have to repeat these steps after a factory reset, but how often do one do that? BTW: the URL for pronterface/printrun has changed: http://www.pronterface.com/

According to your pictures the traverse path is longer than the size of the buildplate. What happens, if you you define the "Machine width / depth" for Cura to the greater value (it looks like the right syringe can reach... mmhh.. probably 250mm)? And you can try to define half of the 97mm offset for each extruder, but as a negative value for the second one. As far as i can see, you can not define an origin other than (0, 0) in Cura and the target is to define an area that both extruders can reach. That means, that one has to "shift around" the possible area a bit by adjusting the size and the extruder offsets. It's just in theory, but seems to be logical to me...

I guess, that it's simply the so called "cold extrusion prevention". With a default printing temperature of 185°C Cura calculates a "Final printing temperature" of 175°C. And if the temperature falls below 170°C the extruder will not do any moves. This value can be modified with the M302 command. You can add this command at the end of the start gcode and check if the behaviour changes: ;reduce the minimum printing temperature to 150CM302 S150

Och, der Firmware ist das egal, wie sie auf den Drucker kommt... Mit Cura geht es einfach und auf Knopfdruck. Aber schau ruhig vorher nochmal nach, welche Version jetzt drauf ist (nur um sicherzugehen, ob es wirklich daran liegt).

First of all i don't understand, why you would need the change material wizard with a direct drive extruder...? But anyway: I assume the instructions for FILAMENT_REVERSAL_SPEED and FILAMENT_INSERT_FAST_SPEED are referring to a motor with 200 steps/rev. If your extruder uses the 837 steps/mm from the instructions, i would make a try with halve of these speeds (or even less), and the same for the acceleration, this would be way more healthy for the motor...

https://ultimaker.com/en/community/50595-cura-27-beta?page=last#reply-189579 only possible solution a.t.m.: if you don't worry to break something, edit the configuration file for your printer with a text editor and enable the "print_sequence" setting.

Wie alt ist Deine Firmware? Es gab einen Fehler, der das M42 Kommando betraf, aber das wurde vor fast zwei Jahren (mit Version 15.04.4) korrigiert.

Das ist auch kaputt, nur anders... 90 flipped normals (die würden Cura aber nicht stören) 28 non-manifolds 16 folds on surface Ich kenne die Möglichkeiten von SolidWorks nicht, aber irgendetwas ist an Deinen Modellen grundlegend falsch...

Ja, Du schaust an der falschen Stelle. Das sind nur die Default-Werte, einige davon werden beim Kompilieren noch ersetzt. Hier am Ende der Zeile z.B.: https://github.com/TinkerGnome/Ultimaker2Marlin/blob/geek_mode/Marlin/package.sh#L64 Für den Standard-Coupler ist das natürlich ungesund, aber es gibt ja auch Umbauten auf andere Hotends, und 3DSolex verspricht ja für den I2K 295°C "all day long". Dafür ist das gedacht.

Definitiv. OpenSCAD importiert die Datei gar nicht, in Meshmixer sind die gröbsten Fehler rot markiert, die Mesh-Analyse in FreeCAD meldet: 23 flipped normals 86 duplicate faces 169 non-manifolds In dem Bild siehst Du auch die internen Flächen, wo Du eigentlich Löcher haben wolltest. So ist das nicht druckbar.

Nope. Can you share some more details? What's the firmware version? Which slicer? What's the printing temperature?

Hi JackTheSlicer, i can only guess that you're talking about Cura 2.7, but which printer...? ...and i assume that you don't want to use a prime tower or an ooze shield for a reason...? There are machine settings in Cura, named "machine_nozzle_heat_up_speed" and "machine_nozzle_cool_down_speed". AFAIK these settings are not accessible from the GUI. Ultimaker uses them for the profile configuration files in the subfolder "quality". So: either override this settings in your printer's definition file, or create a custom quality profile according to your combination of material, printer and variant. If you use an Ultimaker brand printer, you can take one of the existing files as an example. (e.g. "...Cura 2.7/resources/quality/ultimaker3/um3_aa0.4_CPE_High_Quality.inst.cfg") I never had a need to fiddle around with this, so: no guarantees... If you've created a new profile there should already exist a file in your configuration folder (in Cura: "Help" -> "Show Configuration Folder", subfolder "quality") Add two lines like this in the section [values] and try it out. ... [values] machine_nozzle_cool_down_speed = 0.85 machine_nozzle_heat_up_speed = 1.5

Actually this was a link to the documentation.... but it seems that the path has changed a bit (at least for firmware 3.7.7). The correct link should be: http:///docs/api/#!/PrintJob/put_print_job_state Anyway, you have always access to the full API Documentation directly from the printer: http:///docs/api/

Nö, für die Tinker-Firmware hab ich irgendwann mal diese Zeile vor der "Warteschleife" eingefügt. Damit funktioniert das dann auch als normales Kommando im GCode (z.B. mit S3D oder OctoPrint). Beim "normalen" Aufruf über das Drucker-Menü wird das Pause-Flag jetzt eben zweimal gesetzt, aber das stört ja nicht.

Die Frage ist: warum hast Du beim UM2 überhaupt ein Startskript? Hast Du den GCode-Flavor in Cura umgestellt? Für GCode-Flavor "Ultimaker 2" muss das Start-Skript leer bleiben, sonst ist alles doppelt... Im Zweifel schau den Anfang der tatsächlich generierten gcode-Datei durch, dann löst sich das Rätsel vielleicht schon. P.S.: Herzlich willkommen im Forum!

M600 wird nur vom UMO (mit UltiController) interpretiert. Der UM2 ignoriert das, statt dessen wurde halt das M601 eingebaut - "card.pause" muss aber vorher auf true gesetzt werden, sonst geht der Ablauf gleich nahtlos weiter.... Wenn Du Dir den Quellcode ansiehst: die Identifier "ULTIPANEL" und "FILAMENTCHANGEENABLE" sind für den UM2 nicht definiert -> also auch kein M600.