SolveSpace Logo SOLVESPACE -- parametric 2d/3d CAD

(you are viewing a thread; or go back to list of threads)

Output to CAM or g-code (by Laurence Rochforr)

I recently got access to a CNC mill.

I'm wondering if people could make suggestions as to how to go about making tool paths and generating g-code from Solvespace models.

Many thanks
Sat Jan 13 2018, 13:58:41
(no subject) (by Andrew)
I am looking at the same problem, and I have found, but not yet used PyCAM, which will generate paths from an STL file.
Sun Jan 14 2018, 11:31:50
(no subject) (by Jonathan Westhues)
SolveSpace can natively generate G code for simple 2d parts; take a look at the "exported g code parameters" in the configuration screen. It can also do 2d cutter radius compensation.

The workflow for anything more complex requires a separate CAM tool, PyCAM (per above), commercial, etc.
Sun Jan 14 2018, 18:44:13
(no subject) (by KevinK)
If you are looking for an open source solution, have a look at the CAM capabilities of Freecad.

There is a good set of tutorial's available on Youtube made by MAGIG CNC Maschines.
They use the latest 0.17 Development release, which might be a bit buggy.

There is also a CAM package for Blender, Blendercam.

Some options from independent developers:
If you have a bit of money to spend, there is ESTLCAM for 50 EURO.
ESTLCAM is a great and simple tool for 2D CAM, and basic 3D CAM.

CAMBAM is also a very versatile CAM tool,not free but for 100 Euro still reasonable.
Mon Jan 15 2018, 18:15:43
(no subject) (by Paul)
I see the g-code options, but how do you actually get it to produce g-code output to a file?
Fri Jun 21 2019, 20:54:27
(no subject) (by Paul)
Never mind. The file-type pulldown on my Gnome setup was very non-obvious.
Fri Jun 21 2019, 21:38:36
G Code Export no G02,G03 (by Yiannikos Pavlis)
I am trying to export a 2D view but arcs and circles are
represented as linear segments with G01. I am very impressed
with the capabilities and performance of this software so far and even consider it as a solid replacement for Solidworks or NX in most cases. However representing arcs with linear segments is a big problem for me. Not only it makes the G Code unreadable, it can lead to inaccuracies. Is there an option I haven't checked that results to this? If not consider me interested in giving a shot at developing a solution. I may not have much experience but I have dabbled in C and can devote some of my time on this.

Love your work,
Yiannikos Pavlis

PS: here's an example of a gcode program I made with two intersecting arcs:
G00 X0 Y0 X0 F10
G00 Y48.30 X-12.94
G02 X-48.30 Y12.94 I12.94 J-48.30
G03 X-12.94 Y48.30 I17.68 J17.68

below is the same toolpath from export 2d view:
see the difference?

