TorchTableToolChainTesting - Revision history

Aidan Williamson at 23:58, 13 June 2014

2014-06-13T23:58:12Z

← Older revision		Revision as of 23:58, 13 June 2014
Line 1:		Line 1:
			{{Template:Category=Torch Table}}
	= Tool chain experiments for Torch Table programming =		= Tool chain experiments for Torch Table programming =

2013-02-04T16:33:42Z

open paths

← Older revision		Revision as of 16:33, 4 February 2013
Line 217:		Line 217:

	=== open paths ===		=== open paths ===
	Many parts require the torch to simply cut along line (not a closed path), for example narrow slots for fold lines. There doesn't seem to be any way to generate an open path with implicitCAD. Maybe gcodetools can identify narrow (<= kerf-width) slots and convert them to open paths. Alternatively a purpose-~~build~~ Python script using the xtree package (parses xml; svg is an xml format) could identify narrow paths.		Many parts require the torch to simply cut along line (not a closed path), for example narrow slots for fold lines. There doesn't seem to be any way to generate an open path with implicitCAD. Maybe gcodetools can identify narrow (<= kerf-width) slots and convert them to open paths. Alternatively a purpose-built Python script using the xtree package (parses xml; svg is an xml format) could identify narrow paths.

	= Alibre -> DXF toolchain =		= Alibre -> DXF toolchain =

2013-02-04T16:33:25Z

open paths

← Older revision		Revision as of 16:33, 4 February 2013
Line 217:		Line 217:

	=== open paths ===		=== open paths ===
	Many parts require the torch to simply cut along line (not a closed path), for example narrow slots for fold lines. There doesn't seem to be any way to generate an open path with implicitCAD. Maybe gcodetools can identify narrow (<= kerf-width) slots and convert them to open paths.		Many parts require the torch to simply cut along line (not a closed path), for example narrow slots for fold lines. There doesn't seem to be any way to generate an open path with implicitCAD. Maybe gcodetools can identify narrow (<= kerf-width) slots and convert them to open paths. Alternatively a purpose-build Python script using the xtree package (parses xml; svg is an xml format) could identify narrow paths.

	= Alibre -> DXF toolchain =		= Alibre -> DXF toolchain =

2013-02-04T06:27:49Z

Tool chain experiments for Torch Table programming

@@ Line 85: / Line 85: @@
 With no output filename specified, it renders to ''<sourcefilename>.svg'' ok. [[User:ChuckH|ChuckH]] 12:29, 14 December 2012 (CET)
 === inkscape ===
@@ Line 232: / Line 213: @@
 [[file:LeadInWoopsies.png|400px]] [[File:gcode_path_cu.png|300px]]
 = Alibre -> DXF toolchain =

2013-02-03T23:51:20Z

implicitCAD hierarchical design

