External Trigger in RRF3

taconite

Hello guys,

I want to configure an endstop input (e6 Stop on Duex5) as an custom Emergency Endstop for RRF3. It seems the documentation on that is not clear (at least to me). So when there is a negative edge on the switch it should run the corresponding triggerX.g file.

It seems that there are two variants
version 1:
Define the pin as an endstop and than as an external trigger. I am not sure if the T5 is correct or it should say E6.

M574 P"!duex.e6stop" S1
M581 T5 S0 R0

version 2:
Define the endstop as an input pin. And than make it to cause an trigger, but from documentation: "P Reserved, may be used in future to allow general I/O pins to cause triggers" Is the future already here?

M950 J2 C"!duex.e6stop"									  
M581 P2 T2 S0 R0

What is the proper way of doing it?

Btw is there a status for printing in the object model (so e.g. (pseudocode) if{status.printing} then ....)

taconite

any ideas?
I tried some options but non seemed to work

nhof

The second way should be more correct. I have my trigger set up in a similar way, but it's on the e0 stop on the main board.

M950 J0 C"!^e0_stop"
M581 P0 T2 S1 R1

How is your switch physically wired? As in, which connections on the board, and what switch type are connected, and how?

taconite

@nhof thank you for your reply

I wired the switch between GND and IN of the last Endstop input on the duex (Extruder 6 stop). It is a normally closed switch

nhof

Great, that gives me a good idea, try checking to see if you actually get a state transition:

Run the following command: M950 J2. This should tell you the active/inactive state of the input

Then trigger the e-stop.

Then run M950 J2 command again with the e-stop triggered, see if the state changed.

IF you're not getting a state transition, the next thing to do is to try enabling the pullup in M950 command, so change yours to M950 J2 C"!^duex.e6stop"

This should ensure it's pulled high when the NC switch is activated and the IN-> GND connection is broken. It will give you an active -> inactive transition you need.

taconite

@nhof okay this seems kind of crazy but I tried the M950 J2 command yesterday and the DWC froze - today I tried it and I get the correct output. I hit the switch --> everything is working as suspected. I am happy but confused cause I changed nothing

does someone know that:
Btw is there a status for printing in the object model (so e.g. (pseudocode) if{status.printing} then ....)
@bearer

@taconite said in External Trigger in RRF3:

Btw is there a status for printing in the object model (so e.g. (pseudocode) if{status.printing} then ....)

maybe look at https://forum.duet3d.com/post/166909 or find some inspiration for keyword to search for there

Unsolved External Trigger in RRF3