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

    Duet3 problem sensor homing, not happen in Duet2

    Scheduled Pinned Locked Moved
    Using Duet Controllers
    3
    8
    394
    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.
    • FBGundefined
      FBG
      last edited by

      Hello everybody!
      i am user of a lot Duet2Ethernet boards with Expansion Breakout.
      All is ok.
      Now I start with my first Duet 3 Mainboard 6HC v1.01A with severals Duet 3 Expansion Board 1XD and with raspberry.
      Everything was config perfectly and all works well, now the WebInterface is really fast!!

      My unique problem is:
      When I do homing...90%times while the axis (indifferent) move to find the sensor...the axis stop because think that the sensor was triggered....
      It always starts to move and when it moves a few cm it stops...as if the sensor had been found!!

      I use a simple sensor switch, tested with NC or NO. I use a good brand wires crossed shielded.

      I use this config:

      ; Endstops
      M574 X1 S1 P"!io3.in"           
      M574 Y1 S1 P"!io7.in"          
      

      Also I tested:

      ; Endstops
      M574 X1 S1 P"^!io3.in"           
      M574 Y1 S1 P"^!io7.in"          
      

      Also I has tested without raspberry and I test with 3.3.0 and 3.4.0 firmware version.

      Today I install a duet2Ethernet, with 3.3.0 and 3.4.0 firmware.
      Everything is absolutely perfect 100% times.

      What happen?? Any idea?

      Best Regards

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

        Remove the !

        Z-Bot CoreXY Build | Thingiverse Profile

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

          @phaedrux I think that I don't explain well....
          I must use ! if the sensor is in NO, and not use if the sensor is in NC..
          As I said, I tested in NO and NC, with same results

          The problem is not that the start to move in opposite direction...start to move in right direction but WHILE is moving to find the sensor...STOP! as the sensor has been triggered! but the sensor is not triggered!

          Best Regards

          Stephen6309undefined 1 Reply Last reply Reply Quote 0
          • Stephen6309undefined
            Stephen6309 @FBG
            last edited by

            @fbg What does M119 show? It should be untriggered when the endstop is unpressed.

            FBGundefined 1 Reply Last reply Reply Quote 0
            • FBGundefined
              FBG @Stephen6309
              last edited by

              @stephen6309 If I send M119 without press any home sensor:

              Endstops - X: not stopped, Y: not stopped, Z: not stopped, Z probe: not stopped
              

              If I send M119 with X sensor pressed:

              Endstops - X: at min stop, Y: not stopped, Z: not stopped, Z probe: not stopped
              

              Same result with others sensors

              Everything is normal....

              Ideas?

              Bes Regards

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

                Is the switch actually functional?
                Do you have continuity on the wiring?

                Z-Bot CoreXY Build | Thingiverse Profile

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

                  @phaedrux The sensors are news and perfect, also I changed for a new and happen the same.

                  Remember @Phaedrux IF I test with a duet2Ethernet ALL works properly.

                  Today I checked that show in "Objet Model->sensors->endstop", if when the axis move and stop the triggered say "yes"...
                  I can confirm that when the axis stop before touch the sensor I don't see TRUE, all time say FALSE.

                  So, if say FALSE all time, because STOP???

                  Firmware problem?
                  Duet3 Hardware problem?

                  Best Regards

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

                    Post your config.g and your homing files. Perhaps you have the homing move shorter than the axis length.

                    @fbg said in Duet3 problem sensor homing, not happen in Duet2:

                    Remember @Phaedrux IF I test with a duet2Ethernet ALL works properly.

                    This makes me think you've wired it incorrectly. Photo?

                    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