Reviewed October 19, 2026 · Based on current Makerloom exports and linked primary documentation.
Compatibility describes a workflow, not a certification. A machine profile is a starting configuration. A controller match is an inference from its documented language. An SVG handoff means another application must finish the job. None of these labels means every model, firmware revision or accessory has been tested on hardware. The project owner uses an M2 workflow; we do not publish model-specific hardware validation records.
Profile available
A preset already exists. Verify your real machine settings.
Controller match
Potential direct G-code workflow. Firmware and setup must match.
SVG handoff
Design here, then make the machine-specific job in external software.
FIND YOUR PATH FROM DESIGN TO MACHINE
Machine & controller directory.
Read the controller label or firmware banner in your machine software. The installed board matters more than the frame’s brand name.
26 workflows listed
Profile available
MakerMade M2
M2 controller / Makerhub workflow
Choose in Makerloom
MakerMade M2
Export / handoff
.nc
Run or finish the job in
Makerhub
Primary workflow used by this project’s owner. Manual router operation; Makerloom’s M2 profile omits spindle-start commands. Set the actual work area and work zero. Its 40 ipm feed cap is an application limit, not a material recipe or a manufacturer maximum.
Confirm your installed controller, usable travel, clearance and router/spindle mode. The profile’s nominal board size and speed caps are editable starting values. No model-specific hardware test is published here.
Use the correct 48 × 30 profile, then confirm real travel and controller settings. A longer machine does not imply a higher safe cutting feed. Check the selected units before loading.
Check the installed board and spindle controls. Configure usable travel and safe feed/plunge caps for your exact setup. Makerloom does not configure the controller or its accessories.
The profile deliberately leaves travel and speed limits blank: enter your model’s values. Use separate single-tool jobs. BitSetter, tool-length probing and machine-specific tool-change sequences need the appropriate Carbide workflow; they are not inserted by this generic export.
Custom controller check; SVG handoff is an alternative
Export / handoff
.nc after validation, or .svg
Run or finish the job in
Carbide Motion / external CAM
Carbide documents common G-code support, but Makerloom has no Nomad-specific preset or tested tool-length sequence. Configure the small work envelope and spindle correctly; do not copy Shapeoko dimensions. For sensor/tool-change workflows, generate the file in suitable CAM.
BlackBox X32 grblHAL; other boards must be checked
Choose in Makerloom
Other GRBL / grblHAL router
Export / handoff
.nc / .gcode
Run or finish the job in
OpenBuilds CONTROL or compatible sender
Compatibility follows the installed controller, not the frame name. Enter real travel and limits; confirm spindle/relay operation. Modified builds can differ substantially.
Check firmware and your exact revision. Set the actual small work envelope, spindle mode and conservative measured cutting settings. Offline-controller file/SD-card requirements vary.
Check the exact revision, homing direction and usable travel. This row does not certify every PRO MAX, RENO or replacement-controller variant. Manufacturer sample files can help establish the expected sender workflow.
A format-based candidate, not a universal machine preset. Verify every emitted command, machine travel, units, Z direction and spindle behavior. A brand label alone cannot establish support.
Onefinity Original / PRO with Buildbotics controller
Onefinity Buildbotics-based controller
Choose in Makerloom
SVG → machine-specific CAM
Export / handoff
.svg → controller-specific toolpath
Run or finish the job in
CAM with a Onefinity/Buildbotics post, then controller interface
No dedicated Makerloom postprocessor is provided. Import the SVG into suitable CAM and choose the correct post for your controller. A generic GRBL profile is not a substitute.
Treat separately from Buildbotics models. Makerloom does not add MASSO tool-change, probing or spindle macros. Confirm the actual controller and use its correct postprocessor.
Avid documents different controller generations. Select the exact machine/controller post, including any spindle, probing and tool-change handling. Makerloom does not supply that postprocessor.
Suitable ShopBot CAM, then ShopBot control software
Makerloom does not create native .sbp part files. Generate the ShopBot job in compatible CAM. Renaming a .nc file to .sbp does not translate the commands.
Import the artwork, check its physical size, then set cut type, cutter compensation and depth in the Shaper workflow. Makerloom G-code is not an Origin job.
Laser mode must already be configured ($32=1), and S maximum must match $30. Makerloom uses M4 dynamic power, S0 travel and millimeters. No Z/focus, air-assist or firmware-configuration commands are supplied. This is conditional on the actual firmware, not the laser brand.
Compatible sender; SVG can be imported into laser software
Check the installed firmware, S scale, work origin and physical bed. Makerloom does not emit the M8 air-assist command; arrange air assist in the manufacturer-approved workflow. Do not assume every model/revision uses the same settings.
Match S maximum to laser_module_maximum_s_value (commonly 1). Output uses G1 S power and G0 S0 travel. A controller conversion does not make a stock K40 board compatible.
.svg → native .rd file or supported software transfer
Run or finish the job in
LightBurn with the correct Ruida device
Import SVG and set all laser operations in the destination software. Makerloom does not generate Ruida binary job files. Check the board model and the software/device support.
Recommended route for D1, S-series, P-series and F-series workflows: import artwork and configure the job in the supported xTool software. Model and firmware support varies. No native xTool project/job file is exported by Makerloom.
Import SVG into the appropriate Luban CNC or laser workspace. Rebuild the toolpaths for the installed module. Generic GRBL output is not a substitute for the Snapmaker workflow.
LightBurn only for supported controllers, or manufacturer-approved tools
No native galvo output, lens correction, field calibration, hatch timing or marking parameters are supplied. If your vendor app cannot import SVG, a separate supported vector conversion is required. Verify exact hardware/software support first.
K40 Whisperer or software supporting your exact board
Do not send GRBL or Smoothieware G-code to the stock board. Confirm the destination’s SVG preparation rules. A replacement Smoothieware/other board must be assessed as a different controller.
These details describe current Makerloom output. They are not instructions to change your firmware settings.
01
Units and positioning
CNC files use G20 for inches or G21 for millimeters, depending on Export units. G90 means absolute coordinates. CNC controls use inches and inches/minute internally; metric export converts XYZ and feed values. Laser exports are always millimeters and mm/min. If the destination displays mm/s, divide mm/min by 60: 600 mm/min is 10 mm/s. A speed entered with the wrong time unit can be off by a factor of 60.
02
Moves and your work zero
Files use G0 travel and G1 cutting moves, with G17 and G94 setup commands. They do not home the machine or establish your work offset. Zero the sender to the same corner/center selected in the design. CNC Z zero is the stock top; laser export uses bottom-left XY work zero and does not position Z/focus.
03
Spindle versus laser power
Manual router mode does not turn the router on for you. Automatic spindle mode adds M3 S…, startup dwell and M5; use it only with verified controls. GRBL laser output uses M4 dynamic power and S0 travel; its S maximum must match the controller. Smoothieware uses its own configured S scale, commonly 1. These modes are not interchangeable.
04
Tools, layers and accessories
Export separate jobs for different tools or cutting layers. Generic export does not provide machine-specific automatic tool changes, probing, BitSetter routines, air assist, autofocus or rotary calibration. The compatibility labels here cover flat vector laser work and conventional three-axis CNC work; they do not certify multi-axis machining or 3D relief jobs.
BEFORE THE FIRST CUT
A quick file check.
Match the installed controller and firmware to the workflow above.
Set actual travel, stock thickness, bit/laser configuration and clearance. Software caps are not recommended material feeds.
Check exported units and dimensions in your sender. After SVG import, verify a known dimension; one inch must remain 25.4 mm.
Choose exactly the letters, backer, shapes or complete job you intend to cut.
Preview the full path, work zero, cutting depth, pass count and travel moves in the destination software.
Use the manufacturer’s setup procedure and an appropriate test on scrap. For a router, check clear travel with the spindle off before the powered run. Supervise the actual job.
If a file will not load.
Confirm that it is an actual toolpath file, not an SVG design, editable project, or unopened ZIP. A different extension alone cannot fix a dialect mismatch. A loading spinner can also be a parsing or file-complexity issue; try a small known-good job to isolate it rather than assuming the USB connection is the cause.
If it imports at the wrong size, check units and SVG import scaling. If your laser software cannot open a Makerloom G-code file, try the SVG handoff and generate a job in that software.
For help, send the machine/model, installed controller and firmware, sender name/version, chosen export/profile and the exact error. Do not send passwords or account credentials.