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

    Automated filament switch on runout

    Scheduled Pinned Locked Moved Unsolved
    Duet Hardware and wiring
    1
    2
    151
    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.
    • berbenundefined
      berben
      last edited by

      Hi,
      currently working on my Hypercube, Duet2 WiFi with DUEX5, FW is 2.05.1.
      Running two independet Z-Motors wired according to the brilliant instructions here:
      https://betrue3d.dk/duet-wifieth-use-m584-to-autolevel-or-sync-z-axis-using-2-or-more-motors/
      Works like a charm.
      I use a E3D cyclops, hence two extruders-motors which are connected to the Duex.
      Next step: Filament runout sensors with automated switch to other filament in case of runout.
      Well, this does not work as anticipated. First I tried the M591 command with endstops C10 and C11 from the CONN_LCD connector. The fact that the Duex endstops cannot be used for M591 is beyond my understanding.
      My config.g:
      ;Filament Sensors
      M591 D0 P1 C10 S1 ; NEW! filament monitor connected to E10_stop
      M591 D1 P1 C11 S1 ; NEW! filament monitor connected to E11_stop

      That does pause the print and allows me to change the filament manually. No solution! As conditional Gcode is not available in 2.05.1, I tried to use M581, combined with trigger#.g files to do my bidding. This is where I'm stuck.

      How do I check the pin-status for an arbitrary pin (would help debugging a lot!)?
      How do I address the ENC_A and ENC_B pins from the CONN_LCD connector in terms of the M581 command?
      Is there a global pin-address register? Meaning a number by which to address any pin on the DUET unconditionally (e.g. endstops are referred to as C4 in one gcode and E0 in the other, makes no sense to me), P1 to P1000 (or any other pin-prefix) would be a much more logical address and could be used across all gcode commands. One pinout image and I'd be happy.

      My try:
      ;Filament Sensors
      ;M591 D0 P1 C10 S1 ; NEW! filament monitor connected to E10_stop
      ;M591 D1 P1 C11 S1 ; NEW! filament monitor connected to E11_stop
      M581 T8 E10 S0 C1 ; NEW! Trigger#8, Endstop 10(Extruder 0), Falling Edge, While printing SD
      M581 T9 E11 S0 C1 ; NEW! Trigger#9, Endstop 11(Extruder 1), Falling Edge, While printing SD

      This does not work and I have no idea why.

      Any ideas?
      Dirk

      1 Reply Last reply Reply Quote 0
      • berbenundefined
        berben
        last edited by

        Found in a post from 2018 that the ENC_A and ENC_B pins can be addressed as E7 and E8.

        Would still like a hardware map.

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