[Miranda]

Hey Sherman,

I know that is frustrating! Based on what you’re describing, this sounds like a machine communication issue between your computer and the CNC controller.

With CNC machines, that connection usually depends on three things:

• The correct USB driver installed
• The correct control software installed
• Windows recognizing the controller through Device Manager

That said, every machine manufacturer handles this differently. So I would keep trying to get ahold of the support for your specific machine.

Good luck,

Miranda

[Miranda]

Hey Bryan,

1. Here’s what to check:

Open each toolpath individually → click Edit → look at the tool assigned there. Confirm it actually says 1/8″ and not an older 1/4″ tool.

Then run the toolpath preview. If your inside corners, slot widths, or small details look tighter than a 1/4″ cutter could physically fit, that’s a good sign it’s calculating with the 1/8″.

The Vectric-based projects later in the course always have you review and simulate toolpaths before exporting for exactly this reason.

So short version: if the toolpath itself says 1/8″, you’re good—even if some database naming looks weird.

2. This sounds like a machine/controller integration issue rather than a course workflow issue.

Since every machine and controller behaves a little differently, the best next step is to reach out to TwoTrees support or check their controller documentation for spindle relay / PWM support and firmware configuration. They’ll know whether your board supports spindle commands like M3/M5 and whether additional wiring or firmware settings are needed.

Metric vs. Imperial

Most often this comes from one of three places:

• Job setup units in Vectric
• Post-processor output
• Controller firmware interpretation

The quickest way to isolate it:

Open the exported gcode and look near the top:

• G20= inches
• G21= millimeters

That tells the controller what units the file is using.

Also, UGS may automatically update jog increments based on the active gcode units—which would explain exactly what you’re seeing.

3. This one usually comes down to one of three things:

A. Actual material thickness vs software thickness
Always measure the board, don’t trust nominal lumber dimensions. Our Vectric playbooks call this out on every project: measure your actual material and update thickness in software if needed.

B. Z-zero accuracy
If Z-zero is even .040–.060″ high, you’ll leave exactly the kind of onion skin you described.

In the course we always zero to the top of material after any air pass or tool change.

C. Units mismatch
And honestly, because you also mentioned the design preview being tiny, this is the one I’d suspect first. That’s a huge clue.

If the project should be around ~10–12″ wide but is showing ~3″, something is almost certainly scaling due to mm/in conversion.

I’d check these in order:

1. Vectric Job Setup → confirm inches
2. Re-import project file and confirm it doesn’t ask to scale on import
3. Verify post-processor matches your controller
4. Check gcode header for G20 vs G21

My gut says you’ll find the mismatch there.

Hope that all helps,

Miranda

[Miranda]

Hey Thomas,

Thanks for reaching out, this is a very common question.

Here are a couple solid ways to handle it:

Option 1: Scale the project down
Open the file in your software and scale it proportionally so it fits within your machine’s cutting area. Just make sure:

• Your hole sizes still match your bit shanks after scaling
• You recheck toolpaths after resizing

Option 2: Modify the layout
You can adjust the design to:

• Reduce spacing between holes
• Remove a row or column
• Split it into two smaller organizers

Either way, the key is making it fit your machine while still keeping it functional for your workflow.

If you want the simplest path forward, I’d recommend scaling it slightly and doing a quick test cut on scrap to confirm your bit fit.

Hope that helps,

Miranda

[Miranda]

Hey Bryan,

For the Welcome Home sign, the course workflow is to download the zipped project file, extract it, then open the extracted project file in Carbide Create. That project uses the flower design with V-carve toolpaths, so I’d avoid converting an HTML download into an SVG if possible. That conversion could definitely create messy vectors or intersections.

For the Flag Tray, the same applies: download the zipped file, extract it, then open the extracted Carbide Create project file. After that, preview/simulate the toolpaths before exporting.

For the Table and 3D Crocodile projects, those are Vectric-based projects. The Crocodile lesson uses Vectric VCarve or above and is built around the 3D relief workflow with separate roughing and finishing toolpaths. It is not listed as a standard SVG-only project file.

The cleanest next step is to go back to each lesson, download the zipped project file again, extract it first, and open the intended project file type directly in the software shown in the lesson instead of converting the browser download. If the download is opening as HTML or nothing appears, try right-clicking the download link and choosing “Save link as,” then make sure the file is saved as the original zipped project folder before extracting it.

Sorry for the confusion,

Miranda

[Miranda]

Hey Bryan,

The small table project and 3D crocodile project should both have downloadable zipped project files in the lesson area, under the materials tab. The table project opens in Vectric, and the crocodile project is also a Vectric 3D carving file, not a standard SVG.It’s important to note that Vectric’s VCarve Pro or higher is required to machine 3D reliefs, so be sure you’re using the right software version.

[Miranda]

Hey James,

Based on what you described, this isn’t a material thickness issue, it’s almost always a Z-zero or cut depth issue.

Here’s the key thing:
Even though you set your material thickness to 0.78″, your machine doesn’t actually “know” where the bottom is. It only knows where Z-zero is and how deep the toolpath tells it to go.

If you ended up with ~0.24″ left, that tells me your cutter only went down about 0.53″ total, which means one of these likely happened:

• Your profile cut depth wasn’t set to cut all the way through
• Your Z-zero was set too high (bit wasn’t truly touching the material when zeroed)
• Or you didn’t include an extra cut depth (offset) past the bottom

How to fix it (this will solve it moving forward):

1. Double-check your Z-zero
Make sure when you zero Z, the bit is just barely touching the top surface, no gap.

2. Set your cut depth deeper than your material
If your material is 0.77″, set your cut depth to something like:

• 0.80″–0.82″

That extra depth ensures you fully cut through, even if your spoilboard isn’t perfectly flat.

3. Run a quick test cut
Before running a full job, do a small profile cut on scrap to confirm it cuts through clean.

Good luck,

Miranda

[Miranda]

Hey James,

No problem, happy to help!

In each unit, above the video, there is a tab that says materials. That is where you will find all the files.

Also, if you ever have a problem finding something, check out lesson 1.2 and it will walk you through how to navigate the course and where things are located.

Hope that helps,

Miranda

[Miranda]

Hey Bryan,

Based on what you described, the first thing I’d go back and verify inside Carveco Maker is that your imported SVG workflow is matching that original setup exactly:

-Make sure your material thickness is set to your actual board thickness, not assumed thickness.

-Make sure your bowl pocket is referencing top of material for Z-zero.

-Make sure the pocket toolpath is a true pocket / area clearance style operation and not something that is being interpreted as a full cut-through.

Before cutting, preview the pocket toolpath and confirm the maximum depth is staying inside the tray shape instead of treating the center like a through-cut.

That leftover center circle you mentioned sounds like Carveco may be reading part of the imported geometry differently than the original project file, which would also line up with the “closed vectors” message you’re seeing on the flag pass.

Since you’re using Carveco Maker instead of the original Carbide Create file, that part becomes a software-specific issue. We don’t troubleshoot third-party software settings directly, so the best next step for the closed-vector/import behavior is to reach out to Carveco Maker support and ask them how they want that SVG cleaned up or converted for a pocket plus flag-carve workflow.

Hope that helps,

Miranda

[Miranda]

Your design is likely set up in inches (12″ x 12″), but somewhere in the export or sender, it’s being interpreted as millimeters.
Since 100mm ≈ 4 inches, that’s why everything is showing up around 4″ instead of full size.

Let’s fix it step-by-step:

First, check your job setup in VCarve:

• Make sure your job size is actually set to inches, not mm
• Confirm it shows something like 12″ x 12″ in the job setup

Next, when exporting toolpaths:

• Make sure you’re using the correct Genmitsu post-processor (INCH version)
• A mm post-processor will shrink your file exactly like you’re seeing

Then, check Gsender:

• Look at the units setting (top or settings area)
• Make sure it’s set to inches, not mm

If Gsender is in mm, it’ll display your file scaled down, even if the file itself is technically correct.

One quick sanity check:

• If your file shows ~100 x 100 in Gsender → that’s mm (≈ 4″)
• If it shows ~12 x 12 → you’re good

[Miranda]

Here’s the basic workflow to follow:

1. Download and unzip the files
When you download the project, it’ll come as a zipped folder.
Right-click → “Extract All” so you can access everything inside.

2. Decide which route you’re taking

• If you want to learn and tweak things → open the project file in your software
• If you just want to run the job → use the G-code file

3. If using the G-code (USG)

• Open your control software (like UGS)
• Connect to your machine
• Load the correct G-code file (each file usually matches a specific bit or step)
• Set your zero:
  • X/Y = lower left corner of your material
  • Z = top of material
• Run the job

4. Important:
Most projects use multiple files (one per tool). That means:

• Run first file (example: pocketing)
• Change the bit when prompted
• Re-zero Z only (not X/Y)
• Run the next file

A couple beginner tips that will save you headaches:

• Always double-check your material size matches the project
• Run an air pass first (lift the bit and simulate the cut)
• Stay near the machine for your first few runs
• Don’t rush; setup is everything in CNC

[Miranda]

Thanks for the detail, that helps.

First, the “No Processor Selected” issue when using “Add Processor” is usually just a quirk of how that window behaves. For your machine (Genmitsu 4040-PRO MAX), you don’t need to add anything custom, you can skip that entirely and just use:

• grbl (mm) or
• grbl (inch)

Those are the correct post processors for your machine.

Now, the bigger issue is this message: “Trial version of the software can only save toolpaths…” That’s the key. This isn’t a post processor problem, it’s a software limitation.

What that means:

• The trial version will only let you export toolpaths from their built-in sample files
• Any file you downloaded (like your Kentucky design) won’t export until the software is activated

So here’s what to do:

If you’re just testing:

• Open one of the included tutorial/sample files
• Select grbl (mm or inch) on the right side
• Export should work fine

If you want to run your Kentucky carve:

• You’ll need the full version of the software to generate toolpaths from that file

Good luck!

[Miranda]

Hey Michael,

The trial only allows you to save toolpaths from their included sample files, which is why it’s blocking you when you try to use Easel as your post processor.

So here’s the deal:

You don’t necessarily need to buy the full version right this second to keep moving forward.

Instead, you’ve got two solid options:

First option: stick with the workflow using the provided files.
If you’re following along with the course projects, those are designed to work within the system and help you learn the process step-by-step. The key focus right now is understanding the workflow, not the specific post processor.

Second option: upgrade when you’re ready.
If you want to start running your own toolpaths (like what you’re trying to do with Easel), then yes you’ll need the full desktop version of VCarve to export those properly.

Good luck!

[Miranda]

The good news is the course files are meant to work across different machines and software setups, and we do have members using a wide range of CNCs successfully, not just the exact machines shown in the lessons.

That said, what you’re describing sounds less like a project file issue and more like a machine/control communication issue. But before you reach out I would check a couple things.

-Make sure the downloaded file was extracted fully before opening it in your software.

-Confirm the job setup matches the playbook exactly, especially material thickness, Z-zero set to the top of material, and XY zero/datum set to the lower-left corner on the projects that call for that. Several of the project playbooks use that exact setup, and they also recommend simulating the toolpaths before exporting and running an optional air pass before the real cut.

-Also make sure you’re exporting with the correct post-processor for your machine/controller workflow. The playbooks do call out using the machine’s correct post-processor when exporting toolpaths.

If the cut is repeatedly pausing, throwing errors, or needing to be resumed 20 times, that’s the point where I’d stop chasing the project file and have Sienci confirm the communication side, sender setup, and correct post for the LongMill MKII. That sounds like the fastest path to getting you running cleanly.

[Miranda]

For Lesson 2 (the Bit Organizer project), you do need a 1/8″ upcut bit for the small detail pocketing toolpaths. The 1/4″ downcut handles the larger pockets and profile cuts, but the 1/8″ upcut is what gives you those clean, tighter detail cuts.

[Miranda]

Here’s how to approach it inside VCarve:

First, set up your job exactly like the playbook outlines:
– Job size: 12″ x 7″
– Material thickness: Measure your walnut and enter the real number
– Z-zero: Top of material
– XY zero: Lower-left corner

Then recreate the same three toolpaths:

Pocketing
Use your 3/4″ bowl and tray bit and create a pocket toolpath for the tray recess. Match the depth shown in the design and preview it carefully.

Engraving
Use a 60° V-bit and create a V-Carve toolpath for the flag details.

Profile Cutout
Use your 1/4″ downcut and create a profile toolpath to cut out the outer shape. Add tabs just like you normally would in VCarve.