I've just checked my work offsets and z g54 is set at minus 102.1950 would this be affecting the script?

I assume you are working in mm?  What number did you replace 50 with in the second edit?

Hi yes In mm I left it at 50mm as it was greater than the 40.5mm height of the tool is that not correct? very grateful for all your help in this thanks

Why do you have a work offset set at all?

maybe your motioncontroller is not supporting the usage of Var(2002).

Hi tha k you for your reply, I am unsure why there is a work offset for the Z axis, it was there when I our based the machine. Should I remove it? I have been thinking that this may be affecting the depth tool as well as a homing limit error that pops up. If you could advise that'd be much appreciated thanks

for a quick check you can replace this line of your macro (!! used twice)

ProbePos = GetVar (2002)

by
ProbePos = GetDRO (2)


Sorry that I haven't replied on this.  I tried the script again to see if it interacts with work offsets, but have found that though I have been using it for years without issues something has changed and it operates differently which may or may not be causing your problem.  Bear with me...

this is a very simple code to check that probing is basicly working:

If GetOemLed (825)=0 Then 'Check to see if the probe is already grounded or faulty
DoOEMButton (1010) 'zero the Z axis so the probe move will start from here
Code "G90 G31 Z-50 F50" 'probing move, can set the feed rate here as well as how far to move
While IsMoving() 'wait while it happens
Wend
Sleep(200)
If GetOemLed (825)=1 Then 'Check to see if the probe is hit
Call SetDro (2, 5) 'set the Z axis DRO to whatever is set as plate thickness
Sleep(200) 'pause for Dro update.
Code "G1 Z10 F500" 'put the Z retract height you want here
Code "(Z axis is now zeroed)" 'puts this message in the status bar
Else
MSGBox "probe not hit !"
Exit Sub
End If
Else
Code "(Z-Plate is grounded, check connection and try again)" 'this goes in the status bar if aplicable
Exit Sub
End If


Sorry that I haven't replied on this.  I tried the script again to see if it interacts with work offsets, but have found that though I have been using it for years without issues something has changed and it operates differently which may or may not be causing your problem.  Bear with me...

Thanks very much appreciate it