61
Mach4 General Discussion / Re: Jogging/Pendant Interface-What is the best way? Ramblings
« on: May 29, 2015, 06:39:51 AM »
"If I use the physical Jog Increment Switch to control the increment, the Mach 4 display shows the correct setting and the "Jogging Inputs" controlled by the physical switches increment accordingly but the "Jogging" Mach display buttons increment according to the previous setting controlled by the Mach4 <Cycle Jog Inc> button. Undecided Bummer Anyone have any ideas "
My joystick uses only Jog functions and not MPG functions, so there is probably no parallel between our interfaces. My challenges were in keeping the environment separated between the screen jogging buttons and the joystick. For example the joystick would stop jogging movement if it was centered (not calling for movement) and this would also shut off the button jogging. The joystick changes the jog rate, so it was always left at zero, which is appropriate for the stick, but then the jog buttons would not work. And so on, and so on . . .
MPG is, at least in part, a separate environment, so there is less 'racing'.
Speculation on your issues; The on-screen Jog increment button and DRO seem to be reporting the current system setting, however, a single jog increment setting would logically be either a separate, undocumented variable, or it sets each axis to the same jog increment. Each axis can have its own setting, so there is going to be a disconnect between the single button and the potential multiple rates. For example, if all axis are not at the same setting, and the on-screen single button/DRO can only display one setting, which axis is it reporting?
As far as I know, there is no function to set ALL axis at once, so you might try setting ALL axis one at a time to the same inc, including your unused axis B and C. Theoretically, this would resolve any confusion in the reading of the current inc by the system 'action' Toggle Inc (or whatever it is called).
Whatever the behavior is, it would likely also apply to jog rate, or any other 'one button, multiple settings' condition.
The odd enable/disable behavior is probably being caused by errors in the original PLC code provided by Newfangled Solutions.
Since I am not using the MPG functions, this is about all the help I can offer.
Good luck with your project and thanks for sharing!
My joystick uses only Jog functions and not MPG functions, so there is probably no parallel between our interfaces. My challenges were in keeping the environment separated between the screen jogging buttons and the joystick. For example the joystick would stop jogging movement if it was centered (not calling for movement) and this would also shut off the button jogging. The joystick changes the jog rate, so it was always left at zero, which is appropriate for the stick, but then the jog buttons would not work. And so on, and so on . . .
MPG is, at least in part, a separate environment, so there is less 'racing'.
Speculation on your issues; The on-screen Jog increment button and DRO seem to be reporting the current system setting, however, a single jog increment setting would logically be either a separate, undocumented variable, or it sets each axis to the same jog increment. Each axis can have its own setting, so there is going to be a disconnect between the single button and the potential multiple rates. For example, if all axis are not at the same setting, and the on-screen single button/DRO can only display one setting, which axis is it reporting?
As far as I know, there is no function to set ALL axis at once, so you might try setting ALL axis one at a time to the same inc, including your unused axis B and C. Theoretically, this would resolve any confusion in the reading of the current inc by the system 'action' Toggle Inc (or whatever it is called).
Whatever the behavior is, it would likely also apply to jog rate, or any other 'one button, multiple settings' condition.
The odd enable/disable behavior is probably being caused by errors in the original PLC code provided by Newfangled Solutions.
Since I am not using the MPG functions, this is about all the help I can offer.
Good luck with your project and thanks for sharing!