tinkergnome

Na gut, aber wenn Du nur mit Octoprint arbeitest (kein UltiGCode), dann kannst Du da auch noch die Länge und Geschwindigkeit für den Rückzug einstellen. Oder für UltiGCode sind die "Retraction"-Werte am Drucker entscheidend. Wenn die richtig eingestellt sind, dürfte es überhaupt kein "Stringing" geben, aber keines davon hast Du uns bisher verraten... Bei 0,06 Layerhöhe kannst Du wahrscheinlich auch noch deutlich die Temperatur reduzieren, das hilft auch. Und "Z anheben vor Rückzug" ist bei der Layerhöhe vermutlich kontraproduktiv, aber das kommt später...

I noticed the following yesterday: load a model, let it slice automatically add a "Pause at z" post processing script save the gcode as a file afterwards: open the settings of the post processing script with the "Tools" button and change a setting (the pause height in this example) save the gcode a second time with the same file filename Result: the file content does not change, the changed height for the pause is ignored. Workaround: Change the position of the model or another parameter (automatically re-slicing is invoked) and save the gcode file again. Now the post processing with the new settings takes place as well. Hope that helps.

Oder die Retraction-Einstellungen am Drucker sind total daneben (Länge und Speed)? Ich glaube, die Werte wurden bisher noch nicht erwähnt (und vorausgesetzt, es wird UltiGCode benutzt).

If you have to edit the json file anyway - it should be possible to enable the visibility (along the way)... ..."extruder_prime_pos_x": { "default_value": 170, "enabled": true },"extruder_prime_pos_y": { "default_value": 6, "enabled": true },...

AFAIK the design of the backplane has changed over time. I'm not sure, but I think that newer models of the UM2 came without the filament guide. This is how it looks at the current UM2+ models:

Hallo Staudi, was schreibt denn Simplify3D in die Kopfzeilen am Anfang der gcode-Datei rein? Vielleicht sind einige Angaben nicht korrekt oder fehlen. Für Deine beiden Punkte käme da in Frage: ;;PRINT.TIME: ???;EXTRUDER_TRAIN.0.MATERIAL.VOLUME_USED: ???;EXTRUDER_TRAIN.1.MATERIAL.VOLUME_USED: ???

Ich glaube, nicht. Außer das diese Kopfzeilen ebenfalls Kommentare sind, die am Anfang der Datei stehen, gibt es da keine Gemeinsamkeiten. Der Header soll im Wesentlichen verhindern, das der Drucker aus Versehen mit einer Datei gefüttert wird, die gar nicht für ihn gedacht ist (z.B. ein Modell für den "Extended", das in den "kleinen" gar nicht reinpasst... ). Man kann Dateien ohne den richtigen Header zwar trotzdem starten, aber es gibt vorher eine Warnung. Es gibt als Erweiterung noch ein oder zwei "custom gcodes", die für das "Häufchen-machen" beim Druckstart verwendet werden können (aber nicht müssen...). Der Rest ist normaler RepRap-Gcode. Ich finde, das ist auch gut so, man behält damit die Flexibilität, einen Slicer seiner Wahl zu benutzen und ist nicht auf Cura beschränkt.

Das ist die falsche Frage... Octoprint kann da nicht viel tun. UltiGCode wird ja nur durch die Kommentarzeilen am Anfang der Datei gekennzeichnet. Nur werden Kommentare im gcode während des Normalbetriebes von der Marlin-Firmware komplett ignoriert. Die einzige Aktion, bei der die "Ulti"-Kommentarzeilen ausgewertet werden, ist die Auswahl einer Datei von sd-Karte direkt am Drucker. Es gibt einfach keine Möglichkeit, dem Drucker von aussen mitzuteilen, das die Materialeinstellungen vom Gerät verwendet werden sollen. Das ist alles. Wenn ich das richtig verstanden habe, wird Ultimaker diesen Weg auch nicht weiter beschreiten. Bei der immer größeren Auswahl an Materialien gibt es inzwischen immer mehr Parameter, die jeweils angepasst werden müssen - das kann der Slicer besser.

