ahoeben

What OS and version of that OS do you use?

The preview in Cura does not simulate the time it takes to move. All line segments take the exact same time, so long moves may seem instantaneous to you. This has always been the case, ever since the "simulation view" has been introduced in Cura 2.5.

As far as I know, this is not supported.

In a word: no. Every PrinterOutputDevice has a PrinterOutputController, and some PrinterOutputControllers implement a sendRawCommand method (the PrinterOutputController will have its can_send_raw_gcode property set to true). But there is no generic way to retreive the response. The requestWrite method is for sending and queueing whole gcode files and is not suitable for individual commands.

Layer height is a global setting, and can be queried from the global container stack; other settings, such as the line width, can be different per extruder, so you have to get them from the extruder stack. from cura.Settings.ExtruderManager import ExtruderManager ... extruders = ExtruderManager.getInstance().getActiveExtruderStacks() line_width= extruders[0].getProperty("line_width", "value")

A bit less of a wag is this list (which is automatically created from fdmprinter.def.json and fdmextruder.def.json): http://files.fieldofview.com/cura/Replacement_Patterns.html

In the version after Cura 4.13, the Simulation View plugin will have a better description, so it is more clear to the end-user what "Simulation View" is and that you should not disable it. In general though, most of Cura is implemented as a "plugin". It is not advisable to just disable plugins that you don't immediately recognize. Chances are you need the functionality provided by the plugin.

If you cannot wait for the new version of the plugin, you can "hack" it by going to Help->Show configuration folder. Browse to plugins\SidebarGUIPlugin\SidebarGUIPlugin, and open plugin.json in the texteditor of your choice. Change the "maximum_cura_version" from "4.12" to "4.13".

When a new release of Cura is available, the Sidebar GUI plugin always needs to be updated. In order for the Sidebar GUI plugin to work, it does quite a bit of "nasty" patching of the original interface. These patches may break the interface when the original interface is changed. So, as a security measure, the plugin checks to see if it has been "approved" for the version of Cura you are using it with. I normally work hard to have an updated version of the plugin ready during the beta period, so when a new stable release of Cura is available, the plugin update is available in the Marketplace. Because I may not always have time immediately when a Cura beta is released, and because updates to plugins need to be checked and approved by Ultimaker developers, there is always a bit of a delay.

"Automatically drops models to the build plate" only deals with the Z axis. There's another option "Ensure models are kept apart" you may want to look at. Even if the STLs are put side by side, you can still select them both, right-click and select "Merge models". This does the same as "Group models", but it positions the models back together by their original origin.

Where/how did you install those profiles? Did you create them in Cura, or did you put files in some place. If the latter, where did you put them?

Unfortunately, this is not the log we need to fully see what is going on. Cura.log can be found either via Help -> Show configuration folder (if you can still open Cura) or in "%APPDATA%\cura\4.12\". The latter is a folder name that you can copy and paste when the start menu is open (ie: copy the %APPDATA%\cura\4.12\ string, press the windows key on your keyboard, and press Ctrl+V).

Test it and you will know. I think the line you quoted was about the "native CAD import plugin" that is only available for people that pay for Cura Essentials, not the plugins that are available in the Marketplace for free (made by @thopiekar).

Hard to tell without having a closer look at the model, but could it be that the top surface is not 100% flat? By the way, the top surface is flat because the normals of the model are pointing inside-out. This *may* be indicative of more issues with your model.

Try the AppImage as proved by Ultimaker instead of the version you installed. The version provided by Ultimaker comes with all the right versions of dependencies required to run Cura in its own "private" package (ie: without affecting the rest of your system).

Thanks for the log files. It does not give me the "golden tip" to fix your issue yet. In your screenshot it seems like Cura cannot find a file that should come with Cura. Can you have a look in "C:\Program Files\Ultimaker Cura 4.12.1\resources\qml\Preferences" to see if ProfileTab.qml exists? For me that folder looks like this (for you the icons may be different, but all these files should be there):

Contact Xvico and ask them.

We need more information. What version of Cura do you use? If you go to Help->Show Configuration folder… there should be a file named cura.log. Please post a link to that file

Cheers!

@gv71, this bug is fixed in Cura 4.13. You could try the beta, which was released this monday: https://github.com/Ultimaker/Cura/releases/tag/4.13-beta

The forum downscales your images, so it is still hard to see what is going on exactly. I think your model is not "manifold". Here's a good article about what that means (and some hints what you can do about it): https://github.com/Ghostkeeper/SettingsGuide/blob/master/resources/articles/troubleshooting/missing_parts.md The best way to diagnose issue like this is if you save a project (File -> Save project), upload that project somewhere and post a link here. Then we can see the actual model and the settings you use.

/w

Out of curiosity: what is different about the steppers of the UM2+C?

The PTFE hotend isolator part has a tendency to deform over time, especially if you print with "hot" or temperature conductive materials. Once it does, it will cause blockages, and it should be replaced. I think you can still find replacement PTFE parts from chinese manufacturers on aliexpress.

As far as I know, the Ultimaker Original is no longer supported by Ultimaker, and the heated bed upgrade kits are no longer produced. The upgrade from an Ultimaker Original with plexiglass bed to one with a heated bed was quite substantial; the whole z-stage was replaced, and you got a second PSU. Fortunately the Ultimaker Original was fully open source, so all specifications of the upgrade kit are available here: https://github.com/Ultimaker/HeatedBedUpgrade I did a quick search on aliexpress to see if a chinese company may have taken the open source plans and made a kit out of it, but no dice. You could try to source all the different parts yourself, but frankly it may be cheaper and certainly less work to get a newer printer that comes with a heated bed.