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

      Yes you have to edit config.g and add M501 at the end.

      As I said, M500 saves SOME settings (like PID tuning or other measured values) to the file config-override.g. And M501 loads that files.

      https://duet3d.dozuki.com/Wiki/Gcode#Section_M500_Store_parameters

      Z-Bot CoreXY Build | Thingiverse Profile

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

        @Atraedes said in Changing pt100 to standard thermistor:

        gone into system in the web ui, found config.g, opened and typed M501 at the end of the file, and its asking if do i want to reset the board and apply the update?

        ok thanks, so to try solve these spurious heating faults, run my pid tune, after it shows results then go into system in the web ui, into config.g, M501 at the end of the file, and reset the board and apply the update?

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

          @Atraedes said in Changing pt100 to standard thermistor:

          Warning: Heater 1 appears to be over-powered. If left on at full power, its temperature is predicted to reach 692C.",

          That's not a heater fault. It's a warning.

          https://duet3d.dozuki.com/Wiki/FAQ#Section_M307_Heater_1_appears_to_be_over_powered_If_left_on_at_full_power_its_temperature_is_predicted_to_reach_521C

          Z-Bot CoreXY Build | Thingiverse Profile

          1 Reply Last reply Reply Quote 0
          • 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
                                            • First post
                                              Last post
                                            Unless otherwise noted, all forum content is licensed under CC-BY-SA