[SOLVED] ProbeBasic NameError: name 'tool' is not defined

Hi all.
Happy New Year!
Fresh install of LinuxCNC 2.9.3 (full image downloaded from wiki link) and freshly installed QtPyVCP and getting the NameError even after patching as per: github.com/LinuxCNC/linuxcnc/pull/3176/files
I have attached edited file and the qtypyvcp.log with .txt extensions.

System loads OK, homes and jogs, but as soon as I do a tool change for probing etc it throws that error.
I have also tried purge and reinstall of QtPyVCP, a reinstall of LinuxCNC as per kcjengr.github.io/probe_basic/index.html (that was a frustrating exercise, arrow keys in Putty were borked and weird permissions plus my user could not shutdown the system! So I opted for an official build).
EDIT: Should have mentioned this is the lathe config!
EDIT 2: Same behavior in the sim, log file for that now attached.
Any help much appreciated.

you are probing in lathe? what probe routines are you using? i don't think i ever defined any probing routines in lathe so is ti possible that the touchprobe isn't defined somewhere as per the subroutines requirement?

Wow I never thought of needing to setup the probe first!
And yes was looking to use probing to calibrate tool offsets, have seen this done by at least one other person and it seemed a useful and reliable method

So the sim does not have probing configured for lathe either?

But to be honest, main reason for using QtPyVCP is because it looks so very, very, nice!

Actually it throws the error when attempting to change tool from 0 to 1.
Would I be correct to say that unless probe routines are created and probe defined, then Probe Basic Lathe cannot be used as an interface for Lathe?

Axis works perfectly, so I can at least use that!

Apologies if this is an obvious thing, still learning here

ok i found the issue and corrected and just pushed the fix to the develop branch. and we are about to make a new release soon to move the current develop to the new stable branch, will be a day or so to follow.

and no, it is a great catch, thanks for bringing it up! it was a stray edit that was saved in the backplotter code and needed fixing.

Nice and thank you!
Applied the fix -self. to tool_actor.py and confirmed now fixed for me.

Now to add my spindle encoder, looking forward to testing the conversational part

happy to help!  sorry for the hiccup!

Chris