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

    Prints Pausing: Connection Interrupted/Unknown msg type 6053

    Scheduled Pinned Locked Moved Unsolved
    General Discussion
    3
    21
    716
    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.
    • p8blrundefined
      p8blr
      last edited by p8blr

      My printer has been pausing mid print throughout the past few days. The problem seems to be intermittent, but when it happened for the third time I updated the firmware. Unfortunately on 3.4.4 it just happened again.

      The console said the connection was interrupted after the pause last time, this time it said the following:
      Error: Board 20 received unknown msg type 6053.

      Hardware:

      • Duet 6HC

      • Duet 1LC

      Software: Release 3.4.4

      Config.g

      ; Configuration file for Duet 3 (firmware version 3)
      ; executed by the firmware on start-up
      ;
      ; generated by RepRapFirmware Configuration Tool v3.2.3 on Mon Jul 26 2021 12:02:50 GMT-0500 (Central Daylight Time)
      
      ; Miscellaneous
      M575 P1 S1 B57600                                            ; enable support for PanelDue
      
      G4 S4 ;dwell
      
      ; General preferences
      G90                                                          ; send absolute coordinates...
      M83                                                          ; ...but relative extruder moves
      M550 P"TXT Stacker 2"                                               ; set printer name
      
      ; Network
      M552 P0.0.0.0 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.0 S1                                                 ; physical drive 0.0 goes forwards
      M569 P0.1 S1                                                 ; physical drive 0.1 goes forwards
      M569 P0.2 S0                                                 ; physical drive 0.2 goes backwards
      M569 P20.0 S1                                               ; physical drive 20.0 goes forwards
      M584 X0.0 Y0.1 Z0.2 E20.0                                   ; set drive mapping
      M350 X32 Y32 Z32 E16 I1                                      ; configure microstepping with interpolation
      M92 X145.395 Y145.402 Z3200 E410.024                          ; set steps per mm was M92 X146.1 Y146.1 Z3200 E400.00   
      M566 X900.00 Y900.00 Z18.00 E600.00                          ; set maximum instantaneous speed changes (mm/min)
      M203 X12000.00 Y12000.00 Z600.00 E1200.00                   ; set maximum speeds (mm/min)
      M201 X400.00 Y400.00 Z100.00 E3000.00                        ; set accelerations (mm/s^2) was z50
      M906 X1800 Y1800 Z2200 E650 I30                                 ; set motor currents (mA) and motor idle factor in per cent was M906 X1000 Y1200 Z1000 E450 I30
      M84 S30                                                      ; Set idle timeout
      
      ; Axis Limits
      M208 X0 Y-45 Z-2 S1                                            ; set axis minima
      M208 X490 Y330 Z645 S0                                       ; set axis maxima
      
      ; Endstops
      M574 X1 S1 P"!io1.in"                                         ; configure active-low endstop for low end on X via pin io0.in with pullup resistor
      ;M574 X2 S1 P"!io3.in"											; configure active-low endstop for low end on X via pin io0.in with pullup resistor
      M574 Y1 S1 P"!io2.in"                                         ; configure active-low endstop for low end on Y via pin io1.in with pullup resistor
      ;M574 Y2 S1 P"!io4.in"											; configure active-low endstop for high end on Y via pin io1.in with pullup resistor
      M574 Z1 S2.2; configure Z-probe endstop for low end on Z
      ;M574 E6 S1 P"!io5.in"											;Filament sensor switch
      
      ; External Triggers
      M950 J3 C"io5.in"											;creates J19 pin for io5 filament sensor
      M581 P3 T1 S1 R1											;filament sensor: P pin, t Trigger 1, S logic, R while printing only
      
      ; Z-Probe
      M558 P8 C"20.io0.in" H1.5 F500:100 T6000 A5 R1                        ; set Z probe type to switch and the dive height + speeds
      G31 P500 X0 Y21.2 Z.94                                         ; set Z probe trigger value, offset and trigger height
      M557 X0:490 Y0:325 P10:7                                      ; define mesh grid
      
      ; 3-point Bed leveling
      ; Z probe has a Y offset ot 21.1mm
      ; back left (72,330)
      ; back right (400,330)
      ; front middle (236,75)
      ; thread pitch M4 X 0.7mm
      M671 X72:400:236 Y330:330:75 P0.7
      
      ; Heaters
      M308 S0 P"temp0" Y"thermistor" T100000 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 B0 R0.160 C880.7 D2.62 S1.00 V23.7                                             ; 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"20.temp0" Y"thermistor" T100000 B4680 C6.455513e-8 ; configure sensor 1 as thermistor on pin 20.temp0
      M950 H1 C"20.out0" T1                                        ; create nozzle heater output on 20.out0 and map it to sensor 1
      M307 H1 B0 R2.925 C170.4 D6.59 S1.00 V23.5                  ; disable bang-bang mode for heater  and set PWM limit
      M143 H1 S450                                                 ; set temperature limit for heater 1 to 450C
      
      ; Fans
      M950 F0 C"20.out1" Q500                                     ; create fan 0 on pin 20.out1 and set its frequency
      M106 P0 S0 H-1                                               ; set fan 0 value. Thermostatic control is turned off
      M950 F1 C"20.out2" Q500                                     ; create fan 1 on pin 20.out2 and set its frequency
      M106 P1 S1 H1 T45                                            ; set fan 1 value. Thermostatic control is turned on
      M950 F2 C"out7" Q500                                     ; create fan 2 on pin out7 and set its frequency (for LED)
      M106 P2 S0 H-1 C"LED"                                             ; set fan 2 value. Thermostatic control is turned off
      
      ; Tools
      M563 P0 S"Main Tool" 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
      
      ; Filament Sensor
      ;M591 D0 P1 C"!io5.in" S1 ;D0 = Extruder 0, P1 = Signal high when filement present, C = pin name, S1 = filament monitoring enabled
      
      ; Custom settings are not defined
      
      T0 ;select tool 0
      

      M115

      FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.4.4 ELECTRONICS: Duet 3 MB6HC v1.01 FIRMWARE_DATE: 2022-10-20 16:19:01
      

      M115 B20

      M115 B20
      Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.4 (2022-10-14 11:46:33)
      

      Thank you.

      jay_s_ukundefined dc42undefined 2 Replies Last reply Reply Quote 0
      • jay_s_ukundefined
        jay_s_uk @p8blr
        last edited by

        @p8blr that tells you you probably have an intermittent connection in your CAN wiring to your toolboard. So check/replace it

        Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

        p8blrundefined 1 Reply Last reply Reply Quote 0
        • p8blrundefined
          p8blr @jay_s_uk
          last edited by

          @jay_s_uk Thanks I'll work on that!

          1 Reply Last reply Reply Quote 0
          • dc42undefined
            dc42 administrators @p8blr
            last edited by

            @p8blr that's very odd, you should only get that message if the Tool1LC board is running older firmware than the main board. Are you certain that you have received the error message since the tool board was upgraded to 3.4.4 ?

            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

            1 Reply Last reply Reply Quote 0
            • p8blrundefined
              p8blr
              last edited by p8blr

              I made a new wire and the same thing happened again. I suppose this new wire could be bad as well, but I'm skeptical of that. No error messages this time. Here's some photos of the lcd and web console. It appears that the whole Duet has been reset.

              console.PNG

              lcd.jpg

              @dc42 said in Prints Pausing: Connection Interrupted/Unknown msg type 6053:

              @p8blr that's very odd, you should only get that message if the Tool1LC board is running older firmware than the main board. Are you certain that you have received the error message since the tool board was upgraded to 3.4.4 ?

              I've restarted this print several times and changed so many things, so I suppose I can't be 100% sure they were running the same version. But I know that as of now they are both on 3.4.4 and I'm still getting the pausing issue.

              jay_s_ukundefined 1 Reply Last reply Reply Quote 0
              • jay_s_ukundefined
                jay_s_uk @p8blr
                last edited by

                @p8blr when you get the reset next time can you get an output of M122 and M122 B20 once reconnected?

                Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                p8blrundefined 1 Reply Last reply Reply Quote 0
                • p8blrundefined
                  p8blr @jay_s_uk
                  last edited by p8blr

                  @jay_s_uk

                  M122
                  === Diagnostics ===
                  RepRapFirmware for Duet 3 MB6HC version 3.4.4 (2022-10-20 16:19:01) running on Duet 3 MB6HC v1.01 (standalone mode)
                  Board ID: 08DJM-9P63L-DJ3S0-7JKDJ-3SJ6T-T8M7B
                  Used output buffers: 3 of 40 (13 max)
                  === RTOS ===
                  Static ram: 152824
                  Dynamic ram: 97228 of which 0 recycled
                  Never used RAM 100620, free system stack 200 words
                  Tasks: NETWORK(ready,29.4%,260) ETHERNET(notifyWait,0.0%,463) HEAT(notifyWait,0.0%,322) Move(notifyWait,0.0%,351) CanReceiv(notifyWait,0.0%,773) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.0%,340) TMC(notifyWait,8.1%,91) MAIN(running,62.5%,1101) IDLE(ready,0.0%,30), total 100.0%
                  Owned mutexes:
                  === Platform ===
                  Last reset 00:44:38 ago, cause: software
                  Last software reset at 2022-11-08 10:40, reason: MemoryProtectionFault iaccViol, GCodes spinning, available RAM 97052, slot 1
                  Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000001 ICSR 0x00400804 BFAR 0x00000000 SP 0x2041b500 Task MAIN Freestk 1670 ok
                  Stack: 00000006 20419a8c 20418198 00000000 000001e8 00489457 20419a8c 00030200 00000000 ffffffff 2041b59c 2042debc 00000000 00000001 00000000 00488f37 2042debc 00000000 00000000 0048927f 00000000 00489457 00000000 ffffffff 31612900 2042debc 20419a8c
                  Error status: 0x00
                  Aux0 errors 0,0,0
                  Step timer max interval 130
                  MCU temperature: min 39.6, current 40.5, max 42.1
                  Supply voltage: min 23.6, current 23.7, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes
                  12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
                  Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                  Events: 0 queued, 0 completed
                  Driver 0: standstill, SG min 0, mspos 156, reads 35581, writes 14 timeouts 0
                  Driver 1: standstill, SG min 0, mspos 612, reads 35581, writes 14 timeouts 0
                  Driver 2: standstill, SG min 0, mspos 484, reads 35581, writes 14 timeouts 0
                  Driver 3: standstill, SG min 0, mspos 8, reads 35585, writes 11 timeouts 0
                  Driver 4: standstill, SG min 0, mspos 8, reads 35585, writes 11 timeouts 0
                  Driver 5: standstill, SG min 0, mspos 8, reads 35585, writes 11 timeouts 0
                  Date/time: 2022-11-08 11:24:49
                  Slowest loop: 11.62ms; fastest: 0.06ms
                  === Storage ===
                  Free file entries: 10
                  SD card 0 detected, interface speed: 25.0MBytes/sec
                  SD card longest read time 5.3ms, write time 0.0ms, max retries 0
                  === Move ===
                  DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
                  === MainDDARing ===
                  Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                  === AuxDDARing ===
                  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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
                  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
                  SBC is idle in state(s) 0
                  Daemon is idle in state(s) 0
                  Aux2 is idle in state(s) 0
                  Autopause is idle in state(s) 0
                  Code queue is empty
                  === CAN ===
                  Messages queued 24104, received 53585, lost 0, boc 0
                  Longest wait 3ms for reply type 6026, peak Tx sync delay 297, free buffers 50 (min 49), ts 13392/13391/0
                  Tx timeouts 0,0,0,0,0,0
                  === Network ===
                  Slowest loop: 5.77ms; fastest: 0.03ms
                  Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
                  HTTP sessions: 1 of 8
                  = Ethernet =
                  State: active
                  Error counts: 0 0 0 1 0 0
                  Socket states: 5 2 2 2 2 0 0 0
                  === Multicast handler ===
                  Responder is inactive, messages received 0, responses 0
                  
                  M122 B20
                  Diagnostics for board 20:
                  Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.4 (2022-10-14 11:46:33)
                  Bootloader ID: not available
                  All averaging filters OK
                  Never used RAM 3608, free system stack 17 words
                  Tasks: Move(notifyWait,0.2%,99) HEAT(notifyWait,0.9%,77) CanAsync(notifyWait,0.0%,55) CanRecv(notifyWait,0.1%,74) CanClock(notifyWait,0.1%,65) TMC(delaying,10.4%,57) MAIN(running,71.2%,351) IDLE(ready,0.0%,40) AIN(delaying,17.1%,142), total 100.0%
                  Last reset 02:14:10 ago, cause: power up
                  Last software reset data not available
                  Driver 0: pos 2776783, 410.0 steps/mm,standstill, SG min 0, read errors 0, write errors 0, ifcnt 14, reads 25464, writes 14, timeouts 0, DMA errors 0, CC errors 0, steps req 3933647 done 3933647
                  Moves scheduled 7354, completed 7354, in progress 0, hiccups 0, step errors 0, maxPrep 707, maxOverdue 1, maxInc 1, mcErrs 0, gcmErrs 0
                  Peak sync jitter -1/5, peak Rx sync delay 602, resyncs 0/1, no step interrupt scheduled
                  VIN voltage: min 23.4, current 23.8, max 23.9
                  MCU temperature: min 25.8C, current 48.8C, max 56.9C
                  Last sensors broadcast 0x00000002 found 1 4 ticks ago, 0 ordering errs, loop time 0
                  CAN messages queued 173810, send timeouts 0, received 79843, lost 0, free buffers 37, min 36, error reg 110000
                  dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 548, adv 35624/74660
                  Accelerometer: none
                  I2C bus errors 4619, naks 4619, other errors 4619
                  
                  jay_s_ukundefined dc42undefined 2 Replies Last reply Reply Quote 0
                  • jay_s_ukundefined
                    jay_s_uk @p8blr
                    last edited by

                    @p8blr looks like the reset is on the mainboard so hopefully @dc42 can shed some light on it

                    Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                    1 Reply Last reply Reply Quote 0
                    • dc42undefined
                      dc42 administrators @p8blr
                      last edited by

                      @p8blr the diagnostic data you posted suggests that the reset may have been caused by an event such as a voltage transient or static discharge. Extruding plastic builds up static discharge; so please ensure that the hot end metalwork is connected to Duet ground, either directly or through a resistor. The latest versions of the tool board have all four mounting holes connected to ground through a resistor, so the mounting screws can be used to ground the hot end; but as your tool board is running an old bootloader version, I don't think that applies to your board.

                      I also suggest you update the bootloader on your tool board. See https://docs.duet3d.com/User_manual/RepRapFirmware/Updating_bootloader.

                      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

                      p8blrundefined 2 Replies Last reply Reply Quote 0
                      • p8blrundefined
                        p8blr @dc42
                        last edited by

                        @dc42 I connected a chassis ground wire directly to the heaterblock. It is a 1.0 toolboard so I used the ground of the power cable instead. Lastly, I went ahead and updated the bootloader on the toolboard and resumed my print. I will update you with the results. Thanks.

                        1 Reply Last reply Reply Quote 0
                        • p8blrundefined
                          p8blr @dc42
                          last edited by p8blr

                          @dc42

                          @p8blr said in Prints Pausing: Connection Interrupted/Unknown msg type 6053:

                          @dc42 I connected a chassis ground wire directly to the heaterblock. It is a 1.0 toolboard so I used the ground of the power cable instead. Lastly, I went ahead and updated the bootloader on the toolboard and resumed my print. I will update you with the results. Thanks.

                          After trying these things, this morning I found my printer stopped again.

                          I don't see anything obvious on the LCD or console, other than the web interface console is blank again.

                          lcd2.jpg

                          Capture.PNG

                          M122
                          === Diagnostics ===
                          RepRapFirmware for Duet 3 MB6HC version 3.4.4 (2022-10-20 16:19:01) running on Duet 3 MB6HC v1.01 (standalone mode)
                          Board ID: 08DJM-9P63L-DJ3S0-7JKDJ-3SJ6T-T8M7B
                          Used output buffers: 1 of 40 (13 max)
                          === RTOS ===
                          Static ram: 152824
                          Dynamic ram: 97228 of which 0 recycled
                          Never used RAM 100620, free system stack 192 words
                          Tasks: NETWORK(ready,1022.7%,232) ETHERNET(notifyWait,0.3%,455) HEAT(notifyWait,0.8%,322) Move(notifyWait,0.1%,351) CanReceiv(notifyWait,1.7%,773) CanSender(notifyWait,0.0%,335) CanClock(delaying,0.4%,340) TMC(notifyWait,638.0%,91) MAIN(running,1033.0%,1101) IDLE(ready,0.0%,30), total 2697.1%
                          Owned mutexes:
                          === Platform ===
                          Last reset 09:40:00 ago, cause: software
                          Last software reset at 2022-11-09 22:11, reason: MemoryProtectionFault mmarValid daccViol, GCodes spinning, available RAM 97028, slot 2
                          Software reset code 0x4163 HFSR 0x00000000 CFSR 0x00000082 ICSR 0x00427804 BFAR 0x0000008a SP 0x2041b530 Task MAIN Freestk 1682 ok
                          Stack: 00000042 2042e250 2041b5a4 00000101 0000023c 00460be7 0045fb98 01030000 00000000 00489457 00000000 ffffffff 0045c58d 2042debc 20419a8c 2042e254 ffffffff 00000000 f25a41f8 0048956f 2042e250 2042aaa0 00000000 f25a41f8 a5a5a5a5 00460bbf 00000000
                          Error status: 0x00
                          Aux0 errors 0,0,0
                          Step timer max interval 131
                          MCU temperature: min 37.3, current 37.8, max 40.6
                          Supply voltage: min 23.6, current 23.7, max 23.8, under voltage events: 0, over voltage events: 0, power good: yes
                          12V rail voltage: min 12.0, current 12.1, max 12.2, under voltage events: 0
                          Heap OK, handles allocated/used 0/0, heap memory allocated/used/recyclable 0/0/0, gc cycles 0
                          Events: 0 queued, 0 completed
                          Driver 0: standstill, SG min 0, mspos 212, reads 58623, writes 14 timeouts 0
                          Driver 1: standstill, SG min 0, mspos 236, reads 58623, writes 14 timeouts 0
                          Driver 2: standstill, SG min 0, mspos 428, reads 58623, writes 14 timeouts 0
                          Driver 3: standstill, SG min 0, mspos 8, reads 58626, writes 11 timeouts 0
                          Driver 4: standstill, SG min 0, mspos 8, reads 58626, writes 11 timeouts 0
                          Driver 5: standstill, SG min 0, mspos 8, reads 58626, writes 11 timeouts 0
                          Date/time: 2022-11-10 07:51:52
                          Slowest loop: 8.07ms; fastest: 0.06ms
                          === Storage ===
                          Free file entries: 10
                          SD card 0 detected, interface speed: 25.0MBytes/sec
                          SD card longest read time 5.5ms, write time 0.0ms, max retries 0
                          === Move ===
                          DMs created 125, segments created 0, maxWait 0ms, bed compensation in use: none, comp offset 0.000
                          === MainDDARing ===
                          Scheduled moves 0, completed 0, hiccups 0, stepErrors 0, LaErrors 0, Underruns [0, 0, 0], CDDA state -1
                          === AuxDDARing ===
                          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 -1 -1 -1 -1 -1 -1 -1 -1, chamber heaters -1 -1 -1 -1, ordering errs 0
                          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
                          SBC is idle in state(s) 0
                          Daemon is idle in state(s) 0
                          Aux2 is idle in state(s) 0
                          Autopause is idle in state(s) 0
                          Code queue is empty
                          === CAN ===
                          Messages queued 313205, received 696040, lost 0, boc 0
                          Longest wait 2ms for reply type 6031, peak Tx sync delay 274, free buffers 50 (min 49), ts 174004/174003/0
                          Tx timeouts 0,0,0,0,0,0
                          === Network ===
                          Slowest loop: 4.39ms; fastest: 0.03ms
                          Responder states: HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0) Telnet(0)
                          HTTP sessions: 1 of 8
                          = Ethernet =
                          State: active
                          Error counts: 0 0 0 1 0 0
                          Socket states: 5 2 2 2 2 0 0 0
                          === Multicast handler ===
                          Responder is inactive, messages received 0, responses 0
                          
                          M122 B20
                          Diagnostics for board 20:
                          Duet TOOL1LC rev 1.0 or earlier firmware version 3.4.4 (2022-10-14 11:46:33)
                          Bootloader ID: SAMC21 bootloader version 2.4 (2021-12-10)
                          All averaging filters OK
                          Never used RAM 3608, free system stack 17 words
                          Tasks: Move(notifyWait,0.0%,99) HEAT(notifyWait,0.2%,75) CanAsync(notifyWait,0.0%,51) CanRecv(notifyWait,0.0%,74) CanClock(notifyWait,0.0%,65) TMC(notifyWait,3.0%,57) MAIN(running,91.9%,351) IDLE(ready,0.0%,40) AIN(delaying,4.9%,142), total 100.0%
                          Last reset 17:32:47 ago, cause: software
                          Last software reset data not available
                          Driver 0: pos 40872078, 410.0 steps/mm,standstill, SG min 2, read errors 0, write errors 0, ifcnt 70, reads 5692, writes 0, timeouts 0, DMA errors 0, CC errors 0, steps req 0 done 0
                          Moves scheduled 119476, completed 119476, in progress 0, hiccups 0, step errors 0, maxPrep 0, maxOverdue 0, maxInc 0, mcErrs 0, gcmErrs 0
                          Peak sync jitter 0/3, peak Rx sync delay 186, resyncs 0/0, no step interrupt scheduled
                          VIN voltage: min 23.8, current 23.8, max 23.8
                          MCU temperature: min 39.5C, current 44.7C, max 53.4C
                          Last sensors broadcast 0x00000002 found 1 188 ticks ago, 0 ordering errs, loop time 0
                          CAN messages queued 254, send timeouts 0, received 110, lost 0, free buffers 37, min 37, error reg 0
                          dup 0, oos 0/0/0/0, bm 0, wbm 0, rxMotionDelay 0
                          Accelerometer: none
                          I2C bus errors 4493, naks 4493, other errors 4493
                          
                          dc42undefined 1 Reply Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators @p8blr
                            last edited by

                            @p8blr thanks for the additional report. It's very different from the first one and again looks like it was caused by a transient rather than a software bug.

                            Do you have the USB port of the MB6HC connected to anything? If so then you may have a USB ground loop, see https://docs.duet3d.com/en/User_manual/Overview/USB_ground_loops.

                            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

                            p8blrundefined 2 Replies Last reply Reply Quote 0
                            • p8blrundefined
                              p8blr @dc42
                              last edited by p8blr

                              @dc42 I do not have USB connected. This printer has been running great for months up until now, and nothing has been changed. I have an oscilloscope, is there anything you'd like me to measure?

                              1 Reply Last reply Reply Quote 0
                              • p8blrundefined
                                p8blr @dc42
                                last edited by p8blr

                                @dc42 It paused again. I've swapped out the 6HC with a spare I had to see if that resolves the issue.

                                p8blrundefined 1 Reply Last reply Reply Quote 0
                                • p8blrundefined
                                  p8blr @p8blr
                                  last edited by

                                  @p8blr The printer paused sometime last night with the new 6HC. Since I've already tried replacing the cable, I assume the problem has to be the 1LC toolboard now...

                                  1 Reply Last reply Reply Quote 0
                                  • Phaedruxundefined Phaedrux marked this topic as a question
                                  • p8blrundefined
                                    p8blr
                                    last edited by

                                    Update. I've swapped out both the duet 3 and toolboard and the printer paused again... I'm going to try swapping out the power supply next. This is very odd because I have two identical printers and one doesn't have this problem, so the power supply is the last variable I can think of...

                                    dc42undefined 1 Reply Last reply Reply Quote 0
                                    • dc42undefined
                                      dc42 administrators @p8blr
                                      last edited by dc42

                                      @p8blr are you absolutely certain that when the printer paused this time, it gave the same message "Error: Board 20 received unknown msg type 6053." ?

                                      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

                                      p8blrundefined 1 Reply Last reply Reply Quote 0
                                      • p8blrundefined
                                        p8blr @dc42
                                        last edited by

                                        @dc42 No it hasn't given that messages any of the last half dozen or so times it's paused. I have no information on the screen, and the console is basically empty, leading me to believe it's being reset.

                                        dc42undefined 1 Reply Last reply Reply Quote 0
                                        • dc42undefined
                                          dc42 administrators @p8blr
                                          last edited by dc42

                                          @p8blr said in Prints Pausing: Connection Interrupted/Unknown msg type 6053:

                                          @dc42 No it hasn't given that messages any of the last half dozen or so times it's paused. I have no information on the screen, and the console is basically empty, leading me to believe it's being reset.

                                          In that case, please post a M122 report for each board in your system.

                                          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

                                          p8blrundefined 2 Replies Last reply Reply Quote 0
                                          • p8blrundefined
                                            p8blr @dc42
                                            last edited by

                                            @dc42 I will once the printer stops again. After replacing the power supply, I removed all the extra grounding wires and restored the printer back to the original boards. It's been running for roughly 24 hours now, so I'm beginning to suspect the power supply was the issue. I'm going to put the suspected bad power supply in a different printer to confirm.

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