CarloK

@AlfonsoCB This are still not all the log files. Try with an empty USB drive when you dump the log files, then it's clear that all the files on the usb drive are important for uploading. So, your printer is a UM3 printer. What firmware version? In 5.2.17 we made a fix for the webcam. Also, your printer is not synchronizing time. It is using a default date in 1970. Could you check your network to allow NTP time synchronization? This might lead to all kind of weird problems.

@ddrsarah Sorry to hear about your problems. Thanks for writing down you analysis so clearly. In firmware 5.2.17 we fixed several problems related to Active Leveling and I hoped we fixed them all, but from your report it turns out we overlooked something. Could you dump your log files to usb and send them to me for analysis? I'm especially interested in the configuration files. On the printer you can find the dump option in the system/diagnostic menu. Send the files to me by clicking my avatar, and then on my personal info page you see the 'message' button on top.

@freuleinzapf @sghong I'm very surprised to hear about your problems as I'm not aware of any changes we made in the print starting routines. Could you try for me: Downgrading to 5.2.16 and tell if the problem still exists? This is easy to do from the menu as 5.2.16 is still available for download. Go on the printer to the software install menu, select the 'testing' version and there you can select 5.2.16 to install. Please report the results here in the forum When the problem still exists after downgrading to 5.2.16, could you dump the log files to usb stick? This is on the printer in the menu system/diagnostics. The files you can email to me through this forum: select my avatar, and then on top of my screen there is a 'message' button.

Sorry for the ugly quotes above. I seldom use the moderator functions of this forum and in splitting an existing thread into a new topic I made a mess out of it.

We have planned more detailed control of the frame lights in a future firmware update. About the color control, only the early UM3 models have RGB LEDs, later printer models have white only. The UM2+C lacks the whole API interface.

What firmware is your printer running? v5.2.17 from a few months ago fixed some of the leveling problems.

Recovering a bricked S-line printer is possible with an SD-card: https://support.ultimaker.com/hc/en-us/articles/360019088780-Firmware-recovery-procedure-for-the-Ultimaker-S3-and-the-Ultimaker-S5-mid-2020-

@iccherry As you can read in this thread, there are two way to connect your printer to Cura: over the Cloud (Digital Factory) and over the local network. Synchronizing materials with Cura/Marketplace is only supported when the printer is connected over the local network. The cloud based synchronization is a feature that's currently being worked on for the S-line of printers, for the UM3 the release is not scheduled yet. So, to add a new material to your UM3, you logout from the Digital Factory in Cura. Ensure your printer can be reached over the local network and material synchronization should happen automatically. Removing a material from the printer isn't supported. It would be very confusing when multiple people are sharing the same printer and materials would disappear, depending on the most recent user. Removing all added materials can be forced by executing a factory reset on the printer.

Setting the model id number (BOM) should only be done once during production, together with the MAC address. With version 5.2.18 (or 5.2.17) we introduced a new software installer, copied from the S-line, and this lacks the routines for setting the model-id. Shouldn't be a problem now the UM3 is no longer in production. Replacement boards should have the correct id programmed. The easiest route to changing the BOM number is perhaps to install v5.2.16 from USB, log in over SSH and run the script, then install the latest firmware again.

Just got confirmed that synchronizing materials over the cloud is a new feature that's being worked on. This will require a firmware update as well which for the UM3 is not planned yet. Synchronizing materials over the local network (previously named cluster) is working already.

@StefanEtter I tried the 3DX Tech ASA from the marketplace, installed in Cura 4.10 and it shows up on my UM3 with firmware 5.3.0. My printer is connected from Cura over the local network. Are you perhaps using the cloud based Digital Factory? Note: I'll be on holiday for over a week, so won't be responding.

