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

    Changing pt100 to standard thermistor

    Scheduled Pinned Locked Moved
    Tuning and tweaking
    6
    76
    3.0k
    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.
    • Phaedruxundefined
      Phaedrux Moderator
      last edited by

      PID tune, send M500 in console, add M501 to config.g. done.

      Z-Bot CoreXY Build | Thingiverse Profile

      Phaedruxundefined 1 Reply Last reply Reply Quote 0
      • Atraedesundefined
        Atraedes
        last edited by

        awesome thanks, much appreciated

        1 Reply Last reply Reply Quote 0
        • Atraedesundefined
          Atraedes
          last edited by

          oh my good lord i am losing my mind...I've done everything, seemed fine, heated up hotend to 200c to do a test cube, and "M501
          Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 612C.", and then "Error: Heating fault on heater 1, temperature excursion exceeded 15.0°C", and it cools down the hotend. I know the first is a warning which i could live with but it then goes into error! Sorry I know i seem like a noob and keep asking questions but i dont get it lol, cables seem fine and ive rechecked everything, do you think there may be another fault elsewhere or is it likely the cables?

          1 Reply Last reply Reply Quote 0
          • Vetiundefined
            Veti
            last edited by

            post a picture of the temperature graph.

            also do you have the silicone sock on?

            1 Reply Last reply Reply Quote 0
            • Atraedesundefined
              Atraedes
              last edited by

              Screenshot 2021-01-12 20.32.24.png
              Yes got a sock on, and thanks for your assistance

              1 Reply Last reply Reply Quote 0
              • Atraedesundefined
                Atraedes
                last edited by

                sorry did you want me to rest the hotend and heat again first?

                1 Reply Last reply Reply Quote 0
                • Atraedesundefined
                  Atraedes
                  last edited by

                  reset the hotend even

                  1 Reply Last reply Reply Quote 0
                  • Vetiundefined
                    Veti
                    last edited by

                    when the error occured

                    1 Reply Last reply Reply Quote 0
                    • Atraedesundefined
                      Atraedes
                      last edited by

                      it happened when i was heating the hotend to 205c to do a test cube

                      1 Reply Last reply Reply Quote 0
                      • Atraedesundefined
                        Atraedes
                        last edited by

                        I've got it heated to 200c now and for the last 15mins or so and it seems ok, but this is probably the 3rd or so time its had a hotend error since i made the changes earlier today

                        1 Reply Last reply Reply Quote 0
                        • Atraedesundefined
                          Atraedes
                          last edited by

                          ok so its just done it again, temp spiked instantly up to 1600, then 1k, and lower but all within seconds, and now its almost cold...

                          1 Reply Last reply Reply Quote 0
                          • Atraedesundefined
                            Atraedes
                            last edited by

                            can i save the set up files and perhaps default the board? perhaps flash it or start again? or will that not change anything?

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

                              If it spiked to 1600C that suggests either an intermittent short circuit, or a short between the heater terminals and the thermistor wires, or ESD. These same causes would explain the error report "last error: short-circuit in sensor" you had when using the PT100.

                              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
                              • Atraedesundefined
                                Atraedes
                                last edited by

                                thanks, i guess you're right as i cant find any other fault i can see, so if the thermistor and heater terminals touch at the heater block that would also cause a short?

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

                                  @Atraedes said in Changing pt100 to standard thermistor:

                                  thanks, i guess you're right as i cant find any other fault i can see, so if the thermistor and heater terminals touch at the heater block that would also cause a short?

                                  It's not uncommon for heater cartridges to develop shorts between the element and the case, which connects the hot end metalwork to VIN. If you also get a short between the temperature sensor and the hot end metalwork, that will short the sensor to VIN.

                                  If you have a connector in the sensor cable, check that connector. Sometimes a single strand of wire escapes the crimp and touches the other one.

                                  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
                                  • Atraedesundefined
                                    Atraedes
                                    last edited by

                                    thanks, i will check that now, i only crimped that ruddy jst connector earlier and now that you mention it that seems the likely cause, many thanks

                                    1 Reply Last reply Reply Quote 0
                                    • Atraedesundefined
                                      Atraedes
                                      last edited by

                                      must have been the thermistor connector in the board, changed it and steady now for 20mins, doing the first test...

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

                                        When did it give that M501 error? Did you send M501?

                                        Z-Bot CoreXY Build | Thingiverse Profile

                                        1 Reply Last reply Reply Quote 0
                                        • Atraedesundefined
                                          Atraedes
                                          last edited by

                                          i did and it still did it, thanks anyway, the machine has found its way out the window so its all good now, thanks anyway

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

                                            You don't send M501. You put it at the end of config.g and that's it.

                                            When the duet powers on it runs through config.g to configure the machine. Then at the end it gets to M501 and then it knows to also load config-override.g, which has your tuned PID settings.

                                            So when you sent M501 when the heater was running at 200c it re-applied any saved PID values it had saved in config-override.g from when you did the PID tuning and saved them with M500. That's probably where the fault came from.

                                            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