CNC Torch Table 2/Research Development - Revision history

Samthetechie: taken content / overflow from old R&D page and also moved Dan's Status to the discussion page!

2013-12-05T03:06:24Z

taken content / overflow from old R&D page and also moved Dan's Status to the discussion page!

Daniel Benamy at 05:51, 1 November 2013

2013-11-01T05:51:47Z

← Older revision		Revision as of 05:51, 1 November 2013
Line 9:		Line 9:
	For the short term Dan plans to get the version 2 table up and running ASAP with the [[RAMPS]] system so we can get something working and build momentum. Then we can quickly iterate to incorporate better modules such as the [[Steppernug]], [[CoolDRV]], or [[CoolRAMPS]] which will allow us to cut faster, better sensors for more reliable operation, fuel control for more efficient fuel usage, etc.		For the short term Dan plans to get the version 2 table up and running ASAP with the [[RAMPS]] system so we can get something working and build momentum. Then we can quickly iterate to incorporate better modules such as the [[Steppernug]], [[CoolDRV]], or [[CoolRAMPS]] which will allow us to cut faster, better sensors for more reliable operation, fuel control for more efficient fuel usage, etc.

	Generally, the strategy is to '''make lots of quick iterations with self-contained improvements''' so we almost always have a working table and project handoff is simpler. Dan is focusing on '''getting something working''' at FeF that we can use to cut parts we need for other machines, '''rather than something that's easily reproducible or perfectly documented'''. Dan's trading off robustness, reproducibility, and user friendly docs for getting it working. Dan's doing this for two reasons: being able to cut [[Warehouse]] parts will save lots of time and money on all other development, and it will be a waste of effort to carefully document stuff that turns out not to work well. Once we get to the point where we can cut useful stuff, Dan (or you!) will need to make any changes needed for ease of reproduction, and create awesome manufacturing guides so others can copy it.		Generally, the strategy is to '''make lots of quick iterations with self-contained improvements''' so we almost always have a working table and project handoff is simpler. If something doesn't work out. it's easy to revert to the previously working state.

			Dan is focusing on '''getting something working''' at FeF that we can use to cut parts we need for other machines, '''rather than something that's easily reproducible or perfectly documented'''. Dan's trading off robustness, reproducibility, and user friendly docs for getting it working. Dan's doing this for two reasons: being able to cut [[Warehouse]] parts will save lots of time and money on all other development, and it will be a waste of effort to carefully document stuff that turns out not to work well. Once we get to the point where we can cut useful stuff, Dan (or you!) will need to make any changes needed for ease of reproduction, and create awesome manufacturing guides so others can copy it.

	Lots of info on the control systems at [[CNC Torch Table 2/Control Overview]].		Lots of info on the control systems at [[CNC Torch Table 2/Control Overview]].

	~~=Next Steps=~~		Concrete tasks that need doing are in github. Go to https://github.com/OSE/CNC-Torch-Table-OSE/issues?state=open and select a milestone on the left, with the little gear icon. Milestone 1 is to be able to cut [[Warehouse]] plates. Milestone 2 is to be able to cut tubes.

	~~Then I'd do incremental improvements, keeping the table working after each step so if I had to leave or something didn't work, it'd be easy to revert to the most recent working stuff.~~

	~~Next steps~~ in github. Go to https://github.com/OSE/CNC-Torch-Table-OSE/issues?state=open and select a milestone on the left, with the little gear icon.

	=Developement Board=		=Developement Board=

Daniel Benamy: /* Status */

2013-11-01T05:50:10Z

Status