G00 X-71.31 Y-1.46
G01 Z10.00 F10.00
G01 X-72.11 Y-4.93 F10.00
G01 X-72.67 Y-8.51 F10.00
G01 X-72.96 Y-12.20 F10.00
G01 X-72.97 Y-15.95 F10.00
G01 X-72.68 Y-19.74 F10.00
G01 X-72.08 Y-23.53 F10.00
G01 X-71.17 Y-27.29 F10.00
G01 X-69.97 Y-30.97 F10.00
G01 X-68.47 Y-34.54 F10.00
G01 X-66.69 Y-37.98 F10.00
G01 X-64.66 Y-41.23 F10.00
G01 X-62.40 Y-44.29 F10.00
G01 X-59.94 Y-47.12 F10.00
G01 X-57.31 Y-49.72 F10.00
G01 X-54.54 Y-52.06 F10.00
G01 X-51.66 Y-54.15 F10.00
G01 X-48.64 Y-56.02 F10.00
G01 X-45.42 Y-57.69 F10.00
G01 X-42.02 Y-59.14 F10.00
G01 X-38.46 Y-60.35 F10.00
G01 X-34.77 Y-61.28 F10.00
G01 X-30.99 Y-61.92 F10.00
G01 X-27.14 Y-62.26 F10.00
G01 X-23.27 Y-62.29 F10.00
G01 X-19.40 Y-62.01 F10.00
G01 X-15.58 Y-61.42 F10.00
G01 X-11.85 Y-60.54 F10.00
G01 X-8.23 Y-59.37 F10.00
G01 X-4.76 Y-57.94 F10.00
G01 X-1.46 Y-56.27 F10.00
G01 X1.65 Y-54.40 F10.00
G01 X4.54 Y-52.34 F10.00
G01 X7.28 Y-50.07 F10.00
G01 X9.89 Y-47.55 F10.00
G01 X12.35 Y-44.79 F10.00
G01 X14.62 Y-41.80 F10.00
G01 X16.68 Y-38.61 F10.00
G01 X18.50 Y-35.23 F10.00
G01 X20.05 Y-31.69 F10.00
G01 X21.31 Y-28.03 F10.00
G01 X22.28 Y-24.27 F10.00
G01 X22.94 Y-20.47 F10.00
G01 X23.29 Y-16.64 F10.00
G01 X23.34 Y-12.84 F10.00
G01 X23.10 Y-9.10 F10.00
G01 X22.57 Y-5.44 F10.00
G01 X21.78 Y-1.90 F10.00
G01 X20.75 Y1.51 F10.00
G01 X19.47 Y4.82 F10.00
G01 X17.92 Y8.10 F10.00
G01 X16.09 Y11.31 F10.00
G01 X13.99 Y14.42 F10.00
G01 X11.61 Y17.39 F10.00
G01 X8.99 Y20.19 F10.00
G01 X6.13 Y22.79 F10.00
G01 X3.06 Y25.16 F10.00
G01 X-0.19 Y27.27 F10.00
G01 X-3.58 Y29.11 F10.00
G01 X-7.09 Y30.67 F10.00
G01 X-10.68 Y31.92 F10.00
G01 X-14.31 Y32.89 F10.00
G01 X-17.95 Y33.55 F10.00
G01 X-21.55 Y33.93 F10.00
G01 X-25.11 Y34.04 F10.00
G01 X-23.95 Y29.61 F10.00
G01 X-23.45 Y24.89 F10.00
G01 X-23.71 Y20.03 F10.00
G01 X-24.75 Y15.20 F10.00
G01 X-26.54 Y10.61 F10.00
G01 X-29.02 Y6.41 F10.00
G01 X-32.04 Y2.75 F10.00
G01 X-35.45 Y-0.31 F10.00
G01 X-39.28 Y-2.82 F10.00
G01 X-43.60 Y-4.80 F10.00
G01 X-48.29 Y-6.11 F10.00
G01 X-53.19 Y-6.66 F10.00
G01 X-58.12 Y-6.42 F10.00
G01 X-62.89 Y-5.42 F10.00
G01 X-67.32 Y-3.73 F10.00
G01 X-71.31 Y-1.46 F10.00
Mon Aug 1 2022, 14:23:36
G Code Export no G02,G03 (by blinkenlight)
The way I'm personally using SolveSpace is I export the 2D contour of the feature I want milled as a SVG file, then I import that into GCAM SE for generating G-code. As it happens, this process preserves arcs as G02/03 entities, although broken up into one arc per quadrant. Fair warning though - while I don't think GCAM SE is particularly hard to use, it does have a bit of a learning curve.
Tue Aug 2 2022, 11:30:22
(no subject) (by Thomas)
I found the best CAM for SolveSpace to be Kiri:Moto.
Fri Aug 19 2022, 04:37:27
(no subject) (by Alper)
I have just about to suggest Kiri:Moto.
Mon Nov 14 2022, 04:55:58
(no subject) (by Thomas)
Kiri:Moto really shines on complex parts and while there is a trace function for chamfers and theoretically engraving, I had to use SolveSpace internal gcode generation for some curvy text yesterday. Pretty straight forward once I found out how to set the Origin (with the camera origin).

Need to test this more, might be a better than expected solution for simple parts. Currently tabs to secure the part is the one vital thing thats missing.
Thu Nov 17 2022, 05:33:38
Output to CAM or g-code (by Walter Cadek)
I think there is no need to output gcode.

Use slicer programs to get gcode.

.STL, .STEP files can be read by several freeware SLICER programs

Examples like:
Prusaslicer --> Download, Forum

The advantage of this programs is, they support all necessary parameters for the 3D-Printer, like:
-Filament diameter.
-Speed for outline and filling, bridging
-slice height
-Fill-Methode (Raster, cubic...)
-Temperature for hotend or baseplate
-and so on....and so on.....
all this parameters are special for the used printer, filament, ........

So I prefer to design the parts in solvespace and generate .stl or .step files,
then load this files in prusa-slicer together with the config for my special printer and the filament (ABS, PETG....) and load the gcode output into the printers SD-card.

This allowed me to produce many parts designed in solvespace.

What I miss is a translation from Openscad files to solvespace, since there are many openscad files in the 3D-Forums available. If they could be adapted, modified and further changed in solvespace, this would be very helpful.

Wbr Walter
Thu Nov 17 2022, 11:59:54
Post a reply to this comment:
Your Name:
Your Email:
(no HTML tags; use plain text, and hit Enter for a line break)
Attached file (if you want, 5 MB max):
© 2008-2022 SolveSpace contributors. Most recent update June 2 2022.