ahoeben

Reportedly this is fixed in Cura 4.10. Please let us know if 4.10 works for you when started on your second display.

The resolution of your printer in the X & Y direction is much higher than the resolution in the Z direction. This explains the z stepping you get when you print this particular model on its back; the top surface has a slope to it.

The short answer: there is no way to control the order of prints. It is a subject of some contention. I think you can affect the order by intelligently nesting groups, eg like grouping the two models you want to print last, then grouping that group with the next, etc until you reach the model you want to print first. So most models will be grouped with a group that consists of one model and a group, etc.

Sure, you can use it, but it won’t work. The pattern replacement code in Cura does not support math, like I said before.

Cura checks if you add a heatup sequence in your start gcode. If you don't, it adds its own heatup before your start gcode. If you don't want Cura to add these lines, make sure your start gcode contains lines which have {material_print_temperature_layer_0} and {material_bed_temperature_layer_0} in them respectively (exactly as typed, Cura will replace the {}-text with the temperatures). eg: G21 ;metric values G90 ;absolute positioning M82 ;set extruder to absolute mode M107 ;start with the fan off ; etc M140 S{material_bed_temperature_layer_0} ;Start heating bed M190 S{material_bed_temperature_layer_0} ;Wait for bed to reach temp before proceeding M104 S{material_print_temperature_layer_0} ;Start heating extruder M109 S{material_print_temperature_layer_0} ;Wait for extruder to reach temp before proceeding ;etc Having this in your start gcode prevents Cura from putting heatup commands in front of your start gcode. This means that you can insert your ABL command anywhere you want to relative to your heatup commands.

You mean like you have in the top right of the forum, next to the Create menu?

In Cura 4.9, the Top/Bottom settings moved from the Shell category to a Top/Bottom category. Pro-tip: there's a search field on top of the settings list. You can type the name of a setting there.

Here's a dedicated utility to upload a .hex file to the controller: https://www.hobbytronics.co.uk/arduino-xloader

Ultimaker Cura needs a functioning firmware on the printer in order to update the firmware. If there is no connection between the printer and Cura, then Cura will not be able to flash the firmware.

This is an indication of what you did wrong. When you updated, you added a new printer. Instead of selecting the Geetech (or Custom FFF Printer) from the list of printers to add, you selected an Ultimaker S5. The Ultimaker S5 uses the UFP file format to add a thumbnail to the gcode. The Geetech does not understand that file format. Add a new printer to Cura, and take care NOT to select the Ultimaker S5 as the type of printer from the list.

Have you tried any of the suggestions in the two posts above yours?

No, the plugin I was talking about would not work for a belt-printer. But I am also the creator of Blackbelt Cura, so nothing is impossible.

I have an Ultimaker S5 that does most of my printing. I don't use the Ultimaker Cloud much though; only local connection and monitoring (and remote via VPN).

Posting your feature suggestion here will not get it seen by the people who would decide if this feature gets implemented. You may be interested in the "Material Settings" plugin that is available in the Marketplace, which lets you select what settings can be set in the Materials preference pane.

I'm game, but I have not used the Digital Library yet. But I know all about connecting printers via the network, be it via Ultimaker Connect or OctoPrint.

I'm sorry, please resend them.

CuraEngine has a command line interface. You can use the commandline interface from Python, PHP, Node.js, or whatever floats your boat... er... server.

But the slice with no top & bottom shows you exactly why you need those "top & bottom" layers in the first place. Without them, you get holes. I think the figures by @GregValiant are pretty clear about why.

Are you aware that the Ultimaker S3 needs 2.85mm filament, as opposed to 1.75mm?

And what is the problem with that?

You could try setting the "Top/bottom pattern" to "concentric" for this model.

Not as far as I know. But an updated version of the plugin supporting Cura 4.10 is now available in the Marketplace.

