#Kerfio Market Compatibility Research

#CNC, Laser, and 3D Printer Support Strategy

Prepared for Babak Delavarpour / Kerfio App - Research date: 30 May 2026

#Executive Summary

Kerfio should become familiar to the CNC, laser, and 3D printer market by organizing compatibility around controller/firmware families first, then exposing brand/model presets on top. This is how successful tools such as LightBurn, gSender, OpenBuilds CONTROL, Pronterface, OctoPrint, Mainsail/Fluidd, and Duet Web Control are understood by users.

The most important first targets are GRBL, grblHAL, FluidNC, Marlin, Klipper/Moonraker, OctoPrint, and RepRapFirmware/Duet. These cover a very large part of the DIY, hobby, maker, and prosumer market. Ruida/Trocen/TopWisdom DSP lasers and EZCad galvo lasers are important, but they should be Phase 2/3 because they are not simple serial G-code devices.

For market credibility, Kerfio must include recognizable presets and workflows: Shapeoko, X-Carve, Sienci LongMill, OpenBuilds, Onefinity, Genmitsu/3018, Ortur, Sculpfun, Atomstack, xTool, OMTech, Prusa, Bambu, Creality, Anycubic, Elegoo, Voron, RatRig, and similar names. But the app should technically ask: “What controller/firmware does this machine use?”

The recommended product strategy is to ship Kerfio v1 with excellent GRBL/FluidNC CNC + laser support and strong Marlin/OctoPrint/Moonraker 3D printer host support, then expand into Duet/Prusa/Bambu workflows, and finally native DSP/galvo/pro CNC integrations.

#Key Market Reality: Brand Names Are Not Enough

The same brand can ship different controllers across product generations. The same controller can appear in many brands. DIY users may replace the original controller entirely. Therefore, Kerfio should never hard-code compatibility only by brand.

A professional compatibility model should have three layers: (1) machine category, such as CNC, laser, or 3D printer; (2) controller/firmware family, such as GRBL, FluidNC, Marlin, Moonraker, Duet, or Ruida; and (3) brand/model preset, such as Shapeoko 5 Pro, X-Carve Pro, Ortur Laser Master 3, or Prusa MK4.

This makes Kerfio feel like an expert tool: users can choose a known brand quickly, while advanced users can choose a generic controller profile for DIY machines.

#Controller and Firmware Compatibility Matrix

#CNC Brands, Models, and Open-Source Projects

#Laser Brands, Models, and Open-Source Projects

#D Printer Brands, Models, and Open-Source Projects

#Recommended Kerfio Built-In Machine Profiles

#Recommended Kerfio Architecture

#Connection Layer

• Serial transport: pyserial adapter with port discovery, baud auto-probe, line-ending rules, ok/error streaming, soft-reset, DTR/RTS options, and log capture.
• Network transport: HTTP client, WebSocket client, TCP socket/Telnet client, mDNS/Bonjour discovery, device ping, reconnect, and timeout management.
• Host API adapters: Moonraker, OctoPrint, Duet/RRF, PrusaLink, Bambu Connect/LAN-compatible workflow, Buildbotics where feasible.

#Machine Capability Layer

• A machine profile should describe axes, travel, origin, homing direction, max feed, units, spindle/laser power range, probe availability, coolant/air assist, camera, enclosure, rotary axis, and tool changer capability.
• Profiles must be editable by users and versioned. Kerfio should ship presets but always allow custom DIY profiles.
• Capability detection should run after connect: firmware identity (M115/$I), settings dump ($$), status format, axis count, probe support, laser mode, temperature tools, SD/storage support, and pause/resume semantics.

#G-code Dialect Layer

• Do not assume one universal G-code. Add dialect packs: GRBL CNC, GRBL laser, Marlin printer, Marlin laser/CNC, Klipper/RepRap, LinuxCNC, Mach3/4, MASSO, Ruida/DSP later.
• Add a G-code analyzer that warns about incompatible commands before sending: unsupported arcs, missing units, missing absolute/relative mode, dangerous Z moves, laser S range mismatch, extrusion commands sent to CNC, spindle commands sent to printers, etc.
• Add post processors and output targets so Kerfio can also be useful when it cannot directly control a proprietary machine.

#UI/UX Layer

