forum.cncdrive.com

Hello,

I have 2 probes, one with "Active High", another with "Active Low". In diagnostics tab everything is fine, I see both probes are properly set and working. But in actual motion (G31 or manual jog movement with Safe probe mode on) it doesn't work, second probe uses "Active Low" flag from 1st probe, not his own.

This is with latest 1.2037 version

Hi,

Could you please post your profile file?
Which controller are you using?
What does not working means? Is the probe not stopping the movement or the movement does not start however the probe is inactive?
Is the issue happen with both probe inputs or the 1st or the second one?

I've quickly tested with a UC400ETH with Probe1. set to port 1 pin 10 and active low and probe2. set to port 1 pin 15 active high and set the JSP mode on.
I've executed a few random G31 codes and joggings and triggered first the probe1. and after the probe2. input and the probing movement always started and stopped on the probe trigger.
So, yet I do not see the issue, some more informations like your profile file and more detailed description about the problem would be helpful.

Hi,
I'm using UC300 USB
Yes, the jog movement does not start, however both probes are inactive.


I have one probe with active high on 15 pin. It works fine,
yesterday I've made a second probe on 13pin with active low state.

I've tried dufferent setups -
1: (first probe only as a probe1, works fine) -
Probe 1 : pin15, port3, active high
Probe 2: pin0 (disabled)

2: (second probe only as a probe1, works fine) -
Probe 1 : pin13, port3, active low
Probe 2: pin0 (disabled)

3: (both probes as probe1 and probe2, don't work) -
Probe 1 : pin15, port3, active high
Probe 2 : pin13, port3, active low
The jog movement does not start, until I press on probe2.

Hi Ivan,

Thanks for the information.
I will test the mentioned configurations asap.

We've managed to debug and correct this issue today.
The problem was only with the UC300USB controller and with the 2nd probe input.
Accidentally the 1st probe input's active low setting was used for the 2nd probe also, so different polarity could not work.
The issue was corrected and will be OK in the next release.

Thank you!