Probe error

[grsabourin]

Hi,

I just bought a machine that is running on Mach 3 with MSM. I have tried to use the probe but I have partial result. If I start the machine and immediately start probing it is work and I'm able to do probing sequences to get edges and surfaces. On the other way if I follow the natural process and I begin by loading my g-code program (this g-code is in metric and probably the machine is set natively in imperial) when I start a probing sequence I get an error like the probe ball size is larger to the step size. It is like something is wrongly converted to imperial to metric. Is someone know where this problem may come from.

Thank you

[DaveCVI]

Hi,
I'm not sure what error message you are seeing.
Please post
1) what you are doing when the error happens,
Are you using a MSM built in probe operation ? If so which one?
Are you trying to go G31 from gcode? if so, please provide a short gcode code sequence that causes the problem.
2) the exact wording of any error message, or even better a screen shot of the message.

Dave

[grsabourin]

Ok I will post more details soon

[grsabourin]

Hi
This is more details about the error I get when I use the probe

The error : Step Off width <= EffProbRadius + MinProbeDistance, Op Canceled

1) what you are doing when the error happens,
MSM version : 2.1.6

1 - I start Mach3 (MSM )
2 - I go directly to WC Offset and select Probing
3 - I load my probing tool ( T250 M6 )
4 - Put the axis in position for probing the edge ( find top surface and move on the side to find the side )
5 - It is working perfectly

6 - I load my g-code in metric
7 - Go back to WC Offset and select probing
8 - put axis in the same position for probing an edge
9 - Start probing the edge
10 - process stopped and I get the error

Are you using a MSM built in probe operation ? If so which one?

Yes I'm using the MSM native probing system

Are you trying to go G31 from gcode? if so, please provide a short gcode code sequence that causes the problem.
No I do not use G31 but I do not know how to use it.

This is the beginning of the G-code program I have loaded

Code: Select all

T3  D=9.47 CR=0. - ZMIN=-3.5 - FLAT END MILL)
G90 G94 G91.1 G40 G49 G17
G21
G28 G91 Z0.
G90

(2D ADAPTIVE1)
M5
M9
T3 M6
S3000 M3
G54
M8
G0 X96.058 Y11.761
G43 Z15. H3
Z5.
Z-1.606
G1 Z-2.553 F400.

2) the exact wording of any error message, or even better a screen shot of the message.

This exact error wording appearing in the top message line : Step Off width <= EffProbRadius + MinProbeDistance, Op Canceled

Thank you for your help

[DaveCVI]

Hi.
The next step is to find what the values are of the items in the error message.
1) Step of width: what is the value of the DRO on the probing "step off width DRO (on the probing page, in the parameters panel)?

2) what is the diameter of the probe that is in the tool table?
Go to the tooling page, use the tool tabel browest panel (upper right) and set the tool # to your probe tool (250 I think you said). What is the diameter value of the probe tool?

2a) what units is the tool table diameter set to?
(you can use the "edit" button to see the tool dialog that shows this).

2b) what is the diameter wear value? Is it = 0?

3) the minimum probe distance is a small number (0.010 inches).

so we are mostly interested in what the other two values are.

Dave

[grsabourin]

Thank you. I get information and gives you news

[grsabourin]

Hi

I have checked parameters (Probing Op parameters) suggested in the previous post. Clearly the issue is the parameters are simply not converted from imperial to metric. I simply convert these values from imperial to metric. Also I have adjusted some (speed) because the operation was to slow compare to the operation done with imperial units. Now I'm able to probe after loading the metric G-code.

Thank you for your help

[DaveCVI]

Hi,
Mach assumes that all tool table values are assumed to be in "Setup units". This is independent of the use of metric or imperial units for motion (G20/G21). G20 and G21 control the units within a gcode program for coordinate system motion only; they do control the interpretation of tool table values.

MSM allows you to enter tool table values for diameter in either metric or imperial units as a "ease of use" feature for a human. However, the internal value is always stored in the machines setup units. It is Mach that gets the values at run time and makes the assumption about the units for tool table values.

As you have figured out, the operator is responsible for setting up the tool table to match the gcode motion mode.

Dave