I checked the Generic HIPS material and it has no printers attached, which explains the material not being selectable in the printer. In fact, in Cura 4.10 the HIPS material is not visible either in the material selection list. HIPS is not supported (yet) by Ultimaker. Perhaps the Generic HIPS material was visible in Cura 4.7, when you started this thread, and settings have been preserved during Cura updates. When you duplicate a material, it also copies the list of supported printers. Since the Generic HIPS didn't support any printers, the material based off this won't support any printers either. Cura is a poor tool for creating a new material, there are more settings than what Cura allows to configure. Our material suppliers get a separate tool for creating print profiles (lots of work). In order to create your own Generic HIPS material you could duplicate a material that has more-or-less similar material properties, this will then copy the hidden parameters as well. When you name the material with brand 'Generic' it will reduce the number of material conflict warnings when starting a print. Note: Since you already experimented a lot with similar named materials you might run in another issue. The printer tries to reduce the size of the list of selectable materials and will only show 1 item for each available material type. So, when you have multiple HIPS materials, it will show only one. Which of the duplicate materials will show is kind of random (always the same on your printer, but might be different on another printer). Remove all your HIPS materials from Cura, create a new HIPS as described above. Remove all installed materials from the printer (factory reset, or login to the printer and manually remove the files). Start Cura and connect to your printer. You should see a Cura message that it sends new materials to your printer. I just created a Generic HIPS material based on PLA (Select 'Create material' in Cura) and another HIPS2 based on CPE+ (using 'duplicate', don't forget to select 'unlink'), and both are visible in my UM3.

There are no components in the UM3 that are affected by time, i.e. no batteries or such components. Is it possible a connector came loose? Was the printer moved around during those 3 months?

This might be a known bug and already fixed. What firmware version are your printers running? When the bug happens again, can you then dump the log files to usb and post them here?

We are looking into ways of communicating to our users what we are working on, i.e. giving ahead notice of what to expect. An example is the Showcase event we are having tomorrow, October 14. New developments are always going on, but not all promising developments make it into an end product. In the past we created expectations that we couldn't live up to, so it's a difficult balance about telling what we are working on and over promising. There is (not yet) a public roadmap for our printers, but when new firmware is released the printer will show a notification. Detailed release notes for the UM2+C are available at our website.

There are many gcode commands to pause a printer but none of these are supported by the UM2+C. We are continuously extending the functionalities of the UM2+C printer and the addition of a 'pause at height' function is high on the wish list. I hope we can release it soon but can't make any hard promises.

Both versions are equal. You can click ignore and it won't show this message again. We used an upload script from the S-line but there is a small difference in how the version numbers are represented; the UM3 has a date extension. '5.3.0.20211003' in the UM3 and shorter '5.3.0' in the S-line.

@R3DE I'm sorry to hear you are disappointed in our printer and I'd like to hear more about your workflow in order to understand your problems and see how we can be of help. The UM S3 printer is a printer from our professional line and has extra features like: 2 materials, flow sensor, active bed leveling, web cam, better touch screen. Important for your situation is that the S3 model also supports printing over the local network next to the cloud based solution. The UM2+C printer had to drop the local network printing feature because of a less powerful processor. The build plate in the S3 model has the same size as UM2+ and can be used equally. Perhaps you are confusing the UM3 printer? The UM3 has the same build plate size, but because of the 2 nozzles and same housing size it's effective printing size with one nozzle was smaller than the UM2+ (equal size with both nozzles). In the S-line this was improved by making the housing wider. The S3 model, however, will have the same mentioned problem that it won't print the UM2+ files. The request for a compatibility mode wasn't heard before. I can't make a promise, but I added it to our list of requested improvements. Do you intend to use the UM2+C printer with USB drives, or would it include a USB-to-mmc converter? Can you elaborate? What are you trying to do that fails? Our intention is to warn against user errors, but it should still be possible to print from a ufp file.

@mahtt I'm sorry to hear that the problem with the corrupted screen still happens on your printer. I could download your log files and nothing out of the ordinary appears there. Let me try to summarize: The corrupted screen problems didn't appear on the 5.2.16 release When the problem occurred you did a recovery install of 5.2.18 to ensure a clean software installation The screen corruption seems to happen mostly nearing the end of a print In 5.2.18 we changed a few things to reduce the screen corruptions, but since we were never able to reproduce the problem we couldn't prove this would fix them for sure. From your logs it seems like you often print small objects, about 5 minutes in duration. Is this true? I'm asking because it triggers a thought; 5 minutes before the end of a print we start producing more data for estimating the end-of-print time.

When I said 'filament error', then it is my normal way of speaking where I mean the whole collection of filament related problems like: running out of material, material blocked by entanglement, blocked nozzle, too much friction by worn out bowden tubes, material slippage because of too hard material or worn out feeder wheel, etc. in all these problem situations the printer will go into a pause state where you can fix the problem or replace the material and then continue your print. So yes, the flow sensor is a great help in using up all those spools with little filament left. I agree that the app in combination with the Digital Factory could be a strong combination. I've forwarded your suggestion.

Your pictures look fine, with the screw head inside the housing. Then, I read your comment again where you mention "the bolt going down deeper"... This means you are turning the bolt the wrong direction! Try turning the other way, this causes the bolt to move upwards and in doing so, creates tension on the spring.

The printers are paused on a filament error, but I don't think we can send a notification (great idea though).

Hi guys, I didn't get to posting an article on how to integrate the S3/S5 feeder with flow sensor on the UM3, but it will arrive soon. I already collected two S5 feeders.