@LePaul I wonder, if you are using the 'standard' workflow - printing from SD-card with UltiGCode - or something different? Have you changed any machine settings in Cura and/or are you printing via USB/Octoprint? ...and the exact version numbers (and operation system) are interesting, "latest version" is too vague...

Take a look at your configuration folder: %LOCALAPPDATA%\cura\machine_instances There's a file with the printer's name that ends with *_settings.inst.cfg

Perhaps because the connector pins are swapped at the plug? If you compare it with the documentation: black is now at the +5V side, and red is ground...?

It seems that every named setting in fdmprinter.def.json can be used: https://ultimaker.com/en/community/35485-cura-24-beta-is-here?page=2#reply-167430

Don't worry, there's nothing wrong with your visual perception. The led ring of the encoder wheel contains multicolor (RGB) leds. Fatal errors are usually indicated by a "glowing" color-change of the encoder wheel. Most likely all came to a halt while the color was green, but before the printer was able to write the exact error message on the screen.

To be honest: I assume i missed something... why do you need a second temperature sensor at the same hotend? It would always report the same temperature as the other one (more or less). The second temperature sensor is not a problem, but a "heater error" is triggered, if you try to heat up a non-existing heater. That's why your gcode should never try to set a temperature for the second extruder. You can always set the target temperature for T0, and change it on every tool change (e.g. with a post-processing script). I bet that's one of the things that the script from Mr. Průša does. It should also be possible to change all this behavior in the firmware. You can decide at some point whatever is easier for you in the end. @gr5 shared his notes about a proper build environment for Windows here.

A first observation: the default UM3 profiles have the prime tower enabled, and it can not be disabled, because this setting is hidden for single extruder machines... I don't know, if this can be overridden by the machine settings. The workaround is: create a profile with disabled prime tower (while the "normal" UM3 is the current printer).

In addition: i think, there is a similar selection for the support extruder (switch it to Extruder 2 even if support is not used). Don't forget to set all temperatures for Extruder 1 to zero (including "Standby Temperature"). Save all settings as a new profile (for the next time), and that's it. I'm pretty sure, that I have done it before...

Oh no, please do not have another project... May i quote Mr. Průša? He says in the comments that all the hard work is done by a post processing script. I think, this is the correct approach to achieve the wanted result without a need for customized firmware and with minimal additional hardware. Personally I would not connect two outputs to one heating element. There is only one hotend, i would stick with one heater and one temperature sensor. The only problem is: the dual Marlin versions are working fine without a second heater, but not without the second temperature sensor (for safety reasons). But a PT100 can be easily faked by a simple resistor. If cold extrusions are allowed (M302), Marlin has no problem to move the second extruder motor (assuming that the faked sensor simulates room temperature). As long as you don't want to mix both materials, some custom tool change scripts and/or a bit of post-processing should do the trick (and is needed anyways for the retraction/priming/wipe tower stuff).

ultimaker3_single.def.json

No more end cap friction on Ultimaker Originals

Does this apply also for the rotary encoder? I ask, because it looks like your encoder works with a different amount of steps per revolution than it should do...

Hi Eric, one reason is probably that there's not such a thing like "UM3-Extended - Error 12C". I assume, that you have to be a bit more precise, if you want useful hints from the community... Where have you bought your printer? Your reseller should be able to forward you to a trained person who can sort this out (together with you).

The standard firmware does not use PID at all for the heated bed. So there is a difference - yes. There were longer discussions in the past (at the time the PID mode was changed for the standard firmware). If you're interested: firmware surface kwality bug 14.07 vs 14.03 Horizontal banding on UM2

In addition: The Assembly Manual is very handy, if you want to know, how things originally should look like...

Read more about Cura Post-Processing Plugins

Well, you need a way to download the files somehow... but after that you can use the firmware update via USB like described in the manual.