• Use familiar sections: Machine, Connect, Jog, Home, Zero, Probe, Console, Files/Jobs, Preview, Layers/Toolpaths, Macros, Settings, Safety, Camera, Logs.
• CNC should feel like Carbide Motion/gSender/OpenBuilds CONTROL: jogging, zeroing, probing, tool changes, overrides, 3D preview, console, macros, run-from-line caution.
• Laser should feel like LightBurn: artboard, layer colors, speed/power/passes, image engraving, vector cut/score/fill, framing, rotary, air assist, material library, camera alignment.
• 3D printer should feel like Pronterface/OctoPrint/Mainsail: temperature graph, extruder/fan controls, homing, bed mesh view, file upload, job start/pause/cancel, terminal, macros, webcam.

#CNC Module - Must-Have Features

• Connection wizard, port/network discovery, firmware detection, settings backup/restore, console, alarm handling.
• Jogging panel with continuous/incremental jog, keyboard/gamepad mappings, feed and rapid override, soft-reset, hold/resume.
• Home, set work zero, G54-G59 work coordinate support, probe/touch plate, Z zero, tool length workflow, tool change pause/resume.
• 3D G-code preview, bounding box, estimated time, min/max travel check, cut depth and Z safety analysis.
• Macro system for surfacing, probing, spindle warm-up, dust collection, coolant, clamps/fixtures, camera alignment later.
• Post-processor targets for GRBL, grblHAL, FluidNC, LinuxCNC, Mach3/4, MASSO, Centroid, Buildbotics, and generic ISO G-code.

#Laser Module - Must-Have Features

• LightBurn-like canvas, import SVG/DXF/PDF/AI-compatible vector when possible, PNG/JPG/BMP image engraving.
• Layer/color workflow: each path or color can have speed, power, passes, line interval, cut/fill/scan mode, order, air assist, Z offset, and kerf compensation.
• Laser safety: low-power fire button, frame/outline, test grid, material library, door/interlock status if controller supports it, warning before M3/M4 laser activation.
• GRBL laser settings: $32 laser mode, S range mapping, M3 vs M4 behavior, laser-on during moves only, power scaling, PWM sanity check.
• Rotary mode, camera alignment, origin/corner selection, absolute/user-origin/current-position modes, overscan, scan offset correction.
• DSP laser roadmap: Ruida/Trocen/TopWisdom support later; in v1 provide export/post workflow and clear compatibility notes.

#D Printer Module - Must-Have Features

• Pronterface-style direct control: connect, home, move axes, extrude/retract, temperature/fan controls, terminal, emergency stop.
• OctoPrint/Moonraker-style network host support: upload G-code, start/pause/cancel, monitor progress, show webcam, read job state and temperatures.
• Temperature graphs, hotend/bed/chamber controls, fan controls, filament load/unload macros, bed mesh view for Klipper/Duet where supported.
• Slicer integration: accept G-code/3MF output from PrusaSlicer, OrcaSlicer, Cura, Bambu Studio workflows where possible.
• Printer profiles: build volume, nozzle diameter, filament presets, extruder count, bed shape, start/end G-code expectations, firmware flavor.
• Careful separation from CNC/laser mode so extrusion commands are never sent to CNC and spindle/laser commands are never accidentally sent to printers.

#Recommended Implementation Roadmap

#How Kerfio Should Look Familiar in the Market

#Final Recommendations

• Position Kerfio as a universal workshop control platform, not only a CNC app. The market language should be: CNC router, laser engraver/cutter, 3D printer, plasma/drag-knife later.
• Do not promise “all brands” directly. Promise “controller/firmware families” and publish a compatibility matrix. This is more technically honest and more professional.
• Ship with named presets for familiar brands, but internally map them to adapters: GRBL, FluidNC, Marlin, Moonraker, OctoPrint, Duet, DSP, etc.
• Create an import/export workflow even for machines Kerfio cannot directly control. Users with proprietary systems still need design, CAM, preview, post-processing, and file preparation.
• Make the first impression familiar: LightBurn-style laser layers, Pronterface/OctoPrint-style 3D printer controls, and gSender/Carbide/OpenBuilds-style CNC control.
• Add a “safe connect” wizard: detect firmware, read settings, ask machine size, force user to confirm emergency stop, homing, travel, laser/spindle power, and test movement at low speed.
• Build every integration as a plugin with a formal adapter interface. This prevents the app from becoming messy as brands/controllers expand.

#Suggested Public Compatibility Wording for Kerfio

