CarloK

The UM3 is still supported, don't worry. As mentioned above, the S5 and UM3 share a common code base and we did plan to release a new UM3 together with the 5.1 release for the S5. However ... There are more technical problems than we anticipated and the UM3 release did not pass our quality tests. The S5 with its graphical interface uses more disk space and this required another partitioning of the internal file system. Converting the existing UM3's to the new disk partition sizes is working, but we keep finding new edge cases that have to be covered as well. We are working hard to get a UM3 release out, but only want to release it when we are confident the update won't brick your printer.

Released v5.1.8 V5.1.8 was released yesterday for the S5. This is a minor update to the previous v5.1.7 and was only released to fix two annoying problems: - Fix: starting a print with custom materials was impossible. The print started with some head movements and then stopped again without error message. - Fix: when you would delete a job from the print queue in Cura Connect, it would also delete another job from the job history.

Yep, the recovery procedure as linked above should get your UM3 up and running again. The reason we didn't protect against this type of mistake is that the software for S5 and UM3 is very similar. In fact, so much alike, that in the near future we are planning to make it the same update-package. But, for the S5 we had to increase some file partitions, and that's what is killing the UM3: a full disk. We can make protection routines in new software, but we were unable to add such functionality to software that's already used in the field (a chicken-egg problem). When you are using the network based update functionality then you can't run into this update problem, but for offline printers you have to be careful which package you install.

@Bandy I moved this question to the Firmware sub-forum. The forum here is mostly user driven, but Ultimaker employees like me do scan the issues as well. I'm one of the software engineers responsible for the firmware in the printer and the problem you describe is new to me but is something that we don't want to happen. Next time when this happens, can you dump the log files to a USB stick and mail them to me? (I see Tinkergnome is typing a bit faster than I am and responded as well since it is now in the right forum). ☺️ For mailing me there should be a 'message' button in the top of my user profile page.

Yep, those display cables are connected wrong. I don't understand why you disconnected them when replacing the 1548 board since those cables are connected to the Olimex board. Here are pictures of my printer. Note how one of the cables is marked with a '1', this is often done during fabrication to distinguish the cables but is not always present (good to add it yourself when missing). EXP1 on the display board is connected to EXP1 on the Olimex board, and similar EXP2 connects EXP2 on both boards..

Strange, the Olimex board in the UM3 should always overwrite the Ultimainboard firmware when the checksum differs from the expected value. What we expect that is wrong in your setup is that you have connected the display connector to the UltimainBoard, i.e. the way it is connected in the UM2 where in the UM3 it must be connected to the OIimex board. Now the UM2 is still present and boots, can't find the printhead and shows this error. With proper cabling it will take about a minute for the UM3 to boot and to re-program the Ultimainboard.

Sorry to hear the printer is troubling you here. I don't follow you in all mentioned problems, but If understand you correctly these are: 1) When doing maintenance you want the lights to be on. That makes sense. Not sure yet if all menu actions should result in the lights going on though. 2) When you are manually working on the printer (menu), then Cura Connect shouldn't try to intervene. Best to keep quiet until 1 minute no user action.

Thanks for reporting this problem, including the photo's. We tried many times to fix the problems in tracking the filament position on abort / pause / filament changing but apparently still haven't got it right. We made it a top priority to redesign this part of the printer. Since it is at the basis of the machine and touches all functions it might be released as small increments over several releases.

This fix will be in the 5.2 release, expected February 2019. The patch release was not foreseen and is an unplanned release to fix a blocking problem. I'm pushing hard to get the led fix in this patch release as well but it's not my call. There are good reasons for keeping the changes to this stable version as small as possible. The led bug fix is tiny, and when feeling brave you can make the fix on your v5.0 or v5.1 firmware: - Edit the file /usr/share/griffin/griffin/led/hardware/drivers/linuxLEDClass.py - The second line from the bottom reads: brightness = str(int(max(1.0, value * float(self._max_brightness)))).encode("ascii") - Change the 1.0 to 0.0 - That's it. I purposely didn't describe how to edit a file on the printer. If you don't know how to do this already, then you better not risk breaking the firmware.

@schen The problem with custom materials not being printed was found. A firmware patch release is expected in about a week and will have version 5.1.8

"material_extruded" as reported in the printhead api is in mm Cura Connects reports the material amount as mm3.

November 2 a patch was supplied where the wrongly named travel speed macro was fixed: https://github.com/Ultimaker/Cura/commit/34b76596f19931cd7498c837e105d95f6db1d445#diff-2cad9b3c673fced30c0d516025e6db56

I just stumbled upon the option to enable/disable the blob per extruder. Not sure when it was introduced but it is present in Cura v3.6 You can use a skirt or brim instead of the blob.

Browsing the forum on a mobile screen but not logged in, then there pops up a huge dialog that suggests to sign up. The dialog is too big to fit a vertical screen (1920 x 1080 resolution). Please remove or resize the large ulti robot graphic so the dialog fits a standard mobile screen again.

The original community member who supplied the D4S profile clearly didn't have such a machine, let alone he ever tested the profile. 😞 @rebekah_harper Your profile looks good, but there are a few things that hold me back from copying as is. - Is extruder 0 the right extruder and 1 the left as stated in your comments? I would expect reversed. - Official size is listed as 225 x 145 x 150. You have 220 x 140 x 150. Which is correct? - Is it true this machine only accepts X3G file format? If yes, then we can configure this as the default file type. Did you test and verify these codes, or are they just copied from another printer / forum post? I hoped enabling the 2nd extruder would suffice, but it looks this whole printer definition has to be checked... 😞

As mentioned above: make the S5 your group host and you'll have the newer Cura Connect that is still to be released for the UM3.

The UM3 firmware is a bit outdated in this aspect, it was released before the S5 was there (apart from a minor update that came out when the S5 was there). We are working very hard to get a new version of the UM3 out so that both the UM3 and S5 are in sync again. Under the hood a lot of things were shuffled around and this makes the update process complicated. We want to do a lot of testing here before we release the new UM3 software.

Administrator: Moved from the Firmware section.

You found a bug in the documentation. Correct is: http://xx/api/v1/materials/<guid> but the documentation web page adds an extra '/' at the end. Remove that and it works. I created a ticket to have the documentation fixed.

Which firmware do you want to compile? I never tried compiling the Tinkergnome version, but a few posts above I confirmed that compiling the Ultimaker firmware is as simple as installing the old Arduino IDE, make your changes and then press the upload button. No need to install Linux shells or MinGW etc. In case you want to install Tinkergnome's firmware someone else should be able to help you.

The Wanhoa profiles were supplied by a community member. We don't own Wanhoa printers, so for all the info and feedback we are dependent on you community people. Regarding this particular printer's configuration I asked more details in the thread about that subject and we will use the provided information to update the 4S's profile. I can't make a promise on the Cura release it will be in. As a workaround you can create your own custom FDM printer in Cura based on the settings of the current Wanhoa 4S and an x-offset of 33mm for the second nozzle.

Oops... We didn't implement it in the first release since there were bigger issues to tackle first and then it was forgotten. Interesting that the request was posted here only 2 years after the UM3 release. I'll bring it under the attention of our product owner.

@schen Thanks for taking the effort to reproduce the problem, this is really appreciated. I can now see 'what' goes wrong: you are using a custom created material and this info is missing from the printer. Understanding as to 'why' it goes wrong and why we didn't find this bug ourselves will take a bit more time but we are looking into it. I'm afraid there isn't going to be an easy workaround but will post an update here in a couple of days.

The Wanhao Duplicator 4s configuration was supplied by a community member. I can put in a request to update the configuration, but for that we need more info. Can someone measure the distance between the two nozzles, i.e. from center of the left nozzle to center of the right nozzle? Cura uses these values to calculate the allowed build volume, i.e. you have the printer's volume size but on some printers not all nozzles can reach all same physical locations.

@schen We failed to reproduce your problem. Did you save the log files by any chance? Which Cura version are you using?