Skip to content

Gmoccapy not starting "out of the box" on Linux (or WSL) #1933

@smoe

Description

@smoe

Sidenote: I need to thank @hansu to also check WSL. That cannot be used for anything time-critical because of the latencies (330 µs for base -> 980 while typing this report, 184 µs for servo -> 566) on a 10 yo i7 and Win10, but we should find out where its limits are. The one or other educational value this should well have.

After installation on Debian (regular Linux machine or WSL) the direct execution of /usr/bin/gmoccapy demands first of an environment variable CONFIG_DIR and once that is given, also one for LINUXCNC_TCL_DIR, so I tried

LINUXCNC_TCL_DIR=/usr/lib/tcltk/linuxcnc CONFIG_DIR=/usr/share/gmoccapy gmoccapy

which led to another error:

Traceback (most recent call last):
  File "/usr/bin/gmoccapy", line 5365, in <module>
    app = gmoccapy(sys.argv)
  File "/usr/bin/gmoccapy", line 172, in __init__
    self.stat.poll()
SystemError: <method 'poll' of 'linuxcnc.stat' objects> returned NULL without setting an exception

This is a bit cryptic. Preferably, some default paths would have been chosen and the user would just start the binary.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions