Duet3D Logo

    Duet3D

    • Register
    • Login
    • Search
    • Categories
    • Tags
    • Documentation
    • Order

    Duex5 error when powering on

    Duet Hardware and wiring
    2
    5
    50
    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.
    • resh
      resh last edited by

      I've got a duet wifi2 and duex5 and when just the ribbon cable and vin is supplied I'm getting numerous errors. It's just when I turn it on and nothing is hot. The errors stop appearing after a couple minutes.

      Error: over temperature shutdown reported by drivers 5 6 7 8 9
      Error: short to ground reported by drivers 5 9

      Thanks for the help

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

        Can you please post your config.g and the results of M122 and M98 P"config.g" ?

        What do you have connected where?

        How do you have your Duex power and ground connected?

        It should be as described here: https://duet3d.dozuki.com/Wiki/Duex2_and_Duex5_Features#Section_Wiring

        Z-Bot CoreXY Build | Thingiverse Profile

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

          @phaedrux The duex5 is connected exactly like the picture you linked. The only thing connected to the duex5 is the power/gnd and the ribbon cable. I'm unfamiliar that last M98 line you're requesting.

          Thanks for the help. I see others posting their config files in a better format than copy/paste. If it's easier that way please let me know how to do that.

          M122
          === Diagnostics ===
          RepRapFirmware for Duet 2 WiFi/Ethernet version 3.3RC3 (2021-05-26 13:47:14) running on Duet WiFi 1.02 or later + DueX5
          Board ID: 08DGM-956GU-DGMSN-6JTD4-3SD6Q-1VRMH
          Used output buffers: 5 of 24 (19 max)
          === RTOS ===
          Static ram: 23876
          Dynamic ram: 75736 of which 0 recycled
          Never used RAM 14804, free system stack 184 words
          Tasks: NETWORK(ready,12.1%,252) HEAT(delaying,0.0%,330) Move(notifyWait,0.1%,319) DUEX(notifyWait,0.0%,24) MAIN(running,85.2%,441) IDLE(ready,2.6%,29), total 100.0%
          Owned mutexes: WiFi(NETWORK)
          === Platform ===
          Last reset 00:00:28 ago, cause: power up
          Last software reset at 2021-03-20 20:52, reason: User, GCodes spinning, available RAM 14960, slot 2
          Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0041f000 BFAR 0xe000ed38 SP 0x00000000 Task MAIN Freestk 0 n/a
          Error status: 0x00
          Aux0 errors 0,0,0
          Step timer max interval 0
          MCU temperature: min 27.7, current 31.1, max 31.4
          Supply voltage: min 23.8, current 24.0, max 24.2, under voltage events: 0, over voltage events: 0, power good: yes
          Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
          Driver 0: position 0, standstill, SG min/max not available
          Driver 1: position 0, standstill, SG min/max not available
          Driver 2: position 0, standstill, SG min/max not available
          Driver 3: position 0, standstill, SG min/max not available
          Driver 4: position 0, standstill, SG min/max not available
          Driver 5: position 0, ok, SG min/max not available
          Driver 6: position 0, ok, SG min/max not available
          Driver 7: position 0, ok, SG min/max not available
          Driver 8: position 0, ok, SG min/max not available
          Driver 9: position 0, ok, SG min/max not available
          Driver 10: position 0
          Driver 11: position 0
          Date/time: 2021-06-08 17:15:11
          Cache data hit count 1005073547
          Slowest loop: 4.89ms; fastest: 0.17ms
          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 3.2ms, write time 0.0ms, max retries 0
          === Move ===
          DMs created 83, maxWait 0ms, bed compensation in use: none, comp offset 0.000
          === MainDDARing ===
          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === AuxDDARing ===
          Scheduled moves 0, completed moves 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
          === Heat ===
          Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
          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 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
          Daemon is idle in state(s) 0
          Autopause is idle in state(s) 0
          Code queue is empty.
          === DueX ===
          Read count 1, 2.12 reads/min
          === Network ===
          Slowest loop: 15.60ms; fastest: 0.00ms
          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0), 0 sessions
          HTTP sessions: 1 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.26
            WiFi MAC address 84:0d:8e:b2:7c:16
            WiFi Vcc 3.36, reset reason Turned on by main processor
            WiFi flash size 4194304, free heap 24960
            WiFi IP address 192.168.1.233
            WiFi signal strength -32dBm, mode 802.11n, reconnections 0, sleep mode modem
            Clock register 00002002
            Socket states: 0 0 0 0 0 0 0 0

          ; Configuration file for Duet WiFi (firmware version 3)
          ; executed by the firmware on start-up
          ;
          ; generated by RepRapFirmware Configuration Tool v3.2.3 on Fri Feb 26 2021 10:46:02 GMT-0500 (Eastern Standard Time)

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

          ; 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 forwards s1 is forward s0 backwards
          M569 P1 S1 ; physical drive 1 goes forwards
          M569 P2 S0 ; physical drive 2 goes forwards
          M569 P3 S1
          M569 P4 S0 ; physical drive 3 goes forwards
          M584 X0 Y1 Z2:4 E3 ; set drive mapping
          M671 X-20:290 Y0:0 S5 ;leadscrews at left (connected to Z) and right (connected to E1) of X axis
          M208 X10:300 Y0:180 ;X carriage moves from -5 to 270, Y bed goes from 0 to 130
          M350 X16 Y16 Z16 E16 I1 ; configure microstepping with interpolation
          M92 X80.00 Y80.00 Z400.00 E420.00 ; set steps per mm
          M566 X900.00 Y900.00 Z60.00 E120.00 ; set maximum instantaneous speed changes (mm/min)
          M203 X6000.00 Y6000.00 Z180.00 E1200.00 ; set maximum speeds (mm/min)
          M201 X500.00 Y500.00 Z20.00 E250.00 ; set accelerations (mm/s^2)
          M906 X800 Y800 Z800 E800 I30 ; set motor currents (mA) and motor idle factor in per cent
          M84 S30 ; Set idle timeout

          ; Axis Limits
          M208 X0 Y0 Z0 S1 ; set axis minima
          M208 X310 Y310 Z180 S0 ; set axis maxima

          ; 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 S2 ; configure Z-probe endstop for high end on Z

          ; Z-Probe ; create servo pin 0 for BLTouch
          M558 P9 C"^zprobe.in" H5 F120 T6000 ; set Z probe type to bltouch and the dive height + speeds
          M950 S0 C"duex.pwm1"
          G31 P500 X27 Y0 Z1.28 ; set Z probe trigger value, offset and trigger height
          M557 X15:215 Y15:195 S20 ; define mesh grid

          ; Heaters
          M308 S0 P"bedtemp" Y"thermistor" T100000 B3950 ; 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 R0.135 C738.7 D1.34 S1.00 V23.5 ; 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.060000e-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 R2.039 C177.8 D6.23 S1.00 V24.0 ; disable bang-bang mode for heater and set PWM limit
          M143 H1 S285 ; set temperature limit for heater 1 to 280C

          ; 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

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

          ; Miscellaneous
          M575 P1 S1 B57600 ;enable support for PanelDue
          T0 ; Select first tool

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

            Do you see any damage on the Duex5 drivers? Can you post a photo?

            When and where was it purchased?

            @resh said in Duex5 error when powering on:

            'm unfamiliar that last M98 line you're requesting.

            M98 P"config.g" runs config.g as a macro and any syntax errors that may not have been caught during bootup will show in the console.

            To post your text as code you encapsulate it with ``` marks above and below the text block.
            

            Z-Bot CoreXY Build | Thingiverse Profile

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

              @phaedrux There's no damage to the chips or surrounding area.

              Got it used off ebay. I'll send it back.

              I appreciate the help.

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