1
I Use This!
Activity Not Available

News

Analyzed over 1 year ago. based on code collected almost 4 years ago.
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 ... [More] i did do the the simuulations in the wrong order to show the fact that the toolath doesnt follow the curved surface. [Less]
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 ... [More] i did do the the simuulations in the wrong order to show the fact that the toolath doesnt follow the curved surface. [Less]
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 ... [More] python, nothing against you or pycam it is directed to the snake & its developers. Whenever I have a problem, Python sure will be the culprit behind it. I know it is great for developers to write software, but it is an absolute mess for perpetual installation... [Less]
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. ... [More] !!! ? Go figure! Basically destroying the workpiece and the machine, by plunging down through the workpiece to the xy plane and machining the bottom flat taking all the material with it in one shot. Sheesh ! This should not be allowed by the constraints... [Less]
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. !!! ? ... [More] Basically destroying the workpiece and the machine, by plunging down through the workpiece to the xy plane. This should not be allowed by the constraints. I will make a screen recording. [Less]
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 ... [More] python, nothing against you or pycam it is directed to the snake & its developers. Whenever I have a problem, Python sure will be the culprit behind it. I know it is great for developers to write software, but it is an absolute mess for perpetual installation... [Less]
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