CarloK

Our graphic designers are against this feature. It's the usual fight between tweakers who want to see lots of details and the majority of users who want to have a simple to use machine. On the whish list is a feature to switch the display between those two layouts but this is not foreseen for the near future. For the UM2(+) you can install the Tinkergnome firmware which does have this feature and lots more. Another workaround is to use the Cura plugin to pause at a configurable layer height.

For you to find out if and where it is in the S5....

I suggest you post this question in the Cura topic: https://community.ultimaker.com/forum/108-cura-plugins/ Then also post what operating system you are using (Windows, Linux, Mac) and which version there of.

Soon a new release for the UM2+ will be created to add the Tough PLA material. In this topic I want to investigate the known problems that we can perhaps fix and add to this new release. At GitHub there is for the UM2+ only 1 reported issue: - A problem with filament grinding after material change. The UM2 repository at GitHub has a few more issues, I will look into those. I'm surprised no other issues have been logged. For example, when testing the material import function I found several bugs (these are fixed now and will be in the next release). Do you people know of more bugs? Then please list them here or on GitHub. No promises that we can squeeze them in the next release, but we will try. Please, only bug reports. Since the UM2 is at end-of-development stage we will only address bugs and issues that enhance the print quality.

For reference: I just found this picture of the AA and BB nozzles on the Ultimaker website:

Nope, firmware for the UM3 and S5 is not (yet) available on Github. But... since the whole engine is written in python you can download it from the printer itself. You will only be missing on the marlin part (motor drivers) and the display code (C++ for UM3 and pyQt for S5).

Adding the build plate temperature to the 'remove object' screen is technically easy. It is just that we have little space to show all the text. I will propose the change and see how our translators react to the smaller text area.

I don't understand; in your original post you said you changed the Cura settings to use Marlin flavour and then the same error occurred. And now you say you have no problem with Cura? Be aware that Cura 3.3 contained a bug in the UM2 machine settings for using the build plate center as origin, depending on the object location, this creates the print outside valid area error. This bug was fixed in Cura 3.4, released just a few days ago.

Check for dirt in your SD card reader slot. Reading invalid data from the SD card is one possible reason for this type of errors. Also read:

Besides a nozzle size problem it could also be a temperature problem. Check the PT100 temperature sensor in the print core. Is it pushed in far enough? Is it making good thermal contact (check how tight the nut is tightened). Perhaps other people have more tips for checking?

Also, double check the file names. With some browsers the files are written with the wrong extensions. The file names should end with ".tar.xz" and ".tar.xz.sig" for the smallest file. But some browsers change this into ".tar.tar" and ".tar.xz.tar" and those are not recognized by the printer.

When searching for info on setting up a VPN you have to know the brand&model of the routers on the two networks. Use those as keywords when searching for VPN setup help.

Cura and the Ultimaker app are scanning your (local) network for the presence of a printer. VPN (virtual private network) is a method for connecting two (remote) networks together so they appear as one. How to configure this very much depends on the network hardware you have, on some routers it is easy, on most devices however it requires serious technical skills because of security related issues.

Yes, this would be nice and has our attention but to make it easy will be considerable engineering effort and is not top priority. Be patient. For now, my best guess is to setup a VPN connection to you printer's network.

