nanoDLP 3.1.1 Emergency Stop not working & other alternatives

  • I am on [FIRMWARE_NAME: RepRapFirmware for Duet 3 MB6HC FIRMWARE_VERSION: 3.1.1 ELECTRONICS: Duet 3 MB6HC v1.01 or later FIRMWARE_DATE: 2020-05-19b2] in nanoDLP mode and I am unable to send an emergency stop command during a home or a move command. The command only registers after those have been completed which defeats the purpose of an emergency stop. I noticed this similarly in Marlin and RepRap mode but only for the home command or any other macro. Is there something I'm missing here?

    If this is a bug of some sort, would I be able to issue an emergency stop with a external trigger or an alternative software trigger asynchronously?
    If so, could someone walk me through how to set up the external trigger for a switch for my firmware version?
    Do I have to use endstops for the trigger or could I use another configuration (My switch will be connected to
    Could I also instead switch the state of my trigger/switch through software so I can perform an emergency stop exclusively through software?

    Ultimately my goal would be to have an emergency stop done through software due to my specific configuration.

  • Moderator

    How are you trying to initiate the emergency stop? PanelDue? DWC button? gcode command?

  • @Phaedrux G Code command over USB.

  • Moderator

    That is a limitation of the USB interface.

    From David "A limitation of USB and Telnet is that a command cannot be executed until the previous command sent over that channel has been either executed or put in the movement pipeline. Whereas emergency stop commands sent from DWC or PanelDue can bypass that."

  • Moderator

    Using a switch to trigger an estop would be the best way to go if possible I think.

  • Can GPIO or fan outputs be set asynchronously over USB? If so, I was thinking of maybe using a wire from that output back into a GPIO input port to be used as an endstop trigger to do an emergency stop.

  • Moderator

    Well I think that runs into the same limitation of USB commands being sequential in general.

Log in to reply