← Older revision		Revision as of 23:51, 3 February 2013
Line 44:		Line 44:
	$quality = 20;		$quality = 20;
	</pre>		</pre>
			=== Bends and tabs ===
			Sheet-metal bends and fold-up tabs are useful features. When designing these it is necessary to make [http://sheetmetal.me/bend-allowance/ bend allowance]. I am hoping to incorporate bend allowance computation into the extopenSCAD toolchain.

	== simple test part ==		== simple test part ==

2013-01-04T16:35:59Z

implicitCAD hierarchical design

← Older revision		Revision as of 16:35, 4 January 2013
Line 17:		Line 17:

	Work in progress [https://github.com/chuck-h/torchtab-mockup on github].		Work in progress [https://github.com/chuck-h/torchtab-mockup on github].

			<pre>
			// cpp test part
			// gantry drive side rail
			#include "StepperMounts/size34.escad"
			#include "HardwareMounts/FlangedBush375.escad"
			mmPerIn = 25.4;
			center_dist = 18;
			lip_width = 2;
			plate_length = center_dist+4;
			plate_width = lip_width+4;
			difference() {
			unit("in") {
			square([plate_length,plate_width]);
			}
			union() {
			translate([2mmPerIn, 4mmPerIn]) size34_cutout(); // motor mount
			translate([(2+center_dist)mmPerIn, 4mmPerIn]) SDPA7Z63FDU375_adjustable(0.375); // idler pulley mount
			foldline([0,lip_width]mmPerIn, [plate_length, lip_width]mmPerIn); // L-fold
			foldUpTab([4,lip_width+1.5]mmPerIn, [8,lip_width+1.5]mmPerIn, -0.75*mmPerIn); // home sensor flag
			foldUpTab([4,lip_width+2.25]mmPerIn, [6,lip_width+2.25]mmPerIn, 0.75*mmPerIn); // limit sensor flag 1
			foldUpTab([center_dist-2,lip_width+2.25]mmPerIn, [center_dist,lip_width+2.25]mmPerIn, 0.75*mmPerIn); // limit sensor flag 2
			}
			}

			$quality = 20;
			</pre>

	== simple test part ==		== simple test part ==

2013-01-04T16:20:43Z

implicitCAD hierarchical design

← Older revision		Revision as of 16:20, 4 January 2013
Line 13:		Line 13:
	== implicitCAD hierarchical design ==		== implicitCAD hierarchical design ==

			[[File:Part.svg\|thumb\|gantry side rail from hierarchical extopenSCAD design]]
	I have been using gnu make and cpp (c macro preprocessor) with extopenSCAD files to manage dependencies.		I have been using gnu make and cpp (c macro preprocessor) with extopenSCAD files to manage dependencies.

2013-01-04T16:16:17Z

Tool chain experiments for Torch Table programming

← Older revision		Revision as of 16:16, 4 January 2013
Line 10:		Line 10:
	*** download implicitCAD using cabal (see [[https://github.com/colah/ImplicitCAD#readme instructions]]), but it does not build properly. (Unfortunately I did not record exactly my sequence of steps here. Among other things I think I needed to copy mingw's gawk program and rename it awk for cabal to build.)		*** download implicitCAD using cabal (see [[https://github.com/colah/ImplicitCAD#readme instructions]]), but it does not build properly. (Unfortunately I did not record exactly my sequence of steps here. Among other things I think I needed to copy mingw's gawk program and rename it awk for cabal to build.)
	*** patch implicitCAD files to enable Windows install. [[file:ImplicitCADWindowsPatch0.doc]]This patch made it compile for me, at the cost of disabling PNG output (not necessary for our toolchain) and disabling file includes (probably painful; need workaround).		*** patch implicitCAD files to enable Windows install. [[file:ImplicitCADWindowsPatch0.doc]]This patch made it compile for me, at the cost of disabling PNG output (not necessary for our toolchain) and disabling file includes (probably painful; need workaround).

			== implicitCAD hierarchical design ==

			I have been using gnu make and cpp (c macro preprocessor) with extopenSCAD files to manage dependencies.

			Work in progress [https://github.com/chuck-h/torchtab-mockup on github].

	== simple test part ==		== simple test part ==

2012-12-14T11:29:32Z

implicitCAD

← Older revision		Revision as of 11:29, 14 December 2012
Line 47:		Line 47:
	extopenscad: Prelude.head: empty list		extopenscad: Prelude.head: empty list
	</pre>		</pre>
	With no output filename specified, it renders to ''<sourcefilename>.svg'' ok.		With no output filename specified, it renders to ''<sourcefilename>.svg'' ok. [[User:ChuckH\|ChuckH]] 12:29, 14 December 2012 (CET)

	=== convert svg scale ===		=== convert svg scale ===

2012-12-14T11:29:08Z

implicitCAD

← Older revision		Revision as of 11:29, 14 December 2012
Line 39:		Line 39:
	extopenscad 164_plate.escad out.svg		extopenscad 164_plate.escad out.svg
	</pre>		</pre>

			Hmmm. This used to work but now it doesn't like the output file being specified
			<pre>
			>extopenscad 164_plate.escad out.svg
			Rendering 3D object to out.svg
			With resolution 17.129469
			extopenscad: Prelude.head: empty list
			</pre>
			With no output filename specified, it renders to ''<sourcefilename>.svg'' ok.

	=== convert svg scale ===		=== convert svg scale ===