11-26-2016, 09:09 AM
I do not have nor have ever used Mach-3. But I did stay in a Holiday Inn ... Oh, never mind, the first part is true but I slept in my own bed last night.
Just thinking out loud here.
Terms:
pendant - the plug-in remote
controller - the piece between the PC running Mach-3 and the servo\stepper drivers
X+ works if it is a G-code command. This suggests that the parallel port on the PC can talk to the controller without any issues. It also suggests that at least parts of Mach-3 are able to manipulate the parallel port ... i.e. if Mach-3 is using the G-code as the source for movement commands then things work fine.
X+ does not work if the source for movement commands is the keyboard or the pendant. If it were just the keyboard or just the pendant I would suspect a hardware failure but is it both so I would initially dismiss that possibility.
Which brings us to "inside Mach-3 the 'manual stimulus' for an X+ movement is not being interpreted correctly".
Again, my knowledge is based on looking at the manual, but I'd review section "5.3 Defining input and output signals that you will use" and see if there is something that "seems to be different than the others", like an emulator turned ... "5.3.3 Emulated input signals" ... or ... "5.3.5 Defining encoder inputs" ... or maybe ... "5.6.2 Configure System Hotkeys" ... or ???
Maybe see if "6.2.3 'Move to' controls" ... a truly lame paragraph but you might be able to figure out what it really means ... to see if it is just the jog buttons that do not go X+ or if it is any manual stimulus for X+ that is being ignored.
Maybe try "5.3.8 Testing" and see if the diagnostic screen allows you to see the status of the inputs ... i.e. something lights up when the keyboard or the pendant provide stimulus.
Just thoughts off the top of my head and looking at the manual for the first time. No actual Mach-3 experience.
Arvid
Just thinking out loud here.
Terms:
pendant - the plug-in remote
controller - the piece between the PC running Mach-3 and the servo\stepper drivers
X+ works if it is a G-code command. This suggests that the parallel port on the PC can talk to the controller without any issues. It also suggests that at least parts of Mach-3 are able to manipulate the parallel port ... i.e. if Mach-3 is using the G-code as the source for movement commands then things work fine.
X+ does not work if the source for movement commands is the keyboard or the pendant. If it were just the keyboard or just the pendant I would suspect a hardware failure but is it both so I would initially dismiss that possibility.
Which brings us to "inside Mach-3 the 'manual stimulus' for an X+ movement is not being interpreted correctly".
Again, my knowledge is based on looking at the manual, but I'd review section "5.3 Defining input and output signals that you will use" and see if there is something that "seems to be different than the others", like an emulator turned ... "5.3.3 Emulated input signals" ... or ... "5.3.5 Defining encoder inputs" ... or maybe ... "5.6.2 Configure System Hotkeys" ... or ???
Maybe see if "6.2.3 'Move to' controls" ... a truly lame paragraph but you might be able to figure out what it really means ... to see if it is just the jog buttons that do not go X+ or if it is any manual stimulus for X+ that is being ignored.
Maybe try "5.3.8 Testing" and see if the diagnostic screen allows you to see the status of the inputs ... i.e. something lights up when the keyboard or the pendant provide stimulus.
Just thoughts off the top of my head and looking at the manual for the first time. No actual Mach-3 experience.
Arvid