Specified probe tool not in spindle error after upgrade

I recently did an upgrade of Probe Basic and LinuxCNC, here are the versions I upgraded from and to.

linuxcnc-uspace/linuxcnc 1:2.9.3 amd64 [upgradable from: 1:2.9.2]
python3-qtpyvcp/stable 4.1.2 all [upgradable from: 4.0-124.dev]
python3-probe-basic/stable 0.6.0 all [upgradable from: 0.5.3-219.dev]

After doing this upgrade and updating the corresponding Probe Basic configuration files I've come across an odd error relating to probing.

When I try to do any probing I get the following error message even though I already have to correct tool loaded.

 

 

If I re-enter the value "1" in the "Probe tool" field under "Probing parameters" everything works again until I restart Probe Basic.

probe basic release you are now on requires the latest subroutine files be copied over as the method of which the parameters are stored has been changed, they are now stored in the var file and the var parameters must also be added in the var file. run a comparison of the updated sim config folder for the var file to show what lines must be added.

there should have been a white notes screen with this documented on requiring changes when you first started probe basic. change notes will always be posted there for releases requiring users to make changes to their configs.

all parameters required for the latest probe basic version are listed here:

kcjengr.github.io/probe_basic/probe_basic_parameters.html


and to see what files may require editing see the configurations docs here:

kcjengr.github.io/probe_basic/machine_config.html

Thanks for a quick reply!

I updated the configuration, copied over the subroutines and python folders but I missed the var file. I'll update it and report back.

that should fix it, if the parameters are not listed in the var they are volatile which is why it works if you enter in the current running instance but doesn't work on restart as the volatile parameters are dumped on exit.  adding in the parameter to the file converts it to persistent!  and will store through restarts.  be aware that if you create a new var file and they are zeroed out, you must renter or run the parameter update via the button in the ui for each section to update the parameter settings and resynchronize. this should never become an issue unless you corrupt your var file or copy a different var in for some reason.  just a heads up on it though!

I added the missing entries to the var file and it solved the issue.

Given that Probe Basic is under active development with frequent configuration changes this got me thinking.

Would it be possible to create a pyhon script that is executed early in startup process and checks if all required Probe Basic specific configuration options are present?

That would alert users to missing configuration options after upgrades and when making new installations.

Unlogic post=318332 userid=35541I added the missing entries to the var file and it solved the issue.

Given that Probe Basic is under active development with frequent configuration changes this got me thinking.

Would it be possible to create a pyhon script that is executed early in startup process and checks if all required Probe Basic specific configuration options are present?

That would alert users to missing configuration options after upgrades and when making new installations.

hmmm, maybe, but I'm not sure how that would look exactly, do you have an idea on how to make it work?
 

For most of the Java applications I've written over the years I included sanity checks of the configuration that executed as early as possible during the startup process before something else had the possibility of crashing due to missing invalid or configuration.

Below is a snippet of code from the Java based DNS server I wrote long ago (unlogic.se/projects/eagledns).

 

Now given how good LinuxCNC and Probe Basic is working I haven't really had to roll up my sleeves and get to familiar with how the bootstrap/initialization of the user interfaces works. But I guess in the case of Probe Basic maybe a hook or method for checking the configuration could be added in QtPyVCP that each derived user interface could then implement and check the configurations before QtPyVCP  proceeds to load the actual GUI.

would certainly be pretty sweet, PB does change fairly frequently since it isn't in the main linuxcnc repo. and i certainly struggle with good ways to a successful method to ensure users can easily update any required changes.

does this seem like something you might want to run with?if so let me know, you are welcome to join us in the qtpyvcp chat:

matrix.to/#/#qtpyvcp:matrix.org

it is hugely helpful when we get folks who can help propel the project forward! A great group of folks and an awesome supportive culture! feel free to pop in!