QTPYVCP and probe basic were broken due to upstream changes that prevent the use of pip to install local modules unless running from a python virtual environment (venv). The QTPYVCP section of the forum has instructions as sticky posts on how to install probe basic and the QTPYVCP both as a user and as a developer. I tested these again on a new Bookworm build today and can confirm it still works.
Regarding probing, I just found today that the QtDragon XYZ sim configurations shipped as standard with Linuxcnc 2.9 also contain similar probing features to Probe Basic. QtDragon seems to have an advantage when being displayed on a 16:9 display with resolution below 1080p. Probe basic does not scale well at lower than 1080p resolutions. Rod Webster *1300 896 832* +61 435 765 611 Vehicle Modifications Network www.vehiclemods.net.au On Tue, 18 Apr 2023 at 19:39, Chris Morley <chrisinnana...@hotmail.com> wrote: > Probe_basic is an independent project, not part of linuxcnc. I think it > would be best to report problems to them directly. > > Chatgpt is a weird way to look for information about linuxcnc IMHO and I > don't think it gave good answers. > > There are probing screens mostly based on an outside linuxcnc program Vesa > (?) probe . > Qtvcp has a version called versa probe, qtvcp also has basicprobe > undoubtedly inspired from probe basic. There is minimal documentation on > these. > > There are many others, all outside of the linuxcnc project. > > Iirc Linuxcnc also has some probing gcode routines but I don't have any > info on that. > Sent from my Galaxy > > Chris > > > -------- Original message -------- > From: Steffen Möller <steffen_moel...@gmx.de> > Date: 2023-04-18 2:51 a.m. (GMT-07:00) > To: LinuxCNC Dev Mailing List <emc-developers@lists.sourceforge.net> > Subject: [Emc-developers] probe_basic - > > 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 > > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > > _______________________________________________ > Emc-developers mailing list > Emc-developers@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/emc-developers > _______________________________________________ Emc-developers mailing list Emc-developers@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/emc-developers
