Work with probe

Hi andy,

don`t know what you mean: add a debug print to the Python handler ?

Hi Everyone,

I'm relatively new to linuxcnc and am still trying to understand how all of the connections are made and I have a more basic question regarding connections to the touch probe and toolsetter. I am using a 7i76e and have a wireless touchprobe and wired toolsetter from vers.by. I understand they both connect to probe-in and once that connection is made, the rest of the code that vers.by has written takes over. My question is if I wanted to connect the tool setting and touchprobe to, for example, pins TB6.13 14 and 15 (touchprobe OUT, touchprobe ERR (with 10k pullup to 24V), and toolsetter OUT (with 10k pullup to 24V)). What needs to be in my machine.hal file to define this connection? It seems like I need something related to something andypugh wrote a year or so ago with an or2 statement or-ing the two signals would end with something like:

loadrt or2
...
addf o2.0 servo-thread
...
net probe-in <= hm2-7i76e.0.7i76.0.0.input-13-not
net length-in <= hm2-7i76e.0.7i76.0.0.input-15-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

I'm obviously using the wrong search terms both in the files provided by vers.by and here as I am certain this is defined, but I haven't had any luck answering this definitively, yet.

Can someone point me to a thread that describes the connection of both sensors?

-Sam

I feel like there are a few syntax errors in that snippet above as well, and it should be more like:

loadrt or2
...
addf or2.0 servo-thread
...
net probe-in <= hm2-7i76e.0.7i76.0.0.input-13-not
net length-in <= hm2-7i76e.0.7i76.0.0.input-15-not
net probe-in => or2.0.in0
net length-in => or2.0.in1
net probe-or-length or2.0.out
net probe-or-length motion.probe-input

That would then connect my probe (pin 13) and my toolsetter (pin 15) via an OR to probe-or-length which is in turn connected to motion.probe-input. Do I understand then correctly that Sergei's code then only needs that motion.probe-input connected and there is nothing more that I need to connect?

And the ERR signal isn't actively used anywhere, I would have to link that up to something else (a buddy has something with a oneshot function ( github.com/PeterMue/ZX45-LinuxCNC/tree/feature/probe-screen ) to handle the error signal.

Has anyone solved the issue in psng probe screen on 2.8 where at the tool change prompt it simply stops and you have to reload? I see it was discussed a couple of pages back but I cant see a fix for it?

Regards,

Cam

Is there a further link I need to create than what is in the psng.hal file?

# Ensure all toolchange pins are free to use
unlinkp iocontrol.0.tool-number
unlinkp iocontrol.0.tool-prep-number
unlinkp iocontrol.0.tool-change
unlinkp iocontrol.0.tool-changed
unlinkp iocontrol.0.tool-prepare
unlinkp iocontrol.0.tool-prepared

net tool-change probe.toolchange-change <= iocontrol.0.tool-change
net tool-changed probe.toolchange-changed => iocontrol.0.tool-changed
net tool-number probe.toolchange-number <= iocontrol.0.tool-number
net tool-prep-number probe.toolchange-prep-number <= iocontrol.0.tool-prep-number
net tool-prep-loop iocontrol.0.tool-prepare <= iocontrol.0.tool-prepared

Hi, same problem. After clicking ok, nothing happens. If i'm waiting long enough, message window is popping up: "it is not possible to change to Auto Mode at the moment". Latest psng code from git.