OpenSCAD - revision history

Dank at 08:29, 2 October 2024

2024-10-02T08:29:12Z

← Older revision		Revision as of 08:29, 2 October 2024
Line 1:		Line 1:
	OpenSCAD is a declarative 3d modeling program. Objects are defined in terms of basic 2D and 3D shapes, and a set of operators is provided to manipulate these objects. It can generate STL files from the command line.		OpenSCAD is a declarative 3d modeling program. Objects are defined in terms of basic 2D and 3D shapes, and a set of operators is provided to manipulate these objects. It can generate STL files from the command line. Note that OpenSCAD approximates arcs with polygons, and emits meshes; it cannot emit e.g. true circles. As a result, there might be fewer G2/G3 arcs in the sliced gcode.

	==Basic shapes==		==Basic shapes==

Dank at 08:22, 2 October 2024

2024-10-02T08:22:22Z

← Older revision		Revision as of 08:22, 2 October 2024
Line 15:		Line 15:

	Generally, in each project I'll have a common file in which my base objects (and their geometry) are declared. Then I build up structures from these objects, relating them using the declared geometries. Be sure to declare the geometries of these structures as their own variables (composed from substructure properties). Then, for each print job, I have a file which <tt>include</tt>s this common file, and calls those <tt>module</tt>s to be printed. There shouldn't be any composition in these files, just any <tt>translate</tt>s, <tt>rotate</tt>s, and <tt>mirror</tt>s necessary to distribute the objects optimally on a print tray. Ensure they're distinct, so that slicing software can treat them as different objects (necessary for e.g. multimaterial printing). Finally, I have a file which assembles all the pieces together as they're expected to be assembled, serving as a check on the objects; neither this file nor the common file are exported to STL.		Generally, in each project I'll have a common file in which my base objects (and their geometry) are declared. Then I build up structures from these objects, relating them using the declared geometries. Be sure to declare the geometries of these structures as their own variables (composed from substructure properties). Then, for each print job, I have a file which <tt>include</tt>s this common file, and calls those <tt>module</tt>s to be printed. There shouldn't be any composition in these files, just any <tt>translate</tt>s, <tt>rotate</tt>s, and <tt>mirror</tt>s necessary to distribute the objects optimally on a print tray. Ensure they're distinct, so that slicing software can treat them as different objects (necessary for e.g. multimaterial printing). Finally, I have a file which assembles all the pieces together as they're expected to be assembled, serving as a check on the objects; neither this file nor the common file are exported to STL.

			[[CATEGORY: 3D Printing]]

Dank: /* use vs include */

2024-10-02T08:12:40Z

use vs include

← Older revision		Revision as of 08:12, 2 October 2024
Line 10:		Line 10:

	==<tt>use</tt> vs <tt>include</tt>==		==<tt>use</tt> vs <tt>include</tt>==
	A SCAD file can include other SCAD files with either the <tt>include</tt> or <tt>use</tt> keywords. <tt>include</tt> statements are replaced with the body of the <tt>include</tt>d file (any <tt>include</tt>s or <tt>use</tt>s within the file are expanded). <tt>use</tt> only lifts <tt>module</tt>s and <tt>function</tt>s, and only affects the current file (i.e. recursive <tt>use</tt>s do not escape beyond the file that <tt>use</tt>s them).		A SCAD file can include other SCAD files with either the <tt>include</tt> or <tt>use</tt> keywords. <tt>include</tt> statements are replaced with the body of the <tt>include</tt>d file (any <tt>include</tt>s or <tt>use</tt>s within the file are expanded). <tt>use</tt> only lifts <tt>module</tt>s and <tt>function</tt>s, and only affects the current file (i.e. recursive <tt>use</tt>s do not escape beyond the file that <tt>use</tt>s them). These cannot be used within a <tt>module</tt> or <tt>function</tt>.

	It's useful to have a file draw its various modules, so that running it at the top level generates examples etc. Such a file can be imported with <tt>use</tt>, and these examples won't be drawn. The downside is that any variables declared in a <tt>use</tt>d file are unavailable, so you might want to wrap them in <tt>function</tt> accessors.		It's useful to have a file draw its various modules, so that running it at the top level generates examples etc. Such a file can be imported with <tt>use</tt>, and these examples won't be drawn. The downside is that any variables declared in a <tt>use</tt>d file are unavailable, so you might want to wrap them in <tt>function</tt> accessors.

	~~These cannot be used within~~ a <tt>module</tt> or <tt>~~function~~</tt>.		Generally, in each project I'll have a common file in which my base objects (and their geometry) are declared. Then I build up structures from these objects, relating them using the declared geometries. Be sure to declare the geometries of these structures as their own variables (composed from substructure properties). Then, for each print job, I have a file which <tt>include</tt>s this common file, and calls those <tt>module</tt>s to be printed. There shouldn't be any composition in these files, just any <tt>translate</tt>s, <tt>rotate</tt>s, and <tt>mirror</tt>s necessary to distribute the objects optimally on a print tray. Ensure they're distinct, so that slicing software can treat them as different objects (necessary for e.g. multimaterial printing). Finally, I have a file which assembles all the pieces together as they're expected to be assembled, serving as a check on the objects; neither this file nor the common file are exported to STL.

Dank: /* use vs include */

2024-10-02T08:02:43Z

use vs include

