Page MenuHomeAleph Objects Inc

Unable to flash firmware for TAZ 4 (Moded to a TAZ 5) with HS toolhead
Open, Needs TriagePublic

Description

Occurs on all versions of Cura that have been attempted both Cura LE and Legacy.

Operating System: Windows

Printer: TAZ 4 modified up to a TAZ 5

Tool Head: HS and adapter

Description of issue: Customer is able to see printer visible when he checks in Cura, is also able to connect to printer through Legacy Cura. Whenever he flashes his firmware he gets a failed to update firmware error. In Cura LE it says due to unknown error in Legacy it gave error codes Verify error at: 0x2 and Verify error at: 0x36. Looking through his Cura log he is getting an ISP error that again listed the 0x2 number right after the ISP error.

Most recent log file attached.

Event Timeline

@karrad Do you have any input on this or suggestions for who to tag in for further assistance? Thanks!

karrad assigned this task to Galadriel.Oct 2 2019, 3:01 PM

@Galadriel Checking that error, the first result on google is an octopi error. Are they trying to flash firmware through octoprint or connected directly to the printer via USB?

Based on the videos they provded it looks like they are flashing directly through Cura. Do you happen to know if they still need to use Cura to flash the firmware even if Octoprint was being used as an intermediary? If not then they are definitely using Cura to flash. Thanks for the input!

karrad added a comment.Oct 2 2019, 3:14 PM

@Galadriel We have done no testing with octoprint on a raspberry pi. (The Pi is not open hardware) So I am not sure about how that would function with flashing firmware.

I would like you to verify they are not connected to Octoprint, and are just plugged directly into the RAMBo from USB.

Aside from that, please also get as much information about their operating system. (specific version of windows, OpenGL Drivers, and any security software they or their IT team may have installed.)

Also if he is able, have him try flashing the hex file through custom firmware and see if that completes.

@karrad Thank you for the help! I followed up with the customer to ask about Octoprint and request that if they are using an intermediary device to try flashing directly through the printer to see if that resolved this. I also asked for a screenshot of his computer properties which should have most of what you were looking for, let me know if there is anything missing and I can follow up with him to ask. I did ask about any special firewalls or anything like that when I spoke to him on the phone and he said he never uses the computer for anything that would require that sort of protection so he just uses the Windows Defender that came with the computer by default.

I did actually have him try a custom firmware flash, not just through the current version of Cura but also through the Legacy version because I have found the Legacy version is sometimes a bit more forgiving. He has been getting the same sort of errors regardless of if he tries a custom or standard firmware upload unfortunately.

karrad added a comment.Oct 4 2019, 8:10 AM

@Galadriel Have him disable windows defender, or specifically allow Cura LulzBot edition full access. It has been known to prevent USB communication with devices in the past.

I also had him try to allow Cura full access when I spoke to him on the phone, unfortunately no luck on that front.
He got back in touch with us to let us know that doesn't use any sort of intermediary like Octoprint. Only thing close that he was using was an extension to his USB Cable, he did try to flash without the extension but still got the same error.
He also tried to use a different computer to see if that might help but was unsuccessful.
I got several photos of his Computer Properties as well as some other photos he included of the internal wiring that he added just in case something was installed incorrectly. Nothing visibly amiss with wiring. Computer properties photos included.


karrad reassigned this task from Galadriel to Yahuba.Oct 4 2019, 2:11 PM
karrad added a subscriber: Yahuba.

@Yahuba Please see if you can flash the default firmware for a TAZ 5 with HS tool head on Windows 10

Yahuba added a comment.Oct 7 2019, 8:15 AM
This comment was removed by Yahuba.
Yahuba added a comment.Oct 7 2019, 9:23 AM

Was able to succesfully Flash FW on Taz 6 with an HS toolhead attached from Windows 10 machine running Cura 3.6.20

@Yahuba Just to verify, you flashed TAZ 5 Firmware onto the RAMBo board in the TAZ 6?

That is correct, here are the steps I took after clearing cache and installing a fresh install of Cura 3.6.20:
Launched Cura and selected Taz 5 printer and HS toolhead during initial set up
Connected to printer and Auto Flashed FW
Confirmed FW flash by checking LCD screen on TaZ 6 which indicated it was a Taz 5 printer.

karrad reassigned this task from Yahuba to Galadriel.Oct 7 2019, 11:42 AM

@Yahuba Thank you much!

@Galadriel We have been able to verify that windows 10 can successfully flash TAZ 5 HS firmware from an auto update using Cura LE 3.6.20. It looks to be something off on the local users side, either hardware or software preventing communication. Does the customer have any other printers or computers he can test on?