Advanced Filtering System misbehaving on Core One
Hi,
(would post it in the "help" subforum but it's impossible to create topic there)
Setup: Core One, FW 6.3.4 (newest available), Advanced Filtering System with HEPA with default settings in menu (AFS fan should be on for 10 minutes after printing to remove bad stuff from the chamber).
Slicer: Orca + Core One built-in menu
Problem: AFS ventilator is being turned off immediately after printing is finished. The head-mounted fan works for couple of minutes more after that.
How to solve this? I think that this setting is very important and should override any slicer behavior.
I discovered one (possibly unrelated) thing in Orca's Core One profile "Machine end G-code" (notice the "M107" code):
{if layer_z < max_print_height}G1 Z{z_offset+min(max_layer_z+1, max_print_height)} F720 ; move print head up{endif}
G1 E-1 F2400 ; additional retraction
M104 S0 ; turn off temperature
M140 S0 ; turn off heatbed
M141 S0 ; disable chamber control
M107 ; turn off fan
G1 X242 Y-9 F10200 ; park
G4 ; wait
M572 S0 ; reset PA
M84 X Y E ; disable motors
; max_layer_z = [max_layer_z]
But I don't think that's it? Can this be a firmware fault? How this works for you guys?
RE: Advanced Filtering System misbehaving on Core One
I'm a little bit disappointed that no answer came - based on my other product ecosystems experiences I somehow expected that if community has no answer at least Prusa employees actively monitors these forums. IMHO it's not being needy, just expecting product support. I'm new in the Prusa ecosystem so maybe I'm doing this wrong: what would you suggest as a way to get the answer from Prusa?
Back to merits: to rephrase and organize my question:
1. Is it true that Orca can override the behavior I set for Adv Filtering System in the menu (keep Adv FS spinning for 10 minutes), and the M107 actually stops this Fan?
2. If so, what would be the proper end sequence on Core One with Adv Filtering system? Something like this?
M107 P0 ; turn off only print cooling fan (P0) G1 X242 Y-9 F10200 ; park G4 ; wait M572 S0 ; reset PA M84 X Y E ; disable motors G4 S600 ; wait 10 min (600 s) M106 P3 S255 ; keep AFS filtration fan on 100%
I have doubts regarding order of the last two steps, also I'm not sure that P0 and P3 are indeed the Fans I hope. Don't want to break anything, so I prefere not to test on PROD 🙂
And more general questions: anyone using Orca's Core One profile (available in 2.3.1 nigthly) and is 100% happy with it?
RE:
@dp-2, Prusa employees do not actively participate in these forums. Your best bet for quick response from them is to use the chat feature.
To your issue, I use Octoprint to control my Core One and serial printing interferes with some of the automated functionality (post print exhaust fan with Advance Filtration being one) so I use Octoprint to run the fan with the following G-code placed into their "after printing" custom G-code.
M106 P4 S200 ;Filter fan to 80%
G4 S300 ;wait 5 minutes
M106 P4 S0 ;Filter fan off
I have not tried inserting this code into the sliced G-code for a print but I see no reason it wouldn't succeed. The definitions for the various G-codes can be (mostly) found at this link Buddy firmware-specific G-code commands which also links to the generic Marlin G-codes.
The M106 command is a generic Fan on command which can be modified with the P parameter to specify the fan to control (default is 0). In the Core One it appears that there are 5 fans controlled by M106, I have not tested beyond P4 but I believe P0 is the hotend cooling fan, P1 is the part cooling fan, P2 and P3 are the enclosure fans and P4 is the Advanced Filtration Fan. The S parameter defines the desired speed from 0-255.
The G4 command with the S parameter allows a wait timer of Sxxx seconds
The M106 P4 S0 turns the fan off (I believe, but have not tested, that M107 P4 will do so as well). M107 is shown in the list without any parameters so I don't know for sure if can pass arguments but if it can I would assume the arguments are the same as M106.
I will note that it appears that executing this code from Octoprint after the print completes seems to interfere with the filament retraction at the end of the print. It seems that the printer firmware is performing this retraction and by the time the vent fan "script" runs the hotend has cooled below extrusion temperature and therefore the filament does not retract. This might be mitigated by putting these lines into the G-code file directly.
I hope this helps with your issue.
Regards,
Steve
RE:
Thank you so much @Steve for such a comprehensive answer!
(BTW Dear Moderator, I hope I'll get a non-moderation posting ability at this moment? 🙂 )
RE:
Hi DP,
There are limitations within this forum software... which are beyond my control...
you can start a Topic (new thread), in the main page for a subsection of the forum, 
but once you enter a thread, you can only 'Reply'
regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility.Location Halifax UK
RE:
I'm a little bit disappointed that no answer came - based on my other product ecosystems experiences I somehow expected that if community has no answer at least Prusa employees actively monitors these forums. IMHO it's not being needy, just expecting product support. I'm new in the Prusa ecosystem so maybe I'm doing this wrong: what would you suggest as a way to get the answer from Prusa?
Hi DP,
As mentioned above,
Prusa personnel rarely monitor this forum directly.
the most direct access to support is via CHAT,
If you have an idea or suggestion, then please go tot he Github page for the product, which is where the developers hang out.
P.S. I often answer posts, where I can, unfortunately Prusa is producing printers faster than My Pension can allow me to participate...
So far I have purchased
Mk1 printer
Mk1 to Mk2 Upgrade
MMU1 for Mk2,
A second Mk2,
Mk2.5 Upgrade
MMU2 upgrade
2 x Mk3 printer,
I had my name down for an XL, but my need for a larger format printer, crystallised before the XL became available, so I bought another suppliers Core XY printer,
I also had an SL1,
My SL1 has been upgraded to an SL1s
My MMU2 has been upgraded to MMU3 and I have a Prusa Enclosure... and
one of My Mk3's is now a Mk3.9
so XL and Core1 have unfortunately passed me by.
also the HT range of Delta printers are out of my range
I also had a Plastic framed 3d printer, (BAD experience)
and I have a 50% share, in a non prusa Delta printer which has helped someone else start 3D printing...
I live in a small bungalow, and this sort of limits my potential for buying new printers...
for my own sanity and because my need for 3d printing has changed, I have given away the plastic framed printer and donated one of the Mk2's to a worthy cause
regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility.Location Halifax UK
RE: Advanced Filtering System misbehaving on Core One
Thank you, all clear
RE: Advanced Filtering System misbehaving on Core One
Thank you for your answer. I did not mean to sound harsh/needy, got carried away due to uncertainty how things work. Getting there 🙂
RE: Advanced Filtering System misbehaving on Core One
I was new Once,
Been there got over excited... wanted answers fast...
Welcome to 3D Printing, (there is no known cure!)
regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility.Location Halifax UK
RE: Advanced Filtering System misbehaving on Core One
Just wanted to confirm if somebody finds this useful. This sequence Steven provided:
M106 P4 S200 ;Filter fan to 80%
G4 S300 ;wait 5 minutes
M106 P4 S0 ;Filter fan off
worked when added to Orca's machine-end section in Core One profile.