Probe and Touchoff

Hi all,

So my config has a tool touch-off and a separate probe.

I have figured out that they both use the Probe-input to work, however, they are both in and both NO. Now I have tried to configure to have them both by setting Probe Input, to both but the load tells me that basically I cannot have two inputs for the probe input. So now I have validated that if I comment out each of the tools separately when connected, they work very well, but looking to have it so that the tools work if both and/or if probe is attached or not. I have attached the ini and Hal files here and input would be appreciated. I noted another thread talking about this and it mentioned using MUX. I tried the adjustments, but to no luck. Can anyone give me the solution to running dual probe-inputs in the ini and io.hal files would be great.




 

If your probe contacts are normally open you could simply pass them through a Hal or2 component.

If your probe contacts are normally closed then you would pass them through an and2 component. With this arrangement you would need to have something to disable one of the inputs if one was to be used while the other is disconnected. For that you could either use a dummy shorted plug or use more Hal logic. Such as passing the signals through another set of and2s or something simular.

Also you many hardware drivers have a -not option for their inputs. You can use those or a "not" component to change the polarity of an input signal if you need to.

The mux component is more for choosing between 2 different "float" values (aka numbers), and isn't really what is needed in this application.

A diagram of the hal logic for disabling with NC inputs might look something like:

Ok all. Im stuck and going around and around in circles. So problem: Have two probes for input. Touch-off (pin0) and Probe (Pin2). But I cannot assign 2 pins to the one probe-input. In addition, want to allow for Probe (Pin2) to be rendered inactive when not connected.

Here is the error: probe2-in cannot be found. Comes up on load.

Here is the logic.
ini file has the inputs defined:
INPUT_0_0 = Probe Input
INPUT_INVERT_0_0 = True
INPUT_SLOW_0_0 = False
INPUT_0_1 = E Stop 0
INPUT_INVERT_0_1 = True
INPUT_SLOW_0_1 = False
INPUT_0_2 = Probe Input
INPUT_INVERT_0_2 = True
INPUT_SLOW_0_2 = False

The io.hal file has a set of logic to select the probe input and check the input for active low before it commences. It looks Ok to me. But I have something screwed up as it seems to be that the flipflop cant/wont work as a storage function. So not sure how to get this actioned. Any ideas?

# Inputs
#net probe-input motion.probe-input <= hm2_7i96s.0.inm.00.input-00-not
#net probe-input motion.probe-input <= hm2_7i96s.0.inm.00.input-02-not

# Define probe inputs (Pin 0 and Pin 2)
net probe1-in       hm2_7i96s.0.inm.00.input-00-not      # Tool Touch-off probe (Pin 0)
net probe2-in       hm2_7i96s.0.inm.00.input-02-not      # Edge Finder probe (Pin 2)

# Load logic components
loadrt and2 count=1
loadrt or2 count=1
loadrt flipflop count=1     # Stores Edge Finder connection status

addf and2.0 servo-thread
addf or2.0 servo-thread
addf flipflop.0 servo-thread

# Flip-flop to store the connected state of the Edge Finder (Pin 2)
net probe2-connected  flipflop.0.data <= probe2-in    # Memory for whether Edge Finder is connected
net probe2-connected-state flipflop.0.out             # Store connected state of Edge Finder

# Enable Edge Finder only when connected
net probe2-allowed and2.0.in0 <= probe2-connected-state
net probe2-final and2.0.out  # Final state of Edge Finder   # Allow probe2 (Edge Finder) if connected

# Send final signal to motion.probe-input
net motion-probe or2.0.out => motion.probe-input

I'm not sure I understand what your trying to do with the fipflop component. I don't think it is necessary. (A hal input pin remembers the value it is given with a setp if it isn't connected to a signal and hal commands like setp in the hal file are only executed once when the hal file is loaded at start up.)

I would probably use a couple of custom M-codes to enable/disable the 2nd probe. In your hal file add a line to setp the value of the and2.0.in0. and remove all other hal file references to that pin. Then in the two M-code files setp the value of and2.0.in0 to true or false to enable and disable the input.


Then to create an M101 M-code create a file containing the following, called M101 save it to your config dir and save as an executable file.
Then you can make another one to disable the probe called M102

I was trying to have this automatically set so that upon login/startup, it is set.

However, Im good with your solution. Only thought would be if I can activate with a button on screen as well. Or better yet, connected to one of the existing buttons like Probing screen. What would be the best way to achieve this? Would that be via User buttons, and if so, how is thee M101 called for use in a User button?

You can call an MDI command with a hal pin, that would then be triggered by your button output, by using a Halui MDI.
linuxcnc.org/docs/html/gui/halui.html#_mdi_2

Or if you are programming your user interface, you can program your gui button to issue MDI commands directly, such as with GadeVCP.
linuxcnc.org/docs/html/gui/gladevcp.html...d_action_mdi_widgets

Ok, so I have the M101 and M102 functioning correctly. It is set as disabled on startup and can activate and deactivate with MDI code in Probe Basic with M101 and M102.

I have used the Template Main to create two buttons. "Edge Probe - ON" and "Edge Probe - OFF", and have them connected and alternating active on selection.

BUT, I cannot find any instructions or examples on how to create the connection from the buttons to the M101 and M102 files so that they can be run on click. Does someone have an example of the process that is used to activate the connection to the M-code files created and stored?
 

Alright. So I have finally figured out what you were pointing to Todd in your links and have activated the .py script and included the M101 and M102 as MACROS into the ini file.

I did this by shifting the default templates out as it appears there can only be a single version of User Sidebar at any one time.

I noticed that the .py script does not seem to show activation of the button on click/toggle. I tried un-commenting the Style sheet, but this is a little above my pay grade.

So next steps is setting the First Macro as toggled on, and when setting the next button, setting focus on the button pushed. Can anyone help me with the .py scripting that would update the button selected in the MDI button .py script in the following link: github.com/kcjengr/probe_basic/pull/84

Thanks in advance.
I am nearly there with an operating system.