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

    GPIO pin assignment on 50 pin header

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    2
    3
    756
    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.
    • janbbeckundefined
      janbbeck
      last edited by

      On the help page here:
      https://duet3d.com/wiki/Using_servos_and_controlling_unused_I/O_pins

      There is a convenient table of logical pin numbers to expansion connector pin numbers for logical pins 60-63. Is there a table anywhere for the remaining expansion header pins?

      It's kind of hard to hunt down. For example, it says "Fans 3-7 are on the DueX5 and DueX2 expansion boards", but it's not clear to me at all which expansion header pins drive those. My guess is that maybe an SPI bus carries more than one of those signals and they are not visible on the expansion header directly.

      I see pins 0-7 map to heaters 0-7. I see names for Heater3-7 on the expansion headers. Does that mean I can use those as input pins using just M307 to disable the corresponding heater?

      As a feature request, it would be nice to add the logical pin numbers to the pins able to be accessed directly here:
      https://duet3d.com/wiki/Duet_WiFi_and_Ethernet_wiring_diagrams

      Thank you for your time,

      Jan

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

        The fans on a DueX are controlled over the I2C bus.

        If you don't have a DueX board then you can use the heater 3 thru 7 pins on the expansion connector as outputs.

        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
        • janbbeckundefined
          janbbeck
          last edited by

          Thanks! Can I use them as inputs as well?

          Something like in the gcode documentation:
          M583 P5 S0 ; Wait for Pin 5 to become 0

          Do commands switch pins' input/output state automatically when using G42/M583?
          Also is there a timeout option for M583 to prevent an infinite loop?

          Thanks again for taking the time!

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