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

    Duet3 and Expansion board channel / trigger question

    Scheduled Pinned Locked Moved
    Duet Hardware and wiring
    2
    2
    75
    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.
    • Tinchusundefined
      Tinchus
      last edited by

      Hello. I will do some tests on a project I have and I would like to know in advance while I wait for some hardware to arrive:

      I have a duet3 board, 3.4.4 in SBC mode. All [printing is handle there.
      I want to add and expansion board. The one I bought has 3 extre stepper drivers and 6 input/output pins. My project includes:

      I will have an extra sensor connected to IO_3. My objective is that when this sensor is triggered (it is and NO sensor), a stepper motor will be used to move a tool I desgned. This stepper motor is connected to driver0.

      In my config all this will be handle by a trigger (lets say test_trigger1.g) and will move this motor some X steps.

      The expasion board is connected to the duet3 using a can cable

      My question is: if Im printing, I guess the main duet3 board will be "busy" handling the printing, si how fast it will be the detection of the sensor connected to IO_3 on the expansion board, will be instantly deteted or I can expect some "delay" beicause the duet3 board is doing the print?

      Also: when the triggered is executed, this execution of the .g file will run in parallel with the print or I can have some risk of the print being stopped for a second while executing that trigger and then the gcode will be resumed?

      Thanks in advanced

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

        @Tinchus said in Duet3 and Expansion board channel / trigger question:

        My question is: if Im printing, I guess the main duet3 board will be "busy" handling the printing, si how fast it will be the detection of the sensor connected to IO_3 on the expansion board, will be instantly deteted or I can expect some "delay" beicause the duet3 board is doing the print?
        Also: when the triggered is executed, this execution of the .g file will run in parallel with the print or I can have some risk of the print being stopped for a second while executing that trigger and then the gcode will be resumed?

        Triggers are pretty much instant, but it will depend on what is being executed at that moment. If it's a single long move, it would normally wait for that gcode command to complete. You can configure it to segment long moves into shorter moves, which would shorten the time to trigger.

        At the moment the print would pause while your trigger macro is executed. I believe part of the 3.5 firmware update will introduce multiple gcode streams, but I'm not 100% on how that will play out in practice. Keep an eye out.

        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