← Older revision		Revision as of 08:02, 2 October 2024
Line 12:		Line 12:
	A SCAD file can include other SCAD files with either the <tt>include</tt> or <tt>use</tt> keywords. <tt>include</tt> statements are replaced with the body of the <tt>include</tt>d file (any <tt>include</tt>s or <tt>use</tt>s within the file are expanded). <tt>use</tt> only lifts <tt>module</tt>s and <tt>function</tt>s, and only affects the current file (i.e. recursive <tt>use</tt>s do not escape beyond the file that <tt>use</tt>s them).		A SCAD file can include other SCAD files with either the <tt>include</tt> or <tt>use</tt> keywords. <tt>include</tt> statements are replaced with the body of the <tt>include</tt>d file (any <tt>include</tt>s or <tt>use</tt>s within the file are expanded). <tt>use</tt> only lifts <tt>module</tt>s and <tt>function</tt>s, and only affects the current file (i.e. recursive <tt>use</tt>s do not escape beyond the file that <tt>use</tt>s them).

	It's useful to have a file draw its various modules, so that running it at the top level generates examples etc. Such a file can be imported with <tt>use</tt>, and these examples won't be drawn.		It's useful to have a file draw its various modules, so that running it at the top level generates examples etc. Such a file can be imported with <tt>use</tt>, and these examples won't be drawn. The downside is that any variables declared in a <tt>use</tt>d file are unavailable, so you might want to wrap them in <tt>function</tt> accessors.

	These cannot be used within a <tt>module</tt> or <tt>function</tt>.		These cannot be used within a <tt>module</tt> or <tt>function</tt>.

Dank: /* Basic shapes */

2024-10-02T07:39:45Z

Basic shapes

← Older revision		Revision as of 07:39, 2 October 2024
Line 2:		Line 2:

	==Basic shapes==		==Basic shapes==
	* ~~Square~~ (rectangle), circle, polygon		* <tt>square</tt> (rectangle), <tt>circle</tt>, <tt>polygon</tt>
	* ~~Cube~~ (rectangular prism), sphere, cylinder, polyhedron		* <tt>cube</tt> (rectangular prism), <tt>sphere</tt>, <tt>cylinder</tt>, <tt>polyhedron</tt>

	<tt>circle</tt> and <tt>cylinder</tt> are approximated using the <tt>fn</tt> system variable. Low values of <tt>fn</tt> can be used to generate regular polygons. A cylinder can have different radii at its top and bottom. A right pentagonal frustrum, for instance, can be generated with <tt>cylinder</tt> using <tt>fn=5</tt>.		<tt>circle</tt> and <tt>cylinder</tt> are approximated using the <tt>fn</tt> system variable. Low values of <tt>fn</tt> can be used to generate regular polygons. A cylinder can have different radii at its top and bottom. A right pentagonal frustrum, for instance, can be generated with <tt>cylinder</tt> using <tt>fn=5</tt>.

Dank at 07:39, 2 October 2024

2024-10-02T07:39:01Z

← Older revision		Revision as of 07:39, 2 October 2024
Line 8:		Line 8:

	A 2D shape can be converted into a 3D one using <tt>linear_extrude</tt> or <tt>rotate_extrude()</tt>.		A 2D shape can be converted into a 3D one using <tt>linear_extrude</tt> or <tt>rotate_extrude()</tt>.

			==<tt>use</tt> vs <tt>include</tt>==
			A SCAD file can include other SCAD files with either the <tt>include</tt> or <tt>use</tt> keywords. <tt>include</tt> statements are replaced with the body of the <tt>include</tt>d file (any <tt>include</tt>s or <tt>use</tt>s within the file are expanded). <tt>use</tt> only lifts <tt>module</tt>s and <tt>function</tt>s, and only affects the current file (i.e. recursive <tt>use</tt>s do not escape beyond the file that <tt>use</tt>s them).

			It's useful to have a file draw its various modules, so that running it at the top level generates examples etc. Such a file can be imported with <tt>use</tt>, and these examples won't be drawn.

			These cannot be used within a <tt>module</tt> or <tt>function</tt>.

Dank: Created page with "OpenSCAD is a declarative 3d modeling program. Objects are defined in terms of basic 2D and 3D shapes, and a set of operators is provided to manipulate these objects. It can generate STL files from the command line. ==Basic shapes== * Square (rectangle), circle, polygon * Cube (rectangular prism), sphere, cylinder, polyhedron `circle` and `cylinder` are approximated using the `fn` system variable. Low values of `fn` can be used to generate r..."

2024-09-29T05:25:47Z

Created page with "OpenSCAD is a declarative 3d modeling program. Objects are defined in terms of basic 2D and 3D shapes, and a set of operators is provided to manipulate these objects. It can generate STL files from the command line. ==Basic shapes== * Square (rectangle), circle, polygon * Cube (rectangular prism), sphere, cylinder, polyhedron <tt>circle</tt> and <tt>cylinder</tt> are approximated using the <tt>fn</tt> system variable. Low values of <tt>fn</tt> can be used to generate r..."

New page

OpenSCAD is a declarative 3d modeling program. Objects are defined in terms of basic 2D and 3D shapes, and a set of operators is provided to manipulate these objects. It can generate STL files from the command line.

==Basic shapes==
* Square (rectangle), circle, polygon
* Cube (rectangular prism), sphere, cylinder, polyhedron

<tt>circle</tt> and <tt>cylinder</tt> are approximated using the <tt>fn</tt> system variable. Low values of <tt>fn</tt> can be used to generate regular polygons. A cylinder can have different radii at its top and bottom. A right pentagonal frustrum, for instance, can be generated with <tt>cylinder</tt> using <tt>fn=5</tt>.

A 2D shape can be converted into a 3D one using <tt>linear_extrude</tt> or <tt>rotate_extrude()</tt>.