Probe Screen V2 Python & file not open errors

After my 'accidental' purchase of a Renishaw probe, I thought I might as well use it. A bit of turning and electronics ( youtube.com/shorts/Yk2ZmRjruxY ) later and I'm now trying to install the Probe Screen V2.

Once I'd editing the ini/hall files as required, I had the Gmoccapy tab and the probe screen displaying OK but when using the 'jog' function on the Probe Screen V2 I get the following error:

Adding DEFAULT_VELOCITY to the [TRAJ] section of the ini file (even though DEFAULT_LINEAR_VELOCITY is the 'new' label?) results in the following similar error (even if DEFAULT_VELOCITY is set to an integer, not a float):

I can still jog OK on the main screen, so thought I'd try the X+ button (the simplest probe operation) on the probe screen.  I then get the following error:

So it would appear I have both a Python error (it looks very similar to the errors I had when writhing t=for the Manualmatic) and a 'file' error - I have no idea what the file is that is not opened.

Initially errors occurred on my proper install but have also now replicated in a vanilla Gmoccapy simulation (ini/hal files attached). I'm using the Raspberry Pi image which is now version 2.8.4.

There are a lot of threads/replies on here about the Probe Screen but I haven't yet found any that match these errors.

Is it likely the Probe Screen is now out of sync with LinuxCNC (last update to the git repository was 4 years ago)?

Any help digging into this would be much appreciated.

fletch wrote:

Is it likely the Probe Screen is now out of sync with LinuxCNC (last update to the git repository was 4 years ago)?

 
Hmm... Working my way through the github forks and this might imply that is the case: github.com/verser-git/probe_screen_v2/co...f12265c314470e5d2b49

Am I using an out of date resource?

Looking at the timestamps, it seems very likely that the handler file will need to be converted to Python 3. This shouldn't be particularly hard.

Thanks Andy - following the 'forking trail'*, I notice you've forked the Probe Screen NG ( github.com/andypugh/probe-screen-ng ) and that antbarney has an NG fork ( github.com/antbarney/probe-screen-ng ) with recent commits for 2.9.

I'm going to back out my V2 config and try the NG version - will report back.

*it would be far quicker and less error prone if github showed the number of commits ahead in the fork lists!

fletch wrote:

Thanks Andy - following the 'forking trail'*, I notice you've forked the Probe Screen NG ( github.com/andypugh/probe-screen-ng )

So I have! Though I think that it probably all that I have done. I had completely forgotten about it
 

Progress of sorts - I can jog without errors but when attempting to X+ probe I get a slow X travel (expected), a long delay (a couple of seconds, not expected), a rapid Z travel (eek!) and then the error:


The 'See notification popup' is a bit of a tease because it just says 'File not open'...

The probe is wired in (the LED goes out on the 7i96 when the probe is activated) and pncconf configured for the probe input. I have not seen any documentation in either V2 or NG regarding linking the probe input to the probe screen - I'm assuming is 'known name' for the probe screen.


Any ideas what this unopened file is called, or how I might find out?

ntb_button_switch_page is a routine in gmoccapy.

There is this bug mentioning it: github.com/LinuxCNC/linuxcnc/issues/1398

Though I don't see "file not open" there so that's probably not related.

Do you get the same error if a G-code file is loaded?

I am a bit concerned to see an M3 mentioned in the context of probing.

I have not loaded any G code while using the probe so far but get the following error when I have loaded (but not run) spiral.ngc from the examples directory:


If I run spiral.ngc first I get the same error but - highly dangerously - the probe screen is now using inches rather than mm for travel movements!! Really pleased I had my hand over the estop! I think I've earned an emoji for that

Edit: Yikes! I just realised what M3 is - we're going to need a bigger emoji!

Please ignore the M1 and M3 - these are debugs from the Manualmatic when task_mode (Manual, MDI, Auto) changes...

fletch wrote:

Code:

but - highly dangerously - the probe screen is now using inches rather than mm for travel movements!! 

OK, that's really serious. Even though the probe screen isn't part of LinuxCNC, enough people use it that I think you should raise a tracker on this at:

github.com/LinuxCNC/linuxcnc/issues

(Maybe mention that I told you to, so that folk don't question the relevance)