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

    Error: M106: Fan number 3 not found

    Scheduled Pinned Locked Moved Solved
    Duet Hardware and wiring
    3
    6
    740
    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.
    • lildannyosoundefined
      lildannyoso
      last edited by

      I am getting an Error : M106: Fan number 3 not found and the part cooling fans are not turning on. Below is the GCode for the fans, and I am not sure why the error is referencing fan 3 instead of fan1.

      ; Fans
      M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off

      Any help would be appreciated.

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

        Please post your full config.g
        The output of M122 would be useful as well.

        Z-Bot CoreXY Build | Thingiverse Profile

        lildannyosoundefined 2 Replies Last reply Reply Quote 0
        • deckingmanundefined
          deckingman @lildannyoso
          last edited by

          @lildannyoso In addition to what @Phaedrux has said, if you have not configured a fan 3, then you need to look at what might be calling for fan 3. When do you get the error? If it's when printing, then the problem might be in the gcode file. If it's when homing, then the problem will be in the homing files. If it's when running other macro's, that's the place to look.

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

          lildannyosoundefined 1 Reply Last reply Reply Quote 0
          • lildannyosoundefined
            lildannyoso @Phaedrux
            last edited by

            @phaedrux
            Here is the complete config file

            ; Configuration file for Duet WiFi (firmware version 3)
            ; executed by the firmware on start-up
            ;
            ; generated by RepRapFirmware Configuration Tool v3.1.4 on Mon Jul 20 2020 19:57:06 GMT-0500 (Central Daylight Time)

            ; General preferences
            G90 ; send absolute coordinates...
            M83 ; ...but relative extruder moves
            M550 P"Anycubic Predator" ; set printer name
            M665 R227 L440.45 B185 H410 ; Set delta radius, diagonal rod length, printable radius and homed height
            M666 X0 Y0 Z0 ; put your endstop adjustments here, or let auto calibration find them

            ; Network
            M552 P192.168.86.37 S1 ; enable network and acquire dynamic address via DHCP
            M586 P0 S1 ; enable HTTP
            M586 P1 S0 ; disable FTP
            M586 P2 S0 ; disable Telnet

            ; Drives
            M569 P0 S0 ; physical drive 0 goes forwards
            M569 P1 S0 ; physical drive 1 goes forwards
            M569 P2 S0 ; physical drive 2 goes forwards
            M569 P3 S0 ; physical drive 3 goes forwards
            M584 X0 Y1 Z2 E3 ; set drive mapping
            M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
            M92 X80.00 Y80.00 Z80.00 E415.00 ; set steps per mm
            M566 X1500.00 Y1500.00 Z1500.00 E1500.00 P1 ; set maximum instantaneous speed changes (mm/min)
            M203 X18000.00 Y18000.00 Z18000.00 E10000.00 ; set maximum speeds (mm/min)
            M201 X1500.00 Y1500.00 Z1500.00 E5000.00 ; set accelerations (mm/s^2)
            M906 X1000 Y1000 Z1000 E1000 I30 ; set motor currents (mA) and motor idle factor in per cent
            M84 S30 ; Set idle timeout

            ; Retraction
            M207 S1.9 F3000 Z0.388 ; Firmware retraction

            ; Axis Limits
            M208 Z0 S1 ; set minimum Z

            ; Endstops
            M574 X2 S1 P"xstop" ; configure active-high endstop for high end on X via pin xstop
            M574 Y2 S1 P"ystop" ; configure active-high endstop for high end on Y via pin ystop
            M574 Z2 S1 P"zstop" ; configure active-high endstop for high end on Z via pin zstop
            M591 D0 P7 C"e0stop" L7 R50:200 E15 S0 ; filament sensor connected to e0_stop

            ; Z-Probe
            M558 P8 R0.4 C"zprobe.in+zprobe.mod" H10 F1200 T6000 ; set Z probe type to effector and the dive height + speeds
            G31 P100 X0 Y0 Z.1 ; set Z probe trigger value, offset and trigger height
            M557 R180 S20 ; define mesh grid

            ; Heaters
            M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 ; configure sensor 0 as thermistor on pin bedtemp
            M950 H0 C"bedheat" T0 ; create bed heater output on bedheat and map it to sensor 0
            M307 H0 A137.8 C533.3 D1.5 V24.3 B0 ; disable bang-bang mode for the bed heater and set PWM limit
            M140 H0 ; map heated bed to heater 0
            M143 H0 S120 ; set temperature limit for heater 0 to 120C
            M308 S1 P"e0temp" Y"pt1000" R4700 ; configure sensor 1 as PT1000 on pin e0temp
            M950 H1 C"e0heat" T1 ; create nozzle heater output on e0heat and map it to sensor 1
            M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit

            ; Fans
            M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
            M106 P1 S0 H-1 ; set fan 1 value. Thermostatic control is turned off

            ; Tools
            M563 P0 S"Hotend" D0 H1 F1 ; 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

            ; Custom settings are not defined
            M572 D0 S0.2 ; pressure advance

            ; Miscellaneous
            M911 S10 R11 P"M913 X0 Y0 G91 M83 G1 Z3 E-5 F1000" ; set voltage thresholds and actions to run on power loss
            M501 ; set the active parameters to those stored in sys/config-override.g

            1 Reply Last reply Reply Quote 0
            • lildannyosoundefined
              lildannyoso @deckingman
              last edited by lildannyoso

              @deckingman I am getting the error while printing. I checked the machine settings in my slicer and it seems to be the issue. The cooling fan number was set to 3. I have set it to 1 and will test it.

              EDIT: Cooling fan number set to 1 in Cura and it now works as intended.

              1 Reply Last reply Reply Quote 1
              • lildannyosoundefined
                lildannyoso @Phaedrux
                last edited by

                @phaedrux Here is the output of M122:
                === Diagnostics ===
                RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet Ethernet 1.02 or later
                Board ID: 08DLM-996RU-N8PS4-7JKD6-3S46T-TUB7N
                Used output buffers: 1 of 24 (13 max)
                === RTOS ===
                Static ram: 27980
                Dynamic ram: 92832 of which 20 recycled
                Exception stack ram used: 472
                Never used ram: 9768
                Tasks: NETWORK(ready,636) HEAT(blocked,1224) MAIN(running,1880) IDLE(ready,80)
                Owned mutexes:
                === Platform ===
                Last reset 00:10:09 ago, cause: power up
                Last software reset time unknown, reason: User, spinning module GCodes, available RAM 9752 bytes (slot 0)
                Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
                Error status: 0
                MCU temperature: min 23.4, current 33.3, max 33.8
                Supply voltage: min 23.8, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
                Driver 0: standstill, SG min/max not available
                Driver 1: standstill, SG min/max not available
                Driver 2: standstill, SG min/max not available
                Driver 3: standstill, SG min/max not available
                Driver 4: standstill, SG min/max not available
                Date/time: 2022-01-14 17:02:33
                Cache data hit count 1164865633
                Slowest loop: 24.20ms; fastest: 0.12ms
                I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
                === Storage ===
                Free file entries: 9
                SD card 0 detected, interface speed: 20.0MBytes/sec
                SD card longest read time 4.6ms, write time 43.6ms, max retries 0
                === Move ===
                Hiccups: 0(0), FreeDm: 169, MinFreeDm: 166, MaxWait: 257672ms
                Bed compensation in use: none, comp offset 0.000
                === MainDDARing ===
                Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                === AuxDDARing ===
                Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
                === Heat ===
                Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
                Heater 0 is on, I-accum = 0.3
                Heater 1 is on, I-accum = 0.0
                === GCodes ===
                Segments left: 0
                Movement lock held by null
                HTTP is idle in state(s) 0
                Telnet is idle in state(s) 0
                File is doing "M190 S65" 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
                Daemon is idle in state(s) 0
                Autopause is idle in state(s) 0
                Code queue is empty.
                === Network ===
                Slowest loop: 44.25ms; fastest: 0.02ms
                Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
                HTTP sessions: 1 of 8
                Interface state active, link 100Mbps full duplex
                === Filament sensors ===
                Extruder 0 sensor: no data received

                1 Reply Last reply Reply Quote 0
                • Phaedruxundefined Phaedrux marked this topic as a question
                • Phaedruxundefined Phaedrux has marked this topic as solved
                • First post
                  Last post
                Unless otherwise noted, all forum content is licensed under CC-BY-SA