Yep, that's the only change you'll notice in the update. (there was also a bootloader fix, but that's only for initial programming in our production facilities).

All UM3 machines were shipped with 3 nozzles: 2x AA and 1x BB, exactly for your use case. Please double check that you didn't store that extra AA core somewhere. That said, the AA and BB cores are almost identical, except for the shape of the last part of the extrusion channel. Using a BB-material in an AA core will cause major problems as described in posts above. The other way around, a BB-core can be used for anything the AA core can print, except that it will ooze a bit more. Try and see for yourself if the results are acceptable. Summary: - BB can print anything but oozes a bit more. - AA oozes less but don't try to use materials like PVA in it !

@Steffen The config.tar is not very important at this moment. When I look at the log files I'm surprised that the logs are very short, less than1 minute since booting. In this time there is no heating shown. Somehow the log file we want to see is not here. Perhaps it was not written to the file system because of the sudden reboot. Do you use the original Ultimaker print cores? Are there perhaps other improvements to your system? Another build plate, power supply, etc? When it happens again, can you post another set of log files, just to see if those contain more info. Do you have another Ultimaker printer from which you can try to swap the external power supply?

@Steffen Sorry to hear your system has problems. The symptoms you describe are not something I've heard of before in the 4.3 release. When it happens again, can you email me the log files from your system, or post them here? (menu: System/Maintenance/Diagnostics/Dump logs to USB)

Thanks for uploading the missing file. Strange is that boot0 and boot2 are the same file, except that boot2 has two extra lines (mentioning the file copying to usb stick). Problem is that in none of the 3 boot log files there is a mentioning of running an upgrade. These are invalid file name formats. The file names should be latest.tar.xz and latest.tar.xz.sig respectively I guess you got bitten by the Windows Explorer or the Windows Edge browser. Those browsers have the terrible habit of changing the file extensions on saving by adding an extra 'tar' at the end and then the files aren't recognized by the printer. Change the names to the ones mentioned above (the small file should be the one ending at tar.xz.sig). Instead of changing the names you can also download the files using another browser like Firefox or Chrome. I'll have the download description updated with this weird Microsoft browser behaviour.

@tomnagel The Marlin reset happened 12 hours into the print, so pre-heating the build plate is not the solution. @The_Rob Updating the firmware won't solve your reset problem but fixes some other issues. Release notes v4.3 It looks like the Hardcore uses a 35W heater like in the UM2 instead of the 25W from the UM3. The UM3 reduced the nozzle power because with the double nozzles there was less power headroom to spare. Updating the power supply for a more powerful version wasn't possible because of safety regulations on the used connector. It is possible to write a new configuration in the Hardcore that specifies the correct heater resistance and so should reduce the power problems. Advantage of contacting 3DSolex is that they can fix this problem for all (future) users. When they do a good job they also tune the PID settings so you will get better print results.

You are running firmware 4.2.5.20180102 An update with lots of Cura Connect fixes is available: 4.3.2 of 20180308

When I look into the log files I see the next part: First you see the command for setting hotend-1 to 220C, this succeeds. Then, one minute later, for some reason the marlin board resets but the Olimex CPU board continues. From then on both cpu-boards are out of sync and after lots of minor error reports, the printer finally stalls on the nozzle-1 heater error but already failed a lot earlier. The main reason for the marlin board to reset 12 hours into a print is because of a power dip. So, in my analysis there are two possible problem causes: 1) There was an external dip in your 230V main (I see you are from Germany). or 2) The internal power consumption was higher than allowed. My gut feeling is that the 3DSolex Hardcore is to blame. This nozzle was not qualified by Ultimaker and most likely contains wrong settings. A standard Ultimaker AA core heats up with a speed of 2.5C / second. From the log I can see the Hardcore heats at 3.7C / second, this means a more powerful heater that will consume more power and could cause the internal power supply to drop voltage. 3DSolex should have programmed the power settings into the nozzle, then the printer would have adjusted for this. Another problem with this 3DSolex Hardcore is that the core also contains settings for the heater algorithm so it will regulate to the requested temperatures, so called PID-settings. I can see in your logs that these are wrong because when requested to go to 175C it actually cools down from 174C to 170C.... There are ways to modify the print core settings, but this isn't easy and shouldn't be made your problem. My suggestion is you contact your supplier so they can help you fix the print core.

Can you make a copy of the system log files and share them here? Procedure: - Insert a USB stick in the printer - From the printer menu select: System > Maintenance > Diagnostics > Dump logs to USB. - Upload the boot files and the config file to a file sharing website like WeTransfer.com (this will be 4 or 5 files) - Share the uploaded files link here.

Time has progressed.... Easiest solution right now is to download the Cura v3.3 beta release which should have the longer type of gcode files again and so hiding the UM2 bug. Note that the bug in the UM2 firmware has also been fixed but I didn't spend time in confirming it was included with this Cura beta version (there is a new firmware released with this Cura beta but it isn't mentioned in the release notes. It will sure be fixed and released in the final Cura 3.3 release). Tip: You could even update your printer with the firmware from the Cura 3.3 beta and then revert to Cura v3.2 if you can't work with the beta.

WeTransfer reports there are 3 files present, the boot0.log file is missing. This is the most important one as it is the last boot. In the printer log files that are present I can see this file was written to usb. Is there any chance for you to upload that missing file?