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

    PT-100 temperature constantly at 2000 degrees after failure

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    11
    54
    7.9k
    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.
    • dc42undefined
      dc42 administrators
      last edited by

      The 0.2V with the Ultimaker sensor sounds plausible, the 2V with the E3D one sounds like an open circuit sensor, or else it's a thermistor not a PT100.

      If you send the M305 P1 X201 command from the Gcode Console, does it return an error message?

      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
      • CoolM8undefined
        CoolM8
        last edited by

        It is all fine when I send M305 P1 X200 or X2001, no error message whatsoever. It even turns off the fan shortly that is set to start at 40 degrees but that runs continuously now because of the 2000 degrees.

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

          What voltage do you read across the outer 2 pins of the 4 pin terminal block? It should be the same 0.2V that you get across the inner ones, with the good PT100 connected.

          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
          • CoolM8undefined
            CoolM8
            last edited by

            Yes the outer 2 pins show 0.2 V as well. I really don't get this, why did it used to work and now nothing helps? There is nothing burnt or damaged on the duet itself.

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

              My best guess is that the SPI bus isn't working but I'm puzzled that there is no error message. Do you have anything connected to the expansion connector?

              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
              • CoolM8undefined
                CoolM8
                last edited by

                Still no, as I've already said.

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

                  I suggest you ask your supplier to replace the Duet.

                  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
                  • CoolM8undefined
                    CoolM8
                    last edited by

                    Well, I've gotten the replacement for the DuetWifi, but since i haven't seen any damage at my previous DuetWifi I haven't had big hopes and thats exaclty what it tourned out. No luck and everything is still the same, giving me a reading of 2000 degrees. I have even tried the solution from here: https://miscsolutions.wordpress.com/2016/06/25/more-delta-printer-upgrades-wifi-and-silence/.
                    There was also the E3D PT100 sensor used and 4 wires were connected to the sensor wires.
                    Now everything is new: the duet, the daughter board & the PT100, so it must be the configration. I have tried the following configs:

                    • M305 P1 X200 (E3D and Ultimaker PT100)
                    • M305 P1 T100000 B4725 C7.060000e-8 R4700 X200 (E3D PT100 only)
                    • M305 P1 X201 (E3D and Ultimaker PT100)
                    • M305 P1 T100000 B4725 C7.060000e-8 R4700 X201 (E3D PT100 only)

                    what else could be the issue here?

                    1 Reply Last reply Reply Quote 0
                    • deckingmanundefined
                      deckingman
                      last edited by

                      Maybe it's because you've set P1 to use both channels (X200 and X201). If you've only got one PT100 and it's used on the hot end, all you need is M305 P1 X200. If you are using 2 PT100s, one for the bed and one for the hot end, then you have something like M305 P0 X200 and M305 P1 X201. You don't need the thermistor and ADC parameters for a PT 100 but those lines probably just get ignored.

                      Ian
                      https://somei3deas.wordpress.com/
                      https://www.youtube.com/@deckingman

                      1 Reply Last reply Reply Quote 0
                      • Dougal1957undefined
                        Dougal1957
                        last edited by

                        Can you post your full Config.g file wonder if there is a line after the M305 that may be overriding it?

                        Doug

                        Ian I think the op has tried all those lines one at a time to try and get to the bottom of the issue not all at the same time

                        1 Reply Last reply Reply Quote 0
                        • CoolM8undefined
                          CoolM8
                          last edited by

                          The strange thing is that it used to work before until it failed in the beginning of a print. Since then i only fiddled around with the M305 P1 command.

                          [[language]]
                          ; Configuration file for Duet WiFi (firmware version 1.17)
                          ; executed by the firmware on start-up
                          ;
                          ; generated by RepRapFirmware Configuration Tool on Wed Apr 19 2017 22:18:05 GMT+0200 (W. Europe Daylight Time)
                          
                          ; General preferences
                          M111 S0 ; Debugging off
                          G21 ; Work in millimetres
                          G90 ; Send absolute coordinates...
                          M83 ; ...but relative extruder moves
                          M555 P2 ; Set firmware compatibility to look like Marlin
                          M208 X0 Y0 Z0 S1 ; Set axis minima
                          M208 X205 Y205 Z205 S0 ; Set axis maxima
                          
                          ; Endstops
                          M574 X1 Y1 Z1 S1 ; Define active high microswitches
                          M558 P0 X0 Y0 Z0 H5 F120 T6000 ; Set Z probe type to switch, the axes for which it is used and the probe + travel speeds
                          G31 P600 X0 Y0 Z0 ; Set Z probe trigger value, offset and trigger height
                          M557 X15:190 Y15:190 S20 ; Define mesh grid
                          
                          ; Drives
                          M569 P0 S1 ; Drive 0 goes forwards
                          M569 P1 S1 ; Drive 1 goes forwards
                          M569 P2 S1 ; Drive 2 goes forwards
                          M569 P3 S1 ; Drive 3 goes forwards
                          M350 X16 Y16 Z8 E16 I0 ; Configure microstepping without interpolation
                          M92 X157.4804 Y157.4804 Z533.3333 E832 ; Set steps per mm
                          M566 X1200 Y1200 Z480 E120 ; Set maximum instantaneous speed changes (mm/min)
                          M203 X8100 Y8100 Z1200 E1200 ; Set maximum speeds (mm/min)
                          M201 X500 Y20 Z250 E250 ; Set accelerations (mm/s^2)
                          M906 X1100 Y1100 Z1100 E1100 I30 ; Set motor currents (mA) and motor idle factor in per cent
                          M84 S30 ; Set idle timeout
                          
                          ; Heaters
                          M143 S310 ; Set maximum heater temperature to 310C
                          M301 H0 S1.00 P10 I0.1 D200 T0.4 W180 B30 ; Use PID on bed heater (may require further tuning)
                          M305 P0 T10000 B3988 C0 R4700 L0 H0 ; Set thermistor + ADC parameters for heater 0
                          M305 P1 X200
                          
                          ; Tools
                          M563 P0 D0 H1 ; Define tool 0
                          G10 P0 X0 Y0 Z0 ; Set tool 0 axis offsets
                          G10 P0 R0 S0 ; Set initial tool 0 active and standby temperatures to 0C
                          
                          ; Network
                          M550 PUltimaker ; Set machine name
                          M552 P0.0.0.0 S1 ; Enable network and acquire dynamic address via DHCP
                          
                          ; Fans
                          M106 P0 S1 I0 F500 H1 T45 ; Set fan 0 value, PWM signal inversion and frequency. Thermostatic control is turned on
                          M106 P1 S1 I0 F500 H-1 ; Set fan 1 value, PWM signal inversion and frequency. Thermostatic control is turned off
                          M106 P2 S1 I0 F500 H-1 ; Set fan 2 value, PWM signal inversion and frequency. Thermostatic control is turned off
                          
                          ; Custom settings are not configured
                          
                          
                          1 Reply Last reply Reply Quote 0
                          • dc42undefined
                            dc42 administrators
                            last edited by

                            Something to try. Go to the GCode console in DWC and send M305 P1 X0 followed by M305 P1 X200. If it can't communicate with the chip on the daughter board, it should return an error message within a few seconds. Repeat for channel 201. If you get no errors, you can test whether the error reporting is working by trying a channel you don't have such as 202 or 203.

                            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
                            • deckingmanundefined
                              deckingman
                              last edited by

                              Taking a step back and reading through this thread, it seems that it was all working fine then suddenly failed. Since then, you've tried a different sensor, a new daughter board and a new duet board. So how about the actual wires that link the sensor to the daughter board? That's the only thing I can think of that you haven't explicitly said has been replaced.

                              Ian
                              https://somei3deas.wordpress.com/
                              https://www.youtube.com/@deckingman

                              1 Reply Last reply Reply Quote 0
                              • CoolM8undefined
                                CoolM8
                                last edited by

                                Yes the error reporting is working and i get no error when calling M305 P1 X0 and M305 P1 X200 or X201 right after that. I've tried that before.

                                Can I somehow debug the firmware? Maybe there i can find out what the issue is.

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

                                  I really don't think it's a firmware issue, because other people (including me) are using PT100 sensors without this problem. Some users see temperature spikes to 2000C, caused by interference. That's why I would really like to know how your board behaves with just the 2 links and a 100 to 180 ohm resistor connected to the terminals.

                                  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
                                  • CoolM8undefined
                                    CoolM8
                                    last edited by

                                    Ok I'm going to get a resistor next week , but I don't expect to see any difference. As i said before, i can already make sure that the resistance between 2 and 3 is of around 180 ohm and the resistance between 1 and 4 is 180 ohm as well.
                                    How can i check if the daughter-board is actually doing anything?
                                    As the UI shows 2000° even when no daughter-board is connected at all, I think the issue must be somewhere there. I just don't get it why it i the exactly the same with the new hardware.

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

                                      The UI will show 2000C whenever a temperature reading can't be obtained after several attempts for any reason. The difference is that when you send the M305 P1 X200 command, you get an error message if no daughter board is connected. You are not getting that error message, which means that the firmware is communicating with the daughter board.

                                      Perhaps we should include a 100 ohm resistor with the daughter boards, to help diagnose this sort of problem.

                                      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
                                      • CoolM8undefined
                                        CoolM8
                                        last edited by

                                        Well, all this because of almost nothing! Things like that always result in the smallest possible issue.
                                        First of all I got a E3D cartridge thermistor instead of a PT100 and the second i ordered was the V6 fixing kit with contains the cartridge thermistor as well. The biggest problem is that they look exactly the the same.
                                        The test with a 150 ohm resistor worked and gave me a result of around 130° instead of 2000°. So I ordered a real PT100 sensor and right now I'm printing all fine with the thermistor in place (logically without the daughter-board in use).

                                        Thanks for all that support.

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

                                          I'm glad you solved it.

                                          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
                                          • DjDemonDundefined
                                            DjDemonD
                                            last edited by

                                            Thought this might be the thread to ask.

                                            I got a daughterboard from T3P3 this morning (ordered yesterday so impressed).

                                            I solder-bridged the pads on RTD1 carefully. I have attached my e3d pt100 (which reads 111ohms at room temp - 30 deg C!) to pins 2 and 3 on the screw terminal.

                                            I added M305 P2 X200 to config.g
                                            and M563 P99 H2 to tool definitions (planning to use this as chamber temp monitor until I get a heater block which can accept the sensor).

                                            But no dice… 2000 deg C showing.
                                            I've checked the daughterboard is properly located over the SPI pins with the bulk of the board facing in.
                                            I've been into console and sent M305 P2 X0 - okay
                                            then M305 P99 X200
                                            "Error: failed to initialise RTD: bad response from sensor"

                                            Any ideas?

                                            Simon. Precision Piezo Z-Probe Technology
                                            www.precisionpiezo.co.uk
                                            PT1000 cartridge sensors NOW IN, just attach to your Duet board directly!

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