Page MenuHomeAleph Objects Inc

Cura 3.6.13, 3.6.10 and 3.6.8 crash on firmware update
Closed, DuplicatePublic

Description

T7997 references this issue with 3.6.8, but to make it clear in the title that it is both versions, I created a new issue ticket. I've never created an issue ticket, so if I'm doing something wrong protocol-wise, please educate me (nicely :-)).

When doing these tests they were with clean installs of each respective version. By clean install I mean using Programs & Features to remove the program, then going to C:\Program Files (x86) and removing the left over program folder, then removing cura folders from both %appdata% and %localappdata% then rebooting the PC (Windows 10) then installing the version of Cura to test with.

This is how Cura 3.6.8 acts:

Test 1 (3.6.8) ...

  • Load Cura, but do NOT "Connect" from "Monitor" screen.
  • Go to manage printers, only have the Pro installed so it's selected, select upgrade firmware.
  • Click "Automatically ugprade Firmware".
  • After few seconds it fails with a dialog that says"Firmware update failed due to communication error.
  • LCD screen goes blank and stays blank.
  • Clicked "Close" on the failure dialog.
  • Now still at the "Upgrade Firmware" dialog.
  • Select "Automatically ugprade Firmware" again.
  • It works with no issues.
  • Exit Cura.
  • Load Cura and repeat the steps above and got same exact results in same exact order.
  • So the behavior was repeatable.

Test 2 (3.6.8) ...

  • Load Cura, but this time DID "Connect" from "Monitor" screen.
  • Wait for connection to complete.
  • Go to manage printers, only have the Pro installed so it's selected, select upgrade firmware.
  • Click "Automatically ugprade Firmware".
  • Program instantly dies and exits.
  • Load Cura and repeat the steps above and got same exact results in same exact order.
  • So the behavior was repeatable.

Test 3 (3.6.8) ...

  • Figuring I need to get the firmware back, I now went back to following the "Test 1" scenario (but got slightly different results).
  • Load Cura, but do NOT "Connect" from "Monitor" screen.
  • Go to manage printers, only have the Pro installed so it's selected, select upgrade firmware.
  • Click "Automatically ugprade Firmware".
  • This time it just blew out of the program - whereas in "Test 1" what happened was getting the comm error dialog.
  • Reloaded Cura, re-ran "Automatically upgrade Firmware" again and this time it just worked with no issues at all.
  • So the results this 3rd time were somewhat inconsistent, but in all cases getting it to easily fail is repeatable.

Now onto Cura 3.6.10 and how it acts:

  • Clean uninstall of 3.6.8 and install of 3.6.10.

Test 1 (3.6.10) ...

  • Load Cura, but do NOT "Connect" from "Monitor" screen.
  • Go to manage printers, only have the Pro installed so it's selected, select upgrade firmware.
  • Click "Automatically ugprade Firmware".
  • After few seconds it fails with a dialog that says"Firmware update failed due to communication error.
  • LCD screen goes blank and stays blank.
  • Clicked "Close" on the failure dialog.
  • Now still at the "Upgrade Firmware" dialog.
  • Select "Automatically ugprade Firmware" again.
  • Cura just immediately blows out and exits - unlike under 3.6.8 where it just worked the second time.
  • Re-run Cura, select automatically upgrade firmware and it just worked - no errors at all.
  • Repeated all the above steps and acted exactly the same - it's repeatable.

Test 2 (3.6.10) ...

  • Load Cura, but this time DID "Connect" from "Monitor" screen.
  • Wait for connection to complete.
  • Go to manage printers, only have the Pro installed so it's selected, select upgrade firmware.
  • Click "Automatically ugprade Firmware".
  • Program instantly dies and exits.
  • Load Cura and repeat the steps above and got same exact results in same exact order.
  • So the behavior was repeatable.

So if a user tries to update while connected it never seems to work under either version.

If updating while NOT connected, there are also issues, but it seems the second time through (again, under the NOT connected scenario) it seems to work although acts slightly different between 3.6.8 and 3.6.10.

Failed firmware updating is scary to most people so this seems like something that should be relatively high priority to fix IMO.

EDIT ...

Cura 3.6.13 exhibits the same exact behavior as 3.6.10, both Test 1 and Test 2 as described above. I noticed this task and the other tasks that talk about firmware crashing still say "Needs Triage". This seems like it should be a fix me yesterday thing :-) (imo). As I said before, I would imagine that most users have some level of freakout when a firmware crash occurs and they see the LCD go fuzzy.

Event Timeline

