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

    A Endstop on Duex5 Not Updating 3.3RC2

    Scheduled Pinned Locked Moved Unsolved
    Using Duet Controllers
    2
    3
    153
    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.
    • DocTruckerundefined
      DocTrucker
      last edited by

      Just trying to figure out what is going wrong here. Endstop light on the board lighting as expected, M119 status report stuck at 'at min stop'. Do I need to release the endstop input from something else first?

      Config File Extract:

      ; Configure Drives
      M569 P0 S0 ; Drive 0 goes forwards
      M569 P1 S1 ; Drive 1 goes forwards
      M569 P2 S0 ; Drive 2 goes forwards
      M569 P3 S1 ; Drive 3 goes forwards                        
      M569 P5 S1 ; Drive 4 goes forwards
      
      M584 X0 Y1:3 Z2; Apply drive mapping to axes
      M584 A5 R1;
      
      ; Configure Axes
      M350 X16 Y16 Z16 A16 I1 ; Configure microstepping
      M92 X400 Y400 Z400  A41.667; Set steps per mm
      M566 X500 Y500 Z500  A200 ; Set maximum instantaneous speed changes (mm/min)
      M203 X2500 Y2500 Z2500  A5000; Set maximum speeds (mm/min)
      M201 X150 Y150 Z150  A18000; Set accelerations (mm/s^2)
      M906 X2400 Y2400 Z2400 I100  A800; Set motor currents (mA)
      
      ; Axis Limits
      M208 X0.00:550.00 Y0.00:520 Z0:94 A-720:720
      
      ; Endstops
      M574 X2 S1 P"xstop"                            ; configure active-high endstop for high end on X via pin xstop
      M574 Y2 S1 P"ystop"                            ; configure active-high endstop for high end on Y via pin ystop
      M574 Z2 S1 P"zstop"                            ; configure active-high endstop for high end on Y via pin zstop
      M574 A1 S1 P"exp.e2stop"                       ; configure active-high endstop for low end on Y via pin exp.e2stop
      

      Running 3 P3Steel with Duet 2. Duet 3 on the shelf looking for a suitable machine. One first generation Duet in a Logo/Turtle style robot!

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

        If you're using the Duex pins the correct pin name is duex.e2stop
        The exp.e2stop pin name is if you were using the expansion header pins directly. See if that works.

        Z-Bot CoreXY Build | Thingiverse Profile

        DocTruckerundefined 1 Reply Last reply Reply Quote 1
        • DocTruckerundefined
          DocTrucker @Phaedrux
          last edited by DocTrucker

          @phaedrux Thanks, I will try that later on after coffee!

          I can see what is read as e2_stop on the Duet schematic is SG_TST on the pinout of the ribbon connector on the duex5 schematic. Interestingly although this is labelled this appears to be left floating with the label not appearing elsewhere on the duex5 schematic. The only thing that comes close is each motor driver chip has a pin labelled SG_TST but according to the schematic this is purposely unconnected. Something seems amiss here, why label an input/output on a schematic and then leave it floating? Better to explicitly label it as not connected and leave the label off?

          Edit: changing to deux.... worked. Just had another issue that the A axis is no longer homing as expected. Maybe todo with changing to fff mode from CNC. Will hold off marking this complete for a while.

          Running 3 P3Steel with Duet 2. Duet 3 on the shelf looking for a suitable machine. One first generation Duet in a Logo/Turtle style robot!

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