Installed 4.20.1 MPG issue?

[adatesman]

Sounds like what I’ve been seeing since upgrading. Probe Enable switch/input is ignored, thereby blocking the MPG in x10 and x100 if I unplug the probe. Have confirmed the input for the enable switch responds (doing the Alt-I thing). Had been working in 4.18. Am now on 4.20.1. Will post report in a moment, probe routine running....

[swissi]

If you follow the steps in the Probe Setup Guide, the probe should work correctly.

-swissi

[adatesman]

Dunno about the OP, but I had and was working. Only thing changed was upgrade from 4.18 to 4.20.1. Input from the Enable switch toggles reliably, but MPG locks if I unplug the probe, which is a different input, regardless of whether Enable switch is on or off. Can only move in x1 on the MPG.

Will go through it again though.

[Fastest1]

Ok, So I too have a separate switch that I push if using the probe. It was not enabled as I suspected.
Pressing Alt I did confirm the switch and probe are operational. When the probe switch is pushed I do only get 1 single step action via the dial or the jog buttons. If the probe switch is off still only x1 on the dial, all speeds available thru the jog button ( I am referring to the controls on the MPG not the VCP) That just made me check the VCP. All controls on the VCP appear to work as they should however I do notice if I select x1, x10 or x100 it automatically jumps from continuous to incremental. I cant remember if it always did that. I can see an argument on that either way.
Btw the probe itself is a Drewtronics. A very nice piece especially for the price.

Yes, if you select X1, X10 or X100 it will automatically put it in incremental mode.
SO, to be clear you issue is resolved?

Marty

No, not at all. You did confirm the actions within the VCP of which I wasnt sure of, but it made sense to default to incremental when selecting steps or multiples of steps, it hasnt changed the actions of the MPG which should mimic the VCP IMO. To be clear, X10 & X100 do nothing on the MPG with any axis regardless of how the probe is switched, sensed or otherwise.

[slodat]

The MPG intentionally limits jogging to x1 when a probe is tripped. Idea is to prevent you from destroying your probe by fast jogging the wrong way.

[martyscncgarage]

Set the probe and probe detect inputs to unused and test.
Review the probe manual that Swissi posted

[Fastest1]

Dunno about the OP, but I had and was working. Only thing changed was upgrade from 4.18 to 4.20.1. Input from the Enable switch toggles reliably, but MPG locks if I unplug the probe, which is a different input, regardless of whether Enable switch is on or off. Can only move in x1 on the MPG.

Will go through it again though.

Thank You. It would appear they are reading a different thread. Mine too was working just fine on prior versions. I did change PC but not to a lesser grade at all. The other variable is the new software version.

[Fastest1]

The MPG intentionally limits jogging to x1 when a probe is tripped. Idea is to prevent you from destroying your probe by fast jogging the wrong way.

Really? So the VCP will allow different movement increments that my MPG cant access? Seems like if a protection was in place it would stop me regardless of which method of movement I chose. Furthermore it would throw a fault or comment as it does if the probe is selected or tripped. This isnt the case.
I will take a video of the entire process in the next day or so.

[slodat]

I'm explaining what I've observed using it, with my probe, yesterday. It does display I'm in x1 on the screen when the probe is tripped and try to jog with the MPG > x1.

[martyscncgarage]

Take the time to re read the probe setup manual as Swissi suggested https://www.centroidcnc.com/centroid_di ... _setup.pdf