Szahari

Hi all, I was beaten to the punch by Link, but here it is officially too: Firmware 5.7.3 has been released for the S-line printers. Theres some much requested features in there, such as the Material Station lights being adjustable for the pro Bundle and the camera streaming images over the cloud in the digital factory (both S5 and S3) You can read the full release notes here. Enjoy!

Hi Huib, your ticket was received in well and good order! we're working on the ticket, and you'll hear back before the end of the day ! Also gonna look into why you got that email! Best

In the investigation of the issue, its been noticed that the following lines are always found in the log files UM3 printers that are affected by the shifted / split screen: Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: Modules linked in: nls_iso8859_1 nls_cp437 vfat fat lm75 af_packet arc4 gpio_pca953x ath9k_htc uvcvideo ath9k_common videobuf2_vmalloc leds_pca963x videobuf2_memops ath9k_hw videobuf2_v4l2 ath videobuf2_core uas mac80211 videodev evdev media cfg80211 rc_cec sun4i_backend sun4i_ts axp20x_usb_power gpio_axp209 axp20x_pek axp20x_adc industrialio at24 sun4i_gpadc nvmem_sunxi_sid sun4i_lradc_keys sunxi_wdt pwm_sun4i ahci_sunxi libahci_platform libahci libata sun4i_ss sun4i_drm_hdmi cec des_generic sun4i_hdmi_i2c rc_core spi_sun4i sun4i_tcon sun4i_drm drm_kms_helper cfbfillrect cfbimgblt cfbcopyarea rotary_encoder drm pwm_beeper cpufreq_dt thermal_sys hwmon i2c_dev rfkill_gpio rfkill sha1_arm_neon sha1_arm sha1_generic ipv6 ssd1307fb syscopyarea sysfillrect sysimgblt fb_sys_fops [last unloaded: gpio_pca953x] Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: CPU: 0 PID: 7 Comm: ksoftirqd/0 Tainted: G W 4.14.32-ultimaker-00309-geaace6d4aede #3 Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: Hardware name: Allwinner sun7i (A20) Family Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<b01102bc>] (unwind_backtrace) from [<b010c17c>] (show_stack+0x10/0x14) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<b010c17c>] (show_stack) from [<b05e54bc>] (dump_stack+0x84/0x98) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<b05e54bc>] (dump_stack) from [<b012beb0>] (__warn+0xe8/0x100) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<b012beb0>] (__warn) from [<b012bf30>] (warn_slowpath_null+0x20/0x28) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<b012bf30>] (warn_slowpath_null) from [<af43cc88>] (ieee80211_rx_napi+0x848/0x9ac [mac80211]) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<af43cc88>] (ieee80211_rx_napi [mac80211]) from [<af574370>] (ath9k_rx_tasklet+0x13c/0x17c [ath9k_htc]) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<af574370>] (ath9k_rx_tasklet [ath9k_htc]) from [<b0130ca8>] (tasklet_action+0x74/0x110) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<b0130ca8>] (tasklet_action) from [<b0101644>] (__do_softirq+0xfc/0x224) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<b0101644>] (__do_softirq) from [<b0130dd4>] (run_ksoftirqd+0x38/0x50) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<b0130dd4>] (run_ksoftirqd) from [<b014c468>] (smpboot_thread_fn+0x11c/0x198) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<b014c468>] (smpboot_thread_fn) from [<b01487d0>] (kthread+0x124/0x154) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: [<b01487d0>] (kthread) from [<b0108208>] (ret_from_fork+0x14/0x2c) Jun 12 19:44:59 ultimakersystem-ccbdd300169b kernel: ---[ end trace a088063bd8ec7c9d ]--- Jun 12 19:44:59 ultimakersystem-ccbdd300169b connmand[259]: wlan0 {newlink} index 3 address 00:0E:8E:72:24:A1 mtu 1500 Jun 12 19:44:59 ultimakersystem-ccbdd300169b connmand[259]: wlan0 {newlink} index 3 operstate 2 <DOWN> Maybe someone in the community understands a bit more whats happening there? All evidence we have supports the fact that a local network configuration setting is causing a corruption in the data. Because of htat,tTogether with the logs, any and all information about your local network configuration may be helpful in the investigation of this issue: - is it home or work network - any peculiarities that stand out for your network? Many devices connected? - Are you using a wifi repeater?

