CNC Torch Table 2/Research Development: Difference between revisions

From Open Source Ecology
Jump to navigation Jump to search
Line 7: Line 7:
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).


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]] which will allow us to cut faster.
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.


Generally, my 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, 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.


Lots of info on the control systems at [[CNC Torch Table 2/Control Overview]]. That page predates me (Dan) so may have outdated info although I've updated much of it.
Lots of info on the control systems at [[CNC Torch Table 2/Control Overview]].


=Next Steps=
=Next Steps=

Revision as of 23:24, 30 October 2013


CNC Torch Table 2
   Home  |  Research & Development  |  Bill of Materials  |  Manufacturing Instructions  |  User's Manual  |  User Reviews    CNC Torch Table 2.png

Status

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).

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.

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.

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

Next Steps

More next steps are in git (link below) and I'll be moving the rest of these there.

  • 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 modify marlin to drive those two drivers identically.
  • Run a simple test gcode program- https://github.com/grbl/grbl/wiki/G-Code-Examples.
  • Draw a rectangle in librecad, run it through dxf2gcode and use 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:

  • 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 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 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.
  • Computer control of the torch since the ratio of fuel to oxygen should change for piercing vs cutting.
  • Endstops.
  • More powerful stepper drivers to allow faster movement (

Developement Board

edit

Design

Torch Table Prototype II Design.

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

Additional discussion at TorchTableModularTooling

Resources

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.