100% cooling fan on print start

[PHNX-666]

even though the part cooling fan is set in slicer to be off for the whole print it is at 100% as soon as the gcode is loaded... unsure how to fix this myself, tried double checking the printer.cfg for wrong pin allocation like it was maybe set as the hotend fan but they all tally up with the stock cfg file

[cptcl]

Same problem here... Started an ASA print 10 min ago and noticed 100% cooling and had to put it manualy to 0. The camber fan does the same btw (but chamber fan did this in stock too)

EDIT: Later... fan also hits 100% for overhang and bridges. its set to 10% for 100% overhang (&bridges) and 5% for 75% overhang and 0% for 50% and 25%.

[CChen616]

These may be related to different slicing software settings.

The macros executed at the start of printing and the Xindi control system do not handle the fan; everything is controlled by the slicing software. Different software may handle this differently.

If you are using the Max3 preset in the Qidi slicer, it may also not be fully compatible with the modified printer.cfg.

Cannot find the exact cause currently.

[PHNX-666]

Im using the most recent version of superslicer not qidi slicer... all fans are set to off for the first 6 layers and 35% for the rest of the print for pa6-gf.... its enabling the fan to 100% as soon as the gcode is loaded and having to manually turn it off , normal operation after manually setting to 0 on the display

[pmbroth]

Just wanted to know if this is still a bug?

[pmbroth]

I just received my new 32g emc, waiting to upgrade till this bug is fixed..

[PHNX-666]

Just wanted to know if this is still a bug?

yes

[CChen616]

I can confirm that these fans can all be controlled using the following command:

M106 P{index} S{speed 0 to 255}

For example, M106 P0 S255.

Please try to add these corresponding control codes to the start print macro of your slicing software.

[pmbroth]

@CChen616 If this works, will you be changing your image, or will this be something we need to do as part of the upgrade? This way, I can update the instruction pdf. Thank you again for your hard work.

[PHNX-666]

@CChen616 thanks for the work around...I will try reinstalling your firmware again... appreciate the effort and work put in to this

[CChen616]

@CChen616 If this works, will you be changing your image, or will this be something we need to do as part of the upgrade? This way, I can update the instruction pdf. Thank you again for your hard work.

This can only be configured in the slicing software and cannot be integrated into the image. If it proves effective, we can add related instructions.

[pmbroth]

I understand it is a configuration, but there has to be a bug somewhere to cause this behavior, as the current firmware does not cause this, unless it is compensated by a gcode startup command currently. Has anyone tested CChens' solution?

[PHNX-666]

Not yet, have everything done for the emmc and micro sd and slicer done but my printer decided to die yesterday, toolhead board blew mid print.... waiting on qidi getting back to me... let me know if you get yours running with the workaround as ive spoolman on other printers and it was nice to have all of them running it

[pmbroth]

@CChen616 - I have a quick question, just tp ensure I'm doing this correctly. I received a new 32gb EEMC direct from MKS - Shoudl I partion it for 8gbs, and leave the rest unallocated before applying the image using balenaEtcher?

[CChen616]

No need for that, I've already enabled armbian resize file system service in that image, it will automatically utilize the full space of the emmc once you flash it.

[pmbroth]

@CChen616 The emmc comes blank, so I just installed linux to format it, as my iwndows 11 does not recignize it, so I should just format for 32gb? correct?

[CChen616]

Windows may require specific drivers to recognize the eMMC reader. Or check if the connection between reader and adapter is solid.

If you are running a virtual machine on your pc at the same time, make sure you are mounting the reader on your localhost (I was confused by this once)

In most cases, Windows will recognize a connected eMMC module, even if it is blank. It may appear as an unallocated disk.

[pmbroth]

The emmc is plugged in and Windows 11 does not see it, I'm using the makerbase board and emmc..

[PHNX-666]

The sd card reader I received with my 32gb didnt work at all, i had to use another i had laying around...

On Mon, 24 Jun 2024 at 15:59, pmbroth @.***> wrote:

The emmc is plugged in and Windows 11 does not see it, I'm using the makerbase board and emmc..

— Reply to this email directly, view it on GitHub https://github.com/CChen616/QIDI_Max3_Bookworm/issues/4#issuecomment-2186784716, or unsubscribe https://github.com/notifications/unsubscribe-auth/BD2IHTQ6TW2343IRTMAZ4FDZJAX3XAVCNFSM6AAAAABJJAW52CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCOBWG44DINZRGY . You are receiving this because you authored the thread.Message ID: @.***>

[pmbroth]

got it workihng, used another reader I had.. :-) I guess porr QA.. Thank you I'm just loaidng thge image onto the EMMC, and did nto have to format it...

[pmbroth]

@CChen616 I have the inductive probe, should I just copy the printer.cfg down from the printer, and then copy it backup after the upgrade - this way I have the printer.cfg which I'm using now?

[CChen616]

The printer.cfg file has undergone some adjustments in the new image. The gcode_macro related sections have been separated into a gcode_macro.cfg file, and the fan and heater sections have been rewritten.

It is recommended to use a text editor to compare the changes, and modify the new printer.cfg on the parts you want to retain. The new printer.cfg is based on an inductive sensor.

[pmbroth]

@CChen616 I made the adjustmenst as needed in the printer config file. The cooling fan comes on 100% at layert 1, i'm going to try your fix in th enext test print

[pmbroth]

I added M106 P0 S0 to start g-code, and once the skirt completed the cooling fan went up to 100

[pmbroth]

I updated the GUI flash today, rebooted, and fans are workring perrfectly as I want for Qidi Slicer and Orca Slicer..

[cptcl]

I updated the GUI flash today, rebooted, and fans are workring perrfectly as I want for Qidi Slicer and Orca Slicer..

What exactly did u flash? Cause I had trouble with the update (and I didn't gain that much of a value) that I reverted back to stock.

[pmbroth]

I updated QD_Max3_UI5.0 , and fans are all working normally. I do not have to manually turn them off at layer 1. After this update, all seems normal..