multiple motion probe inputs

More
18 Dec 2020 07:48 - 18 Dec 2020 07:50 #192307 by alkabal
My shared solution on first page is like relay switch...


M64P1 activate the probe output
M65P1 inhibit touch probe output
Last edit: 18 Dec 2020 07:50 by alkabal.

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

More
18 Dec 2020 08:28 #192309 by roland
Replied by roland on topic multiple motion probe inputs
I also use a tool length sensor and a touch-probe. Each sensor is connected to a separate input on the Mesa card.
I use the gen_muxeric component to switch between the inputs.

To switch the inputs you need G64P0 and G63P0 in the 3D-Probe macro.

This works with NO and NC. The unused touch probe can be unplugged.

#  ---probe signal---
loadrt mux_generic config=bb2
addf mux-gen.00 servo-thread 
net probe-is-3d    mux-gen.00.sel-bit-00  motion.digital-out-00
net probe-in-wzl1  mux-gen.00.in-bit-00   hm2_7i92.0.7i76.0.0.input-30-not
net probe-in-3d    mux-gen.00.in-bit-01   hm2_7i92.0.7i76.0.0.input-31-not
net probe-in       mux-gen.00.out-bit     motion.probe-input

--
Roland
The following user(s) said Thank You: Stran_ge

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

More
18 Dec 2020 09:22 - 18 Dec 2020 09:37 #192312 by alkabal

To switch the inputs you need G64P0 and G63P0 in the 3D-Probe macro.
--
Roland


Did you mean M64 M65 ?

with my solution near similar you can also use both sensor at same time ex : probing the toolsetter with the probe :) (not really needed but really better for security)

And same as you in my macro i usr M64P1 (P2) or M65P1 (P2) for managing one other or both
Last edit: 18 Dec 2020 09:37 by alkabal.

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

More
18 Dec 2020 10:10 #192317 by Stran_ge
@roland i will try this, thank you

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

More
18 Dec 2020 10:19 #192319 by roland
Replied by roland on topic multiple motion probe inputs
alkabal, you are right G... is nonsense. Correct is M64 and M65

I was probably still a little too tired when I wrote that :unsure:

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

More
18 Dec 2020 11:50 #192322 by alkabal
is there any reason for use mux-gen rather than mux2 ?

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

More
18 Dec 2020 11:55 #192323 by roland
Replied by roland on topic multiple motion probe inputs
mux2 works with "float" signals..
we need "bit" signals here. Therefore the config=bb2
The following user(s) said Thank You: alkabal

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

More
18 Dec 2020 15:00 #192334 by Stran_ge
Thank you guys very much!
I was able to solve my problem with the method roland provided and alk mentioned earlier :)

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

More
06 Jan 2021 12:43 #194211 by zinsade


...with my solution near similar you can also use both sensor at same time ex : probing the toolsetter with the probe :) (not really needed but really better for security)...


Hello alkabal,
I agree.
I have to apologize for my poor English because I unfortunately need a translator.
In my opinion, it is important to have both sensors, the 3D probe (touch probe) and the tool measuring device (toolsetter) active at the same time. This gives you the opportunity to measure the exact position of the tool sensor with the 3D button.
I saw that you are working on a new version "probe-screen-ng".
I think that's great!
Can I make a wish about this?
When you're done with this, could you make a good installation guide for it?
Or maybe program a script for automatic installation?
I am very curious how it will continue.
With best regards from Germany
Peter

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

More
06 Jan 2021 15:19 #194235 by alkabal
Hi

I'm not good for script and doc but yes is will try to enhance that.

My actual fork is near to work fine but is very different than "official" fork, i will need to test all the change done (i hope this evening)

Br

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

Time to create page: 0.100 seconds
Powered by Kunena Forum