Issues driving Fans Duex5 Board



  • Recently procured a Duet2Wifi and DUEX5 board for my e3D tool-changing reference implementation. When going through the checks to start commissioning my system I noted that the fans wired to the DUEX5 board would not turn on. Trying to address them with the M106 command did not cause them to engauge. On start up one of the aforementioned fans would attempt to spin up and then stop moving, after which calls to it would not be hindered. To verify the wiring harness I swapped those fans into the always on pins on the DUET2Wifi. I can confirm that when plugged into the alway on pins those fans do in fact spin.

    As I am rather new to Duet boards and my last printer controller board was an Azteeg-X3, I recognize that this could be due to my unfamiliarity with the hardware.

    https://imgur.com/bYgXM3m - Image of wiring on the toolchanger

    In Config.g the following lines of code are used for the Fans

    ; Fans
    M106 P0 S0 ; UNUSED
    M106 P1 S255 H1 T70 ; T0 HE
    M106 P2 S0 ; T0 PCF
    M106 P3 S255 H2 T70 ; T1 HE
    M106 P4 S0 ; T1 PCF
    M106 P5 S255 H3 T70 ; T2 HE
    M106 P6 S0 ; T2 PCF
    M106 P7 S255 H4 T70 ; T3 HE
    M106 P8 S0 ; T3 PCF

    If you have any advice for what I should try to get this addressed or can verify that I have exhausted my options I would greatly appreciate it.


  • administrators

    Please send M122 and post the result.



  • @T3P3Tony

    M122
    === Diagnostics ===
    RepRapFirmware for Duet 2 WiFi/Ethernet version 2.02(RTOS) running on Duet WiFi 1.02 or later + DueX5
    Board ID: 08DGM-917DA-G4MSD-6J9DD-3S86M-18UBA
    Used output buffers: 3 of 20 (11 max)
    === RTOS ===
    Static ram: 25524
    Dynamic ram: 99580 of which 0 recycled
    Exception stack ram used: 328
    Never used ram: 5640
    Tasks: NETWORK(ready,544) HEAT(blocked,1232) MAIN(running,3812) IDLE(ready,200)
    Owned mutexes:
    === Platform ===
    Last reset 00:00:49 ago, cause: power up
    Last software reset at 2019-10-23 22:50, reason: User, spinning module GCodes, available RAM 5384 bytes (slot 0)
    Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
    Error status: 0
    Free file entries: 10
    SD card 0 detected, interface speed: 20.0MBytes/sec
    SD card longest block write time: 0.0ms, max retries 0
    MCU temperature: min 28.9, current 32.9, max 33.2
    Supply voltage: min 24.3, current 24.4, max 24.5, 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
    Driver 5: standstill, SG min/max not available
    Driver 6: standstill, SG min/max not available
    Driver 7: standstill, SG min/max not available
    Driver 8: standstill, SG min/max not available
    Driver 9: standstill, SG min/max not available
    Date/time: 2019-10-31 17:53:21
    Cache data hit count 167679944
    Slowest loop: 6.96ms; fastest: 0.07ms
    I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0
    === Move ===
    Hiccups: 0, StepErrors: 0, LaErrors: 0, FreeDm: 240, MinFreeDm: 240, MaxWait: 0ms, Underruns: 0, 0
    Scheduled moves: 0, completed moves: 0
    Bed compensation in use: none
    Bed probe heights: 0.000 0.000 0.000 0.000 0.000
    === Heat ===
    Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1
    === GCodes ===
    Segments left: 0
    Stack records: 1 allocated, 0 in use
    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
    serial is idle in state(s) 0
    aux is idle in state(s) 0
    daemon is idle in state(s) 0
    queue is idle in state(s) 0
    autopause is idle in state(s) 0
    Code queue is empty.
    === Network ===
    Slowest loop: 22.89ms; fastest: 0.00ms
    Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
    HTTP sessions: 1 of 8

    WiFi -
    Network state is running
    WiFi module is connected to access point
    Failed messages: pending 0, notready 0, noresp 0
    WiFi firmware version 1.22
    WiFi MAC address ec:fa:bc:25:33:4a
    WiFi Vcc 3.35, reset reason Turned on by main processor
    WiFi flash size 4194304, free heap 28360
    WiFi IP address 192.168.0.26
    WiFi signal strength -50dBm, reconnections 0, sleep mode modem
    Socket states: 0 0 0 0 0 0 0 0



  • @ShadowLiger You have the fans set to thermostatic mode to come on when a heater reaches 70 deg C. So just to be clear, are you saying when a heater reaches the set temperature, the fans do not spin?

    Manually trying to turn on the fans by using M106 Pn Sn commands will not work when they are set to thermostatic mode.


  • administrators

    @ShadowLiger said in Issues driving Fans Duex5 Board:

    In Config.g the following lines of code are used for the Fans
    ; Fans
    M106 P0 S0 ; UNUSED
    M106 P1 S255 H1 T70 ; T0 HE
    M106 P2 S0 ; T0 PCF
    M106 P3 S255 H2 T70 ; T1 HE
    M106 P4 S0 ; T1 PCF
    M106 P5 S255 H3 T70 ; T2 HE
    M106 P6 S0 ; T2 PCF
    M106 P7 S255 H4 T70 ; T3 HE
    M106 P8 S0 ; T3 PCF

    With config.g as above, I would expect that you can control fans 0,2,4,6 and 8 manually. For example, the command M106 P6 S1 should turn fan 6 on at full speed. If you can't:

    First, check that the DueX5 is being recognised. Send M115 and see what the FIRMWARE ELECTRONICS string is. It should mention the DueX5. Your M122 report mentions the DueX5, so this should be OK.

    Second, check that the the VFAN jumper on the DueX is present and in the correct place.

    Third, if you have set the VFAN jumper to the 12V position, check that the 12V_EN pins are jumpered.



  • M115

    FIRMWARE_NAME: RepRapFirmware for Duet 2 WiFi/Ethernet FIRMWARE_VERSION: 2.02(RTOS) ELECTRONICS: Duet WiFi 1.02 or later + DueX5 FIRMWARE_DATE: 2018-12-24b1

    I can get the part cooling fans to turn but none of the hot end fans connected to the DUEX5 board. The fans at issue right now are plugged into Fan 5 and 7 (P5 and P7). Those are I believe addressed by the following in config.g

    M106 P5 S255 H3 T70 ; T2 HE
    M106 P7 S255 H4 T70 ; T3 HE

    I verified the wiring for those fans by plugging them into the always on pins on the DUET2Wifi to ensure that they do in fact spin. I nominally use those pins for the HE fans for T0 and T1.

    Below is a picture of the current jumper pin on the DUEX5 board.
    https://imgur.com/8fzIqjn

    To the best of my knowledge the fan jumper is in the correct position, but could certainly use a second opinion. These are to drive the HE fans that come with the e3D V6 toolhead.

    Inspecting the images in the Toolchanger Dozuki, Steps 13 and 14 it appears they jumped Vin like I have but it's hard to make out.
    https://e3d-online.dozuki.com/Guide/09+-+Wiring./112?lang=en

    If I should shift that jumper or would like me to do so just say the word.

    PS: Thank you very much for your time.



  • Solved!!! Thank you all for your time. The misunderstanding was indeed mine...

    in the config.g code

    M106 P5 S255 H3 T70 ; T2 HE

    I was operating under the impression that they were set to Always-On by default by the earlier part of that line of code. A fellow toolchanger user informed me of this behavior and I reviewed the syntax more closely.

    https://reprap.org/wiki/G-code#M106:_Fan_On

    Tnnn Set thermostatic mode trigger temperature
    Hnn:nn:nn... Select heaters monitored when in thermostatic mode1 3

    The H3 T70 implied that the fan would be operating at speed S255 anytime the hotend 3 temperature was over 70c.

    Crisis averted, thank you very much for all your help and suggestions.


Log in to reply