Forum Menu

Second Probe

More
5 years 9 months ago #194456 by JohnnyCNC
Replied by JohnnyCNC on topic Second Probe
I'm using multiple or2s so ignore the limit switch ones. This setup is working for me.

loadrt or2 names=or2.x_limit_switch,or2.y_limit_switch,or2.z_limit_switch,or2.probe_in
addf or2.probe_in servo-thread
addf or2.x_limit_switch servo-thread
addf or2.y_limit_switch servo-thread
addf or2.z_limit_switch servo-thread

#Touch-plate
net deb-tplate-in debounce.0.0.in <= hm2_5i25.0.7i76.0.0.input-05-not
net tplate-in debounce.0.0.out
net tplate-in => or2.probe_in.in0

#3d Probe
net deb-probe-in debounce.2.0.in <= hm2_5i25.0.7i76.0.0.input-11-not
net probe-in debounce.2.0.out
net probe-in => or2.probe_in.in1

Please Log in or Create an account to join the conversation.

More
5 years 9 months ago - 5 years 9 months ago #194460 by alkabal
Replied by alkabal on topic Second Probe
I copy past again, i use this config all the days at this moment.

the two pass option is imo a good things allow you to add more or2 and2 and other in other place in the file or in other hal llike postgui
Code:
# --- probe signals separated for probe + toolsetter with status checking and possible bypass from macro --- # --- some link for securing probe are done inside spindle and orient config-- loadrt or2 names=or2.combined-touch loadrt and2 names=and2.combined-probe loadrt and2 names=and2.combined-setter loadrt not names=not.combined-probe-on loadrt not names=not.combined-setter-on addf or2.combined-touch servo-thread addf not.combined-probe-on servo-thread addf not.combined-setter-on servo-thread addf and2.combined-probe servo-thread addf and2.combined-setter servo-thread net touch-probe-not-in <= motion.digital-out-01 net touch-probe-not-in => not.combined-probe-on.in net touch-setter-not-in <= motion.digital-out-02 net touch-setter-not-in => not.combined-setter-on.in net touch-setter <= [HMOT](CARD0).7i76.0.0.input-14 # probe is NC NPN with pullup #or #net touch-setter <= [HMOT](CARD0).7i76.0.0.input-14-not # probe is NC PNP net touch-probe => and2.combined-probe.in0 net touch-probe-on-psng <= not.combined-probe-on.out # M65 P1 activate / M64 P1 inhibit net touch-probe-on-psng => and2.combined-probe.in1; net touch-probe-and2-psng <= and2.combined-probe.out net touch-probe-and2-psng => or2.combined-touch.in0 net touch-setter <= [HMOT](CARD0).7i76.0.0.input-15 # setter is NC NPN with pullup #or #net touch-setter <= [HMOT](CARD0).7i76.0.0.input-15-not # setter is NC PNP net touch-setter => and2.combined-setter.in0 net touch-setter-on-psng <= not.combined-setter-on.out # M65 P2 activate / M64 P2 inhibit net touch-setter-on-psng => and2.combined-setter.in1 net touch-setter-and2-psng <= and2.combined-setter.out net touch-setter-and2-psng => or2.combined-touch.in1 net touch-probe-combined <= or2.combined-touch.out net touch-probe-combined => motion.probe-input

edited message for clarification
Last edit: 5 years 9 months ago by alkabal.

Please Log in or Create an account to join the conversation.

More
5 years 9 months ago #194555 by mrmike
Replied by mrmike on topic Second Probe
The issue I seem to have with this setup is the probe being tripped anytime \I have the NC probe plugged in. I checked the hal pins on the HAL configuration window, and the probes show red until I trip either of the probes. When I unplug the NC probe, the Z-axis moves freely, and will home.
I by-passes the wiring from the NC probe in case there was some interference, and changed the gpio.
When I use M65/M64 to turn off the NC probe, all is well, when I activate that probe, the Z-axis
I have used the above script, only changing the and2 and not to one line for now.
Any suggestions?

Please Log in or Create an account to join the conversation.

More
5 years 9 months ago - 5 years 9 months ago #194558 by alkabal
Replied by alkabal on topic Second Probe
It seem you need to use something like [HMOT] (CARD0) .7i76.0.0.input-14-not

Maybe your probe is NC but it is PNP or NPN can do the difference !

and2.combined-probe.in0 need to be FALSE with probe connected and TRUE when triggered or unconnected
and2.combined-setter.in0 need to be FALSE with setter connected and TRUE when triggered or unconnected

so you need "your-input-pin-not" or use a not component
Last edit: 5 years 9 months ago by alkabal.

Please Log in or Create an account to join the conversation.

More
5 years 9 months ago #194756 by andypugh
Replied by andypugh on topic Second Probe

mrmike wrote: Any suggestions?


Have a look near the end of the similar thread previously linked to where I show a custom HAL component that latches the state of up to 8 probe inputs when the machine is turned on (F2) and then drives the motion.probe-in pin whenever is sees a _change_ in any input.

Please Log in or Create an account to join the conversation.

More
5 years 4 months ago #212780 by hoffb77
Replied by hoffb77 on topic Second Probe


Easy and Cheap....Plus it keeps debris out of the jack.

Please Log in or Create an account to join the conversation.

Time to create page: 0.189 seconds
Powered by Kunena Forum