but just for the hell of it can you post your macro please?

Ian

Everything is working great with 28.1 now. The plate height check is very fast.

Here is my macro

PierceHeight = GetUserDRO(1000)
CutHeight = GetUserDRO(1001)
PierceTime = GetUserDRO(1002)
CurrentZ = getDRO(2)
While IsMoving()
Wend

If GetOEMLed(825) = 0 Then
Code "G28.1 Z" & CurrentZ
While IsMoving()
Wend
Code "G92 Z0.0"
While IsMoving()
Wend
Code "G0 Z" & PierceHeight
While IsMoving()
Wend
DoSpinCW()
While Not isActive(Input1)
Wend

Code "G4 P" &PierceTime 'Pierce Delay
While IsMoving()
Wend
Code "G0 Z" & GetUserDRO(1001)
While IsMoving()
Wend

Else
Code "(Torch is On Surface Hit STOP and Fix)"
End If   

Glad you got it shooting sparks like you want it.

(;-) TP

It shoots sparks, but not quite like I want since I get to start a new battle with the high freq plasma noise interfearance ... yay

Sheilding and grounding are your best buds

(;-) TP

So G28.1 fixes it.  Can we conclude that there is a problem with G31?  for whatever reason...maybe a config setting...on my machines, Z axis G31 accel follows the X or Y axis.  If memory serves, it follows the X.   I was hoping to see a G31 fix come out of this thread.

YEP, I will agree there is a problem with G31 as you stated(;-). You may want to run this by Andrew for further testing before they will consider a fix.

The main reason I would never had seen it is I run all the axis's at the same parameters for accel/velocity.

Good Job, (;-) TP

The main reason I would never had seen it is I run all the axis's at the same parameters for accel/velocity.

So do I.  Every now and then I play around with the accel settings.  That's when I notice it.  Other than some random testing, I run all axes at 30.  Stirling tested this and said it was fine on his machine...Z axis G31 followed the Z axis accel settings.  That's why I was wondering is it was a config setting.

 I am not sure I know of any config setting that would effect it that way. I do not have a machine setup here at the house to test probing with Mach3 and Vista64 do not get along (;-) and will not simulate correctly. SO I cannot say one way or the other. BUT looking at the test vid would indicate there IS a problem. You can see and hear the difference. I used a sound analyser to see the ramp and decay of the sound the motors made.
Many years of loud noise leaves you half deaf in many freq ranges so I have to SEE the sound sometimes.

(;-)TP

Certainly a strange one. I too normally run all three at the same settings but played with them to test this out. Like I say - all seemed well. Just a shot to nothing - you guys haven't got/had anything going on with swapAxis() by any chance? (clutching at straws here).

Ian