NC Probe and MPG Issues

[phazertwo]

Before I get started... I wanted to say that I have searched this and found the following two threads that seem to be right on point for the same issue.
viewtopic.php?f=60&t=3994&p=31925

viewtopic.php?f=60&t=4098

I have read (multiple times) the probe setup document provided by Centroid. I don't think I'm missing anything there, but it wouldn't be the first time I missed something.

I recently setup my NC probe (DrewTronics S5000LED). Probing is working great, and I'm getting better than expected results! The only issue I have is with the MPG.

Probe detect is wired to input 6, and the probe tripped is wired to input 7, like the probing document has it. The probe detect is built into the connector for the probe, when I connect it to the mill, it simply jumps input 6 to ground. Input 7 for the probe is setup for a normally closed probe, which is to say that the circuit opens when the probe hits something. This all seems to be working just fine, and like I said above, I'm getting great probing results.

The issue is with the MPG. When the probe is plugged in the MPG works like normal, no issues. It will jog in 1x, 10x or 100x. When the probe hits something, I can only move in 1x. On the VCP I can only move the opposite direction that it was traveling before the probe hit. All normal. However when I unplug the probe, the VCP works like normal (fast jog, slow jog, incremental), and the MPG will only work in 1x. If I plug the probe back in MPG works in all 3 "speeds" again. Watching the inputs, they are all flopping as would be expected when I plug the probe in, trip it, and unplug it.

In the two threads above, I believe they are having the same issue. Everyone is pointing to the NC probe, which makes sense. The NC probe looks like it's tripped as soon as you unplug the probe... but isn't that what the probe detect is for? I understand that the probe detect has other functions, but shouldn't disabling slow jog on the MPG be one of them? Or am I missing something else. Also, on of the threads above the user had no issues with an older version of CNC12, and now has this issue with 4.20.

Video helping explain... I hope... (sorry, not great at shooting video).
VID_20200322_133613 by Phazer Two, on Flickr

Also, sorry that I don't have pics of the cabinet. It's currently blocked in by another project that is immovable. I really don't see this being a wiring error, as inputs are working exactly how they should be.

Any help would be appreciated.
Thanks,
PZ

[swissi]

phazertwo,

I can't reproduce your problem with the same probe settings you have.

When you disconnect your probe, do your LED's for Input 6 & 7 look like this?

Input 6 and 7 LEDs

Capture21.JPG (8.45 KiB) Viewed 2899 times

LED 6 must be red and 7 must be green with a Line on top.

-swissi

[tblough]

The line on top of input 7means it has been "forced" closed. Input 7 IS NOT reflecting the true state of the input!

https://www.google.com/url?q=https://ww ... screen.pdf

[cncsnw]

The line on top (overscore) means that the input is inverted.

A forced input would have an underscore.

[tblough]

Thanks Marc. I noticed that just after you posted!

[phazertwo]

phazertwo,

I can't reproduce your problem with the same probe settings you have.

When you disconnect your probe, do your LED's for Input 6 & 7 look like this?


Capture21.JPG


LED 6 must be red and 7 must be green with a Line on top.

-swissi

Yes, 6 is red, and 7 is green.

PZ

[swissi]

phazertwo,

I think I found your problem. When you have only a Touch Probe and no Tool Touch Off device, the Wizard automatically configures the Touch Probe as a TT but does not automatically sync the Input State when triggered for the TT.

Go into the Tool Touch Off Page in the Wizard and adjust the Input state when triggered to "Open" too.

Let us know if this doesn't fix the problem.

-swissi

[phazertwo]

phazertwo,

I think I found your problem. When you have only a Touch Probe and no Tool Touch Off device, the Wizard automatically configures the Touch Probe as a TT but does not automatically sync the Input State when triggered for the TT.

Go into the Tool Touch Off Page in the Wizard and adjust the Input state when triggered to "Open" too.

Let us know if this doesn't fix the problem.

-swissi

Nailed it! Looks like the wizard automatically assigns the TT the same input as the probe if you don't give it it's own input. I changed it to open as Swissi said, and she is rockin'!

Just for fun, I also assigned a blank input to TT and that also fixed the issue.

Thanks for the help! This community is pretty amazing!

PZ