Calling Separate Trigger Files
-
Hi,
I am trying to call a separate trigger file similar to how a pause is called by T1. I made a new trigger g-code file named "TRIGGER2.g" and to call it in the config by the command "M582 T2" but it doesn't seem to be executing. Is this because of the name of the file or should I be calling it differently?
-
@msugar It should be lower case - i.e. "trigger2.g". Also, it needs to be in the /sys directory (in case you've put it elsewhere).
-
@deckingman Both of these suggestions are already done. I think my problem is that my expansion Duex5 is not monitoring the inputs or I have a problem with my code monitoring inputs. I am trying to monitor inputs on the expansion board so that if the inputs are not met then the move motors will not be triggered.
-
@msugar A quick look at your config.g seems to indicate that you are trying to use the temperature daughter board pins (cs5 and cs6) as trigger pins. Have you been told that these should work because it seems highly unlikely to me? Suggest you try one of the spare duex5 estops instead.
-
@deckingman Would these pins be the ones labeled E_2stop, E_3stop etc.? If so these are the ones I currently have them wired into. What are the appropriate names of these pins? based on your response it seems as if I have the wrong name for the physical pin.
-
@msugar said in Calling Separate Trigger Files:
What are the appropriate names of these pins?
https://docs.duet3d.com/en/Duet3D_hardware/Duet_2_family/DueX2_and_DueX5#pin-names
