On 4/18/23 04:50, Steffen Möller wrote:
Hello,
on https://www.facebook.com/groups/1887325441579936/posts/3264707197175080/
someone reported difficulties to get probe_basic to run because the
auto-triggered attempt to install dependencies via pip had failed. Is there an
alternative to probe_basic that is shipping as part of the regular LinuxCNC
setup?
The following is what ChatGPT has answered:
"LinuxCNC does include some alternative probing scripts that are shipped as
part of the regular LinuxCNC setup. These alternative probing scripts are written in
the Tcl programming language and can be used as an alternative to probe_basic if you
encounter issues with its installation or dependencies.
One such alternative probing script is called probe-tk.py, which is a graphical user
interface (GUI) based probing script that comes with LinuxCNC. You can access it through
the "Touch Off" button in the Axis interface of LinuxCNC. This script provides
similar functionality to probe_basic and can be used for various probing operations, such
as setting tool length offsets or finding workpiece edges.
To use probe-tk.py, you can open the Axis interface of LinuxCNC, navigate to the
"Touch Off" button, and click on it to launch the probe-tk.py script. This will
open a graphical window where you can interactively perform probing operations.
Alternatively, LinuxCNC also provides other built-in probing scripts, such as
g38.2 and g38.3, which are G-code commands used for probing operations. These
commands can be used directly in G-code programs to perform probing operations
without the need for additional Python scripts.
It's worth noting that the availability and functionality of probing scripts may
vary depending on the specific version of LinuxCNC you are using, as well as any
modifications or configurations made to your system. It's always recommended to
refer to the official LinuxCNC documentation and community resources for up-to-date
information on probing operations and available scripts."
Is there anything to correct/improve/extend on that answer?
To mind came https://github.com/linuxcnc-probe-screen/probe-screen-ng and
https://github.com/linuxcnc-probe-screen/probe-screen-ng but GMOCCAPY has its
own, right?
Is there an easy way to direct our users a bit when they look into our
documentation? I do not find any such info straight-forward to find.
Many thanks!
Steffen
I have several probing scripts written in gcode using variations of
G38.number to find hole centers, part edges, tlo's and such, been using
the G38 family of probes since the linuxcnc 2.4 days at least, possibly
even earlier, as my first install was Proctor's brain dead, which was
anything but, which was 2.1 IIRC, so g38.2 etc has been a mainstay in
linuxcnc for close to 2 decades. Someone searching for "probe" in our
docs should have that as the top of the reference list. It should also
explain that a probe is something you define in your .hal file with an
example or 2. It does not exist until an input pin is defined in the
hal file. As Picard has said many times, make it so. :o)>
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
.
Cheers, Gene Heskett.
--
"There are four boxes to be used in defense of liberty:
soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author, 1940)
If we desire respect for the law, we must first make the law respectable.
- Louis D. Brandeis
Genes Web page <http://geneslinuxbox.net:6309/>
_______________________________________________
Emc-developers mailing list
Emc-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/emc-developers
