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

    Hotend heater does not show up in DWC

    Scheduled Pinned Locked Moved
    Duet Web Control
    8
    22
    1.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.
    • foesiundefined
      foesi @cosmowave
      last edited by

      @cosmowave I use the orignal Tronxy TR leveling sensor.

      https://www.tronxyonline.com/Tronxy-Black-TR-Auto-Leveling-Sensor-p1486299.html

      I run it with 12V because I have not connected it to the 5V or the 3.3V of the IO port.

      1 Reply Last reply Reply Quote 0
      • Norderundefined
        Norder
        last edited by

        @droftarts said in Hotend heater does not show up in DWC:

        I got it to work whith a trigger value of 1000 and the usual value is 964.

        With the comment he meant his Z-Probe.
        Not the thermistor.

        DDA5X... 0.9° Stepper... Linearrails... Duet 2 Wifi... PT100 Board... Duet IR-Probe... Dyze Pro Kit up to 500°C.. etc
        Thingiverse

        droftartsundefined 1 Reply Last reply Reply Quote 0
        • droftartsundefined
          droftarts administrators @Norder
          last edited by

          @norder oops! Thanks, reading on phone screen, I missed that! I’ve deleted my reply.

          Ian

          Bed-slinger - Mini5+ WiFi/1LC | RRP Fisher v1 - D2 WiFi | Polargraph - D2 WiFi | TronXY X5S - 6HC/Roto | CNC router - 6HC | Tractus3D T1250 - D2 Eth

          1 Reply Last reply Reply Quote 0
          • cosmowaveundefined
            cosmowave @foesi
            last edited by cosmowave

            @foesi said in Hotend heater does not show up in DWC:

            Is there a way to get the normal value down to 0?

            An analog sensor needs at minimum a bit offset.

            How is the sensor configured in config.g?
            Can you exactly describe your wiring please.

            Mankati FSXT+, DeltaTowerV2, E3D MS/TC

            foesiundefined 1 Reply Last reply Reply Quote 0
            • jumpedwithbothfeetundefined
              jumpedwithbothfeet @foesi
              last edited by

              This post is deleted!
              1 Reply Last reply Reply Quote 0
              • foesiundefined
                foesi @cosmowave
                last edited by

                @cosmowave the sensor is configured like this:

                ; Z-Probe
                M558 P1 C"!io3.in" H5 F120 T6000 ; set Z probe type to switch and the dive height + speeds
                G31 P999 X-41 Y5 Z5 ; set Z probe trigger value, offset and trigger height
                M557 X50:550 Y50:550 S50 ; define mesh grid

                I have connected the signal to the io3.in of the IO_3 port. The + and - are connected to the 12V port in the center of the board.

                cosmowaveundefined 1 Reply Last reply Reply Quote 0
                • cosmowaveundefined
                  cosmowave @foesi
                  last edited by

                  @foesi For me, the config and wiring seems ok.
                  Perhaps it helps when you insert a resistor into the signal line from probe to io3 pin to get a lower value?
                  But i'm not completely sure if this will work...

                  Mankati FSXT+, DeltaTowerV2, E3D MS/TC

                  1 Reply Last reply Reply Quote 0
                  • mendenmhundefined
                    mendenmh @foesi
                    last edited by mendenmh

                    @foesi
                    "but I have put 84000 there which is the resistance I measured at around 18°C"

                    That's a really unlikely resistance for a 100k thermistor at 18C. It should be well above 100k, close to 150k, at that temperature. These thermistors are specified at 25C, and have a negative temperature coefficient, which means the resistance is higher at lower temperatures.

                    Is it possible you used your fingers to hold the meter leads on the thermistor, and got a reduced reading due to leakage through your skin?

                    Anyways, use the nominal 100k value in your calibration. It is probably very close to correct.

                    jay_s_ukundefined 1 Reply Last reply Reply Quote 0
                    • jay_s_ukundefined
                      jay_s_uk @mendenmh
                      last edited by

                      @mendenmh the resistance of normal thermistors goes down when the temperature increases. Thats what NTC means negative temperature coefficient, so the values go in opposite directions.
                      PT100/1000 are positive temperature, so both values go in the same direction

                      @foesi using 84000 is incorrect. the value stated in the firmware is the value the thermistor will read at 0 degrees, so 100000 is what you should be using

                      Owns various duet boards and is the main wiki maintainer for the Teamgloomy LPC/STM32 port of RRF. Assume I'm running whatever the latest beta/stable build is

                      mendenmhundefined 1 Reply Last reply Reply Quote 0
                      • mendenmhundefined
                        mendenmh @jay_s_uk
                        last edited by

                        @jay_s_uk You and I said the same thing, about the negative temperature coefficient. I said resistance is higher at lower temperatures; you corrected to lower at higher temperatures. 🙂

                        However, your statement about the value for a thermistor being specified at zero degrees is wrong. Most thermistors are standardized at 25C. Pt100/Pt1000 are, indeed, standardized at 0C. But it is still correct that the 100000 is the right number to have put in the file.

                        1 Reply Last reply Reply Quote 1
                        • jumpedwithbothfeetundefined jumpedwithbothfeet referenced this topic
                        • First post
                          Last post
                        Unless otherwise noted, all forum content is licensed under CC-BY-SA