User Install for Probe Basic Py3 (For Machine Control)

Cool. thanks. i will be trying this after dinner.

Just attempted to do a clean install and it seems like the new Repo links are broken!
Do we still have the google drive link?
links in question:

repository.qtpyvcp.com/repo/probe-basic-...5.3-3+81.dev_all.deb

repository.qtpyvcp.com/repo/qtpyvcp-dev/...4871882e.dev_all.deb

repository.qtpyvcp.com/repo/hiyapyco/pyt...pyco_0.5.1-1_all.deb

Thanks in advance
Kris

go back to the first post. they changes the page and have new links

I ran into a problem trying to run Probe Basic Lathe. I installed Probe Basic following the instructions in the machine control install thread. I can run the probe basic mill sim, but the probe basic sim version throws the error:

Any tips on how to get the lathe GUI to work? Thanks!

hello ottoragam!

thanks for the report, I just checked it was broken
i just updated probe-basic-latthe to python3-probe-basic_0.5.3-88.dev_all.deb

you can find it now in the docs or this link
repository.qtpyvcp.com/repo/probe-basic-...0.5.3-88.dev_all.deb

thanks

Thanks TurBoss. I uninstalled the old package and installed the updated one and I can launch both the simulated GUI and my own configuration now.

So, I was going to make a post, but I did manage to solve this, but wanted to post this here incase anyone else was having a similar issue.

-  What Linux OS being used including kernel type?

I am doing a test run in a virtualbox vm before I do a real install on my linuxcnc box, since it's currently working well on axis from the linux.org 2.9 install.

Installed Debian 12.4 net version (also tried the dvd iso the first time as the machine will rarely have internet connection, same issue)
Kernal 6.1.0-17-amd64

-  What version of Linuxcnc is installed?

2.9.0~pre1+git20230208.f1270d6ed7

-  What version of QtPyVCP and Probe Basic is installed?

QtPyVCP 0+unkown,

Qt Info
version 5.15.8

-  How did you install Probe Basic? Quickstart guide? Dev Guide? 

kcjengr.github.io/probe_basic/quick_start.html

-  Have you gone through your ini and hal files and compared to the sim config files to make any changes needed?

-  Have you added all of the necessary files in your config folder that probe basic needs to run?

-  Have you tested the sim version to see if the problem exists there also? (if the sim functions properly, it is a good indicator your issue is in your config)

Does not apply

Attached a screenshot, but basically up until "sudo dpkg -i python3-qtpyvcp_4.0-45.dev_all.deb" everything goes smoothly. It's at this point it says package python3-distro is not installed. However you can see when I type in python3 into terminal it returns python 3.11.2

So I ran "sudo apt --fix-broken install" and reran the command with success. So it seems something is broken from a fresh install. I did run sudo apt update first thing.



 

the best method to use is the apt install from the quickstart guide, this will be the easiest to maintains and update going forward.

gents,
i would like to get some advise please. i have performed now a 2nd install, i tried APT ansd DEB also. i have an issue that :- the startup of probe basic takes "ages" compared to qtdragon, i mean like 30-40 sec( of course i could live with that, i just saw on my friend install it takes max 5sec.
- i can not reset estop. as i click on it timer froze up to 5-7 sec, nothing happens. the logic in hal was working fine with qtdragon so i assume there is nothing wrong there. 
1 more thing that is still very confusing me, that in the configuration guide, "Step 2: Copy required files" it says "Copy the required files from the probe_basic_machine_config_setup_files folder to the Pncconf config folder." but ther are 2 folders, machine_config_setup_files folder AND probe_basic folder, both contained similar folders and files. From which i should copy the files?
thx in advance

Review the config in settings section to make sure everything is there that needs to be. 30-40 seconds means something is wrong in the config most likely. Just go through line by line and read everything carefully to make sure you didn't overlook anything. Should fix your issue. When in doubt compare to the SIM config. If it works as expected then go through your machine config again and find the error or missing item.