Navigation

    Duet3D Logo

    Duet3D

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

    Heater Fault Troubleshooting

    Duet Hardware and wiring
    6
    26
    2608
    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.
    • jgbowman
      jgbowman last edited by

      The temperature on my heater is not increasing. I believe I have the wiring correct but have issues in the configuration. Any suggestions?

      0_1530286268937_Heater config.PNG 0_1530286276570_G-code config.PNG

      T3P3Tony 1 Reply Last reply Reply Quote 0
      • jgbowman
        jgbowman last edited by

        @dc42 please help

        1 Reply Last reply Reply Quote 0
        • paboman
          paboman last edited by

          you have some kind of wiring problem, as you can see you have a lot of 2000°C spikes in the graph.
          maybe loose connection

          1 Reply Last reply Reply Quote 0
          • jgbowman
            jgbowman last edited by

            @paboman I'm still trying to figure out the wiring issues for the pt100 sensor, but I believe that should be separate from the actual heaters.

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

              Interference in pt100 wiring can be mitigated by using a twisted 4 wire connection.

              https://duet3d.dozuki.com/Wiki/Connecting_PT100_temperature_sensors

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

                @phaedrux I only have a two-wire pt100 sensor. Both sensors are wired the same exact way, however one of them works while the other is completely dysfunctional.

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

                  Each of those two wires can be split into another 2 wires.

                  https://miscsolutions.wordpress.com/2016/06/25/more-delta-printer-upgrades-wifi-and-silence/

                  It really is the best way to run a pt100. Highly fault tolerant.

                  You can attempt to isolate the issue by separating the pt100 wires physically from any other wiring and see if the reading spikes are resolved.

                  1 Reply Last reply Reply Quote 0
                  • T3P3Tony
                    T3P3Tony administrators @jgbowman last edited by

                    @jgbowman those spikes look like more than noise to me. As others have mentioned you can get intermittent spikes from noise however the first one is really long and looks like a poor connection to me (or possibly a faulty PT100 daughterboard).

                    Can you check the connection and try sawapping the channels to see if the 2000C fault follows the PT100 sensor.

                    1 Reply Last reply Reply Quote 0
                    • jgbowman
                      jgbowman last edited by

                      0_1530559541176_Z-Axis.PNG

                      @T3P3Tony, @dc42 , We have figured out the Heaters Fault configuration. We are now having issues configuring the Z-axis. Any suggestions as to why the manual Z-Bed Probing is asking us to adjust the X-Axis?

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

                        @jgbowman, it's because you have mismatched versions of the firmware and Duet Web Control.

                        jgbowman 1 Reply Last reply Reply Quote 1
                        • jgbowman
                          jgbowman @dc42 last edited by

                          @dc42 I updated all of my firmware to 1.21 and this successfully switched the setting from x-axis to z-axis. Only thing is that I now get this error when trying to manually probe the z-axis.0_1530628399450_homez error.PNG

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

                            For now you will need to add command M564 H0 to config.g to allow movement of an axis before it is homed. This will be fixed in future firmware and DWC revisions.

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

                              @dc42 I added it here, but I'm still getting the same result.
                              0_1530651614202_config g.PNG

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

                                Odd, that should have fixed it. Please run M564 without parameters and see whether it says movement is allowed when the axis concerned is not homed.

                                jgbowman 1 Reply Last reply Reply Quote 0
                                • mrehorstdmd
                                  mrehorstdmd @jgbowman last edited by mrehorstdmd

                                  @jgbowman

                                  Where did you get the PT100 sensor? More importantly, what is the insulation material on the leads?

                                  I recently tried to use some cheapo PT100 sensors with teflon insulation on the leads and after a couple weeks of occasional ABS printing I started getting the same sort of weird heater faults you did, including the spikes to 2k. I checked the resistance between the PT100 leads and the metal casing and found that one of the leads shorted to the case. The case is in contact with the heater block, which in my printer is grounded.

                                  Swapping in a new PT100 sensor will fix the problem temporarily, until the teflon wire insulation inside the sensor housing breaks down due to the high temperature.

                                  Teflon insulation going into the metal sensor housing is a no-go for high temperature use. The E3D PT100 sensor has fiberglass insulation which should be reliable at high temperatures.

                                  jgbowman 1 Reply Last reply Reply Quote 1
                                  • jgbowman
                                    jgbowman @dc42 last edited by

                                    @dc42 It says movement before homing is not permitted. All of the firmware is updated to 1.21 except for the paneldue, could that be the problem?

                                    dc42 1 Reply Last reply Reply Quote 0
                                    • jgbowman
                                      jgbowman @mrehorstdmd last edited by

                                      @mrehorstdmd Not sure where my boss got the sensors, but I've tried to switch out a couple of them, so i'm pretty sure it's either a wiring or configuration issue. I ordered a new daughterboard because that seems like the most likely fix. For now i have got it working with regular thermistors though.

                                      mrehorstdmd 1 Reply Last reply Reply Quote 0
                                      • mrehorstdmd
                                        mrehorstdmd @jgbowman last edited by

                                        @jgbowman

                                        Do they have Teflon insulation on the wires?

                                        jgbowman 1 Reply Last reply Reply Quote 0
                                        • jgbowman
                                          jgbowman @mrehorstdmd last edited by

                                          @mrehorstdmd i believe so

                                          mrehorstdmd 1 Reply Last reply Reply Quote 0
                                          • mrehorstdmd
                                            mrehorstdmd @jgbowman last edited by

                                            @jgbowman

                                            Teflon breaks down at ABS print temperatures. If the Teflon breaks down inside the casing, it will short to the case and that will cause erratic behavior. Check the resistance between the wires and the metal casing of the sensor- any noninfinite reading is bad.

                                            I had the same problem a week ago. Swapping in a new PT100 of the same type will fix it temporarily, until the Teflon breaks down.

                                            PT100 sensors that are going to be used in the hot-end should have fiberglass insulation on the leads. E3D's PT100 sensor does.

                                            jgbowman 1 Reply Last reply Reply Quote 0
                                            • jgbowman
                                              jgbowman @mrehorstdmd last edited by

                                              @mrehorstdmd Thank you, although switching out the pt100s doesn't even temporarily fix the problem for me, so I'm sure i'm having another issue. Will definitely look into the E3D sensors though.

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

                                                @jgbowman said in Heater Fault Troubleshooting:

                                                @dc42 It says movement before homing is not permitted.

                                                Then the M564 H0 command in config.g isn't working. Try retyping it.

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

                                                  @dc42 I tried moving it around a bit, but to no effect. Even though I put 1.20 and later in the configuration settings, config.g still says 1.17-1.19. Could this have something to do with my issues?0_1530811118179_config g2.PNG

                                                  T3P3Tony 1 Reply Last reply Reply Quote 0
                                                  • T3P3Tony
                                                    T3P3Tony administrators @jgbowman last edited by

                                                    @jgbowman the header at the top of config.g is just a comment written by the configurator.

                                                    If you go into the gcode console screen and type M564 H0, send that and then type M564. What does it report?

                                                    jgbowman 1 Reply Last reply Reply Quote 0
                                                    • jgbowman
                                                      jgbowman @T3P3Tony last edited by

                                                      @t3p3tony That got it working, thank you

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