TWEEAKIE, Unless YOU went into teh XML and made changes there is no way that mach3 SHOULD currupt teh XML. BUT there is a bug there that causes it. It is NOT your fault.
This happens with the LPT as well.
It is a LONG STANDING BUG.
(;-) TP
what evidence should I look for of this?
I have a backup of the working config, here's the diff. I don't see anything here that seems grossly out of place (the input differences are me turning off the Y home so that the machine can be used, by manually zero'ing Y).
The OEMDROs are I assume what is included from Sieg, I built a config from the one they distribute.
Inches = original
production = the one I'm using
diffs = diffs
suggest you check the ports and pins settings for inputs that they are still set.
then have a look on the diagnostics page and see if they are tripping
(presume you have physically tested the switch with a meter...?)
Like I said, one day works, next day doesn't. Nothing had changed in the config. I did not check the switch with a meter because it still works, as far as stopping the motors when it trips. There is no 'grind' as the motors try to run past their thread limits, they stop when the limit switch is triggered as they should, but the input in mach isn't showing up. Yes I tried tripping the switches with my fingers while watching the input signals, notta on that axis, the other axes do show a signal and do work. That's why I'm thinking a bad pin on the board or the smoothstepper must be the culprit, up to there everything works, the signal just isn't making it out from there to the PC.
Switching the pins on the ESS is a good idea and could eliminate the dead pin theory, didn't think about that, thanks!