Probing issues with X-Carve

Yesterday all was fine, today, not so much

When trying to probe on my x-carve, I click probing, Select XYZ Probe Block, Make sure “Z” is selected and click Next, Click Next again then click Execute on Z. the prob goes down VERY slowly and will eventually error. Here is the error message: ALARM:5

Probe fail. Probe did not contact the workpiece within the programmed travel for G38.2 and G38.4.

On or near line 4:

Yesterday the probe would go down at a good rate, touch the puck, raise, then go down again much slower. Today it is moving even slower than the slow speed yesterday.

Any help would be appreciated.

sounds like probe settings not right

try checking under custom g code that after G38.2 you have a z travel far enough to go from top to bottom most say add 10 mill to travel distance

going slowly same check F after G38.2 and maybe under move tab what is Z speed set to may have changed fo some reason

i think it does have a time limit to reach probe than alarm 5 kicks in

Checked the g code settings, everything looks fine.

What I don’t understand it it was all working fantastic, then all of a sudden, it starts giving me issues.

if you up load the mage file here support or someone else may be able to figure it out

for you, byseeing whtat is inside your file

I think the issue was with the individual file (my other files worked fine) so I just deleted it and started again from scratch. Thanks everyone for the help.

I am also having this issue. Thru trial and error I found something that works to fix it but there has to be a better way. What I think is happening is that even though my units throughout the software are set to imperial (in), the probe function is working in metric (mm). If I go into the console and type command G20 to switch to imperial units it resolves the problem. The only trouble I have now is remembering to do that each time. Maybe its a problem in my process, I open a file when starting MM that is in imperial units, home the machine, move to a position to set 0 from with a touch probe, and execute the probe command. If I foget to add the G20 line to the console, the probe times out before touching the block, sounds like the same thing that happened to the OP.