multiple motion probe inputs

More
16 Dec 2020 20:16 #192175 by tommylight
Why not use the "NOT" hal component on both the inputs?
That way even when you disconnect them, to HAL nothing has changed.

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

More
16 Dec 2020 20:28 - 16 Dec 2020 20:30 #192181 by Stran_ge
i did use not on both inputs since they are normaly closed switches.
hm2_7i76e.0.7i76.0.0.input-08-not
hm2_7i76e.0.7i76.0.0.input-09-not
Last edit: 16 Dec 2020 20:30 by Stran_ge.

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

More
16 Dec 2020 20:45 #192188 by tommylight
Use the NOT component to invert those inputs:
net invert_pin_1 ==== hm2_7i76e.0.7i76.0.0.input-08-not >> not.0.in
net inverted_out_1==== probe-in << not.0.out

Something like that. Added = <> so it is easier to follow.

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

More
16 Dec 2020 21:02 #192191 by Stran_ge
hmm the official documentation for the NOT component is very sparse...

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

More
16 Dec 2020 21:08 #192194 by Stran_ge
How would that change my Situation, i already invert my inputs with -not so im confused what it would change to invert them again (back to normal state)

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

More
16 Dec 2020 21:10 - 09 Jan 2021 02:35 #192195 by alkabal
Imo this change nothing

You need to add a logic for deativate the output from Or2 if probe is see as unconnected

I have copy past my config that is close to be able to do that using M64 M65

maybe something like this can work :


# --- probe signals separated for probe + toolsetter with status managing (beta)
loadrt or2 names=or2.combined-touch
loadrt and2 names=and2.combined-probe
addf or2.combined-touch servo-thread
addf and2.combined-probe servo-thread


net touch-probe <= [HMOT](CARD0).7i76.0.0.input-14-not
net touch-probe => and2.combined-probe.in0
net touch-probe-on-psng <= [HMOT](CARD0).7i76.0.0.input-14
# i think this is too easy and need to add some timedelay else the probe stop to work if you simply use it
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
net touch-setter => or2.combined-touch.in1

net touch-probe-combined <= or2.combined-touch.out
net touch-probe-combined => motion.probe-input

100% untested and 100% sure that need more to allow working
Last edit: 09 Jan 2021 02:35 by alkabal.

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

More
16 Dec 2020 21:31 #192197 by Stran_ge
not sure what this part means
[HMOT](CARD0)

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

More
16 Dec 2020 21:52 #192199 by tommylight

not sure what this part means
[HMOT](CARD0)

HMOT section in the ini file, CRAD0 name <<< used for Mesa boards so in case of changing the card from say 7i96 to 7i76E there is only one entry that needs to be changed, not every line in hal pertaining to that card.

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

More
17 Dec 2020 19:27 #192271 by footpetaljones
I may be speaking blasphemy, but a software solution might not be the best method. At a former employer we had the same problem with Renishaw tool setters and spindle probes. I wired both probe triggers to a relay (one to the NO contact, the other to the NC contact), whenever we wanted to use the spindle probe, fire an M code to turn the relay on, probe whatever we needed, fire another M code to turn the relay off. When the relay is off, the tool setter can be used for tool setting or tool breakage detection.

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

More
18 Dec 2020 06:57 #192306 by Stran_ge
yeah, i was going to do this if noone knew a good software solution

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

Time to create page: 0.121 seconds
Powered by Kunena Forum