- Posts: 48
- Thank you received: 0
Connecting a tool setter and touch probe at the same time
1 year 4 months ago #330058
by kubes
Connecting a tool setter and touch probe at the same time was created by kubes
I did not see any other input other than motion.probe-in, is this used for both a tool length setter and a touch probe? My HW will support several inputs, and I would like to have each hard-wired in, without the need to swap cables, etc.
Is there a dedicated motion input for a tool length setter? If not what is the best means to have to separate HW inputs?
Thanks!!!
Is there a dedicated motion input for a tool length setter? If not what is the best means to have to separate HW inputs?
Thanks!!!
Please Log in to join the conversation.
1 year 4 months ago #330179
by rodw
Replied by rodw on topic Connecting a tool setter and touch probe at the same time
Linuxcnc only has one probe input.
You need to devise a way to check which probing method is in use in hal.
One simple way would be to set a digital input in gcode before probing for tool height.
You need to devise a way to check which probing method is in use in hal.
One simple way would be to set a digital input in gcode before probing for tool height.
Please Log in to join the conversation.
1 year 4 months ago #330192
by kubes
Replied by kubes on topic Connecting a tool setter and touch probe at the same time
Thanks, and to confirm both tool setting and probing use "probe-input"?
If so, then I am considering using mux2 and utilizing M64 and M65 to select which digital input the tool setter and digital probe are connected to.
If so, then I am considering using mux2 and utilizing M64 and M65 to select which digital input the tool setter and digital probe are connected to.
Please Log in to join the conversation.
- juliankoenig87
- Offline
- Premium Member
-
Less
More
- Posts: 120
- Thank you received: 0
1 year 4 months ago #330207
by juliankoenig87
Replied by juliankoenig87 on topic Connecting a tool setter and touch probe at the same time
Its way more easy. You can connect two hardware inputs to the probe-input without having to choose the specific one. As long as you do not disconnect for example the 3d probe and having a active probe signal by that.
In this case you can have a workaround and setting the input of the 3d probe to a ignored one while not having a specific tool in the machine. So for example 3d Probe is tool 1 and tool 1 is not in the machine -> disable the hw input of the 3d probe.
In this case you can have a workaround and setting the input of the 3d probe to a ignored one while not having a specific tool in the machine. So for example 3d Probe is tool 1 and tool 1 is not in the machine -> disable the hw input of the 3d probe.
Please Log in to join the conversation.
1 year 4 months ago #330482
by kubes
Replied by kubes on topic Connecting a tool setter and touch probe at the same time
I took a slightly different direction. By adding a "probe-connected" hw pin, I can select probe or toolsetter. This also has the benefit of checking if the probe is connected in the probe sub routine.
As my probe uses a USB-C connector, it's not a USB device; it simply uses D- and D+ as the trigger pins. And the fact that USB-C can be flipped, I was able to use the CC pins (which are tied together on the probe's USB port) to have a hardware pin when the touch probe cable is connected.
BTW: the toolset I have is NC, so I needed to invert the pin. (I guess lcec does not support '-not')
here the sniplet of my hal:
As my probe uses a USB-C connector, it's not a USB device; it simply uses D- and D+ as the trigger pins. And the fact that USB-C can be flipped, I was able to use the CC pins (which are tied together on the probe's USB port) to have a hardware pin when the touch probe cable is connected.
BTW: the toolset I have is NC, so I needed to invert the pin. (I guess lcec does not support '-not')
here the sniplet of my hal:
Code:
loadrt mux_generic config="bb2"
addf mux-gen.00 servo-thread
...
# the UI is connected in postgui.hal
# this handles the hw, which probe is connected
# 3=probe-connected, 4=probe-trigger (NO), 5=tool-setter-trigger (NC)
net probe-connect lcec.0.Z.din.3 => mux-gen.00.sel-bit-00 motion.digital-in-00
net probe-in mux-gen.00.out-bit => motion.probe-input
net probe-trigger lcec.0.Z.din.4 => mux-gen.00.in-bit-01
net toolsetter-trigger not.1.out => mux-gen.00.in-bit-00
net toolsetter-trigger-inv lcec.0.Z.din.5 => not.1.in
Please Log in to join the conversation.
Time to create page: 0.084 seconds