← Older revision		Revision as of 05:50, 1 November 2013
Line 5:		Line 5:
	This is Dan Benamy's understanding as of Oct 2013:		This is Dan Benamy's understanding as of Oct 2013:

	There have been various ambitious projects over the past few years to do amazing things with the torch table. Unfortunately none of them seem to have reached the finish line (including integration with all the other work).		There have been various ambitious projects over the past few years to do amazing things with the torch table. Unfortunately none of them seem to have reached the finish line (including integration with all the other work) and so FeF never got a table we could use for fabrication.

	For the short term Dan plans to get the version 2 table up and running ASAP with the [[RAMPS]] system so we can get something working and build momentum. Then we can quickly iterate to incorporate better modules such as the [[Steppernug]], [[CoolDRV]], or [[CoolRAMPS]] which will allow us to cut faster, sensors for more reliable operation, fuel control for more efficient fuel usage, etc.		For the short term Dan plans to get the version 2 table up and running ASAP with the [[RAMPS]] system so we can get something working and build momentum. Then we can quickly iterate to incorporate better modules such as the [[Steppernug]], [[CoolDRV]], or [[CoolRAMPS]] which will allow us to cut faster, better sensors for more reliable operation, fuel control for more efficient fuel usage, etc.

	Generally, ~~Dan's~~ strategy is to '''make lots of quick iterations with self-contained improvements''' so we almost always have a working table and project handoff is simpler. ~~I'm also~~ focusing on '''getting something working''' at FeF that we can use to cut parts we need for other machines, '''rather than something that's easily reproducible or perfectly documented'''. I'm trading off reproducibility and user friendly docs for getting it working for two reasons: 1- being able to cut [[Warehouse]] parts will save lots of time and money on all other development~~. 2-~~ it will ~~also~~ be a waste of effort to carefully document stuff that turns out not to work well. Once we get to the point where we can cut useful stuff, I (or you!) will need to make any changes needed for ease of reproduction, and create awesome manufacturing guides so others can copy it.		Generally, the strategy is to '''make lots of quick iterations with self-contained improvements''' so we almost always have a working table and project handoff is simpler. Dan is focusing on '''getting something working''' at FeF that we can use to cut parts we need for other machines, '''rather than something that's easily reproducible or perfectly documented'''. Dan's trading off robustness, reproducibility, and user friendly docs for getting it working. Dan's doing this for two reasons: being able to cut [[Warehouse]] parts will save lots of time and money on all other development, and it will be a waste of effort to carefully document stuff that turns out not to work well. Once we get to the point where we can cut useful stuff, Dan (or you!) will need to make any changes needed for ease of reproduction, and create awesome manufacturing guides so others can copy it.

	Lots of info on the control systems at [[CNC Torch Table 2/Control Overview]].		Lots of info on the control systems at [[CNC Torch Table 2/Control Overview]].

Daniel Benamy: /* Next Steps */

2013-11-01T05:47:49Z

Next Steps

← Older revision		Revision as of 05:47, 1 November 2013
Line 14:		Line 14:

	=Next Steps=		=Next Steps=

	* Run a simple test gcode program- https://github.com/grbl/grbl/wiki/G-Code-Examples.

	Then I'd do incremental improvements, keeping the table working after each step so if I had to leave or something didn't work, it'd be easy to revert to the most recent working stuff.		Then I'd do incremental improvements, keeping the table working after each step so if I had to leave or something didn't work, it'd be easy to revert to the most recent working stuff.

Daniel Benamy: /* Next Steps */

2013-10-31T17:42:17Z

Next Steps

← Older revision		Revision as of 17:42, 31 October 2013
Line 19:		Line 19:
	Then I'd do incremental improvements, keeping the table working after each step so if I had to leave or something didn't work, it'd be easy to revert to the most recent working stuff.		Then I'd do incremental improvements, keeping the table working after each step so if I had to leave or something didn't work, it'd be easy to revert to the most recent working stuff.

	~~Tasks~~ in github ~~(link below)~~. ~~Sort by~~ milestone.		Next steps in github. Go to https://github.com/OSE/CNC-Torch-Table-OSE/issues?state=open and select a milestone on the left, with the little gear icon.

	=Developement Board=		=Developement Board=

Daniel Benamy: /* Next Steps */

2013-10-31T17:37:45Z

Next Steps

