Which file formats and design software work?¶
Design in the application that produces the cleanest geometry, then export through a format your installed M-Series mLaser build lists in its Open/Import dialog. Gweike's M-Series manual demonstrates opening supplied cutting/engraving files but does not publish one reliable, versioned format matrix in the reviewed archive.
Practical format strategy¶
- Use a vector exchange format such as DXF or SVG only when your installed mLaser build confirms it for contours, profiles, and line engraving.
- Use a supported raster format such as PNG/JPG/BMP only for raster/scan engraving workflows, not for precision cut contours.
- Export text as curves/outlines when font substitution would be unacceptable; keep an editable source copy.
- Flatten unsupported effects, clipping masks, linked images, and live CAD objects before export.
- Prefer simple 2D paths and an older/common DXF variant if a modern export imports incorrectly.
Common format lists published for other Gweike/mLaser products are useful clues, not proof for the M-Series. Verify your build rather than relying on an MCore, G2, or old Makeblock mLaser page with the same software name.
Import verification checklist¶
- Include a known reference dimension in the design.
- Confirm mLaser's displayed width/height immediately after import.
- Look for a 25.4× inch/mm error.
- Zoom into arcs, splines, circles, and corners for broken or faceted paths.
- Remove duplicates and verify every contour is open/closed as intended.
- Assign layers/processes again and verify output is disabled on construction geometry.
- Sort inner features before outside profiles where appropriate.
- Simulate the full path, then frame with emission disabled.
Recommended division of labor¶
- CAD: dimensioned mechanical profiles and assemblies.
- Vector editor: artwork, logos, text outlines, and cleanup.
- Raster editor: tonal images prepared for scan engraving.
- mLaser: final layer/process assignment, path ordering, controller connection, framing, calibration, and execution.
LightBurn can be used as a design/export tool if it produces a file your mLaser build imports correctly, but it should not be treated as an M-Series controller: current LightBurn compatibility.
If import fails¶
Create a minimal file containing one square and circle. Try the exact format/version shown as supported by mLaser. If it imports, simplify or re-export the original in sections to locate unsupported geometry. Do not solve an import error with controller firmware or machine-parameter changes.