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

    HEATER Faults

    Scheduled Pinned Locked Moved
    General Discussion
    3
    13
    471
    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.
    • PaulHewundefined
      PaulHew @synergy41
      last edited by

      @synergy41 as a suggestion, please remove this line before sending config.g 🙂

      M587 S"Livebox-2AF2" ...
      

      Also a M122, please.

      I am presuming that this all was working before and nothing has changed, apart from using RRF3.

      My first idea was that the heaters needed tuning, but after looking at other posts, it could be a config or an issue with the thermistor.

      Might be worth tuning the heaters while you wait for someone more knowledgeable to see this post.

      Regards,
      Paul

      RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
      Voron 2.4 disassembled..... Waiting for the RailCore Mini....

      synergy41undefined 1 Reply Last reply Reply Quote 0
      • synergy41undefined
        synergy41 @PaulHew
        last edited by

        @PaulHew said in HEATER Faults:

        @synergy41 as a suggestion, please remove this line before sending config.g 🙂

        M587 S"Livebox-2AF2" ...
        

        Also a M122, please.

        I am presuming that this all was working before and nothing has changed, apart from using RRF3.

        My first idea was that the heaters needed tuning, but after looking at other posts, it could be a config or an issue with the thermistor.

        Might be worth tuning the heaters while you wait for someone more knowledgeable to see this post.

        Regards,
        Paul

        Yes, everything works well before the update.
        Here is the M122,*

        **06/04/2020 à 11:30:08: M122: === Diagnostics ===
        RepRapFirmware for Duet 2 WiFi/Ethernet version 3.01-RC6 running on Duet WiFi 1.02 or later
        Board ID: 08DDM-9FAM2-LW4SD-6J9FL-3SJ6J-KJZ7Y
        Used output buffers: 3 of 24 (24 max)
        === RTOS ===
        Static ram: 28052
        Dynamic ram: 92796 of which 60 recycled
        Exception stack ram used: 304
        Never used ram: 9860
        Tasks: NETWORK(ready,748) HEAT(blocked,1244) MAIN(running,1544) IDLE(ready,80)
        Owned mutexes: WiFi(NETWORK)
        === Platform ===
        Last reset 00:03:00 ago, cause: power up
        Last software reset at 2020-04-05 15:14, reason: User, spinning module GCodes, available RAM 9124 bytes (slot 1)
        Software reset code 0x0003 HFSR 0x00000000 CFSR 0x00000000 ICSR 0x0441f000 BFAR 0xe000ed38 SP 0xffffffff Task 0x4e49414d
        Error status: 4
        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 16.0, current 24.4, max 24.8
        Supply voltage: min 24.3, current 24.5, max 24.7, 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
        Date/time: 2020-04-06 11:30:07
        Cache data hit count 320110440
        Slowest loop: 11.02ms; fastest: 0.14ms
        I2C nak errors 0, send timeouts 0, receive timeouts 0, finishTimeouts 0, resets 0
        === Move ===
        Hiccups: 0(0), FreeDm: 169, MinFreeDm: 169, MaxWait: 0ms
        Bed compensation in use: mesh, comp offset 0.000
        === MainDDARing ===
        Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
        === AuxDDARing ===
        Scheduled moves: 0, completed moves: 0, StepErrors: 0, LaErrors: 0, Underruns: 0, 0 CDDA state: -1
        === Heat ===
        Bed heaters = 0 -1 -1 -1, chamberHeaters = -1 -1 -1 -1
        === 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
        Daemon is idle in state(s) 0
        Autopause is idle in state(s) 0
        Code queue is empty.
        === Network ===
        Slowest loop: 19.00ms; fastest: 0.00ms
        Responder states: HTTP(2) HTTP(0) HTTP(0) HTTP(0) FTP(0) Telnet(0)
        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.23
          WiFi MAC address 5c:cf:7f:ee:6a:e7
          WiFi Vcc 3.40, reset reason Unknown
          WiFi flash size 4194304, free heap 23808
          WiFi IP address 192.168.1.18
          WiFi signal strength -64dBm, reconnections 0, sleep mode modem
          Socket states: 0 0 0 0 0 0 0 0**

        I LOVE MY DUET WIFI

        Board: Duet 2 WiFi (2WiFi)
        Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.1 (2022-06-01)
        Duet WiFi Server Version: 1.26
        Duet Web Control 3.4.1

        Cura 4.10

        PaulHewundefined 1 Reply Last reply Reply Quote 0
        • PaulHewundefined
          PaulHew @synergy41
          last edited by

          @synergy41 said in HEATER Faults:
          Thanks for the info.

          Try tuning your heaters so your are using PID values instead of Bang-Bang.

          M303 H0 S(Max temp you run with, ie 80)
          then do the same with H1

          This document is helpful
          https://duet3d.dozuki.com/Wiki/Tuning_the_heater_temperature_control

          Let us know how you get on.

          Paul.

          RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
          Voron 2.4 disassembled..... Waiting for the RailCore Mini....

          synergy41undefined 1 Reply Last reply Reply Quote 0
          • synergy41undefined
            synergy41 @PaulHew
            last edited by

            @PaulHew
            He doesn't want to go through the process?
            Capture d'écran 2020-04-06 12.11.15.png

            I LOVE MY DUET WIFI

            Board: Duet 2 WiFi (2WiFi)
            Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.1 (2022-06-01)
            Duet WiFi Server Version: 1.26
            Duet Web Control 3.4.1

            Cura 4.10

            1 Reply Last reply Reply Quote 0
            • PaulHewundefined
              PaulHew
              last edited by

              Check wiring first.

              Do you have the original config.g pre RRF3?

              P.

              RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
              Voron 2.4 disassembled..... Waiting for the RailCore Mini....

              synergy41undefined 1 Reply Last reply Reply Quote 0
              • synergy41undefined
                synergy41 @PaulHew
                last edited by

                @PaulHew
                here is the old file.
                config.g

                I LOVE MY DUET WIFI

                Board: Duet 2 WiFi (2WiFi)
                Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.1 (2022-06-01)
                Duet WiFi Server Version: 1.26
                Duet Web Control 3.4.1

                Cura 4.10

                PaulHewundefined 1 Reply Last reply Reply Quote 0
                • PaulHewundefined
                  PaulHew @synergy41
                  last edited by

                  Config looks fine.
                  Could be wiring or sensor could of gone faulty.

                  I guess you have a E3D hotend?
                  This is from my config

                  ;HotEnd Configuration
                  M308 S1 P"e0temp" Y"thermistor" A"E3Dv6" T100000 B4725 R4700 C7.06e-8 H0 L0	;A"E3Dv6"
                  M950 H1 C"e0heat" T1				;
                  M143 H1 S280                                                   ; Max temp
                  M307 H1 A503.9 C237.3 D4.9 V24.2 B0        ; PID tuning
                  

                  You might want to try moving the heater to a spare heater and try again, to see if the issue follows.

                  I still suspect wiring or thermistor.

                  Am hoping someone more knowledgeable might jump in!

                  RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                  Voron 2.4 disassembled..... Waiting for the RailCore Mini....

                  synergy41undefined 1 Reply Last reply Reply Quote 1
                  • synergy41undefined
                    synergy41 @PaulHew
                    last edited by

                    @PaulHew
                    I think you were right, there must be a cable problem.
                    I have removed all the plastic collars from my cable management and now it is fine if not a slight temperature
                    variation of + - 2 °.

                    I LOVE MY DUET WIFI

                    Board: Duet 2 WiFi (2WiFi)
                    Firmware: RepRapFirmware for Duet 2 WiFi/Ethernet 3.4.1 (2022-06-01)
                    Duet WiFi Server Version: 1.26
                    Duet Web Control 3.4.1

                    Cura 4.10

                    1 Reply Last reply Reply Quote 0
                    • PaulHewundefined
                      PaulHew
                      last edited by

                      Brilliant, at least you know where the problem lies now.

                      thanks for letting us know.

                      I recommend tuning your heaters to achieve the best performance and not use Bang-Bang mode.

                      Regards,
                      Paul

                      RailCore II - Duet Mini + 1LC, Voron V0.1 - Duet Mini
                      Voron 2.4 disassembled..... Waiting for the RailCore Mini....

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

                        The huge drop shown in the temp graph indicates that the sensor has lost communication with the board entirely. Failing crimp or cable exacerbated by movement and flexing during a print as you've found.

                        Z-Bot CoreXY Build | Thingiverse Profile

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