[ex-egll]

I have been using probing for a while now and it has been working fine. The last couple of days the probing is having a problem. The code I am using has been borrowed from various sources and modified:

'	VBScript For probing Left In the X direction

ProbeDia = GetUserDRO(1152)

If GetOemLed (825) <> 0 Then 		'Check to see if the probe is already
	Code "(Probe plate is grounded, Operation Aborted)" 'Display Message
Else
	Code "G4 P1"					'Pause 1 second to give time to position probe plate
	CurrentFeed = GetOemDRO(818) 	'Get the current feedrate to return to later
	Code "F4"

'	Probe left

	XNew = GetDro(0) - 3			'Probe to current position -3 inches
	Code "G31 X" &XNew
	While IsMoving()				'Wait for move to complete
	Wend
	XNew = GetVar(2000)				'Read the touch point
	Code "G0 X" &XNew				'Move back to the hit point incase there was an overshoot
	While IsMoving ()
	Wend
	Code "F" &CurrentFeed 			'Restore original feed rate
 	If ProbeDia = 0 Then
		 SetOemDro(800,0)			'Set X axis to 0
		 Code "G4 P0.25" 			'Pause for Dro to update.
	Else
		 SetOemDro(800,ProbeDia/2)	'Adjust X axis DRO for Probe Diameter
		 Code "G4 P0.25" 			'Pause for Dro to update.
	End If
End If

It works perfectly EXCEPT when I hit the "Machine Coords button on Mach3 to display the Machine Coordinates. Once displaying MC and probing the X probe will work fine when the probe is moving to the right, but if I try to probe from the right (probe moving left) the probe takes off to the right and continues until the limit switch stops the movement, similar problem with Y probing.

Any thoughts?

Barry

[ger21]

Add this before probing:



If GetOemLED(16)<>0 Then ' Check for Machine Coordinates
Code "(Please change to working coordinates)"
Exit Sub ' Exit if in Machine Coordinates
End If

[ger21]

You'll also need to add a t the beginning a:

Sub Main()

And at the end an:

End Sub

[ex-egll]

Hi Gerry, that makes sense, but why would displaying Machine Coords cause this, or does pushing the machine coords button do more than just change the display?

I guess I could also use DoOEMButton(256) in your addition to display working coordinates before it starts probing?

Barry

[ger21]

but why would displaying Machine Coords cause this

It could be one of two reasons I can guess at, but don't know for sure.
1) Being in Machine coordinates possibly changes the value of Var(2000)
2) Either the wrong value is being written to DRO 800, or no value is written to it.

It would take a little testing to figure out exactly why it doesn't work.
All I know is that most of the "good" probing code I've seen has the sample code I posted above in it.

It doesn't take much code to do some basic probing. It takes a lot more to make it reliable in all situations.

[ex-egll]

Thanks for the followup Gerry, may do some investigating when I get a spare moment

Barry