Can you show us pictures of how exactly misaligned the print is coming out? If the XY calibration is successful, then maybe theres some Cura print settings that can be improved? If you have spare print cores also lying around, it could be trying to use them to see if theres a difference in behaviour.

Hi Jason, Thanks for your feedback! I think we learn something new all the time about usage into the printers. I think it wouldn't be an impossible task to restore the functionality. The use case you've mentioned is outside something that we would normally consider however, but its always great to see how people are using these printers. I'll go ahead and poke around and see what can be done in terms of restoring this functionality. As always, the more demand the better it is to get priority on something, so if more likely it is to get picked up sooner rather than later!

Hi all, New firmware for the S5 and the S3 has been released today. In line with the change of mycloud to digitalfactory, you will see some branding changes, and some cloud feature improvements. You can read more about it in the blog. You can view the full release notes for the S5 here, and for the S3 here. If you want to download the .swu for a USB download, you can do that from this S5 page or this S3 page Thanks for your time!

Jonas & Roli, Could you please give me as detailed a possible on your printer and network setup? Are you using a home, or company (more stringent) network access? Are you using a S5, pro bundle, and are there more printers in the group? Roli, is the printer not re-establishing connection itself? A cura connect reset is needed? The more information the better. You can also PM me if things are confidential Thanks

Sorry to hear about these network problems. We have firmware coming up that may be able to tackle some of these networking issues. The upcoming firmware will mostly focus on updated cloud features, and with it some network improvements for connect. ETA this week.

Certainly not what I expect. I see that there's an ongoing support request for you, thank you for raising it that way! It really helps with tracing and troubleshooting all support requests. @Jonas98 Very pleased you got your first print successful. Do you maybe have images or a short video of this crashing into printcore and this sausage that you refer to? If there was a a blockage, impeding flow than the printer correctly produced the ER65. And without divulging too much, I can certainly say we are aware and working towards more solutions for the PVA printing. This firmware doesn't change to much on the PVA printability in itself, but we felt it still had a lot of value to get out there.

Not yet, not in this version. This firmware mainly optimizes the processes within the machine.

Hey everyone, thank you for your patience. I'm pleased to inform you that we have released a new firmware version for the Ultimaker S5. Firmware 5.6.8 will solve a number of issues you may have encountered recently. You can read more about it in this post. You can download it directly from your machine if it is network connected, or fetch the .swu file that goes on a USB from here. Cheers!

Hi Brolman, Can you please elaborate more on why you are experiencing no 3D printing? We would be happy to help you if you encountering any blocking issues. Of course, we are aware of its issues and experiencing many of the issues you guys have reported here. We too, as users of ultimaker products use the workarounds which we have already communicated. @Link - With regards to the XY calibration - we are fortunate that our printers do not require this procedure often. Part of our QC before dispatching a printer for sale is that the printer MUST be tested with a dual print. You will receive the test print within the box. Therefore, the XY calibration has been done before shipping and you should receive a printer which has its print cores calibrated. If you require changing of cores straight away then the XY calibration should be done - but the workaround of manually pushing the filament through to the nozzle before the filament deposition starts will solve your issue. What this also means is, that current printers being shipped out with the old stable (5.1.8) firmware. The updated hotfix firmware is in active development and you will be alerted of the release date as we know more. I can understand the frustration that it has taken this long, but as Sander said this hotfix is there to fix many problems. Our earlier communication did not take into account how our Firmware team would like to build the next version. It is always a balancing act of building the thing right, building the right thing, and building it fast. Our hotfix has been decided to fix all known issues, which takes time. More on the release date will follow.