If you want to contribute to Cura, you are going to have to get to know "git", a version management system. There are many tutorials on youtube about how to use git. There is a nice integration into Windows Explorer called "TortoiseGIT", though some developers frown on some of the simplifications and limitations it implies. Many IDEs have git functionality integrated. I use a combination of tortoisegit and the command line git. The workflow is that you "fork" the repository on github into your own account, then "git clone" that onto your local machine. Now you can make changes, though it is best to make those changes into a new "branch". One branch per feature/fix. Once you have confirmed the fix/feature to work for you locally, you "commit" the changes locally, and then "push" them to your forked repository on github. From there, you can make a "pull request", which is a request to the Ultimaker devs to have a look at the changes you made to your repository and "merge" (or "pull") them into the main repository. Once you looked at one or two youtube videos about git workflows, the terms in quotes will start to look familiar. The PYTHONPATH is an environment variable like PATH, which points to (additional) folders where Python looks for modules.

You could set up a full "from source" installation as outlined in the article linked to by @nallath. But personally I prefer skipping getting CuraEngine to compile, and just set up a python virtual environment with the required modules and bits from a released version of Cura. * Check out the Cura and Uranium and libCharon repositories in separate folders * Alongside those two folders create a bin folder containing the following files extracted from an offical Cura release: Arcus.pyd CuraEngine.exe libgcc_s_seh-1.dll libgomp-1.dll libifcoremd.dll libimalloc.dll libiomp5md.dll libmmd.dll libstdc++-6.dll libwinpthread-1.dll nlopt.dll pynest2d.pyd Savitar.pyd * Create a Python 3.8 64 bit virtual environment, and add the bin folder, the Uranium folder and the libCharon folder to the PYTHONPATH * Install the following modules: appdirs==1.4.3 atomicwrites==1.4.0 attrs==20.3.0 Automat==20.2.0 certifi==2019.11.28 cffi==1.13.1 chardet==3.0.4 colorama==0.4.4 colorlog==4.8.0 comtypes==1.1.7 constantly==15.1.0 cryptography==2.8 decorator==4.4.0 hyperlink==21.0.0 idna==2.8 ifaddr==0.1.7 importlib-metadata==3.10.0 incremental==21.3.0 iniconfig==1.1.1 keyring==23.0.1 mypy==0.740 mypy-extensions==0.4.3 netifaces==0.10.9 networkx==2.3 numpy==1.19.5+mkl numpy-stl==2.10.1 packaging==18.0 pip==21.0.1 pluggy==0.13.1 py==1.10.0 pycollada==0.6 pycparser==2.19 PyHamcrest==2.0.2 pyparsing==2.4.2 PyQt5==5.15.0 PyQt5-sip==12.8.1 pyserial==3.4 pytest==6.2.3 python-dateutil==2.8.0 python-utils==2.3.0 pywin32==300 pywin32-ctypes==0.2.0 PyYAML==5.1.2 requests==2.22.0 scipy==1.5.4 sentry-sdk==0.13.5 setuptools==49.2.1 Shapely==1.7.1 sip==4.19.24 six==1.12.0 toml==0.10.2 trimesh==3.2.33 Twisted==19.10.0 typed-ast==1.4.2 typing==3.7.4 typing-extensions==3.7.4.3 urllib3==1.25.6 zeroconf==0.24.1 zipp==3.4.1 zope.interface==5.3.0 For some of these modules, it is going to be easier to use a wheel from https://www.lfd.uci.edu/~gohlke/pythonlibs/ instead of pip. Unless I forgot something (which is entirely possible), you should then be able to run Cura from source by going into the Cura folder and running python cura_app.py

There are no assignments. There is a LONG list of "defered" issues which are basically very valid bugs or features, but Ultimaker devs will not be spending time of them because there is too much work to do that is deemed more important for Ultimaker. But many people will thank you for having a go at them. https://github.com/Ultimaker/Cura/issues?q=is%3Aopen+is%3Aissue+label%3A"Status%3A+Deferred"