Hi Danny,
There are different ways to solve this problem depending on what you are using as an input and where you want to have the stop routine.

If this is a true limit on the range of motion, you can use our dedicated limit switches and catch the error with #LIMSWI

Additionally, if you have a standard digital input with #ININT, or if you are monitoring a parameter, you can have a thread that monitors a parameter in a tight loop.

If you need to have an interrupt sent to a host PC, you can use the EI or UI commands to send an interrupt to the host PC and our API libraries (current generation is gclib) can easily handle the interrupt.

Regards,
Andrew

Hi!

I'm looking for documentation on User Interrupts, which seems to be a very promising feature. The command reference for the DMC-41x3 on the UI command notes that

"EI,,h must be set to a valid UDP port (set by the host, not the DMC code, is recommended)"

What does that mean? From the EI documentations description I can only extract that argument n_3 is a "Preconfigured UDP handle for interrupt transmission" (-1 disabled, 0-7 indicate Handles A-H, respectively). I would therefore assume, that a User Interrupt, e.g. would be set up like this:

EI ,,3

and triggered like this:

UI 3

But that does not seem to be the case. Can someone point me in the right direction or towards additional documentation?

Thanks,
Moritz