Duet3D Logo Duet3D
    • Tags
    • Documentation
    • Order
    • Register
    • Login

    Layer fan kicking on randomly

    Scheduled Pinned Locked Moved
    Using Duet Controllers
    3
    8
    342
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • mherundefined
      mher
      last edited by Phaedrux

      Hi Guys,

      I'm just starting off with setting up my first machine with a duet board and I'm trying to get my fans up and running correctly now.
      I've build a vcore-3 500 version in case anyone was wondering.

      Now I've wired up everything and added a toolboard to make wiring a lot cleaner at the toolhead.
      My config is as follows config.g

      What happens is that the layer fan starts up randomly and whenever I adjust the slider to 0 on the interface it runs back up to 100 automatically.
      I'm running in SBC mode

      Here a quick view of what happens exactly

      deckingmanundefined 1 Reply Last reply Reply Quote 0
      • Phaedruxundefined
        Phaedrux Moderator
        last edited by

        Can you copy and paste your config.g into a post? I can't seem to download it.

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • Phaedruxundefined
          Phaedrux Moderator
          last edited by

          Nevermind. It seems like your animated GIF was causing some problems on the page.

          ; General preferences
          M575 P1 S1 B57600                       ; enable support for PanelDue
          G90                                     ; send absolute coordinates...
          M83                                     ; ...but relative extruder moves
          M550 P"vcore3"                        	; set printer name
          M669 K1                                 ; CoreXY
          G29 S1                                  ; Set Units to Millimeters
          G4 S2									; Wait for the toolboard to come online
          
          ; Drives
          M569 P0.0 S1 D3                         ; physical drive Z1 goes forwards
          M569 P0.1 S1 D3                         ; physical drive Z2 goes forwards
          M569 P0.2 S1 D3                         ; physical drive Z3 goes forwards
          M569 P121.0 S1 D3                       ; physical drive Extruder goes forwards
          M569 P0.3 S0 D3                         ; physical drive X goes forwards
          M569 P0.4 S0 D3                         ; physical drive Y goes forwards
          M584 X0.3 Y0.4 Z0.1:0.0:0.2 E0.5        ; set drive mapping
          M350 X16 Y16 Z16 E16 I1                 ; configure microstepping with interpolation
          
          M92 X80.00 Y80.00 Z800.00               ; set steps per mm
          M906 X1000 Y1000 Z800 I30               ; set motor currents (mA) and motor idle factor in per cent
          M84 S30                                 ; Set idle timeout
          
          M566 X400.00 Y400.00 Z6.00 E120.00 P1          ; set maximum instantaneous speed changes (mm/min)
          M203 X10800.00 Y10800.00 Z1000.00 E3600.00     ; set maximum speeds (mm/min)
          M201 X3000.00 Y3000.00 Z100.00 E3600.00        ; set accelerations (mm/s^2)
          
          ; Axis Limits
          M208 X0 Y0 Z0 S1                               ; set axis minima
          M208 X510 Y500 Z500 S0                         ; set axis maxima
          
          ; Endstops
          M574 Y2 S1 P"io1.in"                           	; configure active y endstop
          M574 X1 S1 P"121.io1.in"						; configure active x endstop
          
          M671 X-4.5:250:504.5 Y-4.52:505:-4.52 S15      ; define positions of Z leadscrews or bed levelling screws
          M557 X20:280 Y20:280 P5                        ; define 5x5 mesh grid
          
          ; Heaters
          M308 S0 P"temp0" Y"thermistor" T100000 B3950 A"Bed"    ; configure sensor 0 as thermistor on pin temp0
          M950 H0 C"out0" T0 Q10                                 ; create bed heater output on out0 and map it to sensor 0
          M307 H0 B0 S1.00                                       ; disable bang-bang mode for the bed heater and set PWM limit
          M140 H0                                                ; map heated bed to heater 0
          M143 H0 S110                                           ; set temperature limit for heater 0 to 110C
          
          M308 S1 P"121.temp0" Y"thermistor" T100000 A"Hotend"   ; configure sensor 1 as thermistor on pin 121.temp0
          M950 H1 C"121.out0" T1         						   ; create nozzle heater output on out2 and map it to sensor 1
          M307 H1 B0 S1.00           							   ; disable bang-bang mode for heater and set PWM limit
          M143 H1 S300              							   ; set the maximum temperature in C for heater
          
          M307 H0 R0.479 K0.250:0.000 D3.55 E1.35 S1.00 B0	   ; Bed PID Tuning
          M307 H1 R2.124 K0.496:0.000 D4.92 E1.35 S1.00 B0 V24 ; Heater PID Tuning
          
          ; Fans
          M950 F0 C"121.out1" Q150                              ; create fan 0 on pin 121.out1 and set its frequency
          M106 P0 S0 H-1 C"Layer Fan"                           ; set fan 0 value. Thermostatic control is turned off
          M950 F1 C"121.out2" Q150                              ; create fan 1 on pin 121.out2 and set its frequency
          M106 P1 S1 H1 T45 C"Heater Fan"                       ; set fan 1 value. Thermostatic control is turned on
          
          ; Tools
          M563 P0 S"MosquitoM" D0 H1 F0           ; define tool 0
          G10 P0 X0 Y0 Z0            				; set tool 0 axis offsets
          G10 P0 R0 S0               				; set initial tool 0 active and standby temperatures to 0C
          
          ;; Run Heater PID Tune!! 
          ;; M307 H1 A751.5 C196.6 D4.7 S1.00 V23.9 B0
          
          ; Z-Probe
          ;; BLTouch
          M950 S0 C"121.io0.out"                     ; Create a servo pin on io0
          M558 P9 C"121.io0.in" H5 F240 T10800 A5    ; set Z probe type to unmodulated and the dive height + speeds
          G31 P25 X-28.00 Y-13.00 Z0.90          ; set Z probe trigger value, offset and trigger height, more Z means closer to the bed
          
          T0
          
          ; Pressure Advance
          ; M572 D0 S0.10
          

          The config looks ok. (Except this command and comment doesn't match: G29 S1 ; Set Units to Millimeters)

          Can you please send M122 and M98 P"config.g" in the gcode console and copy paste the results here?

          The only time I see the layer fan slider behave that way is during a print if the sliced gcode file is constantly changing the fan speed, but your gif didn't look like it was during a print.

          Z-Bot CoreXY Build | Thingiverse Profile

          mherundefined 1 Reply Last reply Reply Quote 0
          • deckingmanundefined
            deckingman @mher
            last edited by

            @mher Search your gcode file for any instances of M106.

            Ian
            https://somei3deas.wordpress.com/
            https://www.youtube.com/@deckingman

            1 Reply Last reply Reply Quote 0
            • mherundefined
              mher @Phaedrux
              last edited by

              @phaedrux said in Layer fan kicking on randomly:

              Can you please send M122 and M98 P"config.g" in the gcode console and copy paste the results here?

              This is indeed happening without running a print. Sometimes it will just stay of for a while and then it'll start running on it's own out of nowhere.

              M122
              === Diagnostics ===
              RepRapFirmware for Duet 3 MB6HC version 3.4.0 (2022-03-15 18:57:24) running on Duet 3 MB6HC v1.01 or later (SBC mode)
              Board ID: 08DJM-956BA-NA3TJ-6J1DJ-3S86P-1T9UT
              Used output buffers: 1 of 40 (12 max)
              === RTOS ===
              Static ram: 151000
              Dynamic ram: 65620 of which 572 recycled
              Never used RAM 133480, free system stack 200 words
              Tasks: SBC(ready,0.5%,487) HEAT(notifyWait,0.0%,327) Move(notifyWait,0.0%,352) CanReceiv(notifyWait,0.0%,797) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.8%,92) MAIN(running,91.6%,923) IDLE(ready,0.0%,30), total 100.0%
              Owned mutexes: HTTP(MAIN)
              === Platform ===
              Last reset 00:01:09 ago, cause: software
              Last software reset at 2022-05-09 09:53, reason: User, GCodes spinning, available RAM 133480, slot 1
              Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x00400000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
              Error status: 0x00
              Aux0 errors 0,0,0
              Step timer max interval 135
              MCU temperature: min 30.3, current 30.9, max 30.9
              Supply voltage: min 24.0, current 24.0, max 24.0, under voltage events: 0, over voltage events: 0, power good: yes
              12V rail voltage: min 12.1, current 12.1, max 12.2, under voltage events: 0
              Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
              Events: 0 queued, 0 completed
              Driver 0: standstill, SG min n/a, mspos 8, reads 11166, writes 0 timeouts 0
              Driver 1: standstill, SG min n/a, mspos 8, reads 11166, writes 0 timeouts 0
              Driver 2: standstill, SG min n/a, mspos 8, reads 11166, writes 0 timeouts 0
              Driver 3: standstill, SG min n/a, mspos 8, reads 11166, writes 0 timeouts 0
              Driver 4: standstill, SG min n/a, mspos 8, reads 11166, writes 0 timeouts 0
              Driver 5: standstill, SG min n/a, mspos 8, reads 11167, writes 0 timeouts 0
              Date/time: 2022-05-09 09:54:15
              Slowest loop: 2.16ms; fastest: 0.05ms
              === Storage ===
              Free file entries: 10
              SD card 0 not detected, interface speed: 37.5MBytes/sec
              SD card longest read time 0.0ms, write time 0.0ms, max retries 0
              === Move ===
              DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
              === MainDDARing ===
              Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
              === AuxDDARing ===
              Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
              === Heat ===
              Bed heaters 0 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
              === GCodes ===
              Segments left: 0
              Movement lock held by null
              HTTP* is doing "M122" in state(s) 0
              Telnet is idle in state(s) 0
              File is idle in state(s) 0
              USB is idle in state(s) 0
              Aux is idle in state(s) 0
              Trigger* is idle in state(s) 0
              Queue is idle in state(s) 0
              LCD is idle in state(s) 0
              SBC is idle in state(s) 0
              Daemon is idle in state(s) 0
              Aux2 is idle in state(s) 0
              Autopause is idle in state(s) 0
              Code queue is empty
              === CAN ===
              Messages queued 231, received 507, lost 0, boc 0
              Longest wait 2ms for reply type 6013, peak Tx sync delay 4, free buffers 50 (min 49), ts 127/127/0
              Tx timeouts 0,0,0,0,0,0
              === SBC interface ===
              Transfer state: 4, failed transfers: 0, checksum errors: 0
              RX/TX seq numbers: 3865/3865
              SPI underruns 0, overruns 0
              State: 5, disconnects: 0, timeouts: 0, IAP RAM available 0x2b880
              Buffer RX/TX: 0/0-0, open files: 0
              === Duet Control Server ===
              Duet Control Server v3.4.0
              Code buffer space: 4096
              Configured SPI speed: 8000000Hz, TfrRdy pin glitches: 0
              Full transfers per second: 39.40, max time between full transfers: 37.3ms, max pin wait times: 28.5ms/3.6ms
              Codes per second: 0.12
              Maximum length of RX/TX data transfers: 3104/844
              

              Running M98 P"config.g" gives no result it just shows up marked green in the console indicating that it was executed successfully.

              1 Reply Last reply Reply Quote 0
              • Phaedruxundefined
                Phaedrux Moderator
                last edited by

                When it's running and when it's off, send M106 P0 and see what it reports.

                Can you check in your DWC settings that the version installed is also 3.4?

                Can you send M122 B121 to get a diagnostics report from the toolboard since that's where the fan is connected?

                Z-Bot CoreXY Build | Thingiverse Profile

                mherundefined 1 Reply Last reply Reply Quote 0
                • mherundefined
                  mher @Phaedrux
                  last edited by

                  @phaedrux
                  When it's off:
                  Fan 0 (Layer Fan), speed 0%, min: 10%, max: 100%, blip: 0.10

                  Shouldn't the min be 0%? Could this be part of the problem?

                  DWC is 3.4.0

                  M122 B121
                  Diagnostics for board 121:
                  Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.0 (2022-03-15 09:00:04)
                  Bootloader ID: not available
                  All averaging filters OK
                  Never used RAM 3576, free system stack 88 words
                  Tasks: Move(notifyWait,0.0%,153) HEAT(notifyWait,0.4%,111) CanAsync(notifyWait,0.0%,65) CanRecv(notifyWait,0.0%,76) CanClock(notifyWait,0.0%,65) TMC(delaying,3.0%,57) MAIN(running,91.7%,351) IDLE(ready,0.0%,40) AIN(delaying,4.9%,142), total 100.0%
                  Last reset 00:03:04 ago, cause: power up
                  Last software reset data not available
                  Driver 0: pos 0, 80.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 10, reads 26570, writes 10, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
                  Moves scheduled 0, completed 0, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
                  Peak sync jitter 0/4, peak Rx sync delay 601, resyncs 0/0, no step interrupt scheduled
                  VIN voltage: min 24.3, current 24.4, max 24.4
                  MCU temperature: min 22.6C, current 33.0C, max 33.0C
                  Last sensors broadcast 0x00000002 found 1 16 ticks ago, 0 ordering errs, loop time 1
                  CAN messages queued 3462, send timeouts 0, received 1594, lost 0, free buffers 37, min 37, error reg 0
                  dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
                  Accelerometer: none
                  I2C bus errors 4619, naks 4619, other errors 4619
                  
                  1 Reply Last reply Reply Quote 0
                  • Phaedruxundefined
                    Phaedrux Moderator
                    last edited by

                    Not sure about that 10%

                    Try sending M106 P0 L0 and then check if it's still 10% min.

                    I also notice that you have the PWM freq at Q150. Can you try returning that to the default 500?

                    Does the hotend heatsink fan behave correctly?

                    Z-Bot CoreXY Build | Thingiverse Profile

                    1 Reply Last reply Reply Quote 0
                    • First post
                      Last post
                    Unless otherwise noted, all forum content is licensed under CC-BY-SA