CNC Torch Table 2/Control Overview

From Open Source Ecology
Jump to: navigation, search

Main > Digital Fabrication > RepLab Tools > Torch Table


Overview

edit

Motor controller and drivers

RAMPS

Dan's using RAMPS in Oct 2013 to get the table up and running ASAP. The plan is then to replace it with something beefier so we can go faster.

Alternatives

See Stepper Motor Controller and Stepper Motor Driver.

Software

G-code Prep

toolchain pathways

ImplicitCAD (see also Parametric_Design_Pilot_Project)

Gcodetools

DXF_to_G-code_Conversion_Tutorial

Computer_to_Microcontroller

Nesting software would be useful. Example commercial product here. Anything open source?

Gcode preheat

Correction for torch cut kerf width ("cutter compensation" in CNC lingo) needed. G40/G41 but grbl does not interpret these.

G Code Runner

aka firmware aka motor controller (distinct from motor driver)

This is the firmware running on Arduino which converts a series of G-code commands to step/direction pulses for the drivers.

Marlin

When Dan Benamy was getting things going again in Oct 2013, he was using Marlin because grbl doesn't work with RAMPS out of the box. Marlin also has pretty much out of the box support for 2 drivers feeding 2 motors on Y which we use for out long axis because it has 2 motors.

  • I cloned marlin from github and checked out the Marlin_v1 tag.
  • Edited Configuration.h
    • #define MOTHERBOARD 35
    • #define DISABLE_E true // For all extruders
    • #define TEMP_SENSOR_0 0 // Since we don't have temp sensors
    • #define TEMP_SENSOR_1 0 // Since we don't have temp sensors
    • #define DEFAULT_AXIS_STEPS_PER_UNIT {128.9304,142.5,200.0*8/3,760*1.1} // nov 1 2013- x and y are the right ballpark for the ose torch table at fef, see https://github.com/OSE/CNC-Torch-Table-OSE/issues/4#issuecomment-27460371 for where these numbers came from
    • I set the "*ENDSTOP_INVERTING" consts as appropriate for our endstops by running gcode M119, seeing if an endstop was triggered, pushing the button, and running M119 again. If the logic was backwards, I flipped the appropriate boolean.
    • I set the travel limits. There are 6 starting with "X_MAX_POS". I set the mins to 0. I set x and y max to 300 and z max to 150 for testing. Once we're calibrated and the table is fixed, we'll make these much bigger.
  • I made home = 0,0,0 = the corner of the torch table near the ping pong table with the tool head fully down. Then I can stand at one end of the table and look down at it and it the standard x is right, y is up orientation. And when looking at it from the side, positive z is up.
  • Edited Configuration_adv.h
    • Uncommented "#define Y_DUAL_STEPPER_DRIVERS". I used Y because Marlin doesn't support dual drivers on X. We'll use Y as the long axis, X as the short axis, and Z as height. The 2nd Y will be output on the 2nd extruder port (E1, http://reprap.org/wiki/RAMPS_1.4#Wiring)
  • Edited pins.h
    • In the section for motherboards 33, 34 35, added "#define Y2_STEP_PIN 36", "#define Y2_DIR_PIN 34", and "#define Y2_ENABLE_PIN 30". This is a Marlin bug and I've submitted a fix upstream- https://github.com/ErikZalm/Marlin/pull/635
  • Opened Marlin/Marlin/Marlin.pde in the arduino ide and clicked to compile and load it to the arduino.

grbl

When someone (Chuck?) was working on using the steppernug, they were running a modified grbl fork https://github.com/chuck-h/grbl/tree/edge. Changes from standard grbl [1]:

  • Hardware I/O reassignment for steppernug interface
    • different pin assignments on Arduino
    • I2C extender
  • substantially revised homing code
    • dual X axis
    • deep changes to stepper drive algorithm (implementing independent-axis trapezoidal move control during homing, as opposed to standard coordinated-axis move control for cutting) which should improve performance on long, limited-aceleration axes like torch table X and Y.

Sending G Code to Firmware

In Oct 2013, Dan can't find host software (gcode sending) that works with marlin. He tried about 8 different programs. For now the process is to use Printrun/Pronterface and copy/paste 3 or so gcodes at a time into there, wait for them to execute, and run the next batch. Pasting them all at once fails (machine does the wrong thing) probably because the instruction buffer in marlin isn't big enough.

See GcodeCommunications for a list of programs to send the g-code file from a host computer to a controller.

Hardware

Talk to Arduino with USB, or for longer distance RS422 e.g. MAX3488E

Testing

Testing

Here's a test gcode file which Dan Benamy hand wrote. It works on marlin and draws a 2 hole by 1 hole plate- https://github.com/OSE/CNC-Torch-Table-OSE/issues/20

Limits and Homing

This whole section hasn't been updated for the Oct 2013 work using RAMPS. See https://github.com/OSE/CNC-Torch-Table-OSE/issues/11 for some of this with RAMPS setup.

Also note that docs from before Oct 2013 refer to the long axis as X but with RAMPS and marlin we had to make the long axis Y.


Dual-motor homing

The x axis (long axis) has 2 stepper motors. In the steppernug system, these have separate driver modules which receive identical step, direction, and enable signals.

For zeroing, the x axis needs to decouple - so if we get the x axis out of parallel, we can jog the x axes back into parallel by hitting their home switches independently. Steppernug supports this by allowing the Arduino to control a gate which blocks step pulses to the second driver module; in this condition the second motor will freeze and only the first motor will move. There is no provision for moving the second motor without moving the first, but that function is not required for the homing algorithm.

Axis sequence

  1. We will home the Z axis to its upper position first, just in case there are obstructions to clear during the X and Y axis homing.
  2. X and Y axes will do their initial fast moves to find home simultaneously (overlapped homing) to save time.
  3. The Y precision home movement will be performed.
  4. The dual-X-axis precision home maneuver will be performed.

Limit and home switch configuration

HomeLimit.PNG

(TODO: add illustration showing distance coded reference mark options)

(Unconfirmed proposal at this time) ChuckH 23:42, 20 October 2012 (CEST)

Each axis has two switches: a limit switch and a home switch.

  • The limit switch is activated at *either* end of travel. Its function is to protect against machine damage.
    • Attempting to move further into the limit when the limit switch is active will cause all axis movement to stop, the torch to be shut off, and any other "safe shutdown" operation to be performed.
    • The limit switch could be hit if the program erroneously commands the tool to move beyond the edge of the table
    • The limit switch could also be hit if the torch table loses step (e.g. by hitting an obstruction) and subsequently performs a movement which takes it to the edge of the table
    • The limit switch may be implemented as two physical switches wired in parallel, or the machine construction may permit a single switch to be used.
    • Repeatable precision of actuation point is not very critical.
    • This function is especially important if the table is expected to do automated cutting without constant human supervision.
  • The home switch transitions between inactive and active at a point partway through the legal travel of the machine.
    • For example, it might be active at the negative end of travel, and go inactive after 6 inches of movement.
    • The home switch is used only for locating a repeatable zero position when the machine is powered on (or when recovering from lost steps)
      • Note that the logical "machine zero" coordinate may be placed at any programmed position relative to the physical home switch.
    • Repeatable precision may be important
      • For the dual-motor axis, to establish accurate squareness
      • For all axes, to pick up in the middle of an interrupted job
      • If fixturing is used for repeat "production style" operations
    • (update, 14-July-2103:) Instead of responding to a single flag location, the home switch could be actuated many times by multiple flags along the travel, with carefully designed nonuniform spacing between flags
      • This implements "distance coded reference marks" (DCRM), e.g. [[2]], [[3]], [[4]]
      • DCRM is often applied to incremental linear encoder systems; the same principle is effective here using motor step count as the "incremental scale".
      • Using DCRM, the axis only needs to traverse two flag transitions after startup in order to unambiguously determine absolute position.
    • By construction, the home switch is active at one end of travel and inactive at the other
      • This allows the machine to know which end of travel it is at in the event the limit switch is activated
      • This, in turn, allows the machine to permit recovery movement from the limit condition back into legal travel, while ignoring a command to go further into the limit zone.

There is an alternative switch configuration which places individual limit switches at the positive and negative limits of legal travel. However the configuration above is preferred because it supports faster homing and simpler control logic. Specifically:

  1. The substantial distance between the end of travel and the home switch location gives the machine overtravel room to do a controlled stop from high speed: maximum slewing speed can be used during initial homing without risk of slamming into the physical end-of-travel.
  2. Home switch placement can minimize the typical startup time.
    • If an axis is usually parked near one end of travel, the home switch can be placed there
    • If the axis position on startup is random, placing the home switch in the center of travel will minimize the average seek time.
    • DCRM can be implemented to obtain short startup/home times no matter what the starting position.
  3. The "safety shutdown" limit-switch function can be always active, and is independent of homing
    • The alternative approach requires logically repurposing a limit switch as home switch during home operations

Switch Types

The steppernug interface provides 5V power to sensor switches so either electronic or mechanical switches are easily accommodated.

  • Mechanical microswitches are simple and effective.
  • A Hall switch (e.g. this) is rugged but its position precision is probably only suitable for limits, not home switches.
  • An optical interrupter (e.g. Sharp GP1A75EJ000F) can give precisely repeatable homing.

Switch response time

The home switch should respond within one motor step time at the "creep speed" used for final approach. This speed might be ~100 steps/sec which gives us ~10ms.

The limit switch should respond quickly enough so that an emergency stop initiated by the switch will stop the machine motion before it hits a mechanical stop. This time is dependent on a lot of different design parameters, but is probably at least 10ms.

The limited response speed required allows us some latitude for noise suppression.

Since all switch signals pass through the I2C expander for I/O, there is about 150 usec (0.15ms) added, see here.

Torch control

Software can use an M code to start the cut (e.g. open cutting-oxygen valve, strike plasma arc).

A second M code could shut down the entire torch (e.g. at the end of an unsupervised cutting session).

See also CNC_Torch_Table/Research_Development#Cutting_Torch

Plasma Torch

Plasma_Cutter_Design#Plasma_Cutter_PC_Interface

This presentation on plasma-cutting accurate holes also suggests that ramping down plasma current while torch is still moving is good practice. (It makes the electrodes last longer.)

Z-axis arc voltage height control. Needs design work.

Cutting speed

Hypertherm:

PlasmaSpeed.jpg


Oxyfuel (oxyacetylene, oxypropane, etc) cutting torch

During cutting, an oxyfuel cutting torch is literally burning the steel with a blast of oxygen; most of the heat comes from oxidizing the iron. However to start a new cut ("piercing") you must preheat the steel, relying on the acetylene or LPG for heat. After the steel is red hot you boost the oxygen flow and make the cut. We will want an oxygen-rated valve controlled by the microprocessor. "Oxygen-rated" mostly means the valve is thoroughly cleaned of all oil or flammable solvents that tend to explode on contact with pure oxygen; good practical reference here. A solenoid valve like this in combination with an ordinary regulator would give basic on/off control, but see better suggestions below.

Fairly technical application note about how to do good oxyfuel machine cutting from ESAB: [5]

This long forum thread contains a lot of information about implementing small-shop CNC oxyfuel with programmed preheat, pierce, and cutting gas controls, auto ignition, etc. Based partly on this information, here are some control design suggestions for an Arduino-based CNC like CoolRAMPS or Steppernug/grbl:

  • use dome loaded regulators (e.g. Victor DL700 [6] [7]) driven by regulated shop air
    DL700.png
    VTS250.png
    • general description of spring- and dome-loaded regulators here
    • It appears that almost any standard screw-handle regulator can be converted to "dome loaded" by sealing up the housing cap and replacing the screw/spring with an air pressure fitting. See video below. A classic dual-stage like the VTS250 should work very nicely for conversion
    • As with manual regulators, if oxy- or fuel-tank pressure exceeds inlet rating of dome-loaded regulator, a first-stage tank regulator will be required.
    • With the dome-loaded regulators, gas on/off as well as pressure setting can be obtained with low-cost shop air components and small valves (e.g 4V130C,AVS-523C1)
    • Using a solid-state pressure sensor for feedback, the Arduino can set the regulated pressures to programmed levels by actuating the pneumatic valves (increase/decrease loading pressure until feedback is correct). See video below and code on github.
  • use an electric igniter (RV fridge igniter, BBQ igniter, spark coil).
  • follow the sequencing of x,y,z motions, pressure changes, on/off, and ignition described by the folks on the forum thread above.
    • Develop a library of pressure/time/positioning parameters for different material thicknesses and tip sizes that can be applied automatically by the G-code programming; this should minimize setup time and tweaking.



Installing a needle valve at the solenoid air valve improved control smoothness a bit compared to video above.

ClippardNeedle.jpg


oxygen

The cutting oxygen for the torch must be high purity (according to the ESAB note above less than 95% purity simply will not cut steel, and >99.5% is required for best quality). Until recently, this meant cryogenically separated oxygen, depending on a large capital plant, and thus the user must rely on commercially provided tank oxygen. For some 30 years, pressure-swing-adsorption (PSA) separators have been available, but standard designs do not remove argon and therefore result in about 95%-oxygen, 5%-argon output gas. PSA construction is low-tech and works very nicely at small scale, e.g. portable breathing-oxygen units, and would be quite suitable for OSE. 95% purity is probably adequate for the preheat flame (ChuckH conjecture). For higher-purity cutting oxygen, PSA can be extended with additional zeolite materials [8] or activated carbon [9]; despite this discussion there is no clear record of small-scale DIY implementation of 99% oxygen PSA.

oxyacetylene

Recommendations from Victor:

Victor Oxy Acetylene.jpg

Commercial oxy-fuel machine cutting heads

  • Czech one with capacitive height sensor feature

Components offered by JB: CNC_Torch_Table_Log#Oct._21.2C_2012

Oxy-propane, -natural gas, etc

Propane instead of acetylene. Note the large preheat oxygen flow (not in a consistent stoichiometric ratio to fuel) in this chart. Odd.

VictorLPGcutting.png

Would gasifier-gas or biogas & oxygen work? Probably, as natural gas is primarily methane and is a commercially successful cutting-torch fuel.

See Also

Distributed_CNC_Motion_Control