Here is my config file, which program do you use to view it?
I use Notepad and Mach4. Here is what I see:
Motor0 is the only motor that is enabled.
The X axis is the only axis that is enabled, and it has Motor0 assigned to it.
In the homing order you have the X axis as #1 (first axis to home).
So far so good.
Looking at the "Configure->Mach", "Input Signals" tab, you have the Darwin/xlimit signal assigned to:
- Input #5
- Motor 0 Home
- Motor 0++
- Motor 0 - -
Disclaimers: I know very little about the Darwin plug-in. And I don't currently have access to our PC that has Darwin installed, so I can't test any of this. Some plug-ins totally ignore the settings in the "Configure-> Mach" dialog. I don't know if the Darwin driver ignores them or uses them. That said...
If the Darwin plug-in had a signal called "xlimit", I would presume it also has a signal called "xhome". Homing is indeed handled entirely in the plug-in, all Mach4 does it tell the plug-in "Home this axis and tell me when you are done". It is **possible** that the Darwin plug-in will only home an axis if there is an input signal assigned to its "xhome" signal, if indeed it does have an "xhome".
OR...
I see in the Darwin section of the Machine.ini file that Motor0's home signal *might* be assigned to Darwin input #29 (I'm guessing as to the meaning of the line "Motor_0_HomeSig=29"). If that really does mean the home signal is Darwin input signal #29, looking further down the INI file, "Input_29" is disabled and has no name. So, as above, perhaps Darwin is refusing to home that axis because there is no input assigned as the home signal.
You might be able to verify this by enabling the Mach4 log window. Go to the "Diagnostic" menu and select "Logging". Then click on the little play button to start the log. Now try to home the machine. See what messages show up in the log window.
Those are my best semi-educated guesses.
Bob