bmh created this task.Jun 18 2019, 6:21 PM
bmh renamed this task from Cura 3.6.10 and 3.6.8 crash on firmware update to Cura 3.6.13, 3.6.10 and 3.6.8 crash on firmware update.Jul 2 2019, 3:27 PM
bmh updated the task description. (Show Details)
Steven added a subscriber: Steven.Jul 19 2019, 1:15 PM

@bmh can you give us the specific release version of Windows 10 you can repeat this on? An example is v10.0.18362

bmh added a comment.Jul 19 2019, 1:32 PM

@bmh can you give us the specific release version of Windows 10 you can repeat this on? An example is v10.0.18362

@Steven, I would be happy to do so when I get home tonight. If there is any other info I can provide, please do not hesitate to ask as I'd love to see this get resolved. :-)

Using C# terminology (I know that is not what this is), is there a general try/catch around the code that performs the update to capture any exceptions that could write a full stack trace to the log file to help determine what is going on? If there is not and you can do something similar to this, I would be more than happy to test it for you to get you more info.

@bmh we just had that discussion in a call to see if there was more we could get on the log. Now that we've finally been able to reproduce the issue we'll see what we can find in the existing logs. If we have to find another way to get info on the crash we'll post it here. Thanks for the help!

Yahuba added a subscriber: Yahuba.Jul 19 2019, 2:05 PM

Replication of "Test 1" from above using 3.6.15

Replication of "Test 2" from above using 3.6.13

bmh added a comment.EditedJul 19 2019, 4:15 PM
In T8014#161007, @bmh wrote:

@bmh can you give us the specific release version of Windows 10 you can repeat this on? An example is v10.0.18362

@Steven, I would be happy to do so when I get home tonight. If there is any other info I can provide, please do not hesitate to ask as I'd love to see this get resolved. :-)

Using C# terminology (I know that is not what this is), is there a general try/catch around the code that performs the update to capture any exceptions that could write a full stack trace to the log file to help determine what is going on? If there is not and you can do something similar to this, I would be more than happy to test it for you to get you more info.

@Steven here is my info:

Edition:Windows 10 Pro
Version:1809
Installed on:2/16/2019
OS build:17763.557
Arch:64-bit
Proc:Intel Core i5-4570S @ 2.90Ghz
Ram:8G
Device:Dell Optiplex 9020

Please let me know if I can provide anything else.

Yahuba added a comment.EditedJul 22 2019, 9:29 AM

Cura 3.6.15 - MacBook Pro - Mojave 10.14.5 - Connected to Taz Pro

  • without connecting first, automatic firmware update produced error message "Firmware update failed due to communication error"
  • staying in "upgrade firmware" dialogue, automatic firmware update was successful on second attempt, followed by a successful print.

Cura 3.6.15 - TazPro - MacBook Pro - Mojave 10.14.5

  • connecting to printer first, automatic firmware update produced error message "Firmware update failed due to communication error"
  • staying in "upgrade firmware" dialogue, automatic firmware update was successful on second attempt, but after closing out all dialogues, "USB printing" status bar read "USB device available" instead of "connected via USB," as in previous test. After connecting to printer, pre-heating temp readings in Cura stalled at 88C for Ext. 1 and 28C for Ext.2 - but read 210C & 30C respectively on TazPro LCD screen and movement commands were not functioning, including home all. After disconnecting and reconnecting the printer, the stalled readings remained the same in Cura and on TazPro LCD.

Yahuba added a comment.EditedJul 22 2019, 12:20 PM

Cura 3.6.15 - TazPro - Debian Strecth

  • without connecting, automatic firmware update ran successfully, and after closing dialogues, "USB printing" status read "Scanning available serial ports for printers" and would not respond to connect command. After pressing "Disconnect" and "Connect" again, the printer connected and repeated same behavior when firmware was auto-updated (stuck on "Scanning available serial ports for printers"). After connecting a third time and not auto-updating firmware, a successful print was completed.

  • after connecting to printer, automatic firmware update froze while updating. After closing update status, remaining in "Upgrade Firmware" dialogue, a second attempt to auto-update was successful, after which the behavior was identical to previous test above following the "Disconnect" and then "Connect" commands.

Cura 3.6.15 - Taz Pro - Ubuntu 18.04
Same behavior as Debian

Testing under 3.6.17, Windows 10:

  • Connect or do NOT connect first - does not matter (I tried both ways)
  • Click Automatically Upgrade Firmware
  • Few seconds then you get "Firmware update failed due to a communication error."
  • Click Close
  • Program does not crash (previously it had)
  • Click Automatically Upgrade Firmware again
  • The second time through it works

So basically it still is failing initially ...

alexei added a subscriber: alexei.Jul 29 2019, 6:16 PM

@bmh, Thanks for the update, it's very helpful. I'm going to close this ticket as duplicate of T8859. The discussion about communication issues will be continued in T7449.