ahoeben

No, there is not.

Use T{initial_extruder_nr} instead of the final T0 Cura will fill in the extruder number of the first used extruder for the {initial_extruder_nr} part.

I have only had one other report of non-responsive fields sofar, but that seems to have resolved itself. Perhaps the two are related? https://github.com/fieldOfView/Cura-SidebarGUIPlugin/issues/2 If it is something I can't replicate myself, it will be very hard to fix. If you could come up with a way to reproduce it ("start Cura, click here, then do that, now the fields are locked"), that would be great.

I would guesstimate that Cura 4.2 will be released around one and a half month from now, barring any unforeseen blocking issues.

You can't. You can install a plugin that will let you scale a loaded model by 25.4 (from inches to mm), but there is no way to have Cura work in mm (nor any other unit of length other than mm).

The updated plugin (4.0.1) is now published in the Marketplace for both Cura 4.0 and Cura 4.1. When Cura 4.2 is released, I will have to make a new version.

Hmm. You covered the tools with the settings. So you use either the tools or the settings? And to show the settings after you have hidden them, you have to click in the top right to have the settings appear on the left. On top of that, you have to shift the viewport (shift drag) every time you launch Cura so the settings panel does not cover the viewport as much. If that all works for you, that's great for you. But I don't think that's optimal. Neither is my solution with the SidebarGUI plugin, but I feel it still gets closer than yours.

Sorry, I forgot to include a changed file. If you already downloaded the file in my previous post, please download the same file again. This time I actually tested it myself...

The printhead in the UM3 is much heavier than that of the UM2+. To maintain good printing quality, settings that affect the speed the head achieves are different between the two, eg the maximum accelleration. Simply put, the UM2+ is a faster printer than the UM3.

“Print as Support” seems to be broken in Cura 4.1. Not your fault (for once 🙂 )

A test-version that should work with both Cura 4.0 and Cura 4.1 is available here: http://files.fieldofview.com/cura/SidebarGUIPlugin-v6.0.0-2019-06-11T21_09_03Z.curapackage Download the file, and drop it into a running Cura application window. Then restart Cura. If this version works, it should be available from the Marketplace as an update soon.

There are two "modes" of specifying coordinates: relative or absolute. You describe absolute coordinates. In relative coordinates each time you use `G0 X1`, the head will move 1 mm. You can change between absolute and relative modes with the G90 and G91 commands respectively. http://marlinfw.org/docs/gcode/G000-G001.html http://marlinfw.org/docs/gcode/G090.html http://marlinfw.org/docs/gcode/G091.html

Putty should work. I am not entirely certain if the checksum that is normally added to every line is mandatory. In that case using Putty would require some math. If you just want to move the head around, that should work without any initialisation. If you want to extrude material, you will first have to heat up the nozzle (the firmware prevents cold extrusions)

At the heart of the UM2 is the same chip as an Arduino Mega. You should be able to talk to open its serial port (using PySerial) and send any gcode to it line by line. The default Baud rate is 250000.

The UM3 is the same type but newer than the UM2+. I don’t think Ultimaker will release a new single extrusion printer any time soon.

I don’t think Ultimaker will divulge this information before they are ready to do so, and the rest of us just don’t know.

Did you press the “Slice” button? Automatic slicing can be turned on in the General preferences, but is turned off by default.

The sidebar plugin will always have to be updated for new versions of Cura. It "patches" specific parts of Cura, and when Cura is changed those patches don't work anymore and have to be redone. I do think there are still good reasons to prefer the sidebar implementation over the floating panels, so I will release an updated version of the plugin at some point, but there are some complicating factors at the moment.

I don't understand what you mean by that. Oh, wait, I re-read your opening post. I get it now, but that's not going to be part of this particular plugin.

Those concerns are mostly theoretical; a feeling that this should not be necessary. I still think this should be fixed properly in the firmware, but until it is the current implementation in the latest version of the plugin should work just fine.

There's a button labeled "Marketplace" in the top right. That's where you download plugins.

You don't have to save a gcode file and upload it through a separate web interface; with the plugin you can upload and start/pause/stop the print directly from Cura.

For Cura 4.0, there's a plugin to restore the sidebar which declutters the view (Sidebar GUI). I'm working on a version for Cura 4.1.

If they are both empty, then I can not help you; the crash seems to happen at a very early point. Perhaps @ghostkeeper or @nallath can help you.

Ok, then let's just assume your original assumption (someone having the same issue as you) was incorrect, and start over. Are there log files in %APPDATA%\cura ?