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

Duet mini keeps restarting if the toolboard is missing

Scheduled Pinned Locked Moved Solved
Firmware installation
3
9
347
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.
  • undefined
    Aurimas
    last edited by 25 Nov 2023, 01:10

    Hi,

    It appears that with the latest version if the toolboard is missing the board kees restarting.
    So it is stuck in a closed cycle and cannot change the 1LC address.

    is there any way to prevent that?
    paneldue is trying to connect to it most of the time too

    Australian design and build large scale 3d printers
    https://aurarum.com.au

    undefined undefined 2 Replies Last reply 25 Nov 2023, 07:37 Reply Quote 0
    • undefined
      dc42 administrators @Aurimas
      last edited by dc42 25 Nov 2023, 07:37

      @Aurimas this is not normal behaviour. Please power the system up with the tool board powered but the CAN connection unplugged at one end, let the Duet reset at least once, then connect CAN so that the Duet starts properly. Then run M122 and post the output here.

      Duet WiFi hardware designer and firmware engineer
      Please do not ask me for Duet support via PM or email, use the forum
      http://www.escher3d.com, https://miscsolutions.wordpress.com

      undefined 1 Reply Last reply 26 Nov 2023, 04:57 Reply Quote 0
      • undefined
        Aurimas @dc42
        last edited by 26 Nov 2023, 04:57

        @dc42 said in Duet mini keeps restarting if the toolboard is missing:

        @Aurimas this is not normal behaviour. Please power the system up with the tool board powered but the CAN connection unplugged at one end, let the Duet reset at least once, then connect CAN so that the Duet starts properly. Then run M122 and post the output here.

        I will give it a go, but it is doing on two different machines at least
        Will update tomorrow

        Australian design and build large scale 3d printers
        https://aurarum.com.au

        1 Reply Last reply Reply Quote 0
        • undefined
          gloomyandy @Aurimas
          last edited by 26 Nov 2023, 05:34

          @Aurimas Can you clarify what you mean by "missing" do you mean that the toolboard is not connected or that it is connected but does not have the address that you are using in your config? Do you just have a single toolboard (or other can-fd device) attached to your mainboard? Which mainboard are you using?

          As well as posting the M122 output as requested by David, it might also be worth posting your config.g file.

          undefined 1 Reply Last reply 26 Nov 2023, 22:56 Reply Quote 0
          • undefined
            Aurimas @gloomyandy
            last edited by 26 Nov 2023, 22:56

            @gloomyandy
            I have 2 toolboards, when I am booting the printer without boards connected - the printer reports timeout and reboots.
            Paneldue keeps cycling between starting up and connecting with the message about the missing boards
            I am pretty sure this wasn't the case with the older version firmware.
            Config file and M122 are below.

            M122
            === Diagnostics ===
            RepRapFirmware for Duet 3 Mini 5+ version 3.5.0-rc.1 (2023-08-31 16:16:56) running on Duet 3 Mini5plus WiFi (standalone mode)
            Board ID: AGMAV-AR6KL-K65J0-409N6-LGW1Z-7XF1B
            Used output buffers: 15 of 40 (40 max)
            Error in macro line 18 while starting up: Response timeout: CAN addr 20, req type 6042, RID=0
            === RTOS ===
            Static ram: 102836
            Dynamic ram: 122840 of which 28 recycled
            Never used RAM 12856, free system stack 198 words
            Tasks: NETWORK(2,nWait,9.1%,219) HEAT(3,nWait,0.0%,327) Move(4,nWait,0.0%,358) CanReceiv(6,nWait,0.1%,796) CanSender(5,nWait,0.0%,337) CanClock(7,delaying,0.0%,351) TMC(4,delaying,1.1%,108) MAIN(1,running,71.1%,704) IDLE(0,ready,17.7%,29) AIN(4,delaying,0.8%,264), total 100.0%
            Owned mutexes: WiFi(NETWORK)
            === Platform ===
            Last reset 00:01:18 ago, cause: software
            Last software reset time unknown, reason: HardFault invState, Gcodes spinning, available RAM 53740, slot 0
            Software reset code 0x4063 HFSR 0x40000000 CFSR 0x00020000 ICSR 0x00000803 BFAR 0xe000ed38 SP 0x20004108 Task MAIN Freestk 1053 ok
            Stack: 00000000 200229b8 200043f4 20004173 ffffffff 00080987 00000000 40070000 00080977 010041e8 00000003 200229b8 200229b8 2001e978 20018668 2001e978 000738b7 00000000 200041f4 00000000 00000000 0000000a 00000003 200041e8 20004220 200041f8 0009c2c1
            Error status: 0x04
            Aux0 errors 0,0,0
            MCU revision 3, ADC conversions started 78251, completed 78249, timed out 0, errs 0
            MCU temperature: min 23.9, current 25.3, max 25.8
            Supply voltage: min 23.7, current 23.8, max 23.9, under voltage events: 0, over voltage events: 0, power good: yes
            Heap OK, handles allocated/used 99/2, heap memory allocated/used/recyclable 2048/64/0, gc cycles 0
            Events: 0 queued, 0 completed
            Driver 0: standstill, SG min 0, read errors 0, write errors 1, ifcnt 44, reads 7073, writes 14, timeouts 0, DMA errors 0, CC errors 0
            Driver 1: standstill, SG min 0, read errors 0, write errors 1, ifcnt 44, reads 7072, writes 14, timeouts 0, DMA errors 0, CC errors 0
            Driver 2: standstill, SG min 0, read errors 0, write errors 1, ifcnt 38, reads 7074, writes 12, timeouts 0, DMA errors 0, CC errors 0
            Driver 3: standstill, SG min 0, read errors 0, write errors 1, ifcnt 38, reads 7074, writes 12, timeouts 0, DMA errors 0, CC errors 0
            Driver 4: standstill, SG min 0, read errors 0, write errors 1, ifcnt 38, reads 7074, writes 12, timeouts 0, DMA errors 0, CC errors 0
            Driver 5: standstill, SG min 0, read errors 0, write errors 1, ifcnt 44, reads 7072, writes 14, timeouts 0, DMA errors 0, CC errors 0
            Driver 6: standstill, SG min 0, read errors 0, write errors 1, ifcnt 44, reads 7072, writes 14, timeouts 0, DMA errors 0, CC errors 0
            Date/time: 2023-11-27 09:53:05
            Cache data hit count 110139057
            Slowest loop: 9.19ms; fastest: 0.14ms
            === Storage ===
            Free file entries: 19
            SD card 0 detected, interface speed: 22.5MBytes/sec
            SD card longest read time 3.7ms, write time 0.0ms, max retries 0
            === Move ===
            DMs created 83, segments created 0, maxWait 0ms, bed compensation in use: none, height map offset 0.000, ebfmin 0.00, ebfmax 0.00
            no step interrupt scheduled
            Moves shaped first try 0, on retry 0, too short 0, wrong shape 0, maybepossible 0
            === DDARing 0 ===
            Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
            === DDARing 1 ===
            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, chamber heaters 4 -1 -1 -1, ordering errs 0
            Heater 1 is on, I-accum = 0.0
            === GCodes ===
            Movement locks held by null, 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
            SBC is idle in state(s) 0
            Daemon is idle in state(s) 0 0, running macro
            Aux2 is idle in state(s) 0
            Autopause is idle in state(s) 0
            File2 is idle in state(s) 0
            Queue2 is idle in state(s) 0
            Q0 segments left 0, axes/extruders owned 0x0000803
            Code queue 0 is empty
            Q1 segments left 0, axes/extruders owned 0x0000000
            Code queue 1 is empty
            === Filament sensors ===
            Extruder 0: no data received
            Extruder 1: no data received
            === CAN ===
            Messages queued 716, received 2166, lost 29, boc 0
            Longest wait 2ms for reply type 6053, peak Tx sync delay 315, free buffers 26 (min 25), ts 391/390/0
            Tx timeouts 0,0,0,0,0,0
            === Network ===
            Slowest loop: 8.42ms; fastest: 0.00ms
            Responder states: MQTT(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
            HTTP sessions: 1 of 8
            === WiFi ===
            Interface state: active
            Module is connected to access point
            Failed messages: pending 0, notrdy 0, noresp 0
            Firmware version 2.1beta4
            MAC address e8:68:e7:e5:b1:d7
            Module reset reason: Power up, Vcc 3.37, flash size 2097152, free heap 42148
            WiFi IP address 192.168.1.82
            Signal strength -33dBm, channel 5, mode 802.11n, reconnections 0
            Clock register 00002001
            Socket states: 0 0 0 0 0 0 0 0
            ; Configuration file for Duet 3 Mini 5+ (firmware version 3)
            ; executed by the firmware on start-up
            ;
            ; generated by RepRapFirmware Configuration Tool v3.2.3 on Sat May 08 2021 10:30:29 GMT+1000 (Australian Eastern Standard Time)
            ; General preferences
            G90 ; send absolute coordinates...
            M83 ; ...but relative extruder moves
            M550 P"Vega - IDEX" ; set printer name
            G4 S1 ;wait for expansion boards to start
            ; Network
            ;M551 P"Vega" ; set password
            M552 S1 ; enable network
            M586 P0 S1 ; enable HTTP
            M586 P1 S0 ; disable FTP
            M586 P2 S0 ; disable Telnet
            M575 P1 S1 B57600
            M584 X0.2 Y0.3 Z0.0:0.1:0.5:0.6 U0.4 E121.0:20.0 ; set drive mapping
            M669 K1 X1:1:0:0 Y-1:1:0:0 U0:0:0:1 Z0:0:1:0 ; select CoreXY mode
            ; Drives
            M569 P0.0 S0 D3 V40 ; physical drive 0.0 goes forwards
            M569 P0.1 S0 D3 V40 ; physical drive 0.1 goes forwards
            M569 P0.2 S1 ;D3 V40 ; physical drive 0.2 goes forwards
            M569 P0.3 S1 ;D3 V40 ; physical drive 0.3 goes forwards
            M569 P0.4 S0 ;D3 V40 ; physical drive 0.4 goes forwards
            M569 P0.5 S0 D3 V40
            M569 P0.6 S0 D3 V40
            M569 P121.0 S0 ;D3 V40
            M569 P20.0 S0 ;D3 V40
            M350 X16 Y16 Z16 U16 T1 E16:16 I1 ; configure microstepping with interpolation
            M671 X-160:730:-160:730 Y130:130:370:370 S14
            M92 X80.00 Y80.00 Z2400.00 U80.00 E400.0:400.0 ; set steps per mm
            M566 X1200.00 Y1200.00 Z20.00 U1200 E3200.00:3200.00 ; set maximum instantaneous speed changes (mm/min)
            M203 X15000.00 Y15000.00 Z280.00 U15000.00 E10200.00:10200.00 ; set maximum speeds (mm/min)
            M201 X5000.00 Y5000.00 Z25.00 U5000.00 E1550.00:1550.00 ; set accelerations (mm/s^2)
            M906 X1600 Y1600 Z850:850:850:850 U1200 E600:600 I30 ; set motor currents (mA) and motor idle factor in per cent
            M84 S90 ; Set idle timeout
            ; Axis Limits
            M208 X-65 Y0 U0 Z-1 S1 ; set axis minima
            M208 X624 Y530 U688 Z420 S0 ; set axis maxima
            M597 X0 U64
            ; Endstops
            M574 X1 S1 P"!io3.in" ; configure switch-type (e.g. microswitch) endstop for low end on X via pin
            M574 Y1 S1 P"!io4.in"
            M574 U2 S1 P"!io2.in"
            M574 Z1 S2 ; configure Z-probe endstop for low end on Z
            ; Z-Probe
            M950 S0 C"121.io0.out" ; create servo pin 0 for BLTouch
            M558 P9 C"121.^io0.in" H5 F2200 T3000 S0.25 ; set Z probe type to bltouch and the dive height + speeds
            G31 P300 X-30 Y5 Z2.5 ; set Z probe trigger value, offset and trigger height Increase Z number if the nozzle is too far
            M557 X50:330 Y25:280 S200
            ; Heaters
            M308 S0 P"temp0" Y"thermistor" T200000 B4138 ; configure sensor 0 as thermistor on pin temp0
            M950 H0 C"out0" T0 ; create bed heater output on out0 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"121.temp0" Y"pt1000" R2200 ; configure sensor 1 as PT1000 on pin 121.temp0
            M950 H1 C"121.out0" T1 ; create nozzle heater output on 121.out0 and map it to sensor 1
            M307 H1 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
            M143 H1 S350
            M308 S2 P"20.temp0" Y"pt1000" R2200 ; configure sensor 2 as PT1000 on pin 121.io0.in
            M950 H2 C"20.out0" T2 ; create nozzle heater output on 122.out0 and map it to sensor 2
            M307 H2 B0 S1.00 ; disable bang-bang mode for heater and set PWM limit
            M143 H2 S350 ; set temperature limit for heater 2 to 350C
            M308 S4 P"temp1" Y"thermistor" T100000 B4138 ; configure sensor 2 as thermistor on pin temp2
            ;M950 H4 C"out5" T4 ; create chamber heater output on out2 and map it to sensor 4
            ;M307 H4 B1 S1.00 ; enable bang-bang mode for the chamber heater and set PWM limit
            M141 H4 ; map chamber to heater 2
            ;M143 H4 S70 ; set temperature limit for heater 2 to 280C
            ; Fans
            M950 F2 C"20.out1" Q500 ; create fan 1 on pin 121.out2 and set its frequency
            M106 P2 S0 ; set fan 1 value. Thermostatic control is turned on
            M950 F1 C"121.out1" Q500 ; create fan 3 on pin 122.out2 and set its frequency
            M106 P1 S0 ; set fan 3 value. Thermostatic control is turned on
            M950 F5 C"out5" Q500 ; create fan 1 on pin out3 and set its frequency
            ;M106 P5 S1 H4 T55 ; set fan 1 value. Thermostatic control is turned on
            M950 F4 C"20.out2" Q500
            M106 P4 T45 H2
            M950 F2 C"121.out2" Q500
            M106 P2 T45 H1
            M950 P12 C"out1"
            M42 P12 S1 ;turn the light on
            M950 F10 C"out6" Q500 ; create fan 2 on pin out5 and set its frequency
            M106 P10 S1 ; set fan 2 value. Thermostatic control is turned on
            ; Tools
            M563 P0 S"Left Extruder" D0 H1 F1 ; define tool 1
            M568 P0 S0 R0 A0
            M563 P1 S"Right extruder" D1 H2 X3 F3 ; define tool 2
            M568 P1 S0 R0 A0
            ; ''' Create a tool that prints 2 copies of the object using both carriages'''
            M563 P2 S"Copy 330x530" D0:1 H1:2 X0:3 F1:1 ; tool 2 uses both extruders, hot end heaters and fans, and maps X to both X and U
            G10 P2 X30 Y0 U-300 S0 R0 ; set tool offsets and temperatures
            M567 P2 E1:1 ; set mix ratio 100% on both extruders
            ;''' Create a tool that prints 2 copies of the object using both carriages'''
            M563 P3 S"Mirror 325x530" D0:1 H1:2 X0:3 F1:1 ; tool 2 uses both extruders, hot end heaters and fans, and maps X to both X and U
            G10 P3 X50 Y0 U-668 S0 R0 ; set tool offsets and temperatures
            M567 P3 E1:1 ; set mix ratio 100% on both extruders
            ; Custom settings are not defined
            M591 D0 P3 C"121.io1.in" S1 R50:150 L24.8 E5.0 ; Duet3D rotating magnet sensor for extruder drive 0 is connected to E0 endstop input, enabled, sensitivity 24.8mm.rev, 70% to 130% tolerance, 3mm detection lengt
            M591 D1 P3 C"20.io1.in" S1 R50:150 L24.8 E5.0 ; Duet3D rotating magnet sensor for extruder drive 0 is connected to E0 endstop input, enabled, sensitivity 24.8mm.rev, 70% to 130% tolerance, 3mm detection length
            ; Miscellaneous
            M575 P1 S0 B57600 ; enable support for PanelDue
            M501 ; load saved parameters from non-volatile memory
            T0
            ; select first tool
            M307 H0 R0.21 K0.586:0.000 D3.70 E1.35 S1.00 B1

            Australian design and build large scale 3d printers
            https://aurarum.com.au

            undefined 1 Reply Last reply 27 Nov 2023, 15:29 Reply Quote 0
            • undefined
              dc42 administrators @Aurimas
              last edited by 27 Nov 2023, 15:29

              @Aurimas thanks. I think this issue is one that I have already fixed. Please try the 3.5.0-rc.1+ firmware at https://www.dropbox.com/scl/fo/tjznycpk7bv7sj71p0ssl/h?rlkey=096p4nvgmigyrb20jj8olg3wu&dl=0.

              Duet WiFi hardware designer and firmware engineer
              Please do not ask me for Duet support via PM or email, use the forum
              http://www.escher3d.com, https://miscsolutions.wordpress.com

              undefined 1 Reply Last reply 28 Nov 2023, 01:11 Reply Quote 0
              • undefined
                Aurimas @dc42
                last edited by 28 Nov 2023, 01:11

                @dc42 thanks a lot - I can confirm that ther issue is solved
                🙂

                Australian design and build large scale 3d printers
                https://aurarum.com.au

                undefined 1 Reply Last reply 28 Nov 2023, 12:09 Reply Quote 0
                • undefined
                  dc42 administrators @Aurimas
                  last edited by 28 Nov 2023, 12:09

                  @Aurimas thanks for confirming. The problem occurred when a filament monitor was configured on a missing expansion board.

                  Duet WiFi hardware designer and firmware engineer
                  Please do not ask me for Duet support via PM or email, use the forum
                  http://www.escher3d.com, https://miscsolutions.wordpress.com

                  undefined 1 Reply Last reply 28 Nov 2023, 20:49 Reply Quote 0
                  • undefined
                    Aurimas @dc42
                    last edited by 28 Nov 2023, 20:49

                    @dc42 said in Duet mini keeps restarting if the toolboard is missing:

                    @Aurimas thanks for confirming. The problem occurred when a filament monitor was configured on a missing expansion board.

                    as long as it is not me it is all good 🙂
                    thanks again

                    Australian design and build large scale 3d printers
                    https://aurarum.com.au

                    1 Reply Last reply Reply Quote 0
                    • droftartsundefined droftarts marked this topic as a question 28 Nov 2023, 21:12
                    • droftartsundefined droftarts has marked this topic as solved 28 Nov 2023, 21:12
                    1 out of 9
                    • First post
                      1/9
                      Last post
                    Unless otherwise noted, all forum content is licensed under CC-BY-SA