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

    Sanity check on Fan setup for laser

    Scheduled Pinned Locked Moved
    Laser Cutters
    2
    3
    214
    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.
    • GeorgeMundefined
      GeorgeM
      last edited by Phaedrux

      For the last two days I have been fighting getting my laser to work with my Duet2 WiFi.
      Now I am wondering if I have a bigger problem with my fans.
      I just converted from 2.0.5 to 3.1.1. I thought things went well overall - even printed a couple of items. But then looking at it more critically I find that the Fan1 (extruder heat sink fan) is on all the time rather than when temp reaching 45 as it should. Fan 0 (parts fan) is not coming on at all even though the slicer calls for it to come on at layer 3 and increase to higher rpm at layer 6. And of course my laser connected to Fan2 does not adjust via laser commands (M3 Sxxx) or turn on or off (M3 S0 or M5). I could really use some help in diagnosing this. I haven't used my printer for about 6 months so I'm really re learning a lot of this. Anyway here are some of the info:

      Power supply 24 volts
      Duet 2 WiFi 1.02
      Firmware 3.1.1

      Here is the config file
      ; Configuration file for Duet WiFi (firmware version 3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.1.3 on Mon Jun 15 2020 11:14:50 GMT-0600 (Mountain Daylight Time)

      ; General preferences
      G90 ; send absolute coordinates...
      M83 ; ...but relative extruder moves
      M550 P"My Printer" ; set printer name
      M669 K1 ; select CoreXY mode

      ; Network
      M552 S1 ; enable network
      M586 P0 S1 ; enable HTTP
      M586 P1 S0 ; disable FTP
      M586 P2 S0 ; disable Telnet

      ; Drives
      M569 P0 S0 ; physical drive 0 goes backwords
      M569 P1 S0 ; physical drive 1 goes backwards
      M569 P2 S0 ; physical drive 2 goes backwards
      M569 P3 S1 ; physical drive 3 goes forwards
      M569 P4 S0 ; physical drive 4 goes backward
      M584 X0 Y1 Z2:4 E3 ;two Z Motors connected to driver outputs A and E1
      M671 X-20:310 Y0:0 S2 ;Leadscrew at left (connected to Z) and right connected to E1) of X axis
      M350 X16 Y16 Z16 E16 U16 I1 ; configure microstepping with interpolation
      M92 X101.84 Y104.96 Z402.42 U402.42 E2892.00 ; set steps per mm
      M566 X500.00 Y500.00 Z100.00 U100.00 E60.00 ; set maximum instantaneous speed changes (mm/min)
      M203 X10000.00 Y10000.00 Z6000.00 U6000.00 E8000.00 ; set maximum speeds (mm/min)
      M201 X800.00 Y800.00 Z30.00 U30.00 E120.00 ; set accelerations (mm/s^2)
      M906 X1200.00 Y1200.00 Z800.00 U800.00 E500.00 I30 ; set motor currents (mA) and motor idle factor in per cent
      M84 S30 ; Set idle timeout

      ; Axis Limits
      M208 X-25 Y-15 Z0 S1 ; set axis minima
      M208 X330 Y340 Z300 S0 ; set axis maxima

      ; Endstops
      M574 X1 S1 P"xstop" ; configure active-high endstop for low end on X via pin xstop
      M574 Y1 S1 P"ystop" ; configure active-high endstop for low end on Y via pin ystop
      M574 Z1 S2 ; configure Z-probe endstop for low end on Z

      ; Z-Probe
      M950 S0 C"exp.heater3" ; create servo pin 0 for BLTouch
      M558 P9 C"^zprobe.in" H3 F120 T4800 ; set Z probe type to bltouch and the dive height + speeds
      G31 P25 X30 Y-10 Z.48 ; set Z probe trigger value, offset and trigger height
      M557 X15:285 Y15:275 P5:5 ; define mesh grid ; define mesh grid
      M376 H10

      ; Heaters
      M308 S0 P"bedtemp" Y"thermistor" T100000 B4138 R4700 ; 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 B1 S1.00 ; enable 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"thermistor" T100000 B4725 C7.06e-8 ; configure sensor 1 as thermistor 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 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
      M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
      M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
      M950 F2 C"!fan2" Q1000 ; create fan 2 on pin fan1 and set its frequency
      M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off

      ; Tools
      M563 P0 S"E3D_V6" 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

      ; Custom settings are not defined
      M501 ; Load saved parameters from non-volatile memory

      Here is a pic of my fan jumpers:
      20200617_101201.jpg

      Thanks for looking
      George

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

        The config looks ok for what you describe.

        Are you able to control the part cooling fan with the slider in DWC?

        Do you have any additional fan commands elsewhere that might be overriding what you have in config.g?

        Send M106 P# to get a read back of the current configuration for each fan.

        Can you also send M122 and report back.

        And send M98 Pconfig.g and report back with any error messages.

        Z-Bot CoreXY Build | Thingiverse Profile

        1 Reply Last reply Reply Quote 0
        • GeorgeMundefined
          GeorgeM
          last edited by

          @Phaedrux said in Sanity check on Fan setup:

          M98 Pconfig.g

          Thank you for replying.
          First off I redid some of the wiring for the fans. Instead of using VIN power I am now supplying the power from a buck to reduce the 24v to 12v via the middle pin on the V Fan Jumper. I also found a loose connection on the Fan0.
          So after that Fan0 and Fan1 are working as they are supposed to. However I am back at not getting Fan2 to control the laser. Even when I hook up a simple fan it does not work. Moving the slider on the Dashboard produces nothing. And when I send m106 commands the slider moves but the fan does not. (By the way I checked with two different fans, both know to be working).

          M98 produces nothing
          Here are the m106 status

          6/17/2020, 5:41:58 PM m106 p0
          Fan 0, speed: 0%, min: 10%, max: 100%, blip: 0.10
          6/17/2020, 5:41:54 PM m106 p1
          Fan 1, speed: 100%, min: 10%, max: 100%, blip: 0.10, temperature: 45.0:45.0C, sensors: 1, current speed: 0%:
          6/17/2020, 5:41:50 PM m106 p2
          Fan 2, speed: 0%, min: 10%, max: 100%, blip: 0.10

          And here is the fan part of my config.g
          ; Fans
          M950 F0 C"fan0" Q500 ; create fan 0 on pin fan0 and set its frequency
          M106 P0 S0 H-1 ; set fan 0 value. Thermostatic control is turned off
          M950 F1 C"fan1" Q500 ; create fan 1 on pin fan1 and set its frequency
          M106 P1 S1 H1 T45 ; set fan 1 value. Thermostatic control is turned on
          M950 F2 C"!fan2" Q1000 ; create fan 2 on pin fan1 and set its frequency
          M106 P2 S0 H-1 ; set fan 2 value. Thermostatic control is turned off

          Lastly here is the M122:

          6/17/2020, 5:36:13 PM === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.1.1 running on Duet WiFi 1.02 or later
          Board ID: 08DGM-9T6BU-FG3SJ-6JKD4-3S46L-TUW7D
          Used output buffers: 3 of 24 (20 max)
          === RTOS ===
          Static ram: 27980
          Dynamic ram: 93984 of which 60 recycled
          Exception stack ram used: 264
          Never used ram: 8784
          Tasks: NETWORK(ready,368) HEAT(blocked,1216) MAIN(running,1816) IDLE(ready,80)
          Owned mutexes: WiFi(NETWORK)
          === Platform ===
          Last reset 00:00:41 ago, cause: power up
          Last software reset at 2020-06-17 10:03, reason: User, spinning module GCodes, available RAM 8784 bytes (slot 2)
          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task MAIN
          Error status: 0
          MCU temperature: min 31.8, current 36.0, max 36.0
          Supply voltage: min 23.7, current 23.8, max 24.0, 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: 2020-06-17 17:35:47
          Cache data hit count 66412690
          Slowest loop: 7.78ms; fastest: 0.14ms
          I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
          === Storage ===
          Free file entries: 10
          SD card 0 detected, interface speed: 20.0MBytes/sec
          SD card longest read time 16.4ms, write time 0.0ms, max retries 0
          === Move ===
          Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
          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
          === 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 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
          Daemon is idle in state(s) 0
          Autopause is idle in state(s) 0
          Code queue is empty.
          === Network ===
          Slowest loop: 23.25ms; fastest: 0.00ms
          Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
          HTTP sessions: 2 of 8

          • WiFi -
            Network state is active
            WiFi module is connected to access point
            Failed messages: pending 0, notready 0, noresp 0
            WiFi firmware version 1.23
            WiFi MAC address cc:50:e3:6a:85:90
            WiFi Vcc 3.35, reset reason Unknown
            WiFi flash size 4194304, free heap 24448
            WiFi IP address 192.168.1.73
            WiFi signal strength -67dBm, reconnections 0, sleep mode modem
            Socket states: 4 0 0 0 0 0 0 0

          I don't see where I am off.

          George

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