← Older revision		Revision as of 17:37, 31 October 2013
Line 16:		Line 16:

	* Run a simple test gcode program- https://github.com/grbl/grbl/wiki/G-Code-Examples.		* Run a simple test gcode program- https://github.com/grbl/grbl/wiki/G-Code-Examples.
	* Draw a rectangle in librecad, run it through [[DXF to G-code Conversion Tutorial \| dxf2gcode]] and use [http://reprap.org/wiki/Pronterface Printrun] to stream it to the arduino. Get the table to draw the rectangle.

	Then I'd do incremental improvements, keeping the table working after each step so if I had to leave or something didn't work, it'd be easy to revert to the most recent working stuff.		Then I'd do incremental improvements, keeping the table working after each step so if I had to leave or something didn't work, it'd be easy to revert to the most recent working stuff.

Daniel Benamy: /* Next Steps */

2013-10-31T05:18:44Z

Next Steps

← Older revision		Revision as of 05:18, 31 October 2013
Line 18:		Line 18:
	* Draw a rectangle in librecad, run it through [[DXF to G-code Conversion Tutorial \| dxf2gcode]] and use [http://reprap.org/wiki/Pronterface Printrun] to stream it to the arduino. Get the table to draw the rectangle.		* Draw a rectangle in librecad, run it through [[DXF to G-code Conversion Tutorial \| dxf2gcode]] and use [http://reprap.org/wiki/Pronterface Printrun] to stream it to the arduino. Get the table to draw the rectangle.

	Then I'd do incremental improvements, keeping the table working after each step so if I had to leave or something didn't work, it'd be easy to revert to the most recent working stuff~~. Steps until we could use the table to actually make parts for fabricating other machines:~~		Then I'd do incremental improvements, keeping the table working after each step so if I had to leave or something didn't work, it'd be easy to revert to the most recent working stuff.
	* Add a circle to the dxf that's not touching the rectangle. Re-run and make sure the head lifts up between the shapes.
	* Add [[DXF_to_G-code_Conversion_Tutorial#Piercing \| gcode postprocessing]] if still needed for piercing and torch width. The "torch" should move back and forth while making an initial "pierce". For the circle, I think it should make the pieces inside the circle. I'm not sure if it should pierce the rectangle inside or on one edge. We want it to make the pierce in a part of the metal we won't use. I wonder how the piercing code knows what that is... There's a conversation [https://groups.google.com/forum/#!msg/dxf2gcode-dev/6ZnNcX3O5i4/d-3NeBfHpbUJ here] about integrating this functionality into dxf2gcode which would be great for ease of use and gives us a gui where maybe we could click where we want the pierce to be.
	* Try it with the real torch!!! For future steps, I'd switch back to the sharpie for testing and only use the torch once things look good.

	~~If we're lucky, this gets us to milestone 1 - can cut useful warehouse plates.~~		Tasks in github (link below). Sort by milestone.

	Tasks ~~for milestone 2 and beyond are~~ in github (link below).

	=Developement Board=		=Developement Board=

Daniel Benamy: /* Next Steps */

2013-10-31T02:47:01Z

Next Steps

← Older revision		Revision as of 02:47, 31 October 2013
Line 15:		Line 15:
	=Next Steps=		=Next Steps=

	* Fix stiff long axis motor.
	* The standard RAMPS setup for 2 motors on one axis is to run them in parallel off one driver. Since our motors draw a fair amount of current, try to use a separate driver for each motor and [http://shapeoko.com/forum/viewtopic.php?f=4&t=1095 modify marlin] to drive those two drivers identically.
	* Run a simple test gcode program- https://github.com/grbl/grbl/wiki/G-Code-Examples.		* Run a simple test gcode program- https://github.com/grbl/grbl/wiki/G-Code-Examples.
	* Draw a rectangle in librecad, run it through [[DXF to G-code Conversion Tutorial \| dxf2gcode]] and use [http://reprap.org/wiki/Pronterface Printrun] to stream it to the arduino. Get the table to draw the rectangle.		* Draw a rectangle in librecad, run it through [[DXF to G-code Conversion Tutorial \| dxf2gcode]] and use [http://reprap.org/wiki/Pronterface Printrun] to stream it to the arduino. Get the table to draw the rectangle.

Daniel Benamy at 00:36, 31 October 2013

2013-10-31T00:36:34Z

← Older revision		Revision as of 00:36, 31 October 2013
Line 30:		Line 30:

	=Developement Board=		=Developement Board=
	<html><iframe width=80% height='~~500~~' frameborder='0' src='https://docs.google.com/spreadsheet/pub?key=0Av4ZjQn4DHJHdDBNVmlFTmZ5S3YxckY3ZkxZc01ISHc&output=html&widget=true'></iframe></html>		<html><iframe width=80% height='400' frameborder='0' src='https://docs.google.com/spreadsheet/pub?key=0Av4ZjQn4DHJHdDBNVmlFTmZ5S3YxckY3ZkxZc01ISHc&output=html&widget=true'></iframe></html>

	[https://docs.google.com/spreadsheet/ccc?key=0Av4ZjQn4DHJHdDBNVmlFTmZ5S3YxckY3ZkxZc01ISHc#gid=2 edit]		[https://docs.google.com/spreadsheet/ccc?key=0Av4ZjQn4DHJHdDBNVmlFTmZ5S3YxckY3ZkxZc01ISHc#gid=2 edit]

	~~=Design=~~
	~~[[Image:Table_Frame.JPG\|none\|360px\|Torch Table Prototype II Design.]]~~

	~~Lots of information about the control system in [[CNC Torch Table 2/Control Overview]].~~

	~~Additional discussion at [[TorchTableModularTooling]]~~

	=Resources=		=Resources=
Line 48:		Line 41:
	** [http://opensourceecology.org/w/images/7/79/CNC_Torch_Table_-_Sketchup_Model.zip] - Sketchup files - I don't know if there are conversions of the solidworks files in github or something else.		** [http://opensourceecology.org/w/images/7/79/CNC_Torch_Table_-_Sketchup_Model.zip] - Sketchup files - I don't know if there are conversions of the solidworks files in github or something else.
	* 2d drawings- [http://opensourceecology.org/w/images/d/d1/Creation_Flame_CNC_Torch_Table_Drawings.zip] - DXFs of motor mounts		* 2d drawings- [http://opensourceecology.org/w/images/d/d1/Creation_Flame_CNC_Torch_Table_Drawings.zip] - DXFs of motor mounts

			=Design=
			[[Image:Table_Frame.JPG\|none\|360px\|Torch Table Prototype II Design.]]

			Lots of information about the control system in [[CNC Torch Table 2/Control Overview]].

			Additional discussion at [[TorchTableModularTooling]]

	=Additional Notes=		=Additional Notes=
	*As a large x-y-z coordinate table, the Torch Table has potential applications with other tooling besides a cutting torch. One limitation is that the drive system is not powerful enough or stiff enough to support heavy cutting-tool forces.		*As a large x-y-z coordinate table, the Torch Table has potential applications with other tooling besides a cutting torch. One limitation is that the drive system is not powerful enough or stiff enough to support heavy cutting-tool forces.

Daniel Benamy: /* Next Steps */

2013-10-31T00:30:07Z

Next Steps

← Older revision		Revision as of 00:30, 31 October 2013
Line 25:		Line 25:
	* Try it with the real torch!!! For future steps, I'd switch back to the sharpie for testing and only use the torch once things look good.		* Try it with the real torch!!! For future steps, I'd switch back to the sharpie for testing and only use the torch once things look good.

	~~More~~ in github (~~see~~ below).		If we're lucky, this gets us to milestone 1 - can cut useful warehouse plates.

			Tasks for milestone 2 and beyond are in github (link below).

	=Developement Board=		=Developement Board=