Dynomotion Forum

Tom,
I forgot to add the screenshot of the red feed rate slider which moves up and down when the Probe , U axis is moved either using manual jog or CNC.
No other axis has this strange behaviour.
I am only using the blue pointer to set the glue time.
Any ideas why ?
I seem to have solved the manual jog motion halt by using the limit switch actions when the probe input is set by an accidental trigger.
Regards,
Tim

Hi Tim,

The Red bar is normally used to show that actual measured spindle speed. It reads the Axis configured for the Spindle. Set the Threading Sensor Type to 0 (none) to disable this.

Normally to do Probing an axis is commanded to do an independent Jog and then a C Program loops watching the Probe input. When detected stops by commanding a Jog Speed of 0. See the ProbeDirection.c example

HTH

Tom,
Thanks for your prompt support and help as always.

I do have a c program for probing using an m code and read an input when I need to probe to set the starting position for the rest of the G code program.

I would like your suggestions regarding halting all axis motion if the probe touches / collides outside of the m code program in the forever loop.

If axis are moving in CNC or mdi Do pc halt appears to work to halt all axis motion.
I suppose I could use Stop coordinated motion and clear stop immediately ?

Your advice on how to halt axis motion if the probe triggers whilst moving individual axis using the arrow manual jog buttons on the screen would be appreciated.

I have code working using the limit switch functions but I think this then interferes with actual machine limits.

I guess I need to read if a jog button is depressed and an input triggered to cause an all axis motion halt ?

What would be the easiest way to implement ?

Having just found an input / switch debounce example in the external buttons c example I need to add debounce to the probe input pin.

Regards ,
Tim

Hi Tim,

If the Probe is triggered calling StopCoordinatedMotion() continuously should stop and prevent any motion. However it would require the probe signal to be removed to allow any motion away from the probe. There isn't any clear way to determine which axis and which direction caused the trigger. Maybe a temporary override to disable the probe to allow you to carefully Jog away from it?