Allright, bridging the Top Pin (NC on the PCB) to the bottom one (io3.in) did the trick.

I had to invert the signal but other than that no changes were necessary on my firmware configuration.

For future reference and anyone who is trying to do something similar:

M950 J1 C"!^100.io3.in" ; Tool1 docking detection GPIO setup

Is the command I use now.

@georgiad AWESOME!!!

@Phaedrux I ordered a board and expect it to arrive by October. If I don't manage to find the offending change by a couple bisecting builds, I'm happy to send it over to Duet3D for inspection.

@phaedrux said in Duet 2 trigger device from Gcode:

take a look here

https://duet3d.dozuki.com/Wiki/Using_servos_and_controlling_unused_IO_pins

Thanks for the information. I must have read this document several times already. It summarizes the method for defining pins well.

I think I'll use the CS5 pin to ground for my application. The hiccup I've had in the literature is finding out what the supplies voltages are. Based on the referenced document, there is no PWM and I believe the output is 3.3V when triggered for CS5 pin.

@justus2342
There is a possibility that actualValue does not achieve the requestedValue which is why I chose that logic.
However @dc42 may have to confirm the details.

(job.file.fileName!=null) will be true if a print job is loaded.
This stops the code from executing if the machine isn't printing.
As I said, without that there is a possibility (depending on your code) that you could send the system into an endless loop after a print finished and the fans shut down thermostatically.
This is also why I tested temperature.

if its a relay module with a transistor to drive the coil, then maybe check the markings on the relay to see if its a 12v coil? it could get a bit toasty if fed 24v