probe basic - toolpath/file preview loading error

spumco wrote:

Adding my two cents here...

I get a similar error message when trying to load a g-code file in PB.  No issues with the backplot but the attached error message pops up when I load the file.

I think I narrowed it down to the tool number being >199.

When I commented out the T407, T823, and T642 it loaded with no complaints.  And when I edited the file it would load fine at T199 (other two commented out) but puked when changed to T200.

I can load the tools in/out of my ATC using the PB interface, and call them up via MDI with no errors.

I can work around this for a short time by renumbering tools, but this is going to be annoying since I imported my F360 library to LCNC and I've got tools up to the 1100-range in the table.

it appears to be a linuxcnc error, i can replicate in axis and it throws an interp error, happened somewhere between 2.9.3-83-g1d5d02d836 and 2.9.3-2099-g9f5a1c8f50
github.com/LinuxCNC/linuxcnc/issues/3174

in the interim, you can uninstall linuxcnc and reinstall using the lockdown deb version which does not prduce the error message, use the deb download links at the bottom of the page here:

linuxcnc.org/downloads/

or follow the newly updated probe basic docs page here for installation instructions on the deb:

kcjengr.github.io/probe_basic/

select develop or stable per your requirement, both tested and work on the 2.9.3 lockdown deb of linuxcnc!

Thanks for bringing this up, the powers that be are aware and are investigating the issue!

Chris

What/Where is this? We cannot reproduce this bug building the 2.9 branch of the linuxcnc github repo we can reproduce this only in master.

im not certain, it may be that it was a molested version. it initially started as an apt install from sudo apt install linuxcnc-uspace-dev mesaflash from the docs instructions and had been updated over the course of that pc build. for now i would say perhaps my install had been modified while troubleshooting dbtools work, so unless it pops up again, i would say assume it is relegated to 2.10.

Is there anything further I can post or attach here (or on GH) to assist?

The error Lcvette posted on GH wasn't exactly the same as mine - at least I don't think so.

it is the same, the message is just better exposed in qtpyvcp. i posted axis results so it would be easier to test and would remove the use of a different gui from the troubleshooting equation.

if you want the error gone install the lockdown 2.9.3 until they get the issue sorted in 2.10.