Tool length sensor and touch probe with Mesa7i76e

More
18 Jan 2019 12:29 #124397 by vmihalca
Hello,

I've bought a tool length sensor and a touch probe and I would like to wire them with Mesa7i76e then configure them in hal.
Here is the documentation of the touch probe:
webseite.sorotec.de/download/anleitungen...r_Manual_R04_ENG.pdf
It can be wired either NPN or PNP...can you tell me how I should wire this using the inputs of mesa?

The tool length sensor is here:
www.sorotec.de/shop/Z-Finder-inductiv-PN...-14mm---NC-6865.html

Does linuxcnc has inputs for both tool length and touch probes?
What pins & signals should I use in hal to capture the input from these two devices?
In axis, I will use the probe screen tab.
github.com/verser-git/probe_screen_v2/blob/master/README.md

Any help is appreciated! :)

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

More
18 Jan 2019 12:55 #124400 by rodw
The 7i76e likes PNP connections. Just wire up per the instructions and it should be fine.

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

More
18 Jan 2019 13:01 #124401 by vmihalca
To what hal signals do I need to wire the input pins in order to make the ProbeScreen to know about these sensors?

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

More
18 Jan 2019 16:06 #124404 by andypugh
LinuxCNC has only one probe input (motion.probe-input)
If you want to have two probes then you need to combine the two inputs in the HAL layer. Probably using an "or2" HAL component.

linuxcnc.org/docs/2.7/html/man/man9/or2.9.html

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

More
23 Jan 2019 20:59 #124682 by vmihalca
I have connected the touch probe to input-04 and tool length sensor to input-05
I can see changes on this inputs when I trip the sensors.

In my hal file I had:
net probe-in => motion.probe-input
But nothing was linked to probe-in, so I added the next line
net probe-in <= hm2-7i76e.0.7i76.0.0.input-04-not

With this, I was able to touch probe a part from the probe screen tab.

Where do I have to link the input-05-not pin in order to be able to use the tool length sensor with the Probe Screen.
Also my tool length sensor can only probe the height of the tool and not the diameter.

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

More
23 Jan 2019 22:23 #124688 by andypugh
The tool diameter hopefully won't change as you fit it into the spindle.
loadrt or2
...
addf o2.0 servo-thread
...
net probe-in <= hm2-7i76e.0.7i76.0.0.input-04-not
net length-in <= hm2-7i76e.0.7i76.0.0.input-05-not
net probe-in => or2.0.in0
net probe-in => or2.0.in1
net probe-or-length or2.0.out
net probe-or-length motion.probe-input

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

More
19 Feb 2019 09:09 #126758 by vmihalca
There is something that I don't understand.
I am using gmoccapy with probescreen.
Using the touch probe with probescreen I have managed to probe a part height and corner.
But I don't know how to use the tool length sensor.
If both the touch probe and tool length sensor are connected to the same motion.probe-input, how does the linuxcnc knows when to consider one and when to consider the other?

I have seen that in the tool table, I have the option to measure tool length, I assume that one should know about the tool height sensor.

I am really beginner with these so there are many missing puzzle pieces.. :)

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

More
19 Feb 2019 13:12 - 19 Feb 2019 13:13 #126767 by Todd Zuercher
Actually Linuxcnc does not see any difference between them. The same input is used (usually) for both. The difference between the two is what Linuxcnc does with the numbers it gathers from the probing and how they are used. (it is all in how the G-code and user-interface is programed.)
Last edit: 19 Feb 2019 13:13 by Todd Zuercher.

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

More
19 Feb 2019 19:43 #126783 by rodw
In a similar but related situation, I wanted to disable the probe wile I was not probing on a plasma cutter so I set a motion.digital-out-nn pin in gcode when I was probing and XOR2'ed it with the 7i76e input so it was ignored unless we were probing. You might be able to extend this technique to specify the probe type.

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

More
20 Feb 2019 22:35 #126836 by vmihalca
Hi Guys,
I have started using gmoccapy and I have an issue loading the tool from the tool editor page or from mdi using M6 T2 G43.
I get the following error:
Linear move on line -1 would exceed Axis Z positive limit.

Could you please give me some hints on this?

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

Time to create page: 0.120 seconds
Powered by Kunena Forum