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] Error 17536 appeared when switching from 6.1.3 to 6.2.0 #4467

Open
Tomycool opened this issue Feb 8, 2025 · 0 comments
Open

[BUG] Error 17536 appeared when switching from 6.1.3 to 6.2.0 #4467

Tomycool opened this issue Feb 8, 2025 · 0 comments
Labels
bug Something isn't working.

Comments

@Tomycool
Copy link

Tomycool commented Feb 8, 2025

Printer model

XL 2T + 3T

Firmware version

6.2.0

Upgrades and modifications

XL Fan Shroud 360°

Printing from...

USB drive

Describe the bug

I allow myself to make this post even if it has already been mentioned previously except that for me it appeared when changing firmware from 6.1.3 to 6.2.0. I had no problem on version 6.1.3, nothing.
I also know that new versions of the parts are available and I will print them when I receive the necessary screws and nuts, it seems relevant to me.
I specify that the maintenance is done rigorously and everything is clean.

The problem is on head 1, it is true that the incriminated part in petg moves a little but the pin is fixed well and does not move.
What I'm wondering about is that I go from a very nice 20-hour multicolor print with input shaper on version 6.1.3 to red screens on 6.2.0 without changing anything.
When the red screens appeared, all the tools were parked.
During the last print that failed (see photo), I was able to see, by checking the toolpath on Prusaslicer, that the last head used was head 2, which leads me to two hypotheses:
1: head 1 (white) makes its layer, makes its mistake, goes to park and lets head 2 (gold) make its layer, park then red screen.
2: head 1 makes its layer, goes to park, head 2 makes its layer, goes to park then red screen except that head 1 is parked so not moving.

Not being in front of the machine when the errors occurred I do not know if the errors leading to the red screen freeze the machine or not.

Image

Image

I went back after several errors to version 6.1.3 without changing anything and for the moment I have no problem.

Image

Thanks in advance
Thomas

How to reproduce

No response

Expected behavior

No response

Files

No response

@Tomycool Tomycool added the bug Something isn't working. label Feb 8, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working.
Projects
None yet
Development

No branches or pull requests

1 participant