I am getting a strange defect after recently adding the UC-100 to my build. The build worked fine with a parallel port in windows 7, but I was tired of dealing with the lack of support with win7 and upgraded to win10 and added the UC-100.
After reconfiguring, setting ports/pins, motor tuning etc - the machine is running fine, the estop works, spindle under full remote control through Mach3, and the motors all operate correctly.
However, the limit switches do not function correctly. In both the UC-100 and the Mach diagnostics page, the input pins do not activate at all, even though the hardware side of the limit switch does show activation signals. When I jog the machine over to a limit switch, the machine does stop as if the limit switch was triggered, but Mach does not indicate a triggered limit, and limit override doesn't work. I have to disconnect the limit switch wire, restart Mach, and then jog the machine off the limit.
The limit switches are pepperl Fuchs proximity sensors, and as I said, they worked fine on the previous build.
I'm using pin 10 for X lim and X home, 11 for y, and 12 for A home.
I know there are some other topics related to this error, but I was not able to find any information that helped.
If anyone has some suggestions, I'm all ears, thanks.