Kerfio supports CNC routers, laser engravers/cutters, and 3D printers through controller and firmware profiles. Initial support focuses on GRBL, grblHAL, FluidNC, Marlin, Klipper/Moonraker, OctoPrint, and RepRapFirmware/Duet workflows, with presets for popular hobby, DIY, and prosumer machines. Some professional DSP lasers, galvo lasers, and proprietary machines may be supported through export/post-processing workflows first, with native integrations added progressively.

#Research Sources

1. LightBurn controller families - LightBurn identifies laser controllers as GCode, DSP, and Galvo, and lists GRBL, Smoothieware, Marlin, FluidNC, grblHAL, xTool, Ruida, Trocen, and TopWisdom among supported families. https://docs.lightburnsoftware.com/2.1/GetStarted/LaserID/
2. LightBurn official product page - LightBurn states direct support for most Ruida, Trocen, TopWisdom, GCode-based controllers, and EZCad-based galvo boards. https://lightburnsoftware.com/
3. FluidNC wiki - FluidNC is ESP32 CNC firmware and preserves Grbl 1.1 compatibility patterns. https://wiki.fluidnc.com/
4. FluidNC serial protocol - FluidNC uses the standard Grbl 1.1 status report for sender compatibility. https://wiki.fluidnc.com/support/serial_protocol
5. Marlin documentation - Marlin is open-source firmware for RepRap/FFF 3D printers, originally derived from Sprinter and grbl. https://marlinfw.org/docs/basics/introduction.html
6. Klipper API server - Klipper exposes an API enabling external applications to query and control the Klipper host software. https://www.klipper3d.org/API_Server.html
7. Moonraker external API - Moonraker uses HTTP for file transfer and WebSocket for events/status/gcode responses. https://moonraker.readthedocs.io/en/latest/external_api/introduction/
8. OctoPrint file API - OctoPrint provides REST file operations for uploading and managing G-code files. https://docs.octoprint.org/en/master/api/files.html
9. OctoPrint job API - OctoPrint provides job commands for start, pause, cancel, and restart operations. https://docs.octoprint.org/en/master/api/job.html
10. RepRapFirmware G-code dictionary - RepRapFirmware follows a GCode-everywhere philosophy and documents supported G-codes. https://docs.duet3d.com/User_manual/Reference/Gcodes
11. RepRapFirmware object model - RepRapFirmware exposes a structured object model with machine/job information. https://docs.duet3d.com/en/User_manual/RepRapFirmware/Object_Model
12. PrusaLink / Prusa Connect - PrusaLink runs locally on the printer/LAN; Prusa Connect is cloud-based. https://help.prusa3d.com/article/prusa-connect-and-prusalink-explained_302608
13. PrusaLink OpenAPI spec - Prusa publishes an OpenAPI specification for Prusa Link Web. https://github.com/prusa3d/Prusa-Link-Web/blob/master/spec/openapi.yaml
14. Bambu third-party integration - Bambu documents third-party integration via Bambu Connect for transmitting sliced files to supported printers. https://wiki.bambulab.com/en/software/third-party-integration
15. Bambu LAN/developer mode guide - Bambu LAN-only/developer mode enables local third-party workflows on supported firmware, with limitations. https://help.simplyprint.io/en/article/bambu-lab-lan-only-mode-and-developer-mode-how-to-enable-xa0hch/
16. Printrun / Pronterface - Printrun is a Python 3D printing host suite that talks to printers and handles printing. https://www.pronterface.com/
17. OpenBuilds CONTROL - OpenBuilds CONTROL connects to CNC, laser, plasma, and drag-knife machines. https://software.openbuilds.com/
18. gSender - gSender supports grbl and grblHAL CNCs over USB or Ethernet and includes jogging, zeroing, visualization, overrides, and browser-based control. https://sienci.com/gsender/
19. Carbide Motion - Carbide Motion controls Shapeoko and Nomad machines and handles jogging, zeroing, job running, and tool changes. https://carbide3d.com/carbidemotion/
20. Inventables X-Carve Pro UGS - Inventables documents connecting X-Carve Pro to Universal Gcode Sender with a specified baud rate. https://inventableshardwaresupport.zendesk.com/hc/en-us/articles/41073528629140-Connecting-X-Carve-Pro-to-Universal-Gcode-Sender-UGS
21. Buildbotics - Buildbotics is an open-source CNC controller with built-in web interface and G-code processor. https://buildbotics.com/
22. Mach3 - Mach3 turns a Windows PC into a CNC machine controller that processes G-code. https://www.machsupport.com/software/mach3/