external trigger debugging

sigmatechnica

Hi
Are there any tools, gcodes or techniques to assist debugging external triggers? I am attempting to build a control panel with physical buttons and have it fire off simple tasks, such as homing, pausing, extruding a little filament etc but all triggers are totally ignored as far as i can tell and none of the trigger files ever get executed.

I'm using a Duet 2 ethernet, that is otherwise working fine. RRF version 3.4.4

trigger configs:

M950 J0 C"^duex.e2stop" ; Input 0 extrude
M581 P0 T2 S1 R0

M950 J1 C"^duex.e3stop" ; Input 1 extrude
M581 P1 T3 S1 R0

M950 J2 C"^duex.e4stop" ; Input 2 pause
M581 P2 T4 S1 R0

M950 J3 C"^duex.e6stop" ; Input 3 resume
M581 P3 T5 S1 R0

M950 J4 C"^e5stop" ; Input 4 home
M581 P4 T6 S1 R0

I have as you can see i'm using pullups and the buttons are pulling the input lines low. i have tried every permutation of inverting, not inverting, triggering on rising edges and falling edges, different endstop pin names and nothing has made any difference. I have also verified the correct signals are reaching the correct pins on they board, which are on the expansion header (i'm using the expansion header directly, without the expansion board) I have trigger{2-6}.g files in the same directory as all the other config files

I have run out of ideas to isolate where the problem may be, any sugestions would be welcomed

Thanks

OwenD

@sigmatechnica
If you're wiring directly to the expansion header on the duet2 then the pin names should be exp.e2_stop etc

sigmatechnica

@OwenD aaah right. I did actuay try it with exp. as per the pin name listing here: https://docs.duet3d.com/Duet3D_hardware/Duet_2_family/Duet_2_WiFi_Ethernet_Hardware_Overview#pin-names however the names there didn't have the underscore, and didn't work. Documentation bug there!

It does work now with the underscore and exp. Thanks!

T3P3Tony

@sigmatechnica this is really confusing to me, can you confirm you ar eusing:

exp.e2_stop

rather than

exp.e2stop

?

AFAIK it should work without the underscore as in the documentation, and the source code:
https://github.com/Duet3D/RepRapFirmware/blob/3.4-dev/src/Config/Pins_DuetNG.h

OwenD

@T3P3Tony said in external trigger debugging:

@sigmatechnica this is really confusing to me, can you confirm you ar eusing:
exp.e2_stop
rather than
exp.e2stop
?

AFAIK it should work without the underscore as in the documentation, and ash in the source code:
https://github.com/Duet3D/RepRapFirmware/blob/3.4-dev/src/Config/Pins_DuetNG.h

@T3P3Tony
I've been using the underscore.
I can't recall now whether it was because I have a problem not using it, or whether it was just because the pin names one the board images are labelled that way (and I was just lucky it worked)
In any case, I just removed all the underscores from my config and all the attached inputs, fans tacho's etc still work, so the OP's issue must have been using duex.e2stop rather than exp.e2stop??

dc42

@OwenD @T3P3Tony it should work with or without the underscore. RRF ignores underscores and dashes when comparing the names of pins, types of temperature sensor, etc.