Page MenuHomeAleph Objects Inc

Cura LE 3.6.15 crashing when updating FW - Taz Pro
Closed, ResolvedPublic


While testing Cura LE 3.6.15 connected to Taz Pro on Windows 10
To reproduce bug:
Connect to printer
the prompt to upgrade FW appears
Go to printer settings and upgrade FW. As soon as you click the Automatically Update FW button, Cura crashes.

Event Timeline

Yahuba created this task.Jul 19 2019, 11:00 AM
bmh added a subscriber: bmh.Jul 19 2019, 11:49 AM

See T8014 for more details ... this needs fixed!! :-) :-) :-)

Steven added a subscriber: Steven.Jul 19 2019, 1:38 PM

@Yahuba do you know when you all updated to that version of Windows 10, v10.0.18362?

Confirmed that this ticket is producing identical results to and should be merged with T8014

@Steven I don't know exactly - feature update history says "feature update to Windows 10, Version 1903 successfully installed on 6/7/2019"

alexei triaged this task as High priority.Jul 22 2019, 11:46 AM
alexei changed the edit policy from "All Users" to "Cura LulzBot Edition (Project)".
alexei added a subscriber: alexei.Jul 22 2019, 11:51 AM

@Yahuba , there must be some permissions issues for serial port access introduced with this update:

2019-07-19 12:55:49,635 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [61]: An uncaught error has occurred!
2019-07-19 12:55:49,638 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [64]: Traceback (most recent call last):
2019-07-19 12:55:49,639 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [64]:   File "C:\Program Files (x86)\cura-lulzbot 3.6\plugins\USBPrinting\", line 114, in updateAllFirmware
2019-07-19 12:55:49,640 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [64]:     self._usb_output_devices[printer_connection].updateFirmware(file_name, update_eeprom)
2019-07-19 12:55:49,641 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [64]:   File "C:\Program Files (x86)\cura-lulzbot 3.6\plugins\USBPrinting\", line 321, in updateFirmware
2019-07-19 12:55:49,643 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [64]:     self._detectSerialPort()
2019-07-19 12:55:49,644 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [64]:   File "C:\Program Files (x86)\cura-lulzbot 3.6\plugins\USBPrinting\", line 368, in _detectSerialPort
2019-07-19 12:55:49,645 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [64]:     serial_connection = serial.Serial(str(self._serial_port), baud_rate, timeout=3, writeTimeout=10000)
2019-07-19 12:55:49,646 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [64]:   File "C:\buildbot\win-slave1\CuraLEDevel-windows\build\build\inst\lib\python3.5\site-packages\serial\", line 31, in __init__
2019-07-19 12:55:49,647 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [64]:   File "C:\buildbot\win-slave1\CuraLEDevel-windows\build\build\inst\lib\python3.5\site-packages\serial\", line 236, in __init__
2019-07-19 12:55:49,648 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [64]:   File "C:\buildbot\win-slave1\CuraLEDevel-windows\build\build\inst\lib\python3.5\site-packages\serial\", line 62, in open
2019-07-19 12:55:49,650 - CRITICAL - [(2188)-MainThread] cura.CrashHandler.__init__ [64]: serial.serialutil.SerialException: could not open port 'COM5': PermissionError(13, 'Access is denied.', None, 5)

I will try to fix the crash itself but I'm not sure what to do when the driver is changing the serial port after going into bootloader mode or back to normal operations.

@victor_larchenko , could you please have a look at what might be wrong here?

I was able to replicate this in Windows 10 with build 3.6.16 attempting to connect to Workhorse.

@alexei, the problem was in connection thread. Update of firmware tried to open port that already open.

karrad reassigned this task from victor_larchenko to alexei.Jul 29 2019, 8:19 AM
karrad raised the priority of this task from High to Unbreak Now!.
karrad added subscribers: victor_larchenko, karrad.

@alexei We will need to get a windows build with this for yahuba to test, can we get it into master?

Merged to master.

alexei reassigned this task from alexei to victor_larchenko.Jul 29 2019, 4:31 PM
alexei closed this task as Resolved.

It seems that the crash itself was fixed, so I'm closing this ticket. For communication problems please use T7449.