Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Some gcodes cause MK3S to reset, give z-axis calibration error, and lose all settings forcing complete re-calibration #4714

Closed
zaniyah opened this issue Jul 13, 2024 · 18 comments

Comments

@zaniyah
Copy link

zaniyah commented Jul 13, 2024

This is a Prusa MK3S, with the latest firmware (3.14) printing from the SD card.

Every time I try to print a specific gcode file, the printer fails saying that there has been a z-axis error. At first I thought that this was a genuine hardware issue, and after tweaking and recalibrating and having successful prints of other things I had printed before, I tried again.

This cycle has been repeated several times now, and the same gcode file always triggers this bug.

Download the top part of this box here as a gcode file:

https://www.printables.com/model/3376-e3d-v6-nozzle-holder-nozzle-holder-nozzle-case/files

Specifically, this one:

https://files.printables.com/media/prints/3376/gcodes/21562_24bde222-9a5d-4c5e-9dd8-2169feb70d7d/top-piece-nozzle-holder_01mm_pla_mk3.gcode

Put on the SD card and attempt to print with a Prusa i3 MK3S with version 3.14 of the firmware, 0.4mm standard brass nozzle and PLA.

Initial bed calibration is fine. When printer starts to print, it almost immediately resets and gives a z-axis error.

@zaniyah zaniyah added the bug label Jul 13, 2024
@rspigner59
Copy link

I'm having the same issue, MK3S with firmware (3.14) printing from SD card. About every fourth print the print re-calibrates the Z-axis. Same info as mine: 0.4mm standard brass nozzle and PLA.
Same error here as well: Initial bed calibration is fine. When printer starts to print, it almost immediately resets and gives a z-axis error

@gudnimg
Copy link
Collaborator

gudnimg commented Jul 13, 2024

Hi 👋 I tried to reproduce this on my MK3S+ but so far have not been successful.

It would help us if you could share exactly what the z-axis error says?

Also when you say "reset" are we talking about a machine reboot or some state of the printer FW?

If you could share the serial logs from the printer that would also be super helpful. The baudrate is 115200.

@zaniyah
Copy link
Author

zaniyah commented Jul 15, 2024

I don't think you'll be able to recreate it with a MK3S+. I have been doing some fiddling around (I now have the upgrade kit) and it seems that under certain circumstances the firmware mistakes the normal older pinda sensor reading for an invalid one, triggering the re-calibration of the z-axis.

@rspigner59
Copy link

rspigner59 commented Jul 15, 2024 via email

@zaniyah
Copy link
Author

zaniyah commented Jul 19, 2024

"Some error encountered, Z-levelling enforced" is the intermittent error. The first error we saw was a completely corrupted screen, and the firmware crashed hard. I had to re-flash the printer.

Now I have this error intermittently, which is making it really, really hard to print the required parts for the MK3S+ upgrade. There seem to be many default settings that are for the MK3S+ and MK4 SuperPINDA but not appropriate for the older MK3S.

@rspigner59
Copy link

There needs to be a fix in the firmware for the MK3S to stop the automatic Z-axis calibration from taking place.

It's not good for the stepper motors since the MK3S lack up-limits to prevent the stepper motors from attempting to move the print head beyond the end of travel. This occurs about every 3rd or 4th print, after bed leveling, then the printer performs a z-axis calibration before printing the object.

@Emmanuel2102
Copy link

Did you activate the 7x7 Z levelling new feature ? I assume that this is this one that doesn't work well. I have solved the issue by setting back the 3x3 bed mesh levelling.

@zzeng5
Copy link

zzeng5 commented Aug 13, 2024

Had same issue on my MK3s 3.14 firmware with 7x7 mesh leveling enabled.

@rspigner59
Copy link

"Did you activate the 7x7 Z leveling new feature ?"
No, mine is [3x3] . The only thing I have done is upgrade to firmware (3.14). Prior to f3.14, I don't recall ever having a z-axis calibration error.

@Scandiravian
Copy link

Scandiravian commented Aug 15, 2024

Seeing the same issue on my mk2.5s. I've never had an z-axis error in the 7 years I've had the printer, but after upgrading to 3.14 I have to run recalibration after most prints. It doesn't fail during printing though, but at the initial calibration so could be related to #4723

@3d-gussner
Copy link
Collaborator

@Scandiravian Did you run the Calibrate Z? This should fix the issue.

@Scandiravian
Copy link

@3d-gussner thanks for the suggestion, but unfortunately that fails as well. I have to run a full XYZ-calibration and change z-calibration to 3x3. All other combinations fail

@3d-gussner
Copy link
Collaborator

This pull request should fix the issue which will be in next release FW 3.14.1.

Copy link

github-actions bot commented Nov 5, 2024

Thank you for your contribution to our project. This issue has not received any updates for 60 days and may be considered "stale." If this issue is still important to you, please add an update within the next 7 days to keep it open. Administrators can manually reopen the issue if necessary.

Copy link

This issue has been closed due to lack of recent activity. Please consider opening a new one if needed.

@github-actions github-actions bot closed this as not planned Won't fix, can't repro, duplicate, stale Nov 13, 2024
@harriettubgirl
Copy link

I keep having this happen also, 3.14 with MK3S+, never had this until I upgraded firmware.

@3d-gussner
Copy link
Collaborator

@harriettubgirl Sorry to hear that, please update the firmware to 3.14.1

@harriettubgirl
Copy link

@harriettubgirl Sorry to hear that, please update the firmware to 3.14.1

Oh thank you, I didn't even see that was out heh

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

8 participants