Hello Guest it is February 03, 2023, 08:35:21 PM

Author Topic: mc.mcJogIncStart  (Read 881 times)

0 Members and 1 Guest are viewing this topic.

« on: October 13, 2018, 04:29:35 PM »
Wondering if anyone has seen this.  I'm using mcJogIncStart to initiate an incremental jog and retrieving the increment from the system.  Everything works great as long as the number I pass to mcJogIncStart is a decimal, like .1, .01, .001.  If I pass a 1, it seems to go haywire.  It moves but not 1" and never the same distance twice.  An incremental jog from the screenset works fine using 1".   Code is below.  Anyone seen this?

mc.mcJogIncStart(inst, mc.Y_AXIS, mc.mcJogGetInc(inst, 1))

Re: mc.mcJogIncStart
« Reply #1 on: October 13, 2018, 04:41:23 PM »
Not at work to test this.  But maybe make it "1.0"  just a thought.  The decimal is very important in some aspects of Mach4.
Chad Byrd
Re: mc.mcJogIncStart
« Reply #2 on: October 15, 2018, 02:44:44 PM »
How are you setting the jog increment value?
If you are using mcJogGetInc, then you should be using mcJogSetInc to set the increment value