Z probing problems

[4.2A]

Ah, okay. But I think that if I would change z after homing (to get nearer to the sensor), the advantage of using such a sensor over determing z=0 with a piece of paper is lost.

Code: Select all

ZFastmin = exec.GetZpos() - SafeZ - 2.0;

Should be the current z heigth - 12, right?

So can I change it to

Code: Select all

ZFastmin = exec.GetZpos() - 30;

to get deeper?

[dezsoe]

No, you jog there before probing. By jogging closer to the sensor you can shorten the time of probing, because the Z has to move less with slow speed if the sensor is closer.

Of course, you can change it as you wrote, it gives more possible way to reach the sensor.

[4.2A]

No, you jog there before probing.

Yes, of course! But instead of jogging and then probing, I can jog it to zero with a piece of paper in one single step.

[4.2A]

I had some problems with the script. These problems are repeatable:

1. Probing, then it returns a z value. Then, changing the z heigth (without tool changing), probing again. It returns a different z value than the first probe!

2. Sometimes, the FastFeedrate is much higher than defined in the script (I assume it is the common z velocity). Then, the z axxis does NOT stop moving down when it gets the stop signal from the sensor. My milling tool has been damaged.

[dezsoe]

The problem is not with the macro, but something with your system. I used this macro in the past 2 years with no problem. Since I made some modifications in the code before I posted it, I ran a lot of tests with no errors. Measuring was in 0.005mm. Never had feed rate problems. So, I don't know what's happening on your machine.

[4.2A]

Anyway... thank you!

[NikolayUA24]

And I thank you!