[OlfCNC]

It's easy to find out if it is the controller or the UC100.
Disconnect your MX4660 from the UC100 and connect a small piece of wire between the input pin of the UC100 and the ground (pins 18 to 25.) and check if the inputs trigger.
If they do then the UC100 input is OK.

[pilotarix]

It's easy to find out if it is the controller or the UC100.
Disconnect your MX4660 from the UC100 and connect a small piece of wire between the input pin of the UC100 and the ground (pins 18 to 25.) and check if the inputs trigger.
If they do then the UC100 input is OK.

OK... thank you for your help!
You are absolutely correct, it was easy and it seems that the UC100 is doing what he is supposed to do. I checked all INPUT pins from 10 - 13 and they all seem to work.

That leaves me with the question how to check the controller, but what else could it be??

Chris

[OlfCNC]

I think debugging the MX4660 will be the harder part, but at least the issue is now localised to that device.
First of all I would check the users manual of the device again to see if the connections you made to the MX are really OK?
Maybe it is just some misconnections. If all is connected properly then I would make some measurements,
I would sure remove the cover from the controller to see the circuit and measure from the inputs forward as the signal goes.
This could become a problem if the drive is in warranty, as opening it up might void the warranty, so after the connection check probably the best option you have is contacting the manufacturer of the MX drive to see what they will advice.