Ultimaker Firmware 5.1.7

[Shadowman 53]

17 minutes ago, CarloK said:

@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

How about the ability to turn the lights off too. This was promised with the last firmware.

 

Thank you

[schen 0]

1 hour ago, CarloK said:

@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

I am glad to hear that!  I look forward to the next firmware release, thanks.

[CarloK 205]

14 hours ago, Shadowman said:

How about the ability to turn the lights off too. This was promised with the last firmware.

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.

[Shadowman 53]

2 hours ago, CarloK said:

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.

Good day

 

I appreciate the information and the means to do so. Furthermore, I understand the teams reluctance to make non-critical incremental changes but rather incorporate it within a fully tested release.

 

For this moment I will await the tested firmware expected in February.

 

Takes care and thank you.

[kmanstudios 1,120]

Yeah, I am going to have to go with fixing the big things and making robust before anything else.

 

Good to see this happening. 💗

[CarloK 205]

On 11/2/2018 at 8:08 AM, kmanstudios said:

There is new behaviour with this version. When I paused the print to clean the carbon off the PVA nozzle it released a long thread of material when resuming instead of a clean continuation as before.

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.

[CarloK 205]

On 11/4/2018 at 9:14 AM, kmanstudios said:

So, I go to load material with the new firmware and a new AA core. It tells me that the X/Y calibration needs to be done. And then the lights start pulsing. Why because this thing is a real nag when it comes to the material options. When I am in an operation such as changing materials, or nozzle calibration or just sitting there whilst preparing a new print, it just starts nagging, nagging, nagging and giving me headaches because of the pulsing lights. This alone is enough to make me want to stop using Cura Connect.

 

1. If I am in an operation such as cleaning nozzles, calibrating offsets, etc., it should not be nagging me.
2. If I hit the ok button and go to do work, it should not come back on and nag me. Or, do you think once is not enough?
3. The pulsing lights bug me badly. That and putting the printer in unavailable mode just turns the lights off making life difficult when trying to do maintenance

None of this makes sense. And really, just because someone decided to make it so, and without options for the user is really not an excuse. The pulsing lights really cause issues with my eyes.

 

The lack of lights when trying to do maintenance is really illogical.

 

Lack of options for the users is even more so.

 

But seriously, when I hit the damned button to agree to change materials, it should not keep coming back on me. Or, does Team UM think I would not notice when I go to print from the queue and it is telling me to change or override?

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.

[kmanstudios 1,120]

1 hour ago, CarloK said:

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.

I will try to be more clear:

When I put the printer into unavailable mode,. the lights go out and I have no control over them. That creates an issue with using 'unavailable; to stop prints going through while doing maintenance. Crazy things like cleaning nozzles, doing hot or cold pulls, etc. Basically, 'unavailable' should stop prints from going through, but not interfere with any other machine functions. Since I cannot see what I am doing, I have not tried any other machine functions, so I have no idea what else may be messed with.

 

1 hour ago, CarloK said:

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.

I do not quite follow this. What I was trying to say is that if I acknowledge the need to change materials or nozzles (The pulsing lights warning to do so), it should stay off and not constantly nag me. It does not do this on the UM3E machines. So, basically:

1. Warning

2. Acknowledgement

3. No more warnings.

 

The one minute timeout you mentioned would not be really helpful if doing a lot of things like cleaning under buildplates, a series of hot pulls and cleaning nozzles, etc that do not require a lot of menu actions.

 

This is how it behaves with the UM3E machines I have.

 

I hope I clarified this...let me know if I bungled it up a bit more.

Edited December 7, 2018 by kmanstudios

[fire4trails 0]

I'm new to the group.  Just received my S5, and ran my first print.  The first thing I noticed was the LED lights lit up my room.  Updated the firmware and they are now dim... but would like them to turn off.  This unit sits in my home office, at the front of my home.  Lights up the entire room.  Checked on how to do this on this forum... and see its a known issue.  I'll continue to follow this, with the hopes that this does get resolved soon. Seems like a simple code fix... but then again, I'm a mechanical guy and not an EE. :-)  Hopefully the pros over at Ultimaker can figure this out.  Mechanically this unit is simple to use, elegant, and makes superb parts.  So, just following to follow this thread!  Cheers everyone.

