Manual tool change + tool lengh touch off

More
5 years 6 months ago - 5 years 6 months ago #204713 by karlram
It seemsto be a "probing with rotating spindle" issue. I need a rotating spindle to measure the tool legth by a laser sensor. Without the S24000M3 command G38.2 works fine. But with the rotating spindle i get allways the non-probe move error.
I made a test with S0M3 -> G38.2 probing works fine. A running spindle leads always into the non-probe error.
Is there a way to run the spindle and probing?

regards
Karlram
Last edit: 5 years 6 months ago by karlram.

Please Log in or Create an account to join the conversation.

More
5 years 6 months ago #204800 by ZincBoy
I just tested this patch on my machine and I can have the spindle turning while probing without issue. A G38.2 behaves as expected when preceded by a S6000M3, a S0M3, or a M5.

One thing to be aware of is that prior to this change, the stop on non-probe move pretty much did not work. As soon as a program or macro was run, the probe input was ignored on non probe moves. If you have any noise on your probe input, you will get non-probe move errors popping up. It is possible that when your drive is on, there is some noise on the probe input?

Please Log in or Create an account to join the conversation.

More
5 years 6 months ago #204803 by andypugh
Good point. It could well be noise from the spindle on the probe input.

If the behaviour on a sim config works OK, then it isn't a problem with the patch.

Please Log in or Create an account to join the conversation.

More
5 years 6 months ago #204917 by karlram
Thank you for your advice. The noise was the problem, exactly the rotating edges of the flute. After an additional debounce of the pin the probing works like expected.
Thank you very much for your support.

Regards
Karlram

Please Log in or Create an account to join the conversation.

More
5 years 6 months ago #206380 by freisei
same problem here with laser-measurement.
github.com/LinuxCNC/linuxcnc/issues/368#issuecomment-822429577

I could add debouncing, but it seems not to be the correct way. I think the behaviour of "probe-while-moving" should be swiched on and off by user in g-code.

Please Log in or Create an account to join the conversation.

More
5 years 5 months ago #208765 by kotlikm
I am trying to run the original sub routines by orangecat for M6 and M600 but the calculations aren't adjusting appropriately for setting G43.1 Z

Is there a way I can see what the global named parameter value has been set to? I can't find a way to see what is being set to double check the math and figure out why it's not working.

Also, does variable #5063 record the value for Z in machine coordinate or the active WCS at a triggered probe?

Please Log in or Create an account to join the conversation.

Time to create page: 0.113 seconds
Powered by Kunena Forum