T0 trigger unlike web-interface estop - plus other issues



  • Hi I'm just raising a few issue here while using RRF 3.1.1 - the T0 external trigger doesn't behave exactly like the emergency stop on the web interface. I'm trying to set up the duet for CNC use and noticing pins are staying active. The pin assigned to turning the spindle on/off does turn off - but I am noticing other pins which I've scheduled to turn on for example for a relay module triggered dust extractor - will remain on. Can it also perform M999 reset - as this reset the pins.

    I'm also noticing that the cancel.g file is not called if for example I run gcode before the machine has been homed, or while jog has been disabled on start up. The gcode movement is prevented and the pin assigned to turning the spindle on does turn off, but I'm finding the other pins which I've scheduled to turn on during the start of a job are not turning off (such as the extractor again)

    The last thing is when the controller is reset the workspace coordinates seem to revert back to 1 or G54, and not the last one used. It would be useful if that information could be started stored when the controller is reset - with the M500 command.

    I'm trying to imagine all the silly little mistakes someone might do when using a CNC machine and safest workflow.


  • Moderator

    Can you share your configuration please?


Log in to reply