Hello Guest it is March 28, 2024, 08:05:06 AM

Author Topic: G31  (Read 2559 times)

0 Members and 1 Guest are viewing this topic.

G31
« on: March 14, 2017, 04:27:43 PM »
Thought I would measure to see what kind of consistency I was getting from my probe strikes.

I put the following code in a button:

 mc.mcCntlGcodeExecuteWait(inst,'G31 X0 F0.5')  -- First slow strike
 r1,rc=mc.mcAxisGetProbePos(inst,0,false)
 r2=mc.mcAxisGetPos(inst,0)
 mc.mcCntlGcodeExecuteWait(inst,'G01 X.3 f0.5')
 mc.mcCntlSetLastError(inst,string.format('%1.4f : %1.4f : %1.4f',r1,r2,r1-r2))


The difference between the position in the dro and the probe strike position is consistently .0080 or .0079

While probing the dro's don't change at all, is that how it should be?

Each time I execute it the positions change:

.1958 : 0.2037 : -.0080
.2036 : 0.2037 : -.0080    - creep of 0.0078
.2115 : 0.2195 : -.0080    - creep of 0.0079

Each time the probe beginning position is closer to the contact position even though I start at .3 and return to .3

Its as if the machine position is adjusting automatically for the difference in strike versus end.  Is it supposed do that?

I have checked my couplings and they are secure and I don't believe I am losing steps.

I am using pmdx411 and their plugin is fairly new and I am using it with m4turn.

Before I go to the pmdx forum I want to confirm that this is not normal behavior.

Thanks,

RT


Re: G31
« Reply #1 on: March 15, 2017, 09:40:01 AM »
Update,

Ran straight from the MDI:

g1 x.4 f.5
g1 x.3

ran 10 times and the positioning was unchanged

ran straight from the mdi:

g31 x0 f.5
g1 x.3

Ran once and hung until I pressed the stop button

Ran straight from the mdi:

g1 x.3
g31 x0 f.5

ran 5 times and each time the x.3 was closer to the centerline by approx .008

Thoughts?

RT
Re: G31
« Reply #2 on: April 02, 2017, 08:31:11 AM »
I have an ess mocontrol board and the code you used works perfectly for my machine!  Your code just catapulted my understanding a leap forward.  That use of the error box is great!

I now can move on with learning how to probe and understanding Lua etc using my own code with G31!!

I guess you have an issue with Pmdx!
Re: G31
« Reply #3 on: April 02, 2017, 11:21:40 AM »
However, I can't get the probing G31 to work more than 2 times in a row.  Just posted that code.
Re: G31
« Reply #4 on: April 02, 2017, 01:35:02 PM »
Working fine now but not sure what I did to fix it!