3.10.1 firmware broken
This version seems to be broken. After upgrading it appears fine but the control knob on the printer does nothing. Flashed the 3.9 version and the printer works correctly.
RE: 3.10.1 firmware broken
Are you VERY sure that you had the EXACT FW version for your specific version of the printer?
RE: 3.10.1 firmware broken
I downloaded 3.10.1 from here:
https://help.prusa3d.com/en/downloads/mk3s-2/firmware
I then got 3.9.3 from the same page and it's printing normally now.
On the previous page MK3S+ shows first, then far down the page is a separate section for MK3S. I have a first generation MK3, upgraded using a MK3s using the prusa kit. No addons or changes. Should I assume the MK3S and MK3S+ are different enough to need different firmware?
RE: 3.10.1 firmware broken
I Agree with @jsw, I just flashed this to my two MK3S+ printers the either day with no issues. I'd check you flashed the corrected file for the model printer you have. the names are similar so it's an easy mistake to make.
Are you VERY sure that you had the EXACT FW version for your specific version of the printer?
RE: 3.10.1 firmware broken
Assuming you have an MK3S+ the file name from that should be
prusa3d_fw_MK3S_MK3S+_3_10_1_4697.hex
I downloaded 3.10.1 from here:
https://help.prusa3d.com/en/downloads/mk3s-2/firmware
I then got 3.9.3 from the same page and it's printing normally now.
On the previous page MK3S+ shows first, then far down the page is a separate section for MK3S. I have a first generation MK3, upgraded using a MK3s using the prusa kit. No addons or changes. Should I assume the MK3S and MK3S+ are different enough to need different firmware?
RE: 3.10.1 firmware broken
It is. It updated, verified, and rebooted. The control knob did nothing. I waited several minutes with no activity. I powered the unit off. It started again as normal but was still unresponsive. I redid the same procedure with "prusa3d_fw_MK3S_3_9_3_3556.hex" and it's now running a print.
RE: 3.10.1 firmware broken
I'm not sure then. I've never seen that behavior before. Can you try going to 3.10.0. I was running that for months before upgrading to 3.10.1
RE: 3.10.1 firmware broken
I have the same issue. Started with firmware, 3.10, which I ended up skipping. Same behavior now. Works fine with 3.9.2.
RE: 3.10.1 firmware broken
Different version of board?
I have the same issue. Started with firmware, 3.10, which I ended up skipping. Same behavior now. Works fine with 3.9.2.
RE: 3.10.1 firmware broken
It's a factory original i3 MK3S. Not sure how that compares to MK3 upgrade.
Not really sure where to get board information. Support menu reports EINSy_10a, E3Dv6full, Nov 10 2020
RE: 3.10.1 firmware broken
Might be worth contacting support
RE: 3.10.1 firmware broken
Looked all over the web site. No links lead to tech support. 🙁
Might be worth contacting support
RE: 3.10.1 firmware broken
Should be able to email support [email protected]
For support: Log into your Eshop account, navigate to support (Help) and live chat is at bottom right in most browsers. If not you may need to disable your ad-blocker temporarily.
Cheerio,
RE: 3.10.1 firmware broken
When I flashed the 3.10.1 on my MK3S, both the cooling fans started spinning at maximum rpms. I did not want to do anything as the flash process already started. I just held the printer down to stop it from flying out of the enclosure 😎
After the flash completed, the fans stopped and everything worked as normal.
RE: 3.10.1 firmware broken
I think this happened to me during the verify step but after that completed everything went to normal. An update from the OP? I'm curious if support was able help you out.
RE: 3.10.1 firmware broken
When I flashed the printer said it was updating, then verifying, then it said it had successfully updated. The printer returned to the main screen and was unresponsive after. I waited several minutes and nothing changed. I powered it off and when started again it remained unresponsive.
I resolved all my issues by down grading to version 3.9.3. I reported it to Prusa for the attention of the devs. It seems like it was not sufficiently tested with old hardware.