Probe Basic is it compatible with Python3?

Yes, "qtpyvcp -h" responded with a list of available run variables.

qtpyvcp -v = QtPyVCP v0.3.19

linuxcnc-dev/scripts/linuxcnc gets the GUI selector panel up.  THere are no qtpyvcp sims in the selector panel - just PB at the bottom.

When I start probe basic, I get this screen output:

LINUXCNC - 2.9.0~pre0
Machine configuration directory is '/home/MILL/linuxcnc-dev/configs/probe_basic'
Machine configuration file is 'probe_basic.ini'
Starting LinuxCNC...
File: tool.tbl Unrecognized line skipped:
    ;Tool  Pocket Z Offset     Diameter     Remark
twopass:invoked with <> options
twopass:found ./hallib/core_sim_5.hal
twopass:found ./hallib/spindle_sim.hal
twopass:found ./hallib/simulated_home_probe_basic.hal
twopass:found ./hallib/sim_cannon.hal
Note: Using POSIX realtime
motion.c: Creating unlock hal pins for joint 4

Traceback (most recent call last):
  File "/home/MILL/.local/bin/probe_basic", line 11, in <module>
    load_entry_point('probe-basic', 'gui_scripts', 'probe_basic')()
  File "/home/MILL/probe_basic/probe_basic/__init__.py", line 18, in main
    vcp_version=__version__)
  File "/home/MILL/.local/lib/python3.7/site-packages/qtpyvcp/utilities/opt_parser.py", line 98, in parse_opts
    raw_args = docopt(doc, version=version_str)
  File "/home/MILL/.local/lib/python3.7/site-packages/docopt.py", line 560, in docopt
    pattern = parse_pattern(formal_usage(DocoptExit.usage), options)
  File "/home/MILL/.local/lib/python3.7/site-packages/docopt.py", line 375, in parse_pattern
    raise tokens.error('unexpected ending: %r' % ' '.join(tokens))
docopt.DocoptLanguageError: unexpected ending: ')'
Shutting down and cleaning up LinuxCNC...
task: 178 cycles, min=0.000009, max=0.010398, avg=0.008422, 0 latency excursions (> 10x expected cycle time of 0.010000s)
Note: Using POSIX realtime
LinuxCNC terminated with an error.  You can find more information in the log:
    /home/MILL/linuxcnc_debug.txt
and
    /home/MILL/linuxcnc_print.txt
as well as in the output of the shell command 'dmesg' and in the terminal



 

That reads like an error with the python script.  It might be an issue with python versions or that particular commit has an error.

I gave up (again) and wiped everything (again).

I've got MX, 2.8, and PB appears to be running.  QtVCP doesn't work, but I'm so tired of this I'm going ignore qtvcp and get back to figuring out how to set this up in axis and then PB.

I'll start a new thread when the next crisis hits.

Thanks,
Ralph

Qtvvp or qtpyvcp?

not familiar with this MX flavour so not really sure what the problems could be.

QtVCP - used for Silverdragon GUI and other VCP's.  That one is broken.

QtPyVCP is working... or at least not throwing errors yet.

Thank you Phill.

Yes, QtVCP was working fine on master branch when I had that installed.  But I simply couldn't get master working with QtPyVCP and Probe Basic.

Everyone here has been very helpful, but nothing has worked all the way through.  I can't count how many iterations and variations I've tried. This forum is littered with my various failures, errors, and frustrations over the past week or so.

Right now, MX, 2.8.2, QtPyVCP, Python(some version), and Probe Basic appear to be playing ok at the moment.  I'm in the middle of cleaning up my HAL file a little after running pncconf and I'll see if I can get something to turn on.

If anyone has a magic solution I'm happy to do whatever he (or anyone else) tells me to do, but I'm tired of failing.

-R

phillc54 wrote:

Sorry I can't help with QtPyVCP or Probe Basic. 

 

Let me re-phrase: I broke QtVCP in some way.

I'm becoming convinced that I have the Anti-Midas touch regarding LCNC.  Everything turns not to gold... but a more brown hue.

I did try running the qtvcp install script for 2.8 from your instructions. Got an error during the script (same error as reported by someone else, can't find the thread).