Activity for PyCAM
-
Kurt Fitzner posted a comment on discussion Help
How does one use the "new" contour strategy? The instructions say it is not "yet" linked into the GUI, but I see others mention it. Is it possible to patch it into the GUI?
-
You need to use the latest version of PyCam from git. None of the releases will work with any modern version of Debian/Ubuntu/Mint.
-
retnev posted a comment on discussion Open Discussion
I followed the source compile instructions for the most recent Pycam release and got the error. "Unable to locate package python-gtk2" It is seemingly uninstallable in Debian/MX21 Anyone has an idea how to get pycam working on Debian ? OS: NAME="MX" VERSION="21.3 (Wildflower)" ID="mx" VERSION_ID="21.3" PRETTY_NAME="MX 21.3 (Wildflower)" ANSI_COLOR="0;34" HOME_URL="https://mxlinux.org" BUG_REPORT_URL="https://mxlinux.org" PRETTY_NAME="MX 21.3 Wildflower" DISTRIB_ID=MX DISTRIB_RELEASE=21.3 DISTRIB_CODENAME="Wildflower"...
-
I followed the source compile instructions for the most recent Pycam release and got the error. "Unable to locate package python-gtk2" It is seemingly uninstallable in Debian/MX21 Anyone has an idea how to get pycam working on Debian ? OS: NAME="MX" VERSION="21.3 (Wildflower)" ID="mx" VERSION_ID="21.3" PRETTY_NAME="MX 21.3 (Wildflower)" ANSI_COLOR="0;34" HOME_URL="https://mxlinux.org" BUG_REPORT_URL="https://mxlinux.org" PRETTY_NAME="MX 21.3 Wildflower" DISTRIB_ID=MX DISTRIB_RELEASE=21.3 DISTRIB_CODENAME="Wildflower"...
-
kingf posted a comment on discussion Help
Even PyCam 0.5.1.1 is still one of the best G-Code path generators available today. SO... to get PyCam to work in windows (tested upto windows 10), you need: gs955w32.exe: 9.55.0 is the LAST Ghost Script supported by PStoEDIT (addresses DXF error) pstoeditsetup_win32.exe: 3.78 latest available inkscape-0.92.5-x64.msi: light weight release (newer versions work) pycam-0.5.1.1_standalone.exe: Star of the show :) (you "might" also need VC_redist.x86.exe= Microsoft Visual C++ Redistributable )
-
Even PyCam 0.5.1.1 is still one of the best G-Code path generators available today. SO... to get PyCam to work in windows (tested upto windows 10), you need: gs955w32.exe: 9.55.0 is the LAST Ghost Script supported by PStoEDIT (addresses DXF error) pstoeditsetup_win32.exe: 3.78 latest available inkscape-0.92.5-x64.msi: light weight release (newer versions work) pycam-0.5.1.1_standalone.exe: Star of the show :) (you "might" also need VC_redist.x86.exe=Microsoft Visual C++ Redistributable )
-
David Francis created ticket #99
Syntax error in scripts/pycam
-
Christopher Dadisman created ticket #98
Python STL Fix
-
In Windows 10 Pro x64 version 1511 , the following toolset worked: Inkscape 0.92.2 (<1.0) pstoedit 3.70 (32 bit) (64 bit does not work) gs905w32.exe (GPL Ghostscript 9.05 32 bit) (<gs952w32.exe) Pycam-0.5.1.1_standalone.exe
-
Mihai X posted a comment on discussion Open Discussion
Hello, Would it be possible/difficult to implement a STL cutter for pycam?
-
Nicolaj Daugaard posted a comment on discussion Help
I get a similar message. Installing svg.path doesn't seem to help. An unexpected exception occoured: please send the text below to the developers of PyCAM. Thanks a lot! Traceback (most recent call last): File "/home/ucn/Desktop/pycam-0.6.4/pycam/Gui/Project.py", line 386, in gui_activity_guard_wrapper result = func(self, args, *kwargs) File "/home/ucn/Desktop/pycam-0.6.4/pycam/Gui/Project.py", line 524, in load_model_file detected_filetype = pycam.Importers.detect_file_type(filename) File "/home/ucn/Desktop/pycam-0.6.4/pycam/Importers/init.py",...
-
David Whiteley posted a comment on discussion Help
pycam asks me to report: An unexpected exception occoured: please send the text below to the developers of PyCAM. Thanks a lot! Traceback (most recent call last): File "/home/cnc/pycam-0/pycam-0.6.4/pycam/Gui/Project.py", line 386, in gui_activity_guard_wrapper result = func(self, args, *kwargs) File "/home/cnc/pycam-0/pycam-0.6.4/pycam/Gui/Project.py", line 524, in load_model_file detected_filetype = pycam.Importers.detect_file_type(filename) File "/home/cnc/pycam-0/pycam-0.6.4/pycam/Importers/init.py",...
-
Lars posted a comment on discussion Help
Indeed it works with the current master branch.
-
JackH posted a comment on discussion Help
Hi, little bump. Is it suppoused to be working in git dev version (PyCAM 0.6-svn)? I can't seem to be able to save tool settings nor configuration file is being created.
-
The openvoronoi library is optional - you can ignore this. I will reduce the verbal severity of this message. Did the process succeed?
-
Bart Coninckx posted a comment on discussion Help
After half an hour Pycam is still calculating but the progess bar hangs. I had this as well in the 0.5.1 version. Not sure why this happens. It does shows a warning about a missing openvoronoi library.
-
OK, it seems I had to explicitly select a model in the process tab. It's calculating now. BC
-
Hi Lars, while doing this I get: No trace models given: you need to assign a 2D model to the engraving process. my model is a SVG though, which should be 2D. What is going wrong? cheers, BC
-
Indeed the newer downloads appeared on github: https://github.com/SebKuzminsky/pycam/releases (see http://pycam.sourceforge.net/)
-
You can choose the strategy "engrave" and pick a "pocketing" mode. Probably you will need to apply the "revise polygon directions" action onto the model first, since pycam uses the direction (clockwise, counterclockwise) for determining "inside" and "outside".
-
Hi Lars, I got these high processing times while using an extruded model (see other post). If I find a way to fill in parts, I won't have to do the extrusion part again, which will benefit processing times. Regarding the version: I used the one on Sourceforge that was downloaded most. I only found 0.6.1 that was higher as a version. Where is 0.6.3 ? cheers, BC
-
Hi Lars, thanks! When I split the design into filled out parts and contour parts, I still face the same problem: how do I tell Pycam to fill in? Cheers, BC
-
Extrusion is the conversion of 2D model into a 3D model. I am not sure, that this is helpful for you with your mdel. Since pycam does not support specific operations for parts of a model, I would suggest, that you split your model into parts that you want to engrave along the outlines and the parts that should be filled. This should allow you to select the proper engrave operation to each polcgon.
-
Indeed pycam's perfomance is not great. Calculation speed mainly depends on the following factors: available processing power modelling density Maybe you can reduce the precision of the model within the range of your target application. Another thing: maybe you want to upgrade to v0.6.3? It does not really change the performance, but it may be helpful for other details. Your version of pycam is more than 8 years old :)
-
I just tried to generate the toolpath for an extruded model and this indicated that the job would take 8 hours! Can this be improved? BC
-
Hi, using 0.5.1 on Linux Mint. The Extrude function takes a very, very longtime. Did not time it, but it is more than 15 minutes. Can this be helped? Cheers, BC
-
I just found out that if I click the "Extrude" button, I get the filled in parts in the example window, but while simulating still only the contours are done. BC
-
Hi, I make my designs with Inkscape by importing bitmap files. In my current design I have filled polygons. When I try to produce G-code and simulate it, I see only the contours being milled. I will attach the SVG file. How can I activate the filling of certain polygons? Cheers, BC
-
Thomas J Powderly posted a comment on discussion Help
Hi, re: version 6.3. Please make the requirement of enum32 more obvious. And that its available as backport for many linuxcnc users ( eg wheezy ). And that the magic is to cd to the enum32 dir, then to do 'python ./setup.py install' . I did not know the 'install' bit and it took quite some time to find out what pythonistas must think is obvious. Thanks for a very nice tool.
-
Thank you for sharing these ressources!
-
COSTAS VLACHIDIS posted a comment on discussion Help
this is the topic : https://sourceforge.net/p/pycam/discussion/860183/thread/ddf61e8d/ and this is the python file link :https://bitbucket.org/raw/cnc_mendel/src and finally this is the jar file lnk :https://www.thingiverse.com/thing:52706 I 'm posting themto help any other that has the same problems. Costas
-
Hi Lars I have resolved this problem to an older posting into yours discusion group,I 've found a posting mensiing the https://chmodux.wordpress.com/2012/07/13/g-code-mendrel/ who has developed java executable thay turns pycad gcode in a form to be executed from Ramps and Marlin sofware.'m using this combination of hardware-software because it has and supports a low cost LCD, and a memory card to store the gcode files under windows. And so it is not obligatory to use the laptop to mill something....
-
Ah - sorry for spontaneously jumping into scripting territory :) "sed" is a commandline tool for text manipulation. The above expression would prefix every line that starts with "x", "y" or "z" with "G01 " in a given file. This kind of tools is available in every unix-like environment. In your case something like "cygwin" (for Windows) would provide such a functionality. But I guess, this is not the best approach for you, if you are currently not used to this kind of tools. Sorry - there is nothing...
-
Good morning from Rodos Island in Greece Please be more specific .What is "sed -i s/^([XYZ])/G01 \1/i' FILENAME" ? Is this some kind of code that I need to enter some how in the Pycam? I'm not a programmer soplease be patient with me. Thank you Costas
-
Ah - I completely misunderstood your question (based on my overly quick reading attempt) :( No: such a GCode dialect is currently not supported by pycam. In case that it is tolerable for you to post-process the GCode on your own, then something like "sed -i s/^([XYZ])/G01 \1/i' FILENAME" could fix your issue.
-
Not exactelly I 'm using Pycam 0.5.1 under windows 7, and my cnc machine works with Marlin software and Ramps 1.4 board. So the produced gcode from Pycam must have G01 befor any x -x -z motion line. Is there any configuration for this? I do not know if any newer version of Pycam can run under windows Thank you
-
pycam supports a setting for "plunge feedrate" (since v0.6.1) that allows to you reduce the speed for downward moves. Is that what you are looking for?
-
Hi I need some pycam configuration to producea ramps compatible gcode. My ramps -Marlin board needs G01 beafor any x -x -z motion line. Thanx in advence
-
This sounds like there were some error messages before? The above indicates that some components (e.g. the available toolpath strategies) were not loaded due to a problem. Anyway: did you try the newest version (0.6.3): https://github.com/SebKuzminsky/pycam/releases ?
-
Smed posted a comment on discussion Help
Exact same problem on Arch Linux. Any solutions?
-
Indeed the v0.6.x releases lack the feature of a persistent configuration storage. This is now fixed with the current (not yet released) master branch for quite some time. I will release it this weekend, I guess. Thanks for raising the topic again!
-
sd3 modified a comment on discussion Help
Has anything happened with this yet? I have been using the 0.5.1 standalone on Windows. The parts I have made turned out nice, but I kept running into issues with the plunge rate. My solution was to change the GRBL settings for Z on the machine to the plunge rate I needed. Unfortunatly that limits all Z movements, not just plunges. I set up a Linux machine specifically to take advantage of the new plunge rate settings. I have installed .0.6.3 and have been getting a feel for the differences in the...
-
Has anything happened with this yet? I have been using the 0.5.1 standalone on Windows. The parts I have made turned out nice, but I kept running into issues with the plunge rate. My solution was to change the GRBL settings for Z on the machine to the plunge rate I needed. Unfortunatly that limits all Z movements, not just plunges. I set up a Linux machine specifically to take advantage of the new plunge rate settings. I have installed .0.6.3 and have been getting a feel for the differences in the...
-
Has anything happened with this yet? I have been using the 0.5.1 standalone on Windows. The parts I have made turned out nice, but I kept running into issues with the plunge rate. My solution was to change the GRBL settings for Z on the machine to the plunge rate I needed. Unfortunatly that limits all Z movements, not just plunges. I set up a Linux machine specifically to take advantage of the new plunge rate settings. I have installed .0.6.3 and have been getting a feel for the differences in the...
-
1) I am not aware of a good approach for doing this in the GCode language. At least for LinuxCNC (http://www.linuxcnc.org/docs/html/gcode/g-code.html) it would work with G28 and G30. But this could conflict with a local usage of these positional registers (e.g. for a tool changer). Additionally I am not sure, if other GCode interpreters offer these commands, as well. Can you share a GCode file that exposes the behaviour that you desire? 2) I am used to position the tool at the surface of the stock...
-
I have two issues setting up Pycam. 1) The tool doesnt return to original position (where it started from after completion of a routine. I can enter this in GCODE manually, but just wonder why this was left out as it is obvious that you dont want to start from a new position and what the tool to return to exactly where it started. 2) I always place the tool on the workpiece and whe the program executes it lifts by a certain prescribed amount and then does the milling and return to that same place...
-
I have two issues setting up Pycam. 1) The tool doesnt return to original position (where it started from after completion of a routine. I can enter tis in GCODE manually, but just wonder why this was left out as it is obvious that you dont want to start from a new position and what the tool to return to exactly where it started. 2) I always place the tool on the workpiece and whe the program executes it lifts by a certain prescribed amount and then does the milling and return to that same place...
-
Installing on a new machine I got rid of the python xy toolpath route issue, so that problem is gone now. I made a video where I am now. Only difference I chose a ball end tool. As you will see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note i did do the the simulations in the wrong order to show the fact that the toolpath doesnt follow the curved surface as it should.
-
I just done exactly the steps you did and this time I get orange tootlpaths, which is great. Last time I got black toolpaths.... 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. !!! ? 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. This should not be allowed by the constraints if the...
-
Installing on a new machine I got rid of the python xy toolpath route issue, so that problem is gone now. I made a videeo where I am now. Only difference I chose a ball end tool. As you will see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note i did do the the simulations in the wrong order to show the fact that the toolpath doesnt follow the curved surface as it should.
-
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black toolpaths.... 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. !!! ? 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. This should not be allowed by the constraints if the toolpaths...
-
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black toolpaths.... 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. !!! ? 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...
-
Lars, hope you could open the screencapture. I did it n MP4. I open it with mpv on linux. Let me know if you need it in ogv
-
Lars, hope you could open the screencapture. I did it n MP4. Let me know if you need it in ogv
-
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. Back to pycam. I have it running again after I tamed the snake so it has nothing to do with pycam. I will record a session for you to see what I do wrong. I really apprecaite your kind help.
-
Installing on a new machine I got rid of the python xy toolpath route issue. Here is a video what it does now. Only difference I chose a ball end tool. As you will see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note i did do the the simulations in the wrong order to show the fact that the toolpath doesnt follow the curved surface.
-
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 will see from the side view the toolpath doesnt follow the curved surface. I really cant see what I do wrong. Note i did do the the simulations in the wrong order to show the fact that the toolpath doesnt follow the curved surface.
-
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 i did do the the simulations in the wrong order to show the fact that the toolpath doesnt follow the curved surface.
-
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 i did do the the simuulations in the wrong order to show the fact that the toolath doesnt follow the curved surface.
-
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 i did do the the simuulations in the wrong order to show the fact that the toolath doesnt follow the curved surface.
-
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black toolpaths.... 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. !!! ? 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...
-
I just done exactly the steps you did and this time I get orange tootlpaths. Last time I got black toolpaths.... 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. !!! ? 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...
-
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 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...
-
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. !!! ? 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...
-
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. !!! ? 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.
-
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 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...
-
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 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...
-
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.
-
I will have to install an order version again. The newest version is too buggy.
-
Attached the entire output during install
-
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 <module> import('pkg_resources').run_script('pycam==0.6.3', 'pycam') File "/usr/lib/python2.7/dist-packages/pkg_resources/init.py", line 739, in run_script self.require(requires)[0].run_script(script_name, ns)...
-
Newest version of Pycam, out of the blue just started crashing. Nothing changed that could cause this. I will have to reinstall again and then I will record my steps as you asked. $ pycam Enabled 4 parallel local processes Segmentation fault $
-
If the issue is resolved outside of pycam, then it is not really resolved in pycam :( I would be happy, if you could find the time to send a screenshot. Thank you!
-
The colors: you can configure these. Maybe I changed mine. The tool during the simulation: you can enable or disable its visibility. Regarding potential preparations after loading the model: no, I just opened the demo1.stl file in pycam. It is weird, that you achieve different results, since all geometry operations are done by pycam itself and not dependent on external libraries. Thus I cannot imagine, how the result could be different on your side. Maybe you want to record a video of your actions,...
-
I installed exactly the version of pycam you used, Used exactly the settings you used on exactly the same file. I end up with different paths and a hollow box. The Paths indicated are black lines not orange as yours (just as a side note) and the top curved surface is ignored as the box is seen as a hollow container not a solid !?. It then machines the sides and the bottom flat part of the object completely ignoring the curved surface. Now I am stumped. The only difference between what I did and you...
-
I installed exactly the version of pycam you used, Used exactly the settings you used on exactly the same file. I end up with different paths and a hollow box. The Paths indicated are black lines not orange as yours (just as a side note) and the top curved surface is ignored as the box is seen as a hollow container not a solid !?. It then machines the sides and the bottom flat part of the object completely ignoring the curved surface. Now I am stumped. The only difference between what I did and you...
-
I installed exactly the version of pycam you used, Used exactly the settings you used on exactly the same file. I end up with different paths and a hollow box. The Paths indicated are black lines not orange as yours (just as a side note, and the top curved surface is ignored as the box is sseen as a hollow container not a solid. It then machines the sides and the bottom flat part of the object completely ignoring the curved surface. Now I am stumped. The only difference between what I did and you...
-
I installed exactly the version of pycam you used, Used exactly the settings you used on exactly the same file. I end up with different paths and a hollow box. The Paths indicated are black lines not orange as yours (just as a side note, and the top curved surface is ignored as the box is sseen as a hollow container not a solid. It then machines the sides and the bottom flat part of the object completely ignoring the curved surface. Now I am stumped. The only difference between what I did and you...
-
I did not notice the little small font 0.6.3 at the top. I guess no-one will find that easily, but it is probably still an unstable version. The font fo 0.6.3 is about 20x smaller than the 0.6.2 and other versions so I never took notice of it till you pointed it out. Thanks P.S. Please consider updating the tar.gz file INSTALL.TXT to contain the instructions what command to run for installation e.g. $] python setup.py install as non-python programmers or general users wont know how to install pycam...
-
I did not notice the little small font 0.6.3 at the top. I guess no-one will find that easily, but it is probably still an unstable version. The font fo 0.6.3 is about 20x smaller than the 0.6.2 and other versions so I never took notice of it till you pointed it out. Thanks
-
On http://pycam.sourceforge.net/ you find a link to https://github.com/SebKuzminsky/pycam/releases
-
Your example About page mentions Pycam 0.6.3 . There is nowhere I can find that version. Where is the download page for 0.6.3 ?
-
That is what has been driving me nuts for more than 6 months! Wish I knew about the bug. This is really helpful thank you very much. I will post back once the newest pycam runs.
-
That is what has been driving me nuts for more than 6 months! Wish I knew about the bug. This is really helpful thank you very much.
-
I am glad, that it is helpful. Indeed I am quite confident, that you can achieve the same (with the same settings) with v0.5.1. But an upgrade should not hurt. Regarding #136: you see the effect of this issue in the video: the surface moves on top of the model are stright instead of being bent down. The issue is not fixed, yet. Thus you should just pick the other grid direction ("y" instead of "x") in order to work around this effect for now.
-
That really looks great ! Wish I could get to that stage, been trying for months. I will go over your video carefully. Was it issue#136 that caused it to create only a single cut along the surface ? I will install same version pycam as you used to repeat your steps. Thank you very much Lars!
-
OK, I transfered the attachment to the new post. Thanks
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt. As you can se this is 2.5D and way inside the capabilities of Pycam according to the manual. To get G-code though...
-
For other interested readers: the referenced model is attached in another thread: https://sourceforge.net/p/pycam/discussion/860183/thread/6980228f/ I tried to create a toolpath for your model. I think, I created a usable toolpath. Please take a look at the attached video, that I recorded. Please note, that the resulting toolpath exposed issue #136. You will need to change the grid direction of the surface process in order to work around this at the moment.
-
Let us continue this separate discussion in the new thread, that you just opened: https://sourceforge.net/p/pycam/discussion/860183/thread/8941a7429a
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt. As you can se this is 2.5D and way inside the capabilities of Pycam according to the manual. To get G-code though...
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt. As you can se this is 2.5D and way inside the capabilities of Pycam according to the manual. To get G-code though...
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt. As you can se this is 2.5D and way inside the capabilities of Pycam according to the manual. To get G-code though...
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt. As you can se this is 2.5D and way inside the capabilities of Pycam according to the manual. To get G-code though...
-
Here is a good example I am trying to CNC a missing piano edge. There is just no way I can get pycam to generate gcode that makes sense. Either it just creates a surfacing routine or it just plunges and cnc's a single line where it has to do the entire surface. I attach my STL model and a config. I tried about every possible config and nothing works. The one added is jut my latest attempt.
-
No problem, I since movedon to dxf2gcode which worked great so I did not have to deal with pycam config problems. So the above issue was resolved using dxf2gcode. I have STL files I need to CNC and that I need pycam for, so I will post it in another topic.
-
That figures, maybe they should call it something different rather than just adding ++. No way for a user to know. Thanks that solves it.
-
Sorry for forgetting your question! 1) the bounding box is used for specifying the depth of the gravure (see http://pycam.sourceforge.net/faq/). This is a bit counter-intuitive, sorry. 2) No, the 2D toolpaths do not try to guess the physical properties of your setup. But it should not add moves within circles that are smaller than the tool radius, if you enabled tool compensation. Regarding gravures for 3D objects: this is an interesting feature, but it is not here, at the moment.
-
pycam++ is something different. You should refer to "pycam" (without "++") instead. You can also find a bit newer things here: https://github.com/SebKuzminsky/pycam/releases (documentation lacks a bit in this regard)
-
Sorry for forgetting your question! Where exactly did you experience an issue? With a 2D model? Maybe you can share a screenshot?
1 >
