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

    Tool Board Heater Tuning Leading To Faults

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    8
    101
    5.2k
    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.
    • fcwiltundefined
      fcwilt @KevinMar
      last edited by

      @kevinmar said in Tool Board Heater Tuning Leading To Faults:

      @fcwilt All boards connected, happens ALWAYS when heating up. Never reaches peak or anything

      But it seems to be happening when the cooling fan kicks in?

      Have you changed the temp of the cooling fan to see if the fault tracks that temp?

      How about adding a M570 for that heater and increase the default P parameter value (5) to something like 30.

      Frederick

      Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

      KevinMarundefined 1 Reply Last reply Reply Quote 0
      • KevinMarundefined
        KevinMar @fcwilt
        last edited by

        @fcwilt Yeah, lowered the fan temp to 50, still faulted at about 78C.

        M750 is at P10, will raise to 30

        fcwiltundefined 1 Reply Last reply Reply Quote 0
        • fcwiltundefined
          fcwilt @KevinMar
          last edited by

          @kevinmar said in Tool Board Heater Tuning Leading To Faults:

          @fcwilt Yeah, lowered the fan temp to 50, still faulted at about 78C.

          M750 is at P10, will raise to 30

          I'm interested to see which parameters affect when the fault occurs.

          It seems we don't know exactly what condition is occurring that is triggering the fault.

          Does a M122 report anything related to the fault?

          Frederick

          Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

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

            I'd still like to see a photo of the hotend in case there is something obvious.

            Z-Bot CoreXY Build | Thingiverse Profile

            fcwiltundefined KevinMarundefined 2 Replies Last reply Reply Quote 0
            • fcwiltundefined
              fcwilt @Phaedrux
              last edited by

              @phaedrux said in Tool Board Heater Tuning Leading To Faults:

              I'd still like to see a photo of the hotend in case there is something obvious.

              Perhaps you know the answer to this question.

              He posted a screen shot showing 3 heaters displaying a fault.

              Does a single heater faulting cause all heaters to display a fault or did all three heaters have to fault at the same time?

              Frederick

              Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

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

                @phaedrux Ask and you shall receive

                IMG_8387.jpg

                1 Reply Last reply Reply Quote 1
                • KevinMarundefined
                  KevinMar @fcwilt
                  last edited by

                  @fcwilt It's a printer with 4 tools, just so happened that the 4th tool continued heating to ~120C before faulting (different M307 parameters). All 4 tools have the issue

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

                    @fcwilt said in Tool Board Heater Tuning Leading To Faults:

                    Does a single heater faulting cause all heaters to display a fault or did all three heaters have to fault at the same time?

                    I can't quite tell from that photo, but is the heater block itself making contact with the body of the extruder, or is there an air gap exposing the heat break?

                    Is there any adjustability on the duct to lower it slightly to direct more air away from the block/nozzle itself?

                    Z-Bot CoreXY Build | Thingiverse Profile

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

                      @phaedrux The Hemera tool and V6 hotend are assembled correctly.
                      There is no adjustability to the fan duct, but the ducting is aimed down to the nozzle. It's a fan duct by Rene Jurack, evaluated by an aerodynamicist at BMW 🙂

                      1 Reply Last reply Reply Quote 0
                      • fcwiltundefined
                        fcwilt @KevinMar
                        last edited by

                        @kevinmar said in Tool Board Heater Tuning Leading To Faults:

                        @fcwilt It's a printer with 4 tools, just so happened that the 4th tool continued heating to ~120C before faulting (different M307 parameters). All 4 tools have the issue

                        When the fault occurs have you issued a M122 to see if anything related to the fault is reported?

                        Frederick

                        Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                        KevinMarundefined 1 Reply Last reply Reply Quote 0
                        • KevinMarundefined
                          KevinMar @fcwilt
                          last edited by KevinMar

                          @fcwilt

                          m122
                          === Diagnostics ===
                          RepRapFirmware for Duet 3 MB6HC version 3.3 (2021-06-15 21:45:47) running on Duet 3 MB6HC v1.01 or later (SBC mode)
                          Board ID: 08DJM-9P63L-DJ3T8-6JKDD-3SD6M-9V4Z9
                          Used output buffers: 1 of 40 (16 max)
                          === RTOS ===
                          Static ram: 150904
                          Dynamic ram: 63832 of which 12 recycled
                          Never used RAM 139444, free system stack 200 words
                          Tasks: SBC(ready,5.3%,298) HEAT(delaying,0.0%,325) Move(notifyWait,0.0%,302) CanReceiv(notifyWait,0.1%,799) CanSender(notifyWait,0.0%,374) CanClock(delaying,0.0%,339) TMC(notifyWait,7.4%,93) MAIN(running,87.0%,922) IDLE(ready,0.1%,29), total 100.0%
                          Owned mutexes: HTTP(MAIN)
                          === Platform ===
                          Last reset 00:01:48 ago, cause: software
                          Last software reset at 2021-08-20 13:46, reason: User, none spinning, available RAM 139444, slot 1
                          Software reset code 0x0012 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0044a000 BFAR 0x00000000 SP 0x00000000 Task SBC Freestk 0 n/a
                          Error status: 0x00
                          Step timer max interval 134
                          MCU temperature: min 38.9, current 39.3, max 39.4
                          Supply voltage: min 24.0, current 24.1, max 24.1, under voltage events: 0, over voltage events: 0, power good: yes
                          12V rail voltage: min 12.1, 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
                          Driver 0: position 0, standstill, reads 14442, writes 16 timeouts 0, SG min/max 0/0
                          Driver 1: position 0, standstill, reads 14442, writes 16 timeouts 0, SG min/max 0/0
                          Driver 2: position 0, standstill, reads 14443, writes 15 timeouts 0, SG min/max 0/0
                          Driver 3: position 0, standstill, reads 14447, writes 11 timeouts 0, SG min/max 0/0
                          Driver 4: position 0, standstill, reads 14443, writes 15 timeouts 0, SG min/max 0/0
                          Driver 5: position 0, standstill, reads 14445, writes 14 timeouts 0, SG min/max 0/0
                          Date/time: 2021-08-20 13:48:32
                          Slowest loop: 60.53ms; fastest: 0.04ms
                          === Storage ===
                          Free file entries: 10
                          SD card 0 not detected, interface speed: 37.5MBytes/sec
                          SD card longest read time 0.0ms, write time 0.0ms, max retries 0
                          === Move ===
                          DMs created 125, 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 -1 -1 -1 -1 -1 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
                          Heater 0 is on, I-accum = 0.2
                          === GCodes ===
                          Segments left: 0
                          Movement lock held by null
                          HTTP* is doing "M122" 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 1033, received 5285, lost 0, longest wait 2ms for reply type 6049, peak Tx sync delay 7, free buffers 49 (min 48), ts 545/544/0
                          Tx timeouts 0,0,0,0,0,0
                          === SBC interface ===
                          State: 4, failed transfers: 0, checksum errors: 0
                          Last transfer: 1ms ago
                          RX/TX seq numbers: 3860/3860
                          SPI underruns 0, overruns 0
                          Disconnects: 0, timeouts: 0, IAP RAM available 0x2c83c
                          Buffer RX/TX: 0/0-0
                          === Duet Control Server ===
                          Duet Control Server v3.3.0
                          Code buffer space: 4096
                          Configured SPI speed: 8000000Hz
                          Full transfers per second: 35.84, max wait times: 5.8ms/0.0ms
                          Codes per second: 1.10
                          Maximum length of RX/TX data transfers: 6116/716
                          
                          fcwiltundefined 1 Reply Last reply Reply Quote 1
                          • fcwiltundefined
                            fcwilt @KevinMar
                            last edited by

                            @kevinmar

                            Thanks for the M122 dump.

                            Sure would like to know what condition is causing the fault. I'm surprised that information is not being displayed somewhere.

                            You mentioned that one heater took longer to fault. Were you able to determine what settings were different that might be relevant?

                            Have you tried disabling the cooling fan to see if it is playing a role in the fault?

                            Frederick

                            Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                            KevinMarundefined 1 Reply Last reply Reply Quote 0
                            • KevinMarundefined
                              KevinMar @fcwilt
                              last edited by

                              @fcwilt Yes, I've tried disabling the fan.
                              The heater that took longer to fault had different M307 parameters at that time

                              fcwiltundefined 1 Reply Last reply Reply Quote 0
                              • fcwiltundefined
                                fcwilt @KevinMar
                                last edited by

                                @kevinmar said in Tool Board Heater Tuning Leading To Faults:

                                @fcwilt Yes, I've tried disabling the fan.

                                And it still faulted?

                                Perhaps @dc42 could explain what conditions can lead to a fault.

                                Frederick

                                Printers: a E3D MS/TC setup and a RatRig Hybrid. Using Duet 3 hardware running 3.4.6

                                1 Reply Last reply Reply Quote 0
                                • bucksurundefined
                                  bucksur
                                  last edited by

                                  I was trying to point out that R, L and N are the only additional parameters for PT1000 devices.

                                  1 Reply Last reply Reply Quote 0
                                  • Fumbleundefined
                                    Fumble
                                    last edited by

                                    Was there any resolution to this?
                                    I just ran tuning having swapped my V1 tool board for a V1.1 and fitting a new power supply and get the same thing the heater faults every time anywhere between 60 and 100 degrees. Replacing the new M307 parameters with the old works OK

                                    IDEX CoreXY Duet3 SBC+6HC+1LC

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