-
Notifications
You must be signed in to change notification settings - Fork 229
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] Enclosure option keeps switching off #4186
Comments
Did three prints today, each time it was off and I had to re-enable the enclosure. Is it a Slicer thing? That the slicer turns it off? |
trim.528A9648-C32C-4B25-AE3D-DE4ED78F007D.MOVThis is what's happening |
trim.0B9D2257-5077-4A8A-AC20-31A6DC0F4E6A.MOV3rd time today... |
This is not a bug, this is a correct behaviour. After the printer detects that the fan is not spinning, it turns enclosure off and displays this message. Did you check the fan for debris and inspect the wiring as the dialog suggests? |
When I enable the enclosure you hear the fan spinning up and is working properly. So that raises the question in my mind, why isn't the fan starting when the print starts, but does start/work when I re-enable the enclosure? And yeah, fan and filter is clean, it has only printed 56hrs since the enclosure is installed. |
It happened again. I started the print, you year spinning up the fan for a second and than turns of with the error message. Turning it on on the display and you hear spinning up the fan and it's just working. |
I can confirm that this happens to my XL5 as well. Running 6.1.3 FW. No debris in the fan or filter. Fan cover removed in case it was too tight like the print fan on the toolheads causing issues. Did not resolve the issue. |
Well, for some reason, printer thinks the fan is not spinning. You still haven't ruled out electrical/mechanical problem. There might be some problem on the tachometer wire. I suggest consulting tech support, unless you are willing to grab oscilloscope and build your own firmware to debug this problem. Just to be clear, I believe you that your enclosure is misbehaving, I just don't think this is a firmware problem given that there are not many reports like this from other users. |
@zuidwijk did a factory reset and updated to the 6.2.0-alpha FW and the issue is resolved. Hope it works for you too. |
No not yet, I'll try within a few days. I'm just not into alpha firmware on production environments... I'll sit this one out till next release. At least my suspicion looks in the right place. |
Yeah I hear you. Haven't had time yet. Way too busy. But I'll contact support anyway for extra check-up. |
Well I’m in contact with support via email. Here another one. Checked if enclosure was enabled, which it was, started a print and again the notification. |
I am having the same issue. Enclose fan works perfectly, passes the check when I turn the enclosure on, but when sending a print through prusa connect, I get that message. If I start a print from the printer, no issue. Re-enabling the enclosure immediately after getting that error message turns the fan on. |
I think the issue happens when running a filament that doesn't need filtration (e.g. PETG). I don't seem to get the issue when running PC-CF, for instance. This is as if the printer checked if the fan was running, regardless if there had been a command to set the fan on or off, so if fan/filtration not requested for that filament, the printer sees that the fan is not running, and complains. |
Printer model
XL 5 tool head
Firmware version
6.1.3
Upgrades and modifications
None
Printing from...
USB
Describe the bug
When a print start (via connect) I get the error message that enclosure fan isn't working.
When I check te settings, the enclosure toggle is off in the settings.
When enabling it starts spinning and prints fine.
The next print same issue, enclosure is switched off again
How to reproduce
Just start a print, it happens every time ... I didn't switched off the printer, its always on.
Expected behavior
When enabling the enclosure in the settings I expect it to remain on, until I switch it off.
Files
No response
The text was updated successfully, but these errors were encountered: