- Shared firmware with LaserCutter
- tool is synchronized with grbl line execution
- hotwire.cpp/.h is integrated in common tool.cpp/.h
- checkout LaserCutter/Firmware for more insides
- Removed source for library modification, use provided libraries instead
- Rotary knob improved (no library needed)
- Libraries for Arduino can be downloaded directly from here (solving some issues with library updateds and conflicts with grbl)
- Added blockdiagrams for setup with Ramps 1.4 / Ramps 1.6
- Added selection guide for hotwire and power supply
- Fans are optional, if not connected, Pin 10 do not need to be cutted
- Simple postprocessor integrated in SketchUp tool Foamcutter.rb
- Please let me know, if you have ideas or need improvements
Arduino based CNC foam cutter with display and SD-Card. Ruby Script for SketchUp Make 2017 to generate gcode. Swift base post processing
My goal was to build a foam based semi scale glider. So a lot of segments and very accurate working would have been necessary. This brought me to the idea to design the glider in SketchUp and build a 4 axis foam cutter.
The base idea ist very simple. Four independent linear axis with NEMA 17 stepper and belts. This simple system is satisfying, because the accuracy of the belt and stepper is better than the impact of the hot wire, it's temperature and feed speed and almost no force is required to cut the foam. The only mechanical topic is to keep the hot wire stretched. Therefore I found a very good idea here on GitHub with retractable reels.
For controlling the four axis I found a solutions based on grbl 8c2 in combination with some Windows bases UIs and gcode sender. For generating the wing profiles I found some windows solutions or professional tools, but not free of charge, neither running on mac. For the fuselage I found only a professional tool. As I don't want a computer in my workshop, the gcode should be executed from a SD card, similar as my 3D printer does. So I came to my project list:
- 4 independent axis
- local display, SD card reader and control buttons
- Arduino based gcode handling, based on grbl 8c2 version adapted for foam cutting.
- fixed frame based on 2020 profiles, v-slot based linear actors (it is my first cnc machine, so there are much easier and better mechanical constructions, have a lock on https://www.rckeith.co.uk)
- only one power supply
- wing design with third party tools:
- WingHelper (I have a licence), export of gcode is possible but post process is required, I use my own post processor in MacOS, see below.
- https://www.youtube.com/watch?v=uWO8kMGxqGU, Java based wing designer, including post processor. Exported dat file needs to be renamed to gcode-file extension. hotwire needs to be switched on manually.
- http://www.diyrcwings.com/app/, Online wing designer, including post processor and hotwire controller. Exported file extensio needs to be changed to .gcode
- fuselage design with SketchUp, therefore I wrote a small tool to generate gcode, see below
- post processing to adapt gcode to machine geometry for MacOS and combine multible jobs, see below
Many thanks to all the guys giving me grad inspirations with their projects
- Mechanic
- Hardware
- Firmware
- Functions
- Working with SketchUp Part 1
- Working with SketchUp Part 2
- Working with SketchUp Part 3
- Working with SketchUp Part 4
- Post processing Basics
- Post processing merging shapes
- Feed speed optimization with preprocessor
- Post processing code insides Part 1
- Post processing code insides Part 2
- 4x linear v-slot actuator with NEMA 17
- 2020 profiles, screws, nuts
- nichrome wire
- 2-4x retractable reel
- Arduino Mega 2560
- 128x64 LCD Display / SD card reader from RepRap with connector to Ramps 1.4 or 1.6
- Ramps 1.4 or 1.6
- 4x stepper driver A4988 (on E0, E1, Y, Z socket 0f ramps)
- 8x micro switch NC as limit switch
- 4x 100nF capacitor
- 12 buttons NO
- 2x LED + resistor 2k2
- DC-DC converter (in: > 30V, out 12V, app. 2A), not for Ramps 1.6
- optional: fans 12V
- wire / connector
Most of it is plugged together straight forward. A detailed list is included in the foamcutter.ino file.
A power supply is used with up to max 35V (limit of on board MOSFET on the Ramps) to supply the hotwire and the DC/DC converter. Refer to chapter Hotwire for voltage / power adjustment and selection of the right power supply. The DC/DC converter supplys 12V DC to the Ramps, display, stepper and Arduino. I would not recommend more than 12V DC, because on the Arduino a linear voltage regulator is used to generate 5V DC and this can be easily over powered / heated, when input voltage is to high. App. 30W are needed for Ramps, display, stepper and Arduino. In addition required power for the fans. I am using this DC/DC converter, powering 4 small fans. To select the right power supply, you need to keep estimate the power for the hotwire (see chapter Hotwire), power for Arduino, Display,... (app 30W) and the fans (20W for the small ones I am using), see chapter Power supply. In my setup, nothing is getting hot, so I do not switch the fans on.... you do not really need fans. Please check your power supply, if cooling is required. Please keep all standards and safety topics in mind, when handling with high voltage on power supply, best is to contact an authorised specialist. A detailed list of all connections/wiring is included in the foamcutter.ino file.
Advantage:
- separate voltage for hotwire, helps to select best resistance wire, see chapter Hotwire. Especially with a small diameter: Higher hotwire voltage allows to have less current in the hotwire, select thiner wires with a higher wire resistance.
Disadvantage:
- additional hardware (DC/DC converter) needed, app 10 EUR
A power supply with 12V DC output is used, because on the Arduino a linear voltage regulator is used to generate 5V DC and this can be easily over powered / heated, when input voltage is to high. App. 30W are needed for Ramps, display, stepper and Arduino. In addition required power for the fans and the hotwire (see chapter Hotwire and Power supply). I did not build a version with Ramps 1.6, but checking all the data sheets and diagrams, there should be no fan required for additional cooling of the Ramps board itself. Please check your power supply, if cooling is required. Please keep all standards and safety topics in mind, when handling with high voltage on power supply, best is to contact an authorised specialist. A detailed list of all connections/wiring is included in the foamcutter.ino file.
Advantage:
- no DC/DC converter is needed
- less wiring
Disadvantage:
- lower voltage for hotwire requires higher current to achieve power for cutting. hotwire is getting thicker.
Other boards may works, as long as they are based on the same or similar pin connection as the Ramps does. See Issues and search for MKS Board.
Selecting the right hotwire is a bit tricky I am cutting XPS foam with a very slow feed rate (100mm/min) for good results. On my machine I have 20 W/m (watt per meter) to achieve good results. For calculation I would recommend to use 25 W/m (fine tuning can be done in power setting parameter).
Get the length L of your hotwire. Keep in mind that you have diagonal traveling of the hotwire, so the wire length is more than the machine width. Get the Input voltage Ui for the hotwire (Ramps 1.4: app 30V (max 35V) / Ramps 1.6: 12V) Calculate the total wire resistance Rtotal and the wire resistance per feet Rf
- Ptotal = L x 25 W/m
- Rtotal = Ui x Ui / Ptotal
- Rf = Rtotal / (L (in m) x 3,28)
The higher the input voltage Ui is, the higher is Rf, the lower the current through the wire and the MOSFET on the ramps. the MOSFET will stay cooler and most important, you can select thiner wires. Now you can find the best fitting wire by checking the wire resistance per feet (Ohm/feet).
Example: Total Hotwire length L = 0,9m. power supply works with output voltage of 30V (= Ui). Ptotal = 0,9 x 25W/m = 22,5 W Rtotal = 30 x 30 / 22,5 = 40 Ohm Rf = 40 / (0,9 x 3,28) = 13 Ohm per feet I would go for Kanthal A1 32G with 13,1 Ohm/feet Link
Due to the calculation with 25W/m you will need to reduce power setting parameter for hotwire a bit to app 90…90%
Next step is to fine tune all your settings
- Go to the hotwire menu , select manual and start with a low power setting.
- Put some foam on it... the foam should not be cut.
- increase power setting until the foam is cut without putting force/weight on it. this is the setting for slow cutting speed (app 100 mm/min). Check out the video.
- Put this setting into the parameter ($5 = feed speed and $27 = hotwire power is stored automatically from your last manual setting).
If your wire is not getting hot enough:
- increase input voltage (only with ramps 1.4: 28V >>> 30V)
- reduce wire length (put the crocodile connections closer together)
- chose a wire with a lower resistance .... thicker wire ;(
If your wire is getting much too hot / cutting is starting below 50% powersetting:
- there is no urgent need to change something
- reduce the voltage a bit. don't go below 10V to have enough power for the stepper
- increase wire length
- choose a wire with higher resistance >>> smaller diameter ;)
Start fine-tuning again until you are happy with the result.
Selecting the right power supply is mainly based on four factors
- input voltage, select this according your region and local
- choosing a power supply to integrate in the foam cutter or as a separate power supply (i.e. laboratory power supply)
- output voltage 12V DC or up to 35V DC. I would not recommend to use more than 60V DC because of risk of electrical shock)
- required power: 30W for Arduino, Display, Stepper + Fans (I use small 12V DC fans with total 20W) + hotwire Ptotal (see chapter Hotwire)
Please keep all standards and safety topics in mind, when handling with high voltage on power supply, best is to contact an authorised specialist.
There are some sets available for 3D printer, including Arduino Mega, Ramps 1.4, 128x64 Display with SD card reader and stepper driver 4988. The firmware can be configured to operate especially with this hardware setup, without buttons, led and limit switches. The usability is limited, but almost no soldering is needed. To use this setup, simply skip all steps related to limit switches, buttons and leds. the local button on the display is used as back button, all other operations can be handled with the jog.
- set USE_LIMIT_SWITCHES to 0 in config.h to disable the limit switches
- set USE_BUTTONS to 0 in config.h to disable the buttons and leds
- cut-off Arduino PIN 10 on Ramps (just cut of the pin-header on the Ramps) (not required if no fan is connected)
- connect Arduino Pin 7 on Ramps to Socket off pin 10 (not required if no fan is connected)
- to reduce EMC connect 100 nF between S and - close to Ramps for limit switches / end stops
- to reduce EMC connect 100 nF between D63 and GND directly on Ramps pin header for AUX-2 (not required if stopp button is close to ramps)
The Arduino and the Ramps board are working without the stepper driver or motors or buttons,…. so only the limit switches should be disabled by setting 4 jumpers to the S and - Pin for X-/X+/Y-/Y+ an the Ramps. After downloading the firmware with the Arduino IDE, please use the Serial Monitor (Baudrate 115200) with the grbl commands to disable hard limits and homing cycle in the parameter. After testing all axis, SD card, …, you can activate the limit switches (hard limits) and the homing cycle again. If you are not disabling the limit switches, you may get a hard error, which blocks all communication to the Arduino (not required, if USE_LIMIT_SWITCHES is set to 0). After that you should
- connect the display to the Ramps
- connect the Arduino with the USB
- load the firmware and check if you get a welcome screen
- add the buttons and LEDs to the Ramps (not required, if USE_BUTTONS is set to 0)
- calculate the steps per mm and set the microstepps according with the jumpers (I use belt and pully with 80 steps / mm)
- add the stepper driver to the Ramps
- adjust the driver link
- connect 12V DC to Ramps 3/4
- add a stepper motor and test operation
The firmware is based on the grbl version 8c2 modified for foam cutter, a modified version of U8G2 library for the display and SdFat with no changes.
Links to the original
- grbl 8c2 foam
- U8G2 Lib by Oli Kraus, tested with version 2.27.6
- SdFat by Bill Greiman, tested with version 1.2.3
Many thanks to you, for writing and sharing this fantastic code. The firmware is a common project with 2 Axis Laser Cutter. Please use defines in config.h to select the right funtionality.
-
Download the foamcutter firmware
-
Download the libraries directly from this github (recommended): /03_Firmware/libraries and store in your ../Arduino/libraries/ folder (prefered, because updates of the original libraries may cause problems with grbl)
-
Select Version FOAM_CUTTER in config.h
Grbl uses almost all resources of the Arduino to control the stepper within an accurate timing. So the standard approach of Arduino is not working any more, because some resources are not available anymore for the Arduino framework. Within the U8G2 I use a software driven SPI on pin D50 to D52. The only thing I needed to change, was the required delay within the SPI. Therefore I changed the delay function to the grbl supported delay function.
The LCD display and the buttons are controlled inside the lcd.h and lcd.cpp. Buttons are read within the lcd_process(), from where all processing functions of the sub menus are called. Functions within the sub menus, which are related to cnc functionality are called as if they would have been called via UART/USB. So you will get an ok over the UART/USB for a local called cnc command, too. The firmware can still be controlled with gcode sender tools via the UART/USB. SD card is processed inside lcd.cpp and lcd_process(), too. Processing of the SD card is handled with a state machine, which reads the selected file char by char, similar as reading the UART. During processing a file from SD card, buttons are ignored, operation can only be stopped with an IRQ of the limit switches or the e-stop. Fan can only be controlled locally on the display. Hotwire can be controlled via the display and with the gcode commands M3/4 for on and M5 for off and Sxxx (0…100) for regulating the power in %.
Please have a lock at the parameters (command $$ over Serial Monitor)
-
e-stop: IRQ based local stop, this does not match the requirements of any safety standard (not available, if USE_BUTTONS is set to 0)
-
Idle stepper
-
Homing (not available, if USE_BUTTONS is set to 0)
- homing including pull-off
- set current position as new pull off position: This function is used to travel from limit switches to machine zero position. Adjust the position with the position menu
-
Position
- adjust each axis independent
- set or travel to a temporary home position
- set or travel to a temporary zero position
- 8 buttons to control the movements (not available, if USE_BUTTONS is set to 0)
- switch speed between feed and homing seek for fast traveling (selected homing seek speed is indicated by LED
-
SD-Card
- read file list from SD-Card (only with defined file extensions (config.h), only from root directory, keep filenames short)
- valid gcode file extensions: .nc, .gcode (you may change the file extension to oneof these)
- execute a file from the SD-Card
- visualise the progress (bytes read and send to gcode processing, not bytes really executed)
-
Hotwire
- switch on/off or change the power in %. New value is stored in the eeprom
- switch on/off with button (not available, if USE_BUTTONS is set to 0)
- indicate status with LED
-
Feed speed
- select the feed speed
- new value is stored in the eeprom
- if gcode includes feed rates, gcode values are used.
- adjust in big steps with Y- / Y+ buttons (not available, if USE_BUTTONS is set to 0)
-
Slicing (previous function name: Cutting)
- this functions allows horizontal or vertical slicing w/o gcode
- select the slicing direction with the 8 buttons for the axis (not available, if USE_BUTTONS is set to 0, direction is selected with jog)
- define the maximum x/y travel for slicing (use position menue)
- executes a cut by preheating the hotwire for 5 seconds
- move back to starting position of the slice with seek-speed
-
Fan
- switch on/off or change the power in %. New value is stored in the eeprom
-
The firmware can still be controlled with gcode sender tools via the UART/USB
Please refer to grbl documentation for parameter settings and first steps. A good point to start is to:
- disable limit switches and homing cycle (not required, if USE_LIMIT_SWITCHES is set to 0)
- set the steps per mm for each axis
- check the direction and adjust with "step port invert mask"
- check travel distances and optimize
- activate homing cycle and check directions and adjust with "homing dir invert mask" (not required, if USE_LIMIT_SWITCHES is set to 0)
- a good setting to start is feedrate 300 mm/min, hotwire 80% on 30V DC for 75 cm hotwire
I use SketchUp for generating the stl-files for my 3D printed parts. I would love to use the easy handling for creating fuselages. I searched the web and found only one hotwire related tool, which is not supported any more. so I decided to write a small tool by myself. This allowas you to generare G90 (abolute positioning) coordinates of combinded edges. Currently I use only linear extrapolation in combination with my post processor. The results are good.
- SketchUp (I am Using SketchUp Make 2017)
- Ruby Code Editor
- CurviLoft
- Download foamcutter.rb from the code section
Open the ruby code editor first and load and execute the foamcutter.rb. This adds 4 menus to the PlugIn menu.
- FoamCutter Settings: you can define some general settings, like inch/mm, used decimals.
- FoamCutter Import how-file: Import profiles from Wing Helper
- FoamCutter Tool: Generates gcode for 2 paths and exports it. The paths it self use the green (x and u) and blue (y and z) axis. Positioning along the red axis does not matter. See tutorial video "Working with SketchUp Part 1-3"
- FoamCutter Tool PP: Generates gcode for the left and the right axis of the foamcutter, this includes a simple post processing. See tutorial video "Working with SketchUp Part 4"
The algorithm searches all related points to an edge. It follows two routes
It uses all edges only once. If you reach a dead end, you may use the third dimension (supporting path) do open up new paths/edges - please keep the rules in mind.
Both paths should have the same number of points and edges. To go for that with more complex objects, it is a good way to use CurviLoft
- create your objects
- use CurviLoft to generate the surface/area between the objects.
- select to show the related edges between the objects (connection lines)
- split these connection lines (ungroup)
- select and group the objects (otherwise the object is not splittet in points)
- delete the connection lines
- use foamcutter tool
- select first and second edge
- save the file
- do the post processing if required
- Working with SketchUp Part 1
- Working with SketchUp Part 2
- Working with SketchUp Part 3
- Working with SketchUp Part 4
Designing the shape of a wing or a fuselage requires in most times an additional step to tell the machine / foam cutter how to produce it. This step is called post processing. It allows you to generate machine executable or interpretable code (gcode) and add machine, tool and material specific information (hot wire temperature, travel speed, position of foam block, …). I wrote a pice of code, do adopt my SketchUp files and my WingHelper Designs to my foam cutter. The code is written in swift for macOS, but the basic ideas can be easily adopted to other languages. All post processing functions are bundled in the class FCalc (FCalc.swift). Interfacing is handled with key to access the values and the labels/descriptions to the values. The values itself are exchanged as Strings, because most of them are changed by user, so all type checking stuff is integrated in FCalc, too. Detailed interface description is available in FCalc.swift.
- Import shapes from gcode, nc, SkechUp foamcutter.rb, Winghelper how, fcf-projects
- Export to gcode
- Load/Save projects as fcf file
- Move and rotate and mirror the shape
- Move and rotate the foam block
- Calculates the movement of the axis
- Speed optimisation, to keep average speed at the edges of the shape close to target feed speed
- Merging of different shapes into one cutting job
- 3D preview and simulation of axis, shape and foam block
- All settings have a unique ID (see SettingsTableKey for all values) for access
- Reading a setting:
- dataTypeForKey(_ key: SettingsTableKey) -> DataType
the Datatype of the setting for correct visualisation/layout - labelForKey(_ key: SettingsTableKey) -> String
the label for the setting - valueForKey(_ key: SettingsTableKey) -> String
the value itself for the key as formatted string
- dataTypeForKey(_ key: SettingsTableKey) -> DataType
- Writing:
- isEditableForKey(_ key: SettingsTableKey) -> Bool
indicates wheather this type is editable - isValueValid(_ key: SettingsTableKey, value: String?) -> Bool
a string can be tested, if it is acceptable for this setting - valueForKey(_ key: SettingsTableKey, value: String?)
writes a string to the setting
- isEditableForKey(_ key: SettingsTableKey) -> Bool
- Usage: Generate an array of SettingsTableKey-values to be displayed and catch the content with the functions above
- All is handled with strings, so no need of type conversion
- Supported filetypes;
- gcode, nc: simple gcode wit G00/G0, G01, G1, G90, G91, ...
- how: Winghelper ICE export with absolute coordinates
- fcf: Foam Cuter File (project) previously saved
- importShapeFromFile(_ file: String) -> Int
= 0 if ok / != 0 if not ok
- Save a file in gcode format
exportGCodeToFile(_ file: String) -> Int
= 0 if ok / != 0 if not ok
- updateSettingsTableView()
called, wenn the table for the settings needs to be updated - updatePositionsTableView(_ atIndex: Int?)
called, wenn the table for the positions needs to be updated - updatePreview(_ node: SCNNode)
called, whenn the Graph is updated, check if Node is already linked
- optional, see FCalc.swift
See folder 99_sample in the code section:
- sample_1.gcode is the export file from foamcutter.rb (SketchUp)
- sample_2.gcode header and commandes were modified manually with text-editor
- sample_pp.gcode is generated with post processor