[Carla_Birch 116]

The led's going off will be in a update in the new year, you can edit the code to fix the problem yourself but it's not something i would risk doing on a machine that costs so much and would wait for the official update.

[ColoRich 1]

On 10/31/2018 at 12:39 PM, SandervG said:

Hi, we just launched a new firmware version for the Ultimaker S5. New firmware for the Ultimaker 3 will follow quickly. 

If you are curious about the release notes? Please follow this link

 

Well, it’s been a while.  Any firmware update for the UM3 yet?

[Smithy 1,146]

Not yet...

[ColoRich 1]

With the introduction of the new flagship S5, is the UM3 even supported anymore?  It looks like the last firmware update was April of last year.

[Smithy 1,146]

Yes I am sure it is, don't worry. As far as I know, the firmware versions should be consolidated, that the UM3 can use the same version or most of it. Then it should be easier and faster to bring new firmware version for the UM3, because it is mainly the firmware of the S5. 

[CarloK 205]

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.

[CarloK 205]

2 hours ago, ColoRich said:

With the introduction of the new flagship S5, is the UM3 even supported anymore?  It looks like the last firmware update was April of last year.

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.

[Smithy 1,146]

3 minutes ago, CarloK said:

but only want to release it when we are confident the update won't brick your printer.

That is really important - Thanks CarloK for the update!

[ColoRich 1]

36 minutes ago, CarloK said:

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.

 

‘Thank you, Carlo.  Will we ever get filament monitoring and Frame LED control?  Both would be great.

Edited January 4, 2019 by ColoRich

[CarloK 205]

Filament monitoring in a UM3 requires addition of a sensor in the feeder. To my knowledge Ultimaker is not planning to sell this as an upgrade. If you can get hold of an S5 feeder than it's not too difficult to get it working though. Perhaps you can even make a community project out of this?

 

I'm not sure what you mean by the Frame LED control. You can already control these LEDs through the menu and web API.

[stoccarda 0]

Does an update on the UM3 from 4.3.3.20180529 to 5.18 using a USB stick work?

The UM3 runs the update, but after reboot still 4.3.3. is indicated.

[Smithy 1,146]

23 minutes ago, stoccarda said:

Does an update on the UM3 from 4.3.3.20180529 to 5.18 using a USB stick work?

The UM3 runs the update, but after reboot still 4.3.3. is indicated.

4.3.3. is the latest firmware for the UM3.

You cannot install the S5 firmware to the UM3.

[stoccarda 0]

Ok, misunderstanding from my side. I saw
https://ultimaker.com/en/ultimaker-firmware

and clicked onto the 'Ultimaker 3' button expecting the 5. on the side

https://ultimaker.com/en/resources/23129-updating-the-firmware

The version number is not shown on this side.

Actually reinstalled the version which was on the UM3

[CarloK 205]

Installing 5.1.8 on the UM3 might brick your printer!!!! Don't try this.

We are working hard to get the UM3 update working but this takes  time to get stable for all situations. 

[stoccarda 0]

Thanks for he warning !!!
I have and will always click on the 'Ultimaker 3' button,

unless we have additionally a 5 😉

[xxTIMMYxCxx 0]

On 11/2/2018 at 12:35 AM, SandervG said:

After reading some of the reports I inquired with our experts and I understood that if you use the pop-up notification there is a (small) chance that the firmware upload might stall. If you use the menu instead, there isn't. That may be counter-intuitive, but I would recommend to not use the notification but the menu instead. 

 

Good news is, this bug is fixed in the new firmware. But in order to benefit from this, you must install it first. (Via the menu.)

It can be found in the release notes, almost at the bottom:

• Fixed crash when initiating the firmware update from the notification popup

@Shadowman , it should be fixed indeed. The LED's bugfix was not listed among some other fixes because the full list would be too long to share. One bulletpoint saying '- And more general (smaller) bug fixes are implemented' should be added to the list. 

 

Unfortunately having just done the firmware update today via the popup - my machine has hung on a blank screen following the 'ultimaker' popup. I would say the bug is still well and alive. What are my options?