-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Mkwrapper Stop block: ModuleNotFoundError: No module named 'preview' #8
Comments
I had some similar module not found issues with my python configs in the fdm folder before i changed the lines from:
to:
Like python 3.7 handles local paths different ? |
This is not a python 2/3 issue:
@cerna |
Poking around in my old ob-ox setup I can find out where the preview comes from there:
And find out that its missing in my newest setup:
However struggling to find out where the: |
Well I can find it in the (from machinekit.io) |
The preview module is compiled in from: |
The whole compile blob shows it to depend on haltalk, czmq and the protobuff stuff:
@cerna |
I'm able to get the preview.so to compile in machinekit-hal however
|
Turns out I needed to use the files from the Emc app src/emc folder instead of the ones from mk-cnc and update previewmodule.cc |
running the gui (MachinekitClient) gives following execption:
|
Looks like mkwrapper needs to be updated to the linuxcnc 2.8 , 2.9 changes: |
This exception seems to be caused by mkwrapper not being updated to the new lcnc axis --> joints update in 2.8 , 2.9. Also same update seems to be needed to the protobuf stuff here |
By editing mkwrapper.py and status.proto I'm finally able to get the Cetus gui to start up execpt for now all the spindle stuff is commented out.
|
Got my machine to jog with standard Cetus Gui
|
Sorry I was unaccounted for the party, had to prioritize my engagements.
My first reaction is to probably delegate it to its own repository. I think it is a better solution to have multiple smallish project with limited functionality than one big doing-it-all. (Mainly because of the dependency graph and maintenance issues stemming from it.)
I am not sure, but I don't think so.(?) All Python packages for Machinekit projects and for LinuxCNC (as far as I know) are comming from apt Debian repository, which installs it in one place. There is no use of _Virtual Environment_s or Pyenv, because combining it with Debian packaging is extremely painful. (And it would make more sense to try something like Nix anyway.) There could be a dichotomy between Python2.x and Python3 version of packages. All in all, it's great that you were able to reach the bottom of it! 👍
My personal opinion on this issue is that all compiled files (here shared libraries) should have a prefix identifying it as a Machinekit file ( |
Hello, I also encountered the same problem, how did you solve it? |
@summerlotus513 |
The whole premise in this thread is to see:
A Is it possible to get the qtquickvcp gui's running by adding the missing preview.so lib ?
Edit: Answer: allmost
B.Find out what else is missing.
Edit Answer at bottom
Based on this suggestion
I compiled Emcapp with full python 3 support using this method:
Then tested the axis sim config: ran without any problems execpt this message:
Mkwrapper:
I used the newest package from machinekit-hal on purpose.
I used this hal config updated for linuxcnc 2.9 (and the newest added soc)
I have a similar version that is tested to work with the compiled in axis gui.
Here is the result of a python3 ./run.py run:
Seems like config is parsed ok however mkwrapper cannot fínd the module preview.
I wonder where this python preview module requested here is supposed to come from.
BTW
With these changes to the linuxcnc script
Im able to run a similar python based hal config
however the end result is the same error traceback
The text was updated successfully, but these errors were encountered: