During ProbeApp configuration, WMPG jogging wheel quit - resolved

[cnckeith]

Can you tell me who you spoke with?

[kb58]

Domenic Pascucci. He was very helpful and took time to work with me to resolve the issue - which appeared to be that wheel pulses weren't getting through, but the jog buttons worked fine. Does the probe-protect feature affect one or both of these functions?

[swissi]

Domenic Pascucci. He was very helpful and took time to work with me to resolve the issue - which appeared to be that wheel pulses weren't getting through, but the jog buttons worked fine. Does the probe-protect feature affect one or both of these functions?

Your problem is a probe configuration problem in CNC12 and is unrelated to the ProbeApp. Looking at your report file, you have the ProbeTripped signal on Input 3 configured as NC (normally closed) but there's no ProbeDetect Input configured. So when you disconnect the TP, CNC12 sees an open Input 3 and assumes the TP has tripped. When the TP is in a tripped state, the jogging wheel on the WMPG is being disabled to protect you from jogging the TP further into the object that caused the TP to trip. You have to switch the jog speed selector of the WMPG to 1x speed to be able to jog away from the object until the trip signal goes away at which point you will be able again to jog in faster speeds with the MPG.

The jog buttons on the VCP work a little different as they allow you to jog while the TP is in trip state in all directions except the direction in which the TP was going when the trip signal occurred.

In your situation, you most likely don't even have the TP connected so CNC12 sees the Input 3 open and because there's no ProbeDetect Input configured, this is treated as a TP trip state by CNC12 which disables the WMPG jogg wheel unless it's switched to the 1x Speed.

To solve this problem, you need to configure a ProbeDetect Input that closes when the TP is connected and opens when the TP gets disconnected.

Hope this clears things up.

-swissi

[kb58]

Thank you, Swissi. I'll be able to check this out once the WMPG arrives. The jog buttons that I was referring to are on the WMPG, but I assume the same applies to those on the VCP.
Since my last post, I added a jumper to the 3D touch probe connector so that when it's plugged in, it grounds ProbeDetect, but have not yet tested it.

[cnckeith]

Domenic Pascucci. He was very helpful and took time to work with me to resolve the issue - which appeared to be that wheel pulses weren't getting through, but the jog buttons worked fine. Does the probe-protect feature affect one or both of these functions?

he must have overlooked probe protection, the MPG's are tested before they ship, very unlikely that the MPG is the problem.

[swissi]

Thank you, Swissi. I'll be able to check this out once the WMPG arrives. The jog buttos that I was referring to are on the WMPG, but I assume the same applies to those on the VCP.
Since my last post, I added a jumper to the 3D touch probe connector so that when it's plugged in, it grounds ProbeDetect, but have not yet tested it.

Read my post again above. I explained that the VCP jog buttons act differently from the WMPG jogging when the TP is in a tripped status.

-swissi

[kb58]

Domenic Pascucci. He was very helpful and took time to work with me to resolve the issue - which appeared to be that wheel pulses weren't getting through, but the jog buttons worked fine. Does the probe-protect feature affect one or both of these functions?

he must have overlooked probe protection, the MPG's are tested before they ship, very unlikely that the MPG is the problem.

I'm sure they are, but since I had it a month before this issue arose, it's irrelevant. I've made enough mistakes here that it's not necessary to invent additional issues, lol.

[kb58]

Yup, sure enough, everyone was correct! Jog is back up and running after adding ProbeProtect to the last open input port... hope I don't need more...