Posted
over 6 years
ago
by
retnev
Installing on a new machine got rid of the python xy toolpath route. Here is a video. Only difference I chose a ball end tool. As you wiull see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note
|
Posted
over 6 years
ago
by
retnev
Installing on a new machine got rid of the python xy toolpath route. Here is a video. Only difference I choses a ball end tool. As you wiull see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note
|
Posted
almost 7 years
ago
by
retnev
No it is a dreaded Python problem as usual. I uninstalled all the python with dpkg. Basically everything mentioning py or python. Then reinstalled all python again, then it worked. I have never encountered such a reckless programming language as
|
Posted
almost 7 years
ago
by
retnev
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black tootlpaths.... this could only be due to the corrupt python stuff. However the toolpaths are still such that it machines dead on the x-y plane @z=0.
|
Posted
almost 7 years
ago
by
retnev
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black tpootlpaths.... this could only be the corrupt python stuff. However the toolpaths are still such that it machines dead on the x-y plane @z=0. !!! ?
|
Posted
almost 7 years
ago
by
retnev
No it is a dreaded Python problem as usual. I uninstalled all the python with dpkg. Basically everything mentioning py or python. Then reinstalled all python again, then it worked. I have never encountered such a reckless programming language as
|
Posted
almost 7 years
ago
by
Lars
Thank you for sharing your experience. I took a look at the log file and did not see a reason for failure. The segmentation fault feels like an issue with a low level library (e.g. gtk or opengl). I cannot tell, what went wrong.
|
Posted
almost 7 years
ago
by
retnev
I will have to install an order version again. The newest version is too buggy.
|
Posted
almost 7 years
ago
by
retnev
Attached the entire output during install
|
Posted
almost 7 years
ago
by
retnev
Reinstalling the newest version creates a spectacular crash. There are no errors during compile. I installed it using the same installation script I initially installed it when it worked afterwards. Now I get $ pycam Traceback (most recent call last): File "/usr/local/bin/pycam", line 4, in
|