CadShift Blog

Waterjet cutting is not laser cutting. A programmer at a waterjet shop evaluates your DXF differently than a laser operator does, and the geometry problems that a laser CAM system tolerates will stop a waterjet program cold. This post covers what you need to know before the file leaves your desk: kerf width, taper, lead-in placement, pierce rules, minimum features, and the geometry requirements that every waterjet CAM system actually checks. ...

A fabricator running a CNC tube laser — Trumpf TruLaser Tube, BLM LT-Free, Mazak FT-150 — expects the DXF cope geometry to land flush against the mating tube. When it doesn’t, someone grinds. When it really doesn’t, the joint gets welded with a visible gap, weakening the bead and failing inspection. The problem starts in SolidWorks before the export ever happens. How SolidWorks Models Weldment Tubes The SolidWorks Weldment feature builds structural members by sweeping a 2D profile sketch along a 3D path. The profile is constant — it maintains its exact shape and size throughout the entire sweep. When two members intersect, SolidWorks trims them automatically to create the cope (the curved notch that allows one tube to seat against another). ...

Most of the questions engineers ask about kerf compensation assume the problem is in the DXF. It almost never is. SolidWorks exports flat patterns with nominal dimensions — exactly as modeled, no offset applied. That’s correct behavior. The question is whether you understand where kerf compensation actually happens, and what breaks when it happens in the wrong place. What Kerf Is and Why It Varies Kerf is the width of material removed by the laser beam — the slot left behind after a cut. On a fiber laser cutting 3mm mild steel, typical kerf width runs 0.08–0.15mm. For thicker material (12mm+) or plasma, it can exceed 1mm. ...

A LinkedIn post earlier this year showed a VBA macro compressing a 40-minute manual batch DXF export down to seconds. It drew significant engagement because every SolidWorks engineer who works with sheet metal has written some version of this macro, or knows someone who has. The basic implementation is not complicated. Iterate assembly components, open each part, call ExportToDWG2, close. For clean assemblies with simple sheet metal parts and consistent filenames, it runs reliably. The problems surface when the assembly contains parts that don’t fit the happy path — and most production assemblies do. ...

A recent r/engineering thread on EBOM-to-MBOM translation collected 134 upvotes and 81 comments. The answers split into two camps: “PLM would fix this if companies actually deployed it properly,” and “our team of eight doesn’t have budget for PDM let alone PLM.” Both responses miss the same root cause. The problem starts in how SolidWorks generates an EBOM and what that structure cannot express that manufacturing requires. What SolidWorks Actually Gives You When you insert a BOM table into a SolidWorks drawing or export one from an assembly, you get a direct reflection of the assembly tree. Each component becomes a row. Sub-assemblies appear as parent items with children. Quantities are instance counts. ...

“Failed to create empty document.” That error message from SolidWorks when opening a STEP file means the STEP importer could not even initialize a document container before hitting a fatal problem. It is not a timeout. It is not a permissions issue. The file has structural corruption that SolidWorks’s geometric kernel cannot work around. If you got this from a vendor file, a downloaded dataset, or a STEP that was partially written when something crashed, SolidWorks is not going to open it. The recovery path goes through a different STEP importer — one with a higher tolerance for malformed AP214 entity references — and then back into SolidWorks via Parasolid. ...

You have a sheet metal weldment with properly named cut list folders: meaningful names built from profile paths and custom properties, properly rolled up into your BOM. Then someone inserts that part into a parent weldment using Insert > Part, or you create a derived configuration that dissolves the cut list context — and every folder name silently reverts to “Sheet” or “Structural Member 1”. This is not a bug. It is a consequence of how SolidWorks tracks cut list folder identity, and understanding the mechanism tells you exactly which fix to apply in which scenario. ...

At some point, someone in your shop opens a SolidWorks part and gets this: Microsoft Excel is required for gauge tables. Please ensure Excel is installed and try again. The popup appears when the Sheet Metal feature dialog tries to open the gauge table file via OLE automation. If Excel is not present — or if it has been uninstalled after the company moved to Google Workspace or LibreOffice — the gauge table feature silently stops working. ...

If you work with sheet metal in SolidWorks, you have three realistic options for getting flat-pattern DXFs out at scale: write a VBA macro, buy PDMPublisher, or use CadShift. Each solves the same core problem — the repetitive manual export — but they sit at very different points on the complexity-vs-cost curve. This is a buyers guide, not a pitch. The right tool depends on your shop’s specific situation. The problem all three tools solve The native SolidWorks workflow for DXF export does not scale. For one part, the right-click → Export to DXF/DWG route is fine. For an assembly with 40 sheet metal parts, you are looking at 30–45 minutes of clicking through the same dialog, checking flat patterns, setting file names, and ensuring consistent layer settings across every export. Miss a part and your laser operator finds out at the machine. A detailed walkthrough of what the manual process involves is in the batch DXF export guide. ...

AutoCAD is the closest tool to the DXF format itself — AutoDesk invented DXF, and the format tracks AutoCAD versions. That proximity creates a false sense of safety. AutoCAD drawings destined for laser cutting fail for reasons that have nothing to do with version support: phantom geometry, Z-elevation surprises, splines the controller can’t handle, and blocks that CAM software silently ignores. The problems are consistent and avoidable, but only if you run a